Stef,
On 19/10/2008, at 8:30 PM, Stéphane Ducasse wrote:
yes but this is still important that we keep the solution to not
rely on TT fonts
Why is that?
Surely basing the font mechanism purely on FreeType would be "Clean"
and "Lean" because of all the stuff you could remove, and the
plugability and parametric paths you could collapse - and it opens the
way to ditching FreeType and using native platform API for text
rendering and metrics, which would undoubtedly be "Better" and "Fast".
The manifesto already says "Not backward compatible", so it can't be
that.
If it's a matter of wanting to cover platforms without FreeType - and
even then you could use the native API unless you are bare metal, then
maybe that should be on the home page with the manifesto.
I understand if using native text APIs falls under 'try to avoid to
reinvent the wheel', but using only the existing FreeType system
doesn't reinvent anything.
I'm just curious about the unwritten parameters of Pharo's
development, because your statement implies some rule.
Cheers,
Antony Blakey
-------------
CTO, Linkuistics Pty Ltd
Ph: 0438 840 787
Every task involves constraint,
Solve the thing without complaint;
There are magic links and chains
Forged to loose our rigid brains.
Structures, structures, though they bind,
Strangely liberate the mind.
-- James Fallen
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
