- Pharo-dev - lists.pharo.org

[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

Re: [Pharo-project] What are the ERROR messages in the Transcript Window in 10243?

by Rob Rothwell

Should I post an issue? Thank your, Rob On Sun, Mar 1, 2009 at 7:54 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Seems a problem in OB: OBDBSuperSend sends #superSenderSelectors, > which is not implemented. > > Adrian > > On Feb 28, 2009, at 19:06 , Rob Rothwell wrote: > > > Maybe I just wasn't able to follow the conversation properly, but if > > you > > open a Transcript in 10243 (dev) and, say, search for the class > > "Morph," you > > will get: > > > > ERROR: Morph class>>overridesSelectors > > ERROR: Morph class>>superSenderSelectors > > ERROR: Morph class>>conflictsSelectors > > ERROR: Morph class>>overridesSelectors > > ERROR: Morph class>>superSenderSelectors > > ERROR: Morph class>>conflictsSelectors > > > > In fact, anytime you do anything (save a method, etc...), it seems > > you get > > these messages, and yet things seem to be working. > > > > Rob > > _______________________________________________ > > 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] changing default font

by Rob Rothwell

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] changing default font

by Sebastian Sastre

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

March 1, 2009