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

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by StÃ©phane Ducasse

I noticed a problem between 11357 and 11363 today apparently class definitions containing traits loses their traits. Stef On May 25, 2010, at 3:10 PM, Torsten Bergmann wrote: > 1. If you select a trait in the browser (for instance "NSTInflating") > and select "browse hierarchy (h)" from the context menu you will > notice a > > Trait(Object)>>doesNotUnderstand: #allSubclassesWithLevelDo:startingLevel: > > error. > > > 2. While it was no problem to build the pharo-dev from a > core 11367 image using ConfigurationOfPharo it now crashes with a DNU > while loading Nile when I use a newer pharo #11371 core image. > > Bye > T. > > > > -- > 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

May 25, 2010

Re: [Pharo-project] FFI Documentation

by Schwab,Wilhelm K

I too am waiting to find something about NB that we should not like. No offense to Sig, there has to be _something_ wrong with it, right? :) A draft list of stuff we should check: (1) many examples of calls with int, float/double, pointers, structs, etc. (2) mac, Linux, Windows (3) callbacks Bonus: (4) calls on separate OS threads so the image can defend itself against something that does not return in a "reasonable" time, with reasonable being up to either the programmer or the end user (which the programmer can hopefully enforce if the image is not locked). Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Denis Kudriashov Sent: Tuesday, May 25, 2010 1:08 PM To: Pharo-project Subject: Re: [Pharo-project] FFI Documentation Hi. Igor Can you compare NB callout functionality with FFI and Alien functionality. Can NB replace FFI, Alien? What absent in NB callout? You implement callbacks with NB. FFI not support it. For me NB foreign interface seems more attractive than something else. 2010/5/21 Igor Stasenko <siguctua(a)gmail.com<mailto:siguctua@gmail.com>> Very nice topic coverage. I hope, eventually NB will also have something like this :) But it having a little different pros/cons table: NB Pros: * as well as for plugin, you can create new functionality that doesn't exist in any library * no need to recompile plugin/VM when you making a changes * all your code is distributed with the Smalltalk code, but there can be complications with platforms * fast - faster than any FFI implementation written in C, and as fast as plugin primitive or even faster Cons: * ?unsafe? - you have to provide a safety layers (But hey, you have to deal with same sorts of stuff, when writing plugin. No magician workers there) * harder to write Yes, its harder than plain smalltalk - true. But i can't say, that writing an assembler is harder than writing a plugin's slang code. If you writing a plugin, you should have an expertise, in VM internals and how to build VM , etc etc and if you writing an native code, you should have an expertise in assembler as well as VM internals. So, they are different, and definitely much harder comparing to plain smalltalk code, but which one is easier is hard to tell. On 20 May 2010 22:25, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr<mailto:stephane.ducasse@inria.fr>> wrote: > thanks sean > this is cool to see such kind of documentation emerging. > > Stef > > On May 20, 2010, at 9:16 PM, Sean P. DeNigris wrote: > >> >> I want to get this info into the help system and/or collaborative book, as >> similar questions pop up regularly on the lists. >> >> I compiled every piece of info I could find. The focus in on FFI, with >> stubs for other strategies. Please read this *very* rough outline for >> missing info and inaccuracies: >> >> FFI >> >> What is FFI and what is it used for? Calling functions in libraries outside >> of the image... >> >> FFI, the Squeak Foreign Function Interface, is used to call functions >> located in shared libraries that are not part of the Squeak VM nor its >> plugins. It also provides means to read and write memory structures that are >> associated with the use of those shared libraries. A typical use is to >> directly invoke operating system APIs. As such, applications that use FFI >> can only be used on the platform(s) that support the particular API being >> used. C conventions are used throughout, though the external function could >> have been written by any language capable of generating object code that >> follows C conventions. FFI is probably the easiest way to do the things it >> does. FFI is pretty fast too. Croquet uses FFI calls to OpenGL for all it's >> drawing routines.[1] >> >> How does FFI work? >> Technically what happens is: >> * you define what the interface is - the parameters, types etc. >> * when you make the call, the FFI logic assembles the data from the Squeak >> Objects into the proper structures according to the routine calling >> conventions for your architecture, and of course manages the return values. >> So no magic but perhaps just a little assembler in the plugin to properly >> deal with all the registers and condition flags. >> >> How do I use it? >> >> 1. make a method (whose structure is similar to a named primitive method) >> >> Example: >> system: aString "name (by convention is apiXxx: e.g. apiSystem:)" >> >> <apicall: long 'system' (char*) module: 'libSystem.dylib'> "first line >> should be the external function specification" >> ^self externalCallFailed. >> >> Let's take it piece by piece: >> >> system: aString >> Method name - by convention named 'apiXxx' >> >> <apicall: long 'system' (char*) module: 'libSystem.dylib'> >> Function specification >> - should be the first line >> - enclosed in angle brackets: < > containing: >> 1. Calling Convention, either apicall: (Pascal convention) or cdecl: (C >> convention) >> - Mac - use either one >> - Unix - use cdecl >> - Windows - use apical >> 2. Return Type (see types) >> 3. External Function Name (literal string) >> 4. Argument Types (a literal array) >> 5. Module - "module: " + [filename of the external library (literal >> string)] (see below). >> >> self externalCallFailed. >> Failure handler >> - normal smalltalk code >> - executed if the linking to or calling the external function fails >> - API calls don't know how to communicate failure like Squeak primitives >> do, so: >> - it does not tell you whether the external function succeeded >> - the most common code is simply '^self externalCallFailed.' >> >> Argument Types >> - must be names of ExternalTypes, either: >> - atomic types (see ExternalType class>>initializeFFIConstants and >> ExternalType class>>initializeAtomicTypes): >> void >> bool >> byte (unsigned) >> sbyte (signed) >> ushort (16-bit unsigned) >> short (16-bit signed) >> ulong (32-bit unsigned) >> long (32-bit signed) >> ulonglong (64-bit unsigned) >> longlong (64-bit signed) >> char (unsigned) >> schar (signed) >> float (single-precision float) >> double (double-precision float) >> >> Structure Types [4] >> - subclass of ExternalStructure >> - class>>fields that returns an array of field descriptions (see below) >> - Example: >> fields >> ^#((red 'byte')(green 'byte')(blue 'byte')) >> - class>>initialize which includes "self defineFields" (which must be >> called before using the class) >> - refer to as MyExternalStructure* (to indicate that the argument or return >> is a pointer to that structure) >> >> Field description [4] >> - 2-element array (or three but that does something else, I'm not sure >> what): >> - first element is the field name >> - second is the type >> >> Mac Memory Allocation Issues [4] (not sure about this) >> >> If you allocate external structures, those with memory outside the Squeak >> process space, you may need to increase the amount of memory that is >> reserved outside the object heap for such use. The Mac OS (9 and previous) >> needs this, other platforms may be able to dynamically get more memory from >> the OS. To see how much memory is currently reserved printIt 'Smalltalk >> extraVMMemory'. To change it, execute 'Smalltalk extraVMMemory: >> someNumberofBytes' Then save your image and quit. When you next start up, >> the amount of memory you requested will be reserved. (JMM) Note the OSX >> versions of the VM ignore extraVMMemory because the memory model for >> OS-X/unix applications is quite different. >> >> Module Name >> - depends on the platform >> - Mac >> - pre Snow Leopard: flexible, can eliminate leading lib or extension e.g. >> 'libc.dylib' becomes 'libc', 'c.dylib', or 'c' >> - Snow Leopard >> - file name must be exact including extension (unless Info.plist is >> altered as in 'Library Location' below) >> - With pre-mach-o VMs >> - For Classic applications, use 'InterfaceLib' >> - For Carbon libs, use 'CarbonLib' >> >> Module Location - where the external library file lives >> - depends on the platform >> - Mac >> - pre Snow Leopard >> - checks VM path and common library paths >> - Snow Leopard >> - only looks in VM bundle's Resources file, you must either [5]: >> - store all external libraries there >> - ln -s path/to/library path/to/VM/Resources/library_name >> - Change the VM's Info.plist "SqueakPluginsBuiltInOrLocalOnly" key from >> "true" to "false." >> Caveats >> - security >> - malicious users could call arbitrary functions in the OS e.g. "format >> c:" from "system.dll" [7] >> - VMs do not protect against buffer overflow from bad parameters [8]: >> "this would require an attacker to execute arbitrary Smalltalk >> code on your server. Of course if they can do that they own you >> anyway, especially if you allow FFi or use the OSProcess plugin" - John >> McIntosh >> >> * difficulty >> - if you make a mistake you'll not drop into the debugger but Squeak will >> just crash [2] >> - If you crash Squeak when it is running the garbage collector, then you >> know your FFI code is leaking bits into object memory [2] >> >> What do I need to use FFI with Squeak? >> >> You need the FFI plugin, which is included with most VM's as of Squeak 3.6 >> or so. >> >> You can also build the plugin yourself. See VMMaker. >> >> References: >> [1] http://wiki.squeak.org/squeak/1414 >> [2] http://wiki.squeak.org/squeak/2424 >> [3] http://wiki.squeak.org/squeak/5716 >> [4] http://wiki.squeak.org/squeak/2426 >> [5] >> http://forum.world.st/squeak-dev-Alien-Squeak-FFI-issues-on-Snow-Leopard-td… >> [6] http://wiki.squeak.org/squeak/5846 >> [7] http://forum.world.st/FFI-Callbacks-td54056.html#a54073 >> [8] http://forum.world.st/Security-td99624.html#a99635: >> >> Other choices: >> In the fall of 2008, Alien the FFI interface (written by Cadence Design >> Systems, Inc.) was put into squeaksource: >> http://www.squeaksource.com/Alien.html. This API allows the primitive to >> call back to Smalltalk Code, and return error code information, and >> apparently is much faster due to a less complex call sequence. >> * if you need callbacks >> * mac-only? >> >> Plugins - write external code and dynamically link it to the VM >> Pros: >> * safest - users are limited to using the functionality you provide and >> can not call other external functions e.g. system rm / >> * fast - faster than FFI >> * you can create new functionality that doesn't exist in any library >> Cons: >> * harder to write >> * plugin must be distributed with the Smalltalk code - there can be >> complications with platforms >> >> Primitive method - invokes behavior in the VM or a plugin [3] >> >> Questions: >> * why would you want to build the FFI plugin yourself? >> * api prefix or no for method names? >> * not sure about pre Snow Leopard library search >> * OSProcess - how does this fit into the bigger picture? >> * "^self externalCallFailed." or "self externalCallFailed." i.e. return self >> or return the result, or doesn't matter? >> * why would a field description have three elements? >> * Mac Memory Allocation Issues? >> -- >> View this message in context: http://forum.world.st/FFI-Documentation-tp2225148p2225148.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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<mailto:Pharo-project@lists.gforge.inria.fr> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 25, 2010

