- Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] New Unix/Linux VM

by Damien Cassou

Hi, I've just published a new Unix/Linux VM based on Exupery-vm-0.15.1: - Rename root directory from 'build' to 'pharo-vm-0.15.1b' - Rename UUIDPlugin to UUIDPlugin.bak (issue #855) http://pharo-project.org/download -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 10, 2009

Re: [Pharo-project] ScriptLoader policies

by Damien Cassou

On Wed, Jun 10, 2009 at 9:53 AM, Damien Cassou<damien.cassou(a)gmail.com> wrote: > What about using Installer which is present in all Pharo. For example: > > instClass ss > Â Â Â Â project: 'OCompletion'; > Â Â Â Â install: 'OCLoader'. instClass being Installer, sorry. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 10, 2009

Re: [Pharo-project] ScriptLoader policies

by Damien Cassou

2009/6/10 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Ok. I did something like that. I will then send an email with the ANN. What about using Installer which is present in all Pharo. For example: instClass ss project: 'OCompletion'; install: 'OCLoader'. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 10, 2009

Re: [Pharo-project] new mailist?

by Oscar Nierstrasz

There is also an RRS feed: http://n2.nabble.com/Pharo-Smalltalk-ft2305563.xml http://n2.nabble.com/Pharo-Smalltalk-f2305563.xml - on On Jun 10, 2009, at 1:08, Jon Hancock wrote: > I have to unsubscribe. This list is too active. It clogs downloading > of my email. It would be wonderful if the list were run on something > with more options such as google groups. thanks guys. look forward > to pharo's continued growth. > > Jon > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 10, 2009

Re: [Pharo-project] Pharo platform dependency (or Seaside one click)

by StÃ©phane Ducasse

Yes. I agree. Now do you have a fix? Stef On Jun 10, 2009, at 8:41 AM, Torsten Bergmann wrote: > I know that many of us use a Mac for running Pharo, but we should > continue to keep pharo platform independent. > > Otherwise we get the "Copy image and debug everywhere" > effects: > > Trying to copy a text from the new Seaside one click > image 2.8.4 using Pharo 10318 will bring up the debugger > on Windows since the default clipboard is pointing to an > instance of MacOSClipboard. > > Also the mac host windows menu + tests is completely > useless on Linux and Windows and will fail. > > At least we should find out if platform changed (at > image startup) and adapt the image. > > Bye > Torsten > > > > > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2009

[Pharo-project] Pharo platform dependency (or Seaside one click)

by Torsten Bergmann

I know that many of us use a Mac for running Pharo, but we should continue to keep pharo platform independent. Otherwise we get the "Copy image and debug everywhere" effects: Trying to copy a text from the new Seaside one click image 2.8.4 using Pharo 10318 will bring up the debugger on Windows since the default clipboard is pointing to an instance of MacOSClipboard. Also the mac host windows menu + tests is completely useless on Linux and Windows and will fail. At least we should find out if platform changed (at image startup) and adapt the image. Bye Torsten -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

June 10, 2009

Re: [Pharo-project] New Extensible Inspector

by StÃ©phane Ducasse

yes but just parsing no symbol resolution. > >>> - Unfolding a branch that contains an element with a very >>> very long >>> printOn: seems to freeze the system. >>> >>> Ok, I should limit the size of the generated string (with ... at the >>> end). >>> >>> I got an error niDescription not found. >>> >>> Do you have an example I can reproduce ? >> >> Hum... Load moose, CAnalyzer, then the linux kernel, and open a >> NewInspector on the model. > > great, you could analyse the linux kernel C code inside Pharo ? > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Smalltalkers do: [:it | All with: Class, (And love: it)] > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2009

Re: [Pharo-project] New Extensible Inspector for Pharo-Core

by StÃ©phane Ducasse

> Excellent! So soon we should only have one tools. > - why when I browse an array I do not get # > > ? I browsed a class and check the class category which should be an array and I got ( ) instead of #( ) > > > - roots are not obviously displayed > > It seems that you lost your symbol > > openOn: t1 > | t2 t3 t4 | > t3 := MorphicToolBuilder new. > (t4 := (t2 := self new on: t1; > yourself) buildWith: > t3) openInWorld. > ^ t2 > > Yes, I have some problem with my image... I'll verify all my > methods... > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 10, 2009

Re: [Pharo-project] Syntax error loading Coral

by StÃ©phane Ducasse

thanks david I also only now simple english (ok with accent because of my first name) ;-D Stef On Jun 10, 2009, at 3:29 AM, David T. Lewis wrote: > On Tue, Jun 09, 2009 at 07:42:57PM +0200, St?phane Ducasse wrote: >> luc >> >>>> "UnixProcess>>argsAsFlatArrayAndOffsets:". I guess it is an UTF-8 >>>> problem. >>>> Any ideas for a solution ? >> >> could you repost an email with a clear test showing that it breaks? >> like that the UnixProcess father may answer :) >> Stef > > A test would be great. I know only simple English, so anything more > complex than 5-bit Baudot encoding may have bugs ;-) > > Note that UnixProcessAccessorTestCase>>testArgsAsFlatArrayAndOffsets > is a test that documents how the method should behave. > > Dave > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2009

Re: [Pharo-project] Lost code

by Damien Pollet

On Wed, Jun 10, 2009 at 05:32, Schwab,Wilhelm K<bschwab(a)anest.ufl.edu> wrote: > I have at times been disappointed to see good coding effort get lost, both in browsers and the debugger. Â In the latter, it seems to happen when it warns about having to revert to a previous block or something along those lines. Â The browser loses are still mysterious to me - maybe it happens if code pane isn't properly associated with the selected class. Â Is there a way that the tools could keep a buffer of a few "accepts" worth of code to salvage such situations? Hmm, if you accepted it, it should have been logged to the changes file, be visible in the change sorter, via the 'Recover from changes' tool, or via the versions button in the browser. However, some confirmation dialogs can also be quite confusing, so are you sure you did accept the modifications ? -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

June 10, 2009