December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Rome port

by StÃ©phane Ducasse

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.

Dec. 17, 2009

Re: [Pharo-project] Fwd: [squeak-dev] Stuff

by keith

On 17 Dec 2009, at 13:26, StÃ©phane Ducasse wrote: > > On Dec 17, 2009, at 2:14 PM, keith wrote: > >> Stef, >> >> I don't think you understand. >> >> You had access to the repository squeakfoundation.org/39a, you the >> privileged elite, release teams etc could contribute to the head of >> SUnit, it was a closed project. squeaksource.com/Testing was proposed >> as the new head of SUnit, it is not for anyone to say let's use this >> its really cool. It is not something to be adopted if it is cool or >> not. It is the head of the community development that is SUnit. If it >> is not cool, then squeaksource.com/Testing is the place to go to >> fix it. >> >> It doesnt matter whether the code in squeaksource.com/Testing is >> rubbish, > > No you take responsibilities for a choice. Your choice is whether to support and work with those who are seeking to collaborate with you, or whether to be rude to them. Starting a new project with a non-open repository, forking off from a starting point 2 years behind head, is actually offensive. Keith

Dec. 17, 2009

Re: [Pharo-project] Class - How to check, if a class I want to create already exists and how to delete it?

by HernÃ¡n Morales Durand

Hi Dirk, Welcome to Smalltalk! 2009/12/17 Dirk Klaschus <klaschus(a)googlemail.com>: > Hi, folks! > > I'm new to Smalltalk, but I love it already. I have two questions, I > couldn't find answers for: > > 1) I have written a method which creates a new class. How can I check, > if the class I want to create does not exist already? > ... > Object > Â Â Â subclass: textKlassenname asSymbol > Â Â Â instanceVariableNames: '' > Â Â Â classVariableNames: '' > Â Â Â poolDictionaries: '' > Â Â Â category: 'ZFriend-Bibliothek' Smalltalk hasClassNamed: #Object > > 2) I want to write a method, which deletes the created class. How can I > do it? > ( Smalltalk at: #YourClass ) removeFromSystem > > P.S.: I did not find any place to look it up for myself. Any hints where > to find such answers? > > > Thanks for your help!!! > Dirk You're welcome. HernÃ¡n > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 17, 2009

Re: [Pharo-project] Rome port

by Michael Rueger

HernÃ¡n Morales Durand wrote: >> To load Rome: >> >> Gofer new >> impara: 'RomePharo'; >> addPackage: 'Rome-BalloonCanvas'; >> addPackage: 'Rome-Base'; >> addPackage: 'Rome-PluginCanvas'; >> addPackage: 'Rome-Fonts'; >> addPackage: 'Rome-Demo'; >> load > > When evaluating that script I get a Warning: > > This package depends on the following classes: addPackage: 'Rome-Reference'; The dependencies obviously are not cleaned up completely yet... > I'm using Pharo-Core 111066 in Windows XP SP2, I proceeded anyway but > then I get a MNU in DisplayScreen class>>tiny (cannot send a walkback > since the menu doesn't appear). I'm missed something? Hmm, can't really explain why that would happen just by loading... Michael

Dec. 17, 2009

Re: [Pharo-project] Rome port

by Michael Rueger

StÃ©phane Ducasse wrote: > Mike > from an infrastructure point of view > it would be good to have all the pharo related files in the same place. > Could not you use PharoTaskForces? Yes, I can move it there now that I have sorted out a usable version :-) Oh, just noticed that you already uploaded packages there earlier. We should remove those though, as some of them are no longer used. Michael

Dec. 17, 2009

Re: [Pharo-project] Rome port

by HernÃ¡n Morales Durand

Hi Michael, 2009/12/17 Michael Rueger <m.rueger(a)acm.org>: > Hi all, > > there is now a Pharo port of Rome :-) > > Quite a few things are still untested and probably broken, freetype > integration isn't what it should be yet, but it basically works. > > You will need the RomePlugin for your platform. > https://gforge.inria.fr/frs/download.php/25047/RomePlugin.bundle.zip > https://gforge.inria.fr/frs/download.php/25046/rome.zip > > To load: > > Get these two packages from PharoInbox (for now) > Graphics-MichaelRueger.168 > FreeType-MichaelRueger.498 > > To load Rome: > > Gofer new > Â Â Â Â impara: 'RomePharo'; > Â Â Â Â addPackage: 'Rome-BalloonCanvas'; > Â Â Â Â addPackage: 'Rome-Base'; > Â Â Â Â addPackage: 'Rome-PluginCanvas'; > Â Â Â Â addPackage: 'Rome-Fonts'; > Â Â Â Â addPackage: 'Rome-Demo'; > Â Â Â Â load When evaluating that script I get a Warning: This package depends on the following classes: RomePath RomeReferenceCanvas You must resolve these dependencies before you will be able to load these definitions: RomeBalloonCanvas RomeBalloonCanvas>>createPath RomeBalloonCanvas>>deviceClear:fill: ... I'm using Pharo-Core 111066 in Windows XP SP2, I proceeded anyway but then I get a MNU in DisplayScreen class>>tiny (cannot send a walkback since the menu doesn't appear). I'm missed something? Cheers, HernÃ¡n

Dec. 17, 2009

[Pharo-project] Class - How to check, if a class I want to create already exists and how to delete it?

by Dirk Klaschus

Hi, folks! I'm new to Smalltalk, but I love it already. I have two questions, I couldn't find answers for: 1) I have written a method which creates a new class. How can I check, if the class I want to create does not exist already? ... Object subclass: textKlassenname asSymbol instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'ZFriend-Bibliothek' 2) I want to write a method, which deletes the created class. How can I do it? P.S.: I did not find any place to look it up for myself. Any hints where to find such answers? Thanks for your help!!! Dirk

Dec. 17, 2009

Re: [Pharo-project] Fwd: [squeak-dev] Stuff

by Marcus Denker

On Dec 17, 2009, at 2:23 PM, StÃ©phane Ducasse wrote: >> (3.10 was only a bug fixing release, nothing visionary) > > I confirm that Yet, we had people speak up praising Edgar and telling the world how much better 3.10 done than 3.9. Marcus

Dec. 17, 2009

Re: [Pharo-project] Rome port

by Michael Rueger

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). 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... Enjoy Michael

Dec. 17, 2009

Re: [Pharo-project] Fwd: [squeak-dev] Stuff

by StÃ©phane Ducasse

>> > > Stef, > > From time to time have a message like this is not something you should shy away from, but instead send it as a leadership call. Yes I know. Thanks. Marcus wrote on his todo to really reply too. Because I'm not the only one :) > Also, as Pharo is now a reality is no longer only a dream but a _vision_. > > As we're articulating on having funding, etc., it's becoming more than a vision but a _project_! > > my 0.019999.... > > -- > Cesar Rabak > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 17, 2009