January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fix to PackageOrganizer>>packageOfClass:

by Danie Roux

On Thu, Jan 7, 2010 at 8:14 PM, Nicolas Cellier wrote: > Would it prevent merging squeak/trunk Collection ? > If yes, I suggest a status quo. No, I checked and could merge both ways (adding methods to Text on Squeak trunk, and Pharo, and "cherry-picking" them both ways). Monticello hangs on to the package name and index only by that - it does not infer it from the class or method. The same problem exists in my Squeak trunk image, btw. In this case only if the name of the shorter package is a symbol: (PackageOrganizer default packageNamed: #OB ifAbsent: [ self error: 'hmm']) includesClass: OBMorphBuilder. (PackageOrganizer default packageNamed: 'OB-Morphic' ifAbsent: [ self error: 'hmm']) includesClass: OBMorphBuilder. I guess there is a biggest issue to be fixed here, namely the proper maintenance of "PackageOrganizer default packages" :-) -- Danie Roux *shuffle* Adore Unix - http://danieroux.com

Jan. 7, 2010

Re: [Pharo-project] About my recursive blues :)

by Igor Stasenko

http://images.4chan.org/fit/src/1262884440787.jpg ;) 2010/1/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > yeap > let's move on now I'm steady mode :) > > Stef > > On Jan 7, 2010, at 6:43 PM, Yanni Chiu wrote: > >> Miguel Enrique CobÃ¡ Martinez wrote: >>> Anyway, my mail was to support the work of Stef and the Pharo team and >>> not to start a flame about Squeak. So let this rest now. >> >> Best to let it rest. The past can't be changed, but the future is in the >> hands of each fork. >> >> There may be similarities along the way, amongst the different forks. >> Shrinking the core image and reloadable packages is likely common to all >> forks - ideally, we'd all arrive at the same core. But there are >> differences too, in the goals of each fork, not just personality >> differences. >> >> Some may feel that energies are wasted with the forks. Probably they're >> right. The question is whether or not the wasted energies can be >> afforded. If multiple forks can draw more resources in total, to offset >> the extra energies expended, then everyone is ahead. It's not clear yet >> whether the overall Squeak/Pharo/Seaside community is growing, and >> whether that would be because of the fork or not. >> >> Also, a little friendly competition, does seem to motivate and inspire >> people. >> >> -- >> Yanni >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Jan. 7, 2010

Re: [Pharo-project] Fix to PackageOrganizer>>packageOfClass:

by Nicolas Cellier

Would it prevent merging squeak/trunk Collection ? If yes, I suggest a status quo. Nicolas 2010/1/7 Danie Roux <lists+pharo(a)danieroux.com>: > All, > > I was confused about the purpose of > PackageInfo>>mostSpecificPackageOfMethod:ifNone: and > PackageInfo>>mostSpecificPackageOfClass:ifNone: > > They seem to be a workaround to the bug that exist in > #packageOfClass:ifNone: and #packageOfMethod:ifNone:? > > I propose this fix, after discussing it with Lukas: > http://code.google.com/p/pharo/issues/detail?id=1752 > > Background of problem: > > In theory it should not be possible for packages to overlap. Every > class, and every method should belong to only one Category. In reality > packaging bugs and other actions does cause packages to be created > that overlap. > > An example in PharoCore, 10505 is this: > > (PackageOrganizer default packageNamed: Â 'Collections' ifAbsent: [ > self error: 'hmm']) includesClass: Text. " true " > (PackageOrganizer default packageNamed: Â 'Collections-Text' ifAbsent: > [ self error: 'hmm']) includesClass: Text. " also true! " > > In the old implementation, #packageOfClass: would have returned the > first category that matches. It will now return the more specific > 'Collections-Text'. > > I suggest that #mostSpecificPackageOfClass* and > #mostSpecificPackageOfMethod* methods be removed as well? > > -- > Danie Roux *shuffle* Adore Unix - http://danieroux.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 7, 2010

Re: [Pharo-project] About my recursive blues :)

by StÃ©phane Ducasse

yeap let's move on now I'm steady mode :) Stef On Jan 7, 2010, at 6:43 PM, Yanni Chiu wrote: > Miguel Enrique CobÃ¡ Martinez wrote: >> Anyway, my mail was to support the work of Stef and the Pharo team and >> not to start a flame about Squeak. So let this rest now. > > Best to let it rest. The past can't be changed, but the future is in the > hands of each fork. > > There may be similarities along the way, amongst the different forks. > Shrinking the core image and reloadable packages is likely common to all > forks - ideally, we'd all arrive at the same core. But there are > differences too, in the goals of each fork, not just personality > differences. > > Some may feel that energies are wasted with the forks. Probably they're > right. The question is whether or not the wasted energies can be > afforded. If multiple forks can draw more resources in total, to offset > the extra energies expended, then everyone is ahead. It's not clear yet > whether the overall Squeak/Pharo/Seaside community is growing, and > whether that would be because of the fork or not. > > Also, a little friendly competition, does seem to motivate and inspire > people. > > -- > Yanni > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 7, 2010

[Pharo-project] pharo cairo new home

by StÃ©phane Ducasse

