- Pharo-dev - lists.pharo.org

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

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

by keith

> > You say you are rewriting PackageInfo, you could have rewritten the > version that is in MC1.5, and built on what was going before. > For example, do you have support for files in MC? do you have support for Package types? do you have Matthew's extra wizzy iteration code? If you had simply said, we will load LevelPlayingField and fix things there, this would have been a different story altogether. You insist on making things hard for yourself, then you complain that you have no time to do things properly. Keith

Dec. 17, 2009

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

by StÃ©phane Ducasse

On Dec 17, 2009, at 12:13 PM, CÃ©drick BÃ©ler wrote: > > keith I think that one key aspect is that we should meet. ESUG this year will have free entry slot. Request one and come. all the sprints were always free access. > > > +10000 > > Then we organize a "workshop". I wish Matthew could join too ! > > > -- > CÃ©drick > _______________________________________________ > 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

[Pharo-project] Smalltalkers needed

by Ramiro Diaz Trepat

I don't know if this is not the proper place for this, in case it isn't my apologies. I will be brief. We have an open position to work in Kapital, the risk management software for derivatives in JPMorgan. It is a large project that runs on VW + Gemstone, among other things, you get lots of clever smalltalkers as colleagues :) The position is based in London and it is not possible to work from another location. If anyone is interested, drop me an email with an English version of your CV to: ramiro(a)diaztrepat.name<mailto:ramiro@diaztrepat.name> Cheers r This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.

Dec. 17, 2009

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

by StÃ©phane Ducasse

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. > it was important to adopt it as an exercise in recognizing > and supporting the communities efforts to make progress rather than to > undermine them. To carry on using the version that is in the closed > repository only did one thing, that was to undermine the input that > went into the "head" project at squeaksource.com/Testing, and it sent > the message out that contributions are not wanted. > > You say you are rewriting PackageInfo, you could have rewritten the > version that is in MC1.5, and built on what was going before. No I'm rewriting from scratch. A real package not based on conventions. There are too much behavior in the existing one. But people may use what I'm doing or not. Before this is not working I have to shut up. > > Keith > > > _______________________________________________ > 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] Fwd: [squeak-dev] Stuff

by StÃ©phane Ducasse

On Dec 17, 2009, at 2:04 PM, keith wrote: > > On 17 Dec 2009, at 06:44, Eliot Miranda wrote: > >> >> >> 2009/12/16 keith <keith_hodges(a)yahoo.co.uk> >> [screed deleted] >> I am no longer in a position to effect things either way, since I have been unable due circumstances to write a single line of code since the squeak board acted as they did. Ranting is all I have left that I can do. >> >> >> Law 9 >> WIN THROUGH YOUR ACTIONS, NEVER THROUGH ARGUMENT >> Any momentary triumph you think you have gained through argument is really a Pyrric victory: The resentment and ill will you stir up is stronger and lasts longer than any momentary change of opinion. It is much more powerful to get others to agree with you through your actions, without saying a word. Demonstrate, do not explicate. >> _____________________________________________ > > My actions are there for all to see, I acted until I am blue in the face. I am the only person who made an active contribution to the development of the corporate squeak vision since Dec 2006 (3.10 was only a bug fixing release, nothing visionary) I confirm that > > When actions run out you have but a shell left. Let me put it another way... If I died on August 20th what would have happened to my work? > > Keith > _______________________________________________ > 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 StÃ©phane Ducasse

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? Stef On Dec 17, 2009, at 1:39 PM, Michael Rueger wrote: > 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 > > > Make sure that Freetype fonts are loaded: > > FreeTypeFontProvider current loadFromSystem. > RomeFontManager resetDefault > > There is no support for strike or TT fonts (yet). > > Michael > > > _______________________________________________ > 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] Fwd: [squeak-dev] Stuff

by keith

> > keith I think that one key aspect is that we should meet. ESUG this > year will have free entry slot. Request one and come. > > > +10000 > > Then we organize a "workshop". I wish Matthew could join too ! It is not going to happen, I am a full time carer 24/7, I cant afford toilet paper let alone trips abroad. Keith

Dec. 17, 2009

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

by keith

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, it was important to adopt it as an exercise in recognizing and supporting the communities efforts to make progress rather than to undermine them. To carry on using the version that is in the closed repository only did one thing, that was to undermine the input that went into the "head" project at squeaksource.com/Testing, and it sent the message out that contributions are not wanted. You say you are rewriting PackageInfo, you could have rewritten the version that is in MC1.5, and built on what was going before. Keith

Dec. 17, 2009