Re: [Pharo-project] "Smalltalk signalLowSpace" freeze the image

by StÃ©phane Ducasse

nicolas proposed a fix for offList http://code.google.com/p/pharo/issues/detail?id=2276 I did not integrate it because the fix is not fixing the problem but kind of an effect. Setf On May 25, 2010, at 4:51 PM, Mariano Martinez Peck wrote: > Hi. Take Pharo 1.0 or Pharo 1.1. The following code, will probably freeze your image: "Smalltalk signalLowSpace" > > Can you reproduce it? or I am the only one ? Let me know and I open a ticket. > > I have tried with all Mac vms. > > I tried the same in Squeak 4.1 and it works correct. Any idea where it can be the problem? > > I tried to debug a lot. Of course, it is freezing in "LowSpaceSemaphore signal". > > I put a halt in #installLowSpaceWatcher and tried to debug #lowSpaceWatcher but I didn't find anything. > > Thanks for any hint. > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 25, 2010

Re: [Pharo-project] [update 1.1] #11371

by Adrian Lienhard

The reason why we have turned it off is because updating Pharo images repeatedly caused problems (in contrast to PharoCore). People then reported issues. Unless this feature is working properly, we shouldn't enable it again. One possible cause of the problems are overrides by external packages in core code. But I think nobody has analyzed the problem in depth so far. Cheers, Adrian On May 25, 2010, at 21:48 , Carla F. Griggio wrote: > That annoyed me too. Shouldn't that option be checked by default? > > On Tuesday, May 25, 2010, laurent laffont <laurent.laffont(a)gmail.com> wrote: >> World Menu -> System -> Software Update >> Cheers,Laurent Laffont >> >> http://pharocasts.blogspot.com/ >> http://magaloma.blogspot.com/ >> >> >> 2010/5/25 Guillermo Polito <guillermopolito(a)gmail.com> >> >> >> I'm sorry but i can't find how to update my 1.1 image. Can I update my image with this changes? Can someone enlight me? :) >> >> Guille, the newbie >> >> >> >> On Mon, May 24, 2010 at 5:16 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> 11371 >> ----- >> - Issue 1281: Button in TestRunner to fileout the test results. Thanks Laurent. >> - Issue 2468: Better method trailer method creation. Part One. Thanks Igor. >> - Issue 2406: MovieMorph should be removed from the core. Thanks Alain. >> - Issue 2467: AlllocationTest#testOutOfMemorySignal fails. Thanks Laurent >> - Issue 2331: Reuse test unload - Now there is an SUnitUnloader. Thanks Guillermo. >> >> Stef >> _______________________________________________ >> 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

May 25, 2010

Re: [Pharo-project] [update 1.1] #11371

by Mariano Martinez Peck

Nooooooooooooooooooooooooo!!!! Don't do a Utilities updateFromServer in a PharoDev image . It was removed intentionally as it could damage and make unstable the dev image. Thats why it is removed from the menu. For the moment, you cannot update a dev image. Just download the next available and announce version. The update work only for PharoCore for the moment. Download a core and you will see such menu. Cheers Mariano On Tue, May 25, 2010 at 4:48 PM, Carla F. Griggio <carla.griggio(a)gmail.com>wrote: > That annoyed me too. Shouldn't that option be checked by default? > > On Tuesday, May 25, 2010, laurent laffont <laurent.laffont(a)gmail.com> te: > > World Menu -> System -> Software Update > > Cheers,Laurent Laffont > > > > http://pharocasts.blogspot.com/ > > http://magaloma.blogspot.com/ > > > > > > 2010/5/25 Guillermo Polito <guillermopolito(a)gmail.com> > > > > > > I'm sorry but i can't find how to update my 1.1 image. Can I update my > image with this changes? Can someone enlight me? :) > > > > Guille, the newbie > > > > > > > > On Mon, May 24, 2010 at 5:16 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > 11371 > > ----- > > - Issue 1281: Button in TestRunner to fileout the test results. Thanks > Laurent. > > - Issue 2468: Better method trailer method creation. Part One. Thanks > Igor. > > - Issue 2406: MovieMorph should be removed from the core. Thanks Alain. > > - Issue 2467: AlllocationTest#testOutOfMemorySignal fails. Thanks Laurent > > - Issue 2331: Reuse test unload - Now there is an SUnitUnloader. Thanks > Guillermo. > > > > Stef > > _______________________________________________ > > 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 >

May 25, 2010

[Pharo-project] Issue 670: Should clean Morph menu

by Guillermo Polito

Hi! I began looking at this issue, and made a list of the menu items that exists in the default morph menu. Maybe we can choose which ones should be removed and which ones are really used. Here it goes: grab copy to paste buffer collapse delete copy text go behind add halo duplicate embed into-> PasteUpMorph SystemWindow resize change color... drop shadow-> show shadow shadow color... shadow offset... layout-> no layout proportional layout table layout change layout inset... child layout-> disable layout in tables horizontal resizing-> rigid shrink wrap space fill vertical resizing-> rigid shrink wrap space fill table layout-> reverse table cells clip to cell size rubber band cells change cell inset... change min cell size... change max cell size... list direction-> ... wrap direction-> ... cell positioning-> ... list centering-> ... wrap centering-> ... list spacing-> ... cell spacing-> ... provide clipping submorphs inspect explore browse hierarchy save morph in file attach to resource show actions debug-> inspect morph inspect owner chain inspect model explore morph browse morph class browse model class explore view hierarchy call #tempCommand define #tempCommand open editing edit label... Cheers, Guille

May 25, 2010

Re: [Pharo-project] [update 1.1] #11371

by Carla F. Griggio

That annoyed me too. Shouldn't that option be checked by default? On Tuesday, May 25, 2010, laurent laffont <laurent.laffont(a)gmail.com> wrote: > World Menu -> System -> Software Update > Cheers,Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > > > 2010/5/25 Guillermo Polito <guillermopolito(a)gmail.com> > > > I'm sorry but i can't find how to update my 1.1 image. Can I update my image with this changes? Can someone enlight me? :) > > Guille, the newbie > > > > On Mon, May 24, 2010 at 5:16 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 11371 > ----- > - Issue 1281: Button in TestRunner to fileout the test results. Thanks Laurent. > - Issue 2468: Better method trailer method creation. Part One. Thanks Igor. > - Issue 2406: MovieMorph should be removed from the core. Thanks Alain. > - Issue 2467: AlllocationTest#testOutOfMemorySignal fails. Thanks Laurent > - Issue 2331: Reuse test unload - Now there is an SUnitUnloader. Thanks Guillermo. > > Stef > _______________________________________________ > 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 > >

May 25, 2010

Re: [Pharo-project] Latex to HelpSystem converter? [WAS] Re: [Metacello] Re: [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Damien Pollet

On Tue, May 25, 2010 at 09:21, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > The only way is the pharo book > Â Â Â Â you can generate latex > Â Â Â Â browse it via google > Â Â Â Â query it. > > There is a visitor so we can produce what we want from the book structure. > Please no copy and paste. Embedding a copy of the pier kernel in the image could work, especially since there is already a morphic pier browser. But then why not browse it online? Embedding is only really useful if it's fully exploiting the possibility of linking between text and code. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

May 25, 2010

Re: [Pharo-project] [update 1.1] #11371

by Guillermo Polito

Thanks! I added it :). On Tue, May 25, 2010 at 4:30 PM, Alain Plantec <alain.plantec(a)free.fr>wrote: > Hi Guile, > The world menu update item is here only if you allow it. > open the setting browser (World menu/System/Settings) > then > System/Updates/Show update option in World menu > Cheers > Alain > > > I don't have that menu item in Pharo Dev 1.1... Is that a bug? What code >> can I evaluate to obtain the same result? >> >> Thanks! >> Guille >> >> 2010/5/25 laurent laffont <laurent.laffont(a)gmail.com <mailto: >> laurent.laffont(a)gmail.com>> >> >> >> World Menu -> System -> Software Update >> >> Cheers, >> >> Laurent Laffont >> >> http://pharocasts.blogspot.com/ >> http://magaloma.blogspot.com/ >> >> >> 2010/5/25 Guillermo Polito <guillermopolito(a)gmail.com >> <mailto:guillermopolito@gmail.com>> >> >> >> I'm sorry but i can't find how to update my 1.1 image. Can I >> update my image with this changes? Can someone enlight me? :) >> >> Guille, the newbie >> >> >> On Mon, May 24, 2010 at 5:16 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> >> >> wrote: >> >> 11371 >> ----- >> - Issue 1281: Button in TestRunner to fileout the test >> results. Thanks Laurent. >> - Issue 2468: Better method trailer method creation. Part >> One. Thanks Igor. >> - Issue 2406: MovieMorph should be removed from the core. >> Thanks Alain. >> - Issue 2467: AlllocationTest#testOutOfMemorySignal fails. >> Thanks Laurent >> - Issue 2331: Reuse test unload - Now there is an >> SUnitUnloader. Thanks Guillermo. >> >> Stef >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> <mailto:Pharo-project@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 >> <mailto:Pharo-project@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 >> <mailto:Pharo-project@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 >

May 25, 2010

Re: [Pharo-project] [update 1.1] #11371

by Alain Plantec

Hi Guile, The world menu update item is here only if you allow it. open the setting browser (World menu/System/Settings) then System/Updates/Show update option in World menu Cheers Alain > I don't have that menu item in Pharo Dev 1.1... Is that a bug? What > code can I evaluate to obtain the same result? > > Thanks! > Guille > > 2010/5/25 laurent laffont <laurent.laffont(a)gmail.com > <mailto:laurent.laffont@gmail.com>> > > World Menu -> System -> Software Update > > Cheers, > > Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > > > 2010/5/25 Guillermo Polito <guillermopolito(a)gmail.com > <mailto:guillermopolito@gmail.com>> > > I'm sorry but i can't find how to update my 1.1 image. Can I > update my image with this changes? Can someone enlight me? :) > > Guille, the newbie > > > On Mon, May 24, 2010 at 5:16 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> > wrote: > > 11371 > ----- > - Issue 1281: Button in TestRunner to fileout the test > results. Thanks Laurent. > - Issue 2468: Better method trailer method creation. Part > One. Thanks Igor. > - Issue 2406: MovieMorph should be removed from the core. > Thanks Alain. > - Issue 2467: AlllocationTest#testOutOfMemorySignal fails. > Thanks Laurent > - Issue 2331: Reuse test unload - Now there is an > SUnitUnloader. Thanks Guillermo. > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > <mailto:Pharo-project@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 > <mailto:Pharo-project@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 > <mailto:Pharo-project@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

May 25, 2010