August 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] Big Smallapack progress on Squeak/Pharo

by StÃ©phane Ducasse

Kind of a sacred day then :) http://gatherer.wizards.com/Pages/Card/Details.aspx?multiverseid=184608 Stef On Aug 23, 2011, at 9:27 PM, Nicolas Cellier wrote: > Hurrah! After 5 years of inaction with eyes turned toward heavens, > brain waiting for a miraculous enlightening, I suddenly had the > illumination and solved most of may Smallapack problems in Squeak! > See http://smallissimo.blogspot.com/2011/08/smallapack-progress-on-squeak.html > This post shall interest anyone using or wanting to use FFI. Unless > maybe I was the last idiot not knowing how to ;) well we are quite a bunch of them here. > This information shall be written in FFI classes comment, in the WIKI > and every place pretending to inform the poor unaware users like me. > > Nicolas >

Aug. 23, 2011

[Pharo-project] FW: little uMorphic progress

by Edgar J. De Cleene

------ Forwarded Message > From: Pavel Krivanek <pavel.krivanek(a)gmail.com> > Reply-To: <Pharo-project(a)lists.gforge.inria.fr> > Date: Tue, 23 Aug 2011 16:31:41 +0200 > To: Pharo Development <pharo-project(a)lists.gforge.inria.fr> > Subject: [Pharo-project] little uMorphic progress > > Hi, > > uMorphic is an experimental image based on Pharo Kernel (+Gofer) that > contains only core of Morphic functionality. It has no windows or > fonts, menus nor halos support, it can only open a basic Morph in the > world and drag it with mouse. The purpose of this image is to provide > information for Morphic packages reorganization. > > Now the basic cleaning was processed on this package so when it is > loaded to basic gofer image, no new Undeclared nor unimplemented > messages are added! :-) So it should be quite stable too. > > It has 2,9 MB and it modifies behavior of 32 methods. > > You may download and try it here: > http://windmap.cz/playground/trash/uMorphic.zip > > Cheers, > -- Pavel > ------ End of Forwarded Message Y funciona en Mac con Squeak 4.2.5beta1U pero no con las VM Cog. GrandisimoÂ Pavel, ahora espero aprender como hacer crecer esta imagen And it works on Mac with 4.2.5beta1U Squeak VM but not with Cog. Pavel great, now I hope to learn how to grow this image Edgar

Aug. 23, 2011

Re: [Pharo-project] little uMorphic progress

by Pavel Krivanek

I cheated ;-) I started with a script (export.st) that takes content of Core packages that are not present in the Gofer image and exports a long file containing definitions of classes and traits (in safe order) and all replaces original methods with proxy methods that when called load original source code, log method name and restart yourself. It is very similar to messages tracking but without VM support. Then I used it for modified initCore script so I got list of messages that are necessary for initialization and function of Morphic doing this tasks. Then I took this list of messages, created a changeset containing it and exported it. Finally I manually checked the Undeclared and unimplemented calls. It is almost the same way that I used for creation of MinimalMorphic image in past. Cheers, -- Pavel On Tue, Aug 23, 2011 at 9:47 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > Very cool. I wonder how you created that load script? > > Lukas > > On 23 August 2011 18:58, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Thanks. I would love to have a cleaner morphic kernel :) >> But it will take time. >> >> Stef >> >> On Aug 23, 2011, at 3:31 PM, Pavel Krivanek wrote: >> >>> Hi, >>> >>> uMorphic is an experimental image based on Pharo Kernel (+Gofer) that >>> contains only core of Morphic functionality. It has no windows or >>> fonts, menus nor halos support, it can only open a basic Morph in the >>> world and drag it with mouse. The purpose of this image is to provide >>> information for Morphic packages reorganization. >>> >>> Now the basic cleaning was processed on this package so when it is >>> loaded to basic gofer image, no new Undeclared nor unimplemented >>> messages are added! :-) So it should be quite stable too. >>> >>> It has 2,9 MB and it modifies behavior of 32 methods. >>> >>> You may download and try it here: >>> http://windmap.cz/playground/trash/uMorphic.zip >>> >>> Cheers, >>> -- Pavel >>> >> >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > >

