On 20/10/2008, at 5:34 PM, Michael Rueger wrote:
I would vote strongly against leaving out Squeak's "native" text
rendering. With Squeak native I mean a method to render text without
any external libraries, e.g. for systems like SqueakNOS, bare metal
systems etc.
How would you justify that in relation to a goal or principle?
Maybe: "Pharo must be usable for bare metal systems" or "Pharo must
not depend on any libraries that don't come with the OS".
In the first case you obviously need *some* external support. Maybe a
definition could be driven by the API requirements of the any
underlying platform.
In the second case you would need to specify the particular OS/version
combinations that are targeted.
Either of those seem better than "no dependence on FreeType" because
they are less arbitrary.
What needs to be done is a proper refactoring of the text, font and
text style system so the different rendering mechanisms are easily
interchangeable and transparent to the programmer.
Sure, but that's somewhat orthogonal to my point.
Antony Blakey
-------------
CTO, Linkuistics Pty Ltd
Ph: 0438 840 787
When I hear somebody sigh, 'Life is hard,' I am always tempted to ask,
'Compared to what?'
-- Sydney Harris
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