with the blessing of mike, I cleaned the PharoTaskForces repository and copied the packages from the impara repository so that you can publish your improvements Gofer new squeaksource: 'PharoTaskForces'; package: 'Rome-Reference'; package: 'Rome-BalloonCanvas'; package: 'Rome-Base'; package: 'Rome-PluginCanvas'; package: 'Rome-Fonts'; package: 'Rome-Demo'; load stef

Jan. 7, 2010

Re: [Pharo-project] [ANN] Icons for Mac users

by Alexandre Bergel

This is really cool Mariano. It works for me. Cheers, Alexandre On 7 Jan 2010, at 13:51, Mariano Martinez Peck wrote: > Hi folks. Once month before I was happy with my Linux box and having > my Pharo icons for .sources, .changes, .image, and vm. Now I have a > mac, and I have the old squeak icons. So.....I created the ones for > Pharo :) > > I attach a zip file with the files. What you have to do is: > > 1) Go to your vm (for example Squeak 4.2.2beta1U.app), and copy it > (backup) with another name in case you don't like the icons > 2) Go to the original VM -> right button -> Show package content > 3) Uncompress, copy and replace my attached files for the ones that > are in /Contents/Resources/ > 4) A reboot may help to see all the changes > > That's all. I hope you like it. > > Cheers > > Mariano > <macIcons.zip>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 7, 2010

[Pharo-project] Fix to PackageOrganizer>>packageOfClass:

by Danie Roux

All, I was confused about the purpose of PackageInfo>>mostSpecificPackageOfMethod:ifNone: and PackageInfo>>mostSpecificPackageOfClass:ifNone: They seem to be a workaround to the bug that exist in #packageOfClass:ifNone: and #packageOfMethod:ifNone:? I propose this fix, after discussing it with Lukas: http://code.google.com/p/pharo/issues/detail?id=1752 Background of problem: In theory it should not be possible for packages to overlap. Every class, and every method should belong to only one Category. In reality packaging bugs and other actions does cause packages to be created that overlap. An example in PharoCore, 10505 is this: (PackageOrganizer default packageNamed: 'Collections' ifAbsent: [ self error: 'hmm']) includesClass: Text. " true " (PackageOrganizer default packageNamed: 'Collections-Text' ifAbsent: [ self error: 'hmm']) includesClass: Text. " also true! " In the old implementation, #packageOfClass: would have returned the first category that matches. It will now return the more specific 'Collections-Text'. I suggest that #mostSpecificPackageOfClass* and #mostSpecificPackageOfMethod* methods be removed as well? -- Danie Roux *shuffle* Adore Unix - http://danieroux.com

Jan. 7, 2010

[Pharo-project] Fwd: [INRIAGforge] January 2010, the 14th : scheduled service downtime

by StÃ©phane Ducasse

I imagine that the english dat is good. Else this is too late :) > Date: January 7, 2010 6:40:25 PM GMT+01:00 > To: stephane.ducasse(a)inria.fr > Subject: [INRIAGforge] January 2010, the 14th : scheduled service downtime > > Due to sheduled maintenance, the INRIA Forge will be shut down from 17h00. > The restart is planned from 19h00 on the same day. > > We apologize for any inconvenience. > > Cordially, > > -- > The InriaGforge Team > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > 14 Octobre 2009 : arrÃªt du service pour maintenance > > La Forge INRIA sera arrÃªtÃ©e Ã partir de 17h00 pour de maintenance. > Le redÃ©marrage est prÃ©vu Ã partir de 19h00 le jour mÃªme. > > Nous sommes dÃ©solÃ©s pour le dÃ©rangement occasionnÃ©. > > Cordialement, > > -- > L'Ã©quipe InriaGforge >

Jan. 7, 2010

Re: [Pharo-project] [ANN] Icons for Mac users

by Mariano Martinez Peck

On Thu, Jan 7, 2010 at 6:42 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > cool! > I noticed that tuesday on windows :) > :) > Do you have an idea to make the distinction stronger between image and > changes :) > > I have no idea at all. I didn't do the icons, I just get the ones that are here: http://gforge.inria.fr/frs/download.php/23453/pharo_document_icons.zip I converted them form png to icns and then I rename them to the name that they have in the mac vm. I don't know who did the icons. Cheers Mariano > Stef > > On Jan 7, 2010, at 5:51 PM, Mariano Martinez Peck wrote: > > > Hi folks. Once month before I was happy with my Linux box and having my > Pharo icons for .sources, .changes, .image, and vm. Now I have a mac, and I > have the old squeak icons. So.....I created the ones for Pharo :) > > > > I attach a zip file with the files. What you have to do is: > > > > 1) Go to your vm (for example Squeak 4.2.2beta1U.app), and copy it > (backup) with another name in case you don't like the icons > > 2) Go to the original VM -> right button -> Show package content > > 3) Uncompress, copy and replace my attached files for the ones that are > in /Contents/Resources/ > > 4) A reboot may help to see all the changes > > > > That's all. I hope you like it. > > > > Cheers > > > > Mariano > > <macIcons.zip>_______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 7, 2010

Re: [Pharo-project] Some notes we took during our experience

by StÃ©phane Ducasse

>> >> - PreferenceBrowserMorph and friends should be removed. >> > sure, its days are counted ;-) heheheh (kind of evil laugh with echo). Even if the PreferenceBrowserMorph was a good guy and I was happy to include it in 3.9 to replace the old one. So it served its time. Stef

Jan. 7, 2010