Aug. 23, 2011

[Pharo-project] [ANN] Big Smallapack progress on Squeak/Pharo

by Nicolas Cellier

Hurrah! After 5 years of inaction with eyes turned toward heavens, brain waiting for a miraculous enlightening, I suddenly had the illumination and solved most of may Smallapack problems in Squeak! See http://smallissimo.blogspot.com/2011/08/smallapack-progress-on-squeak.html This post shall interest anyone using or wanting to use FFI. Unless maybe I was the last idiot not knowing how to ;) This information shall be written in FFI classes comment, in the WIKI and every place pretending to inform the poor unaware users like me. Nicolas

Aug. 23, 2011

Re: [Pharo-project] little uMorphic progress

by Lukas Renggli

Very cool. I wonder how you created that load script? Lukas On 23 August 2011 18:58, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks. I would love to have a cleaner morphic kernel :) > But it will take time. > > Stef > > On Aug 23, 2011, at 3:31 PM, Pavel Krivanek wrote: > >> Hi, >> >> uMorphic is an experimental image based on Pharo Kernel (+Gofer) that >> contains only core of Morphic functionality. It has no windows or >> fonts, menus nor halos support, it can only open a basic Morph in the >> world and drag it with mouse. The purpose of this image is to provide >> information for Morphic packages reorganization. >> >> Now the basic cleaning was processed on this package so when it is >> loaded to basic gofer image, no new Undeclared nor unimplemented >> messages are added! :-) So it should be quite stable too. >> >> It has 2,9 MB and it modifies behavior of 32 methods. >> >> You may download and try it here: >> http://windmap.cz/playground/trash/uMorphic.zip >> >> Cheers, >> -- Pavel >> > > > -- Lukas Renggli www.lukas-renggli.ch

Aug. 23, 2011

Re: [Pharo-project] little uMorphic progress

by Edgar J. De Cleene

Congrats Pavel!! In UTN now, can't wait until return home and try. Enviado desde mi iPad El 23/08/2011, a las 13:58, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> escribiÃ³: > Thanks. I would love to have a cleaner morphic kernel :) > But it will take time. > > Stef > > On Aug 23, 2011, at 3:31 PM, Pavel Krivanek wrote: > >> Hi, >> >> uMorphic is an experimental image based on Pharo Kernel (+Gofer) that >> contains only core of Morphic functionality. It has no windows or >> fonts, menus nor halos support, it can only open a basic Morph in the >> world and drag it with mouse. The purpose of this image is to provide >> information for Morphic packages reorganization. >> >> Now the basic cleaning was processed on this package so when it is >> loaded to basic gofer image, no new Undeclared nor unimplemented >> messages are added! :-) So it should be quite stable too. >> >> It has 2,9 MB and it modifies behavior of 32 methods. >> >> You may download and try it here: >> http://windmap.cz/playground/trash/uMorphic.zip >> >> Cheers, >> -- Pavel >> > >

Aug. 23, 2011

[Pharo-project] Using system fonts in Pharo

by Ilmari Vacklin

Using Pharo 1.3, I'm trying to load system fonts into the image. However, if I the "Launch" button next to "Update fonts from system", nothing seems to happen. What is the expected behaviour of the button?

Aug. 23, 2011

Re: [Pharo-project] Little fix for #4697

by StÃ©phane Ducasse

Thanks and indeed you are right. Stef On Aug 23, 2011, at 6:15 PM, Michael Roberts wrote: > In inbox: > > Name: Tools-MikeRoberts.658 > > Issue: 4697 > -Fix to OrderedCollectionInspector that fails #fieldList on > OrderedCollections that are not fully formed. > > > ---- > > I did a little fix for this bug, that prevents the debugger stepping > into OrderedCollection new. I mention this to folks working on tools > because it is an interesting edge case. If you specialise an > inspector for a particular class, for example, you have to handle the > case where the object is not fully formed. e.g right after basicNew, > or in the middle of some initialisation. > > It failed for the debugger, because it relies on embedding an > inspector for the receiver (bottom left) panel. So i guess this edge > case is subtle... > > cheers, > Mike >

Aug. 23, 2011

Re: [Pharo-project] Some bugs

by StÃ©phane Ducasse

Thanks andrea Welcome to the pharo mailing-list and community. Now I think that this is important that inside netstyle you also consider that if pharo is important for you (which I imagine) that you should also contribute. Bug reporting is already a contribution. Pharo is an open-source software mainly supported by the free time of people, people that are often do not earning their money from their pharo work (I thank them for all that). I also understand that people can get frustrated by changes but what can we do? May be people can gather and check the fixes that are important to fix but we do not have the force to maintain. Imagine well that we have one engineer full time since 8 months. Stef On Aug 23, 2011, at 8:54 AM, Andrea BrÃ¼hlmann wrote: > Hello, > > I reported some bugs on the issue tracker and hope you can help me with them! > > > 4681: Accepting with the enter key does not work > http://code.google.com/p/pharo/issues/detail?id=4681 > > 4682: Code completion makes strange cursor placements and too many spaces > http://code.google.com/p/pharo/issues/detail?id=4682 > > 4683: Code completion breaks some search fields (errors during typing) > http://code.google.com/p/pharo/issues/detail?id=4683 > > 4684: Missing ctrl+w (methodNamesContainingIt:) > http://code.google.com/p/pharo/issues/detail?id=4684 > > 4685: Merge dialog: cannot resolve conflict with removed method > http://code.google.com/p/pharo/issues/detail?id=4685 > > 4686: Method category change creates no new version > http://code.google.com/p/pharo/issues/detail?id=4686 > > 4687: Errors during coding (MessageNotUnderstood: receiver of "morph" is nil) > http://code.google.com/p/pharo/issues/detail?id=4687 > > 4688: Progress bar disappears on image save > http://code.google.com/p/pharo/issues/detail?id=4688 > > 4689: MessageTally bug > http://code.google.com/p/pharo/issues/detail?id=4689 > > 4690: Progress bar position > http://code.google.com/p/pharo/issues/detail?id=4690 > > 4691: Bad line breaks in code until window is resized (because of bold text?) > http://code.google.com/p/pharo/issues/detail?id=4691 > > 4692: Drop downs should select the default entry (topmost) instead of a middle one > http://code.google.com/p/pharo/issues/detail?id=4692 > > 4693: Line breaks in tooltips are wrong > http://code.google.com/p/pharo/issues/detail?id=4693 > > 4694: Debugger: stepping over an error can not open a new debugger until I hit cmd+. > http://code.google.com/p/pharo/issues/detail?id=4694 > > 4695: Time asString prints nanos unrounded > http://code.google.com/p/pharo/issues/detail?id=4695 > > > -- > Andrea BrÃ¼hlmann >

Aug. 23, 2011

Re: [Pharo-project] Some bugs

by Clara Allende

Imagine IBM paying engineers to maintain an smalltalk application during like 10 years, and I still find some really ugly bugs hehe On 23 August 2011 14:12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Don't feel guilty :) > But send fixes so that we can collect them for a given version. > > And we will not get perfect systems. Imagine IBM payed during several year > 100 engineers to build eclipse > and so far we got one engineer 8 months. > > Stef > > > On Aug 23, 2011, at 9:57 AM, Lukas Renggli wrote: > > >>> Now I think the subliminal message of this thread is that the Pharo > >>> community should focus on making the existing images really stable > >>> before hacking away on Pharo 1.4 and beyond ... :-) > >> > >> And we need more people actually looking at the bug tracker... I > sometimes > >> feel a bit lonely... > > > > Yes, I feel guilty of not being able to contribute more fixes. You are > > doing the excellent job of integrating submitted patches > > instantaneous. > > > > The problem is that the unstable versions are pushed extremely hard, > > while the supposedly stable versions are still unstable. I don't see > > how this can possibly work? > > > > Subsequently, I hesitate to submit a patch for an old version because > > I know it won't be possible to merge it into newer versions. This is a > > vicious circle. > > > > Lukas > > > > -- > > Lukas Renggli > > www.lukas-renggli.ch > > > > >

Aug. 23, 2011