On Dec 17, 2009, at 2:29 PM, Michael Rueger wrote: > Michael Rueger wrote: >> Hi all, >> >> there is now a Pharo port of Rome :-) > > Just a few remarks about what Rome is :-) > > Rome provides a hierarchy of canvas classes which share a common > protocol. Applications using Rome can switch backends without worrying > about protocol incompatibilities as is the case with the different > Morphic canvases right now. > > Most prominent canvas is the RomePluginCanvas which interfaces with > Cairo. (maybe we should rename the class). please! this is fun because this is the first thing i thought when I read this mail :)
> Cairo itself provides > different backends so this offers access to pdf, ps and svg output. > > The only other working class right now is the balloon canvas, using the > balloon engine as a backend. > > A nice goal would be to migrate all drawing code to the Rome protocol, > adding e.g. a Bitblt canvas in the process. > > The Rom-Demo package has a couple of examples how to use Rome, although > some of the demos aren't working yet (they were built against an early > version of Rome). > > Currently there is no integration of Yoshiki's Pango extensions as there > was a fork in the plugin code a while back. Integration is on the to do > list though. > > Sophie made extensive use of Rome plus quite sophisticated font and > graphical style classes, so this would open up a new era of Pharo > looking even better :-) Need to port the style classes into Pharo though... Thanks. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
