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

Re: [Pharo-project] [ANN] 1.2 Dev Packages are loading :)

by Peter Hugosson-Miller

Hehehe, I sure recognize that "pattern", since I've done it myself on occasion: copy/paste error when writing accessors. You write the getter first, save it, then edit it to create the setter... -- Cheers, Peter. On 9 dec 2010, at 07:35, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I do not understand > > why > > model: aModel > ^model > > such kind of methods are the solution. > > To me it looks like a hack or a design problem > > > On Dec 9, 2010, at 2:58 AM, Guillermo Polito wrote: > >> Sorry, It'll fail until Issue 3385 in pharo: TextEditor doest not understand #model gets fixed. :S >> >> Cheers, >> Guille >> >> >> On Wed, Dec 8, 2010 at 8:48 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On Dec 8, 2010, at 10:25 AM, Marcus Denker wrote: >> >>> >>> On Dec 7, 2010, at 8:42 PM, Guillermo Polito wrote: >>> >>>> Ok, I've done some fixes to OB and OC, and committed them to PharoTaskForces as a temporary solution. >>>> >>>> To load current configuration: >>>> >>>> Gofer it squeaksource: 'MetacelloRepository'; >>>> package: 'ConfigurationOfPharo'; >>>> load. >>>> >>>> (ConfigurationOfPharo project version: '1.2-beta2') load. >>>> >>>> Can Hudson help us in building Dev images? >>> >>> Yes, will set up a build for 1.2 today. >> >> I have set one up that takes 1.2 core, runs updates and then tries to build dev >> >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/ >> >> It is failing right now. >> >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/2/console >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> > >

Dec. 9, 2010

Re: [Pharo-project] Issue 3385 in pharo: TextEditor doest not understand #model

by pharo＠googlecode.com

Comment #3 on issue 3385 by stephane.ducasse: TextEditor doest not understand #model http://code.google.com/p/pharo/issues/detail?id=3385 I do not understand why this is the solution model: aModel ^model it looks like a hack

Dec. 9, 2010

Re: [Pharo-project] [ANN] 1.2 Dev Packages are loading :)

by StÃ©phane Ducasse

I do not understand why model: aModel ^model such kind of methods are the solution. To me it looks like a hack or a design problem On Dec 9, 2010, at 2:58 AM, Guillermo Polito wrote: > Sorry, It'll fail until Issue 3385 in pharo: TextEditor doest not understand #model gets fixed. :S > > Cheers, > Guille > > > On Wed, Dec 8, 2010 at 8:48 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Dec 8, 2010, at 10:25 AM, Marcus Denker wrote: > >> >> On Dec 7, 2010, at 8:42 PM, Guillermo Polito wrote: >> >>> Ok, I've done some fixes to OB and OC, and committed them to PharoTaskForces as a temporary solution. >>> >>> To load current configuration: >>> >>> Gofer it squeaksource: 'MetacelloRepository'; >>> package: 'ConfigurationOfPharo'; >>> load. >>> >>> (ConfigurationOfPharo project version: '1.2-beta2') load. >>> >>> Can Hudson help us in building Dev images? >> >> Yes, will set up a build for 1.2 today. > > I have set one up that takes 1.2 core, runs updates and then tries to build dev > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/ > > It is failing right now. > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/2/console > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Dec. 9, 2010

Re: [Pharo-project] Issue 3391 in pharo: BlockClosure>>assertWithDescription: sends #logFailure:

by pharo＠googlecode.com

Updates: Labels: Milestone-1.2 Comment #1 on issue 3391 by stephane.ducasse: BlockClosure>>assertWithDescription: sends #logFailure: http://code.google.com/p/pharo/issues/detail?id=3391 argh we should fix that!

Dec. 9, 2010

Re: [Pharo-project] Where does Regex-Core and friends live

by StÃ©phane Ducasse

On Dec 9, 2010, at 12:57 AM, Dale Henrichs wrote: > I am porting the latest Regex to GemStone and in the interest of Pharo compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo repository. > > In loading Regex-Tests-Core I found some compile errors (doubled '.', a common porting problem) in RxParserTest>>testTranslatingMatchesUsing and RxParserTest>>test, but I don't know where the home repository (other then Pharo) resides, where I could submit my updates. commit in the inbox > I've got a GemSource repository, but I'm actually hoping (haven't run tests yet:) that I will be able to use Regex-Core without making any GemStone-specific changes ... Yes I hope too > > Dale >

Dec. 9, 2010

Re: [Pharo-project] Issue 3385 in pharo: TextEditor doest not understand #model

by pharo＠googlecode.com

Updates: Status: fixed Labels: Milestone-1.2 Comment #2 on issue 3385 by stephane.ducasse: TextEditor doest not understand #model http://code.google.com/p/pharo/issues/detail?id=3385 (No comment was entered for this change.)

