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

[Pharo-project] from #foo:bar: to foo: arg1 bar: arg2

by StÃ©phane Ducasse

Hi does one of you get to know a method for doing that? #foo:bar: -> foo: arg1 bar: arg2 Stef

March 1, 2009

Re: [Pharo-project] changing default font

by StÃ©phane Ducasse

Hi sebastian So far we only have the web site and the code.google site. I'm not really a blogger (I'm writing too much other stuff --- soon you will see :). But if somebody would like to have a blog I would happily read and comment. > I'm happy to see that pharo has a lot to be a winner I can start now :) My personal wish for pharo is not really to win but to make itself in a clean, lean robust new invention of Smalltalk. I stress invention here because may be it will not be 100% Smalltalk but a Smalltalk with better stuff: first class variables, better MOP who knows. Anyway thanks for your nice words. Stef > great script thanks! > hey Pharo project already has an official blog? I mean, I image how > good this simple things would help to propagate the pharo ideavirus > when posted in cool posts by a team of developers. Ideally a team of > authors with a an editor (to filter possible misconceptions about > pharo project policy) could do good stuff a lot more fun than > manuals and FAQs. > I'm happy to see that pharo has a lot to be a winner > cheers, > sebastian > > De: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr > ] En nombre de Rob Rothwell > Enviado el: Sunday, March 01, 2009 13:19 > Para: Pharo-project(a)lists.gforge.inria.fr > Asunto: Re: [Pharo-project] changing default font > > And if you get tired of setting your fonts individually, you can set > them all at once: > > font := LogicalFont familyName: 'Andika Basic' pointSize: 10. > codeFont := LogicalFont familyName: 'DejaVu Sans Mono' > pointSize: 9. > Preferences setListFontTo: font. > Preferences setMenuFontTo: font. > Preferences setCodeFontTo: codeFont. > Preferences setButtonFontTo: font. > Preferences setSystemFontTo: font. > font := LogicalFont familyName: 'Andika Basic' pointSize: 11. > Preferences setWindowTitleFontTo: font. > > Just replace the font names with those of your choice! > > Rob > > On Sun, Mar 1, 2009 at 10:56 AM, Sebastian Sastre <ssastre(a)seaswork.com > > wrote: > It suddendly started to work, I think it was SqueakFFIPrims.dll that > was missing > > cheers, > sebastian > > > > -----Mensaje original----- > > De: pharo-project-bounces(a)lists.gforge.inria.fr > > [mailto:pharo-project-bounces@lists.gforge.inria.fr] En > > nombre de Sebastian Sastre > > Enviado el: Sunday, March 01, 2009 12:06 > > Para: Pharo-project(a)lists.gforge.inria.fr > > Asunto: [Pharo-project] changing default font > > > > hi there, > > sorry for the noob question but I see pharo has freetype in > > the image but it's > > only accuny font among options. Shouldn't freetype read the > > fonts on the system > > and offer those too? > > thanks, > > sebastian > > > > > > _______________________________________________ > > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 1, 2009

Re: [Pharo-project] [squeak-dev] [Idea] method source with it

by Mariano Martinez Peck

Lukas: good news! thanks for it. I tried to test it but doesn't work for me. I updated the packages you said but after then, I am trying to open a system browser and I get the following error. I guess I must update another package, but I don't know. Anyway, don't worry. I can test it then when all of these changes are included in pharo image. thanks again. MessageNotUnderstood: OBMetaNode>>filters OBMetaNode(Object)>>doesNotUnderstand: #filters OBPackageBrowser class>>defaultMetaNode OBPackageBrowser class(OBBrowser class)>>new OBPackageBrowser class(OBBrowser class)>>open OBPackageBrowserAdaptor class(OBSystemBrowserAdaptor class)>>open DEVToolSet class(StandardToolSet class)>>openClassBrowser [] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: {[(selArgCount := selector numArgs) = 0 ifTrue: [target perform: selector] ...]} BlockContext>>ensure: CursorWithMask(Cursor)>>showWhile: ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: MouseButtonEvent>>sentTo: ToggleMenuItemMorph(Morph)>>handleEvent: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>dispatchEvent:with: ToggleMenuItemMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>dispatchEvent:with: MenuMorph(Morph)>>processEvent:using: OBMetaNode(Object)>>doesNotUnderstand: #filters OBPackageBrowser class>>defaultMetaNode OBPackageBrowser class(OBBrowser class)>>new OBPackageBrowser class(OBBrowser class)>>open OBPackageBrowserAdaptor class(OBSystemBrowserAdaptor class)>>open DEVToolSet class(StandardToolSet class)>>openClassBrowser [] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: {[(selArgCount := selector numArgs) = 0 ifTrue: [target perform: selector] ...]} BlockContext>>ensure: CursorWithMask(Cursor)>>showWhile: ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: MouseButtonEvent>>sentTo: ToggleMenuItemMorph(Morph)>>handleEvent: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>dispatchEvent:with: ToggleMenuItemMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>dispatchEvent:with: MenuMorph(Morph)>>processEvent:using: doesNotUnderstand: aMessage "Handle the fact that there was an attempt to send the given message to the receiver but the receiver does not understand this message (typically sent from the machine when a message is sent to the receiver and no method is defined for that selector)." "Testing: (3 activeProcess)" MessageNotUnderstood new message: aMessage; receiver: self; signal. ^ aMessage sentTo: self. On Sun, Mar 1, 2009 at 8:36 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > >> Not at the moment, I noticed myself several times that this would be > >> useful. If I find time, I will have a look at it tomorrow. > > > > No problem. I was just asking :) > > Update in this order: > > 1. AST-lr.164 > 2. Refactoring-Core-lr.40 > 3. OB-Refactory-lr.141 > 4. OB-Regex-lr.15 > > To get case insensitive matching when building environments/scopes > make sure that the expression ends with "/i". All the commands include > a regular expression example now, that should help you get started. > > Note, that this versions also reorganize the menus a bit, after a > discussion with Stephane and David. Environments are now called > scopes, but other than that it is the same. > > Lukas > > > > > >> > >> > Suppose you have more than 1 match of what you are looking in the same > >> > method, is there a way to go one after the other putting the color > over > >> > the > >> > world ? > >> > >> Not without hacking into ParagraphEditor. There is unfortunately no > >> easy way to highlight several occurrences. > > > > :( Ok. Thanks anyway for the tip. > > > >> > >> Lukas > >> > >> -- > >> Lukas Renggli > >> http://www.lukas-renggli.ch > >> > >> _______________________________________________ > >> 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 > > > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 1, 2009

[Pharo-project] towards pharo 1.0 (from pavel)

by StÃ©phane Ducasse

> > Hi Stef, > > there are some opened issues so we may start with them: > 310 and 311 - the goal is to be able to unload all tests. As Adrian > sugested, we may place it the package Tests - at least for now. > 346 - easy and safe to integrate > 348 - very important issue. Maybe you should place in one update fix > for MorphicUIManager>>interactiveParserFor: and in the next the rest > of the patch to prevent loading problems > There was one wrong step in the development of Pharo during removing > of MVC. Pharo deleted all MVC related code however in some cases it > was the sign to use the UIManager. > 71, 59 - very critical patch but I will have to check if the patches > are suitable for the latest pharo > > I suggest to remove the unused class variable Current from the > ColorTheme (issue 467) firstly - that cleans a lot of obsoleteClasses. > > I think that we need one important step in the development of Pharo - > the next image that will not contain any code that can be unloaded. > That should help us to increase the Pharo quality because now most > packges are on the logical level in contradistiction to KernelImage > where all packages are standalone unloadable entities. > The ideal state is when we have the minimal core image with logical > packages (like Collections) and the rest will be all unloadable > packages. > > Cheers, > -- Pavel > > > > On Sun, Mar 1, 2009 at 9:57 AM, stephane ducasse > <stephane.ducasse(a)free.fr> wrote: >> >>> The KernelImage ZOO including the building environment is here: >>> http://squeak.cz/public/pub/KernelImage/current/ >>> >>> Of course it is not perfect - the smallest image works only in Linux >>> and MorphicCore needs a lot of fixes so people should start with >>> MorphicExt and so on but it is usable starting point if someone is >>> interested... >>> >>> -- Pavel >> >> Hi pavel >> >> do you have some fixes, cs list that we could slowly integrate to >> pharo? >> >> Stef >> >

March 1, 2009

Re: [Pharo-project] changing default font

by Sebastian Sastre

great script thanks! hey Pharo project already has an official blog? I mean, I image how good this simple things would help to propagate the pharo ideavirus when posted in cool posts by a team of developers. Ideally a team of authors with a an editor (to filter possible misconceptions about pharo project policy) could do good stuff a lot more fun than manuals and FAQs. I'm happy to see that pharo has a lot to be a winner cheers, sebastian _____ De: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] En nombre de Rob Rothwell Enviado el: Sunday, March 01, 2009 13:19 Para: Pharo-project(a)lists.gforge.inria.fr Asunto: Re: [Pharo-project] changing default font And if you get tired of setting your fonts individually, you can set them all at once: font := LogicalFont familyName: 'Andika Basic' pointSize: 10. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. font := LogicalFont familyName: 'Andika Basic' pointSize: 11. Preferences setWindowTitleFontTo: font. Just replace the font names with those of your choice! Rob On Sun, Mar 1, 2009 at 10:56 AM, Sebastian Sastre <ssastre(a)seaswork.com> wrote: It suddendly started to work, I think it was SqueakFFIPrims.dll that was missing cheers, sebastian > -----Mensaje original----- > De: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr] En > nombre de Sebastian Sastre > Enviado el: Sunday, March 01, 2009 12:06 > Para: Pharo-project(a)lists.gforge.inria.fr > Asunto: [Pharo-project] changing default font > > hi there, > sorry for the noob question but I see pharo has freetype in > the image but it's > only accuny font among options. Shouldn't freetype read the > fonts on the system > and offer those too? > thanks, > sebastian > > > _______________________________________________ > 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

March 1, 2009

Re: [Pharo-project] can't load seaside 2.9a2

by StÃ©phane Ducasse

Damien it should be fixed. At least I integrated in 10245 the latest fixes of mike. So may be now you just need to load the Kom package which is in the inbox. If you give a try let us know. Stef On Mar 1, 2009, at 6:09 PM, Damien Cassou wrote: > On Sat, Feb 28, 2009 at 2:41 PM, Sebastian Sastre <ssastre(a)seaswork.com > > wrote: >> first of all thanks for making Pharo. I can see there is a lot to >> do but I'm so >> glad to see an open smalltalk evoluting in such a direction. >> >> I wanted to give a try with a web app I'm porting to seaside 2.9a2 >> but it won't >> load (I mean seaside 2.9a2). It's complaining about problems >> related to >> MIMEDocuments. >> >> Looks like the ones in squeak 3.10.2 are first class objects >> instead of strings, >> the mime database and such. >> >> I'm missing some update? >> thanks and all the best > > This is a known bug and it's getting fixed. Please subscribe to the > following issue if you want to know when it is fixed. > > http://code.google.com/p/pharo/issues/detail?id=520 > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 1, 2009

Re: [Pharo-project] issue 467 update - obsolete Classes

by StÃ©phane Ducasse

Thanks! I will check that. Now I'm getting sick :( Stef On Mar 1, 2009, at 6:11 PM, Pavel Krivanek wrote: > Hi, > > I added some code to the issue 467 so all obsolete classes can be > removed (part of Milestone-1.0) > > Cheers, > -- Pavel > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 1, 2009

[Pharo-project] issue 467 update - obsolete Classes

by Pavel Krivanek

Hi, I added some code to the issue 467 so all obsolete classes can be removed (part of Milestone-1.0) Cheers, -- Pavel

March 1, 2009

Re: [Pharo-project] can't load seaside 2.9a2

by Damien Cassou

On Sat, Feb 28, 2009 at 2:41 PM, Sebastian Sastre <ssastre(a)seaswork.com> wrote: > first of all thanks for making Pharo. I can see there is a lot to do but I'm so > glad to see an open smalltalk evoluting in such a direction. > > I wanted to give a try with a web app I'm porting to seaside 2.9a2 but it won't > load (I mean seaside 2.9a2). It's complaining about problems related to > MIMEDocuments. > > Looks like the ones in squeak 3.10.2 are first class objects instead of strings, > the mime database and such. > > I'm missing some update? > thanks and all the best This is a known bug and it's getting fixed. Please subscribe to the following issue if you want to know when it is fixed. http://code.google.com/p/pharo/issues/detail?id=520 -- Damien Cassou http://damiencassou.seasidehosting.st

March 1, 2009

Re: [Pharo-project] Some issues with Pharo-dev build #10243

by Damien Cassou

On Fri, Feb 27, 2009 at 9:34 PM, David RÃ¶thlisberger <squeak(a)webcitas.ch> wrote: > Hm, not sure whether this is convenient. I mean every commit to the OB repository has > to be tested very carefully then, and I cannot commit experimental features anymore, > because they automatically get loaded with #loadOBAlpha as it is right now. > What is the motiviation to not longer build pharo-dev with the OB versions published > in Universe? I don't know, was just trying things to see what is best :-). Please continue to push the versions you want into SqueakSource as you always did. -- Damien Cassou http://damiencassou.seasidehosting.st

March 1, 2009