Just an idea how to call the package: Romph-Rendering if you swizzle first 3 letters, you'll get
Morph-Rendering :) On 24 May 2010 14:36, Igor Stasenko <[email protected]> wrote: > On 24 May 2010 13:36, Stéphane Ducasse <[email protected]> wrote: >> >> On May 23, 2010, at 11:04 PM, Igor Stasenko wrote: >> >>> 2010/5/23 Javier Pimás <[email protected]>: >>>> Hi, may I ask how you are rendering these fonts? You parse the glyphs and >>>> then render lines with opengl or use freetype to render to a texture >>>> without >>>> antialiasing or both? >>> >>> Squeak has already a TT font reader, so i just taking the data from there >>> and piping to GPU. >>> What you see here is freely scalable vector/curve rendering done >>> completely on GPU. >>> >>>> If you asked me, I'd say I like the method but for >>>> fonts they look a bit blury, I'd say too much for the smaller ones. >>> >>> I think this is best what you can achieve without hinting / subpixel AA. >>> >>>> Also, what are you working on? >>>> >>> I once did a GLCanvas, >>> and now i want to reiterate and improve it using new callout mechanism >>> (NativeBoost), >>> and full coverage of OpenGL API, with all extensions available at your >>> disposal. >> >> Igor it would be good it we could have >> >> NativeBoostRomeCanvas >> >> if you see what I mean :) >> > > Yes, i actually want to do that. > > I plan to inject the new methods into a Morph > > Morph>>fullDrawOnRomeCanvas: aCanvas > Morph>>drawOnRomeCanvas: aCanvas > > which should tell the morph to use a different instructions/commands > to perform drawing, > to conform with RomeReferenceCanvas protocol. > > I don't want to repeat a balloon canvas protocol. > > Then, eventually, when we will have everything ready, > we will be free to use different rendering backend than Balloon canvas. > > And its important to make it a non-intrusive. > So, the plan is: > > - create a separate package, which will contain extension methods > to Morph and its various subclasses. And maybe some little classes. > > - this package !!_should not_!! have any dependencies on Rome , and > should be loaded cleanly, > even if you don't have Rome installed. > It only should conform with Rome canvas protocol for implementing rendering. > > This will ensure a backend agnostic nature of new morphic rendering code. > > If you think this plan is cool, then lets pick a package name and > repository, and i will start happy coding :) > >>> >>>> Regards, >>>> Javier. >>>> >>>> 2010/5/23 Igor Stasenko <[email protected]> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [email protected] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