Dec. 9, 2010

Re: [Pharo-project] [ANN] 1.2 Dev Packages are loading :)

by StÃ©phane Ducasse

ok you mean integrated. Please change the status to fixed else we do not see it when scanning what should be merged. Stef On Dec 9, 2010, at 2:58 AM, Guillermo Polito wrote: > Sorry, It'll fail until Issue 3385 in pharo: TextEditor doest not understand #model gets fixed. :S > > Cheers, > Guille > > > On Wed, Dec 8, 2010 at 8:48 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Dec 8, 2010, at 10:25 AM, Marcus Denker wrote: > >> >> On Dec 7, 2010, at 8:42 PM, Guillermo Polito wrote: >> >>> Ok, I've done some fixes to OB and OC, and committed them to PharoTaskForces as a temporary solution. >>> >>> To load current configuration: >>> >>> Gofer it squeaksource: 'MetacelloRepository'; >>> package: 'ConfigurationOfPharo'; >>> load. >>> >>> (ConfigurationOfPharo project version: '1.2-beta2') load. >>> >>> Can Hudson help us in building Dev images? >> >> Yes, will set up a build for 1.2 today. > > I have set one up that takes 1.2 core, runs updates and then tries to build dev > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/ > > It is failing right now. > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/2/console > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Dec. 9, 2010

Re: [Pharo-project] Fuel - a fast object deployment tool

by StÃ©phane Ducasse

BTW when giving feedback consider that the guy doing that is spending a lot of time and this will be his master and that the code was not optimize and that there is no dedicated primitive in play. So we will see at the end and I was thinking that our little community would be much more positive but we will continue because we believe that there is some value in that. Stef

Dec. 9, 2010

Re: [Pharo-project] Fuel - a fast object deployment tool

by StÃ©phane Ducasse

It does! It seems that you did not work in VW2.5 and 3.0 and when parcels arrived loading was realllllly a big difference I do not see why this would not the same with Fuel. Stef >>>>> The difference is that in Fuel there is no managment for "shared objects". >> Fuel is not for swapping (there are no stubs/proxies and becomes), and the >> idea is that you write on a file, ALL (not only those objects that are ONLY >> accessible by the roots, like in ImageSegment) the objects reachable from >> user defined roots. >> >> Fuel is similar to ReferenceStream and subclasses, a XML serializer, or any >> serializers, etc...but MOSTLY, to Parcels. It is very similar to VisualWorks >> parcel. >> >> Another important thing is that it is binary. The idea is that maybe in a >> future we have a Monticello that doesn't need a mcz (code) + Compiler, but >> instead, just load binary code (fuel files). This would be muuuch faster >> that current Monticello, and even more, for minimal images, we wouldn't need >> a Compiler. >> Finally, Fuel is designed (like Parcels) to be very fast at loading time :) > > Well, I doubt if speed is really important, since you're loading everything at most once. And the current tools are really fast IMHO. The following numbers are from Squeak: > [ Compiler recompileAll ] timeToRun. 29083. > CompiledMethod allInstances size. 60701. > [ CompiledMethod allInstancesDo: [ :each | each getSource ] ] timeToRun. 1133. > So the compiler is compiling 2087 methods per second on average. You can load 53575 methods per second from a file on average. If it's zipped, than it may be a bit slower, say a factor of 2-3x slowdown. So you can still load and compile more than 1800 methods per second. I guess thats fast enough. > > Even if Fuel can be 10x faster, it doesn't really make a difference IMHO. > > > Levente > >> >> Cheers >> >> Mariano >> >> >> >> >>> It looks exciting! >>> >>> Alexandre >>> >>> >>>> >>>>> >>>>> Alexandre >>>>> >>>>> >>>>> On 8 Dec 2010, at 13:50, Martin Dias wrote: >>>>> >>>>>> Hi all >>>>>> >>>>>> Last months I and Tristan have been working on Fuel project, an object >>>>>> binary serialization tool. The idea is that objects are much more >>>>>> times loaded than stored, therefore it is worth to spend time while >>>>>> storing in order to have faster loading and user experience. We >>>>>> present an implementation of a pickle format that is based on >>>>>> clustering similar objects. >>>>>> >>>>>> There is a summary of the project below, but more complete information >>>>>> is available here: http://rmod.lille.inria.fr/web/pier/software/Fuel >>>>>> >>>>>> The implementation still needs a lot of work to be really useful, >>>>>> optimizations should be done, but we'll be glad to get feedback of the >>>>>> community. >>>>>> >>>>>> >>>>>> = Pickle format = >>>>>> >>>>>> The pickle format and the serialization algorithm main idea, is >>>>>> explained in this slides: >>>>>> >>>>>> http://www.slideshare.net/tinchodias/fuel-serialization-in-an-example >>>>>> >>>>>> >>>>>> = Current features = >>>>>> >>>>>> - Class shape changing (when a variable has been added, or removed, or >>>>>> its index changed) >>>>>> - Serialize most of the basic objects. >>>>>> - Serialize (almost) any CompiledMethod >>>>>> - Detection of global or class variables >>>>>> - Support for cyclic object graphs >>>>>> - Tests >>>>>> >>>>>> >>>>>> = Next steps = >>>>>> >>>>>> - Improve version checking. >>>>>> - Optimize performance. >>>>>> - Serialize more kinds of objects: >>>>>> -- Class with its complete description. >>>>>> -- Method contexts >>>>>> -- Active block closures >>>>>> -- Continuation >>>>>> - Some improvements for the user: >>>>>> -- pre and post actions to be executed. >>>>>> -- easily say 'this object is singleton'. >>>>>> - Partial loading of a stored graph. >>>>>> - Fast statistics/brief info extraction of a stored graph. >>>>>> - ConfigurationOfFuel. >>>>>> - Be able to deploy materialization behavior only (independent from >>>>>> the serialization behavior) >>>>>> >>>>>> >>>>>> = Download = >>>>>> >>>>>> In a Pharo 1.1 or 1.1.1 evaluate: >>>>>> >>>>>> Gofer new >>>>>> squeaksource: 'Fuel'; >>>>>> version: 'Fuel-MartinDias.74'; >>>>>> version: 'FuelBenchmarks-MartinDias.4'; >>>>>> load. >>>>>> >>>>>> >>>>>> = Benchmarks = >>>>>> >>>>>> You can run benchmarks executing this line (results in Transcript): >>>>>> >>>>>> FLBenchmarks newBasic run. >>>>>> >>>>>> >>>>>> Thank you! >>>>>> Martin Dias >>>>>> >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> >> >

Dec. 9, 2010

Re: [Pharo-project] Morph wont delete in pharo, cant select it...

by Joseph T. Bore

This worked great, thanks. I have an osx machine running on non apple hardware where the solution was less obvious but on my Mac it worked great, thanks everyone! jb On Dec 8, 2010, at 3:01 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > don't cry... > > Try alt + shift + click to bring the halos. > > We did it like that else the halos gets really in your way all the time. > > Stef > > > On Dec 8, 2010, at 8:55 PM, Joseph T. Bore wrote: > >> >> ive had my fingers in knots over here trying what seems like every control/alt/shift left button/right button combination. >> >> control is usually the way to get the alternate click on a mac with one button but this is the third button. im having no luck. >> >> >> >> >> On Dec 8, 2010, at 2:52 PM, Gary Chambers wrote: >> >>> Not sure, having no Mac (only iPad etc...) >>> Try opt-shift clicks perhaps? >>> Shift is a definite component of the magic combination! >>> >>> Regards, Gary >>> >>> ----- Original Message ----- From: "Joseph T. Bore" <jbore(a)tjtech.com> >>> To: <Pharo-project(a)lists.gforge.inria.fr> >>> Sent: Wednesday, December 08, 2010 7:36 PM >>> Subject: Re: [Pharo-project] Morph wont delete in pharo, cant select it... >>> >>> >>> >>> anyway to get that on a mac with a 2 button mouse? im on a laptop, i have 2 buttons, but not three. is there some preference that can be set to give me access to that? >>> >>> >>> On Dec 8, 2010, at 2:28 PM, Gary Chambers wrote: >>> >>>> Try shift-mid-click on morph for halo. >>>> >>>> Regards, Gary >>>> >>>> ----- Original Message ----- From: "Joseph T. Bore" <jbore(a)tjtech.com> >>>> To: <Pharo-project(a)lists.gforge.inria.fr> >>>> Sent: Wednesday, December 08, 2010 7:16 PM >>>> Subject: [Pharo-project] Morph wont delete in pharo, cant select it... >>>> >>>> >>>> >>>> am i doing something obviously wrong?: >>>> >>>> i have downloaded Pharo 1.1.1 (single click) for Mac OSX >>>> >>>> bring up the image then: >>>> >>>> Morph new openInWorld, do it. (get a nice blue square, perfect) >>>> >>>> click to pick it up and move it around, all is well >>>> >>>> control click, brings up menu for morph >>>> >>>> here is where the problems start >>>> >>>> delete menu option, Blue square wont go away... >>>> >>>> add halos menu option gives halos but they are on the PasteupMorph (the desktop i think). >>>> >>>> i cant find any way to get rid of this morph, will i have a blue friend forever? >>>> >>>> im sure im doing something obviously wrong, just dont know what it is... >>>> >>>> >>>> >>> >>> >>> >> >> > >

Dec. 9, 2010