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

[Pharo-project] plan for 1.1

by Torsten Bergmann

Interesting, in an 11371 AND the new 11373 core image this works: --------------------------------------------------------------------- Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfNile'; load. ((Smalltalk at: #ConfigurationOfNile) project version: '1.1') load --------------------------------------------------------------------- but this --------------------------------------------------------------------- Gofer new squeaksource: 'MetaSource'; package: 'ConfigurationOfMetaSource'; load. (Smalltalk at: #ConfigurationOfMetaSource) load --------------------------------------------------------------------- => which indirectly loads ConfigurationOfPharo => which indirectly uses 1.1 of ConfigurationOfNile => which crashes while loading Nile with the stack below. If you use older 11367 core image it works without any problem. Bye T. NSAbstractInflateStream(Object)>>doesNotUnderstand: #huffmanTableFrom:mappedBy: Receiver: a NSAbstractInflateStream Arguments and temporary variables: aMessage: huffmanTableFrom: #(8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8...etc... exception: MessageNotUnderstood: NSAbstractInflateStream>>huffmanTableFrom:mapp...etc... resumeValue: nil Receiver's instance variables: state: nil bitBuf: nil bitPos: nil source: nil sourcePos: nil sourceLimit: nil litTable: nil distTable: nil sourceStream: nil crc: nil position: nil readLimit: nil collection: nil NSAbstractInflateStream class>>initialize Receiver: NSAbstractInflateStream Arguments and temporary variables: low: #(1 2 3 4 5 7 9 13 17 25 33 49 65 97 129 193 257 385 513 769 1025 1537 204...etc... high: #(0 0 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 10 11 11 12 12 13 13) i: 258 i: 30 i: 31 Receiver's instance variables: superclass: Object methodDict: a MethodDictionary(#atEnd->(NSAbstractInflateStream>>#atEnd "a Comp...etc... format: 156 instanceVariables: #('state' 'bitBuf' 'bitPos' 'source' 'sourcePos' 'sourceLimi...etc... organization: ('testing' atEnd) ('requirements' bitBuf bitBuf: bitBuff bitBuff:...etc... subclasses: {NSGZipReadStream. NSZLibReadStream. NSZipReadStream} name: #NSAbstractInflateStream classPool: a Dictionary(#BlockProceedBit->8 #BlockTypes->#(#processStoredBlock ...etc... sharedPools: nil environment: a SystemDictionary(lots of globals) category: #'Nile-Clients-Inflate-Deflate' traitComposition: {} localSelectors: nil MCMethodDefinition>>postloadOver: Receiver: a MCMethodDefinition(NSAbstractInflateStream class>>initialize) Arguments and temporary variables: aDefinition: nil Receiver's instance variables: classIsMeta: true source: 'initialize | low high | "InflateStream initialize" MaxBits := 16. ...etc... category: #initialization selector: #initialize className: #NSAbstractInflateStream timeStamp: 'cyrille.delaunay 6/3/2009 14:40' [] in [] in [] in MCPackageLoader>>basicLoad Receiver: a MCPackageLoader Arguments and temporary variables: ea: a MCMethodDefinition(NSAbstractInflateStream class>>initialize) Receiver's instance variables: requirements: #() unloadableDefinitions: a SortedCollection() obsoletions: a Dictionary() additions: an OrderedCollection(a MCOrganizationDefinition(#(#'Nile-Clients-Bin...etc... removals: an OrderedCollection() errorDefinitions: an OrderedCollection() provisions: a Set(#CompiledMethodTest #CommentedEvent #TestValueWithinFix #Comp...etc... methodAdditions: an OrderedCollection(a MethodAddition a MethodAddition a Metho...etc... [] in [] in OrderedCollection(Collection)>>do:displayingProgress:every: Receiver: an OrderedCollection(a MCOrganizationDefinition(#(#'Nile-Clients-BinaryOrTextStream' #'Nil...etc... Arguments and temporary variables: <<error during printing> Receiver's instance variables: array: an Array(a MCOrganizationDefinition(#(#'Nile-Clients-BinaryOrTextStream'...etc... firstIndex: 1 lastIndex: 1499 OrderedCollection>>do: Receiver: an OrderedCollection(a MCOrganizationDefinition(#(#'Nile-Clients-BinaryOrTextStream' #'Nil...etc... Arguments and temporary variables: aBlock: [closure] in [] in OrderedCollection(Collection)>>do:displayingProgress...etc... index: 1152 Receiver's instance variables: array: an Array(a MCOrganizationDefinition(#(#'Nile-Clients-BinaryOrTextStream'...etc... firstIndex: 1 lastIndex: 1499 [] in OrderedCollection(Collection)>>do:displayingProgress:every: Receiver: an OrderedCollection(a MCOrganizationDefinition(#(#'Nile-Clients-BinaryOrTextStream' #'Nil...etc... Arguments and temporary variables: <<error during printing> Receiver's instance variables: array: an Array(a MCOrganizationDefinition(#(#'Nile-Clients-BinaryOrTextStream'...etc... firstIndex: 1 lastIndex: 1499 [] in [] in ProgressInitiationException>>defaultMorphicAction Receiver: ProgressInitiationException: Arguments and temporary variables: progress: [closure] in SystemProgressMorph>>label:min:max: result: #(nil) Receiver's instance variables: messageText: nil tag: nil signalContext: ProgressInitiationException(Exception)>>signal handlerContext: nil outerContext: nil workBlock: [closure] in OrderedCollection(Collection)>>do:displayingProgress:ev...etc... maxVal: 1499 minVal: 0 aPoint: 351@285 progressTitle: '' BlockClosure>>on:do: Receiver: [closure] in [] in ProgressInitiationException>>defaultMorphicAction Arguments and temporary variables: exception: ProgressNotification handlerAction: [closure] in [] in ProgressInitiationException>>defaultMorphicAc...etc... handlerActive: true Receiver's instance variables: outerContext: [] in ProgressInitiationException>>defaultMorphicAction startpc: 83 numArgs: 0 [] in ProgressInitiationException>>defaultMorphicAction Receiver: ProgressInitiationException: Arguments and temporary variables: progress: [closure] in SystemProgressMorph>>label:min:max: result: #(nil) Receiver's instance variables: messageText: nil tag: nil signalContext: ProgressInitiationException(Exception)>>signal handlerContext: nil outerContext: nil workBlock: [closure] in OrderedCollection(Collection)>>do:displayingProgress:ev...etc... maxVal: 1499 minVal: 0 aPoint: 351@285 progressTitle: '' BlockClosure>>ensure: Receiver: [closure] in ProgressInitiationException>>defaultMorphicAction Arguments and temporary variables: aBlock: [closure] in ProgressInitiationException>>defaultMorphicAction complete: nil returnValue: nil Receiver's instance variables: -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

May 27, 2010

Re: [Pharo-project] CommandShell

by David T. Lewis

On Thu, May 27, 2010 at 09:04:37AM +0200, laurent laffont wrote: > Hi Dave, > > I've managed to make it running in Pharo (remove all isMorphic ifFalse ... > stuff, change menu registration, a little work is needed to adapt to Pharo > new settings system). It works (I can publish a package when back at home). > > Now I suppose you want to keep it running on Squeak, I don't know how to > handle differences on world menu and preferences. > > For the MVC part, is there some value in keeping it ? Hi Laurent, Thanks, I would be very interested in seeing your changes, especially the menu registration fixes. I do want to keep this working on MVC and on other Squeak images. What I really need to do is repackage CommandShell and OSProcess so that everything is not all in two giant packages. I originally "packaged" these many years ago before Squeak had real packages and Monticello, so I basically separated things into two completely separate SAR packages that could be independently maintained (even though CommandShell and OSProcess were intended to work together). That was quite a project at the time, but it is badly out of date now, so I need to go back and make this stuff work properly with Metacello configurations. Dave

May 27, 2010

Re: [Pharo-project] Gettext package in PharoNonCorePackages

by Hilaire Fernandes

I don't think so Hilaire Mariano Martinez Peck a Ã©crit : > Thanks Hilaire. Do you think this should be added to PharoDev? Because > most of PharoNonCorePackages do. > > Cheers > > Mariano > > On Wed, May 26, 2010 at 9:11 PM, Hilaire Fernandes > <hilaire.fernandes(a)gmail.com > <mailto:hilaire.fernandes@gmail.com>> wrote: > > I move the gettext package there, as it is the right place for long > term support for this package. > > Please, from now, commit any change there. > > http://www.squeaksource.com/PharoNonCorePackages > > Hilaire > > > _______________________________________________ > 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 27, 2010

Re: [Pharo-project] difference between Sequenceable and Ordered

by Nicolas Cellier

Ordered have the capability of adding/removing elements, Sequenceable not necessarily (think of Arrayed) Nicolas 2010/5/27 Tristan Bourgois <tr.bourgois(a)laposte.net>: > > Thanks, that's very interesting but not really help me sorry! > Sorry may be the question are not very precise. > My question is about the behavior so I put it in the context: > > I refactoring the collection in trait and I search if > there are a difference between a Sequenceable and > Ordered behavior. Because if there are not difference > I don't create trait for the Ordered behavior. > > So do you think there are difference between the two behavior? > > -- > View this message in context: http://forum.world.st/difference-between-Sequenceable-and-Ordered-tp2231718… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 27, 2010

Re: [Pharo-project] plan for 1.1

by StÃ©phane Ducasse

I lost again a couple of hours because the bug only appears with glamour so I will rollback the createClass of MCClassDefinition for now. Stef On May 27, 2010, at 11:02 AM, StÃ©phane Ducasse wrote: > Torsten > > can you give a try to see if it fixes your problems with the latest cs? > Apparently Torch is ok now. > > Stef > > On May 26, 2010, at 4:05 PM, StÃ©phane Ducasse wrote: > >>> Stef wrote >>>> I found the traits bug :) >>> >>> OK, can we expect a fix in the next update (11373?). >> >> yes of course I was exhausted and had to sleep. >> http://code.google.com/p/pharo/issues/detail?id=2477 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 27, 2010

Re: [Pharo-project] Bug with Debug Test in OB: BlockCannotReturn

by Lukas Renggli

Having a good and easily reproducible bug description is half of the working fixing the actual bug. Lukas 2010/5/27 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Thanks Lukas. It is funny. It takes more time to me submitting the issue > than the time to wait in gmail and receive Lukas fixes hahhahahah > > > On Thu, May 27, 2010 at 12:08 PM, Lukas Renggli <renggli(a)gmail.com> wrote: >> >> It's fixed in >> >> Â Name: OB-SUnitIntegration-lr.29 >> Â Author: lr >> Â Time: 27 May 2010, 12:04:41 pm >> Â UUID: 77fd95eb-754d-49fe-859f-fc3508adc94f >> Â Ancestors: OB-SUnitIntegration-lr.28 >> >> Lukas >> >> 2010/5/27 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> > Hi folks. I have the following issue: >> > >> > http://code.google.com/p/pharo/issues/detail?id=2485 >> > >> > Pharo image: Pharo-1.1-11367-Beta >> > Pharo core version: 11367 >> > >> > Virtual machine used: Mac 2.4.2 >> > Class browser used if applicable: OB >> > >> > Steps to reproduce: >> > 1. Open a system browser >> > 2. Select a class that has tests. Example ArrayLiteralTest. >> > 3. Select any test method, like testByteArrayBase. >> > >> > 4. Right button, "debug test" >> > 5. When the debugger raise, just click on Proceed >> > >> > There you will get a BlockCannotReturn: Block Cannot Return >> > >> > I attach PharoDebug.log in the issue tracker. >> > >> > Cheers >> > >> > >> > Mariano >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> 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 > -- Lukas Renggli www.lukas-renggli.ch

May 27, 2010

Re: [Pharo-project] Bug with Debug Test in OB: BlockCannotReturn

by Mariano Martinez Peck

Thanks Lukas. It is funny. It takes more time to me submitting the issue than the time to wait in gmail and receive Lukas fixes hahhahahah On Thu, May 27, 2010 at 12:08 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > It's fixed in > > Name: OB-SUnitIntegration-lr.29 > Author: lr > Time: 27 May 2010, 12:04:41 pm > UUID: 77fd95eb-754d-49fe-859f-fc3508adc94f > Ancestors: OB-SUnitIntegration-lr.28 > > Lukas > > 2010/5/27 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Hi folks. I have the following issue: > > > > http://code.google.com/p/pharo/issues/detail?id=2485 > > > > Pharo image: Pharo-1.1-11367-Beta > > Pharo core version: 11367 > > > > Virtual machine used: Mac 2.4.2 > > Class browser used if applicable: OB > > > > Steps to reproduce: > > 1. Open a system browser > > 2. Select a class that has tests. Example ArrayLiteralTest. > > 3. Select any test method, like testByteArrayBase. > > > > 4. Right button, "debug test" > > 5. When the debugger raise, just click on Proceed > > > > There you will get a BlockCannotReturn: Block Cannot Return > > > > I attach PharoDebug.log in the issue tracker. > > > > Cheers > > > > > > Mariano > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 27, 2010

Re: [Pharo-project] Image Lockdown/Deployment mode

by Mariano Martinez Peck

> Maybe the old "Lockdown" package could be a start: > http://wiki.squeak.org/squeak/518 > > .... > I think of a loadable package "ImageLocker" with a class > that can set/unset the appropriate preferences and provide > alternative error handlers, menues, ... > > Any comments? > > I really like it. I would love to have such features. Maybe we can elaborate it and try to have it for 1.2 Just creating a wiki page or an issue with label 1.2 will persist this thread. > Thx > T. > > BTW: I remember having a hard time with the "deployment step" in most > commercial environments due to "striping" the image. Grrrrr me too. A lot of times, the "reduce" step didn't include me methods because they don't *seemed* to have senders. But those methods were really called, buy by reflection. Then I suffered some DNUs at production :( > Now this > is partly adressed by building images bottom to top using > Metacello now. One could load his app based on a core without > the extended dev-tools. > > But Pharo should really care to also easily disable developer > facilities so developers may use it as the platform for > their next project. > > > -- > 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 27, 2010

Re: [Pharo-project] [squeak-dev] Towards clean unloading Morphic (an idea)

by Hannes Hirzel

On 5/20/10, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hello, > > i just thought, that in order to get down to a minimal kernel image, > it would be nice to move all Morphic globals into a shared pool. > > Things like, World, ActiveWorld > could be placed into a MorphicPool class. > > Then we can make an easy transition > 1. add this pool to classes which using that global & recompile them > > 2. for classes, which should have no dependency from Morphic, > use a messages like > > Object >> currentWorld > ^ (Smalltalk at: #MorphicPool ifAbsent: [ self error: 'bummer' ]) > currentWorld . > > Then, i hope, you can unload the Morphic using MC and it will leave no > trace in an image (or at least less trace than usual ;). > > Same could be applied to Graphics package (to get rid a Display global) > > -- > Best regards, > Igor Stasenko AKA sig. Hello If have read all the other mails in this thread. The proposal by Igo may be implemented with the means available. Is there any strong reason not to move ahead with this? Kind regards Hannes

May 27, 2010

Re: [Pharo-project] Bug with Debug Test in OB: BlockCannotReturn

by Lukas Renggli

It's fixed in Name: OB-SUnitIntegration-lr.29 Author: lr Time: 27 May 2010, 12:04:41 pm UUID: 77fd95eb-754d-49fe-859f-fc3508adc94f Ancestors: OB-SUnitIntegration-lr.28 Lukas 2010/5/27 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi folks. I have the following issue: > > http://code.google.com/p/pharo/issues/detail?id=2485 > > Pharo image: Pharo-1.1-11367-Beta > Pharo core version: 11367 > > Virtual machine used: Mac 2.4.2 > Class browser used if applicable: OB > > Steps to reproduce: > 1. Open a system browser > 2. Select a class that has tests. Example ArrayLiteralTest. > 3. Select any test method, like testByteArrayBase. > > 4. Right button, "debug test" > 5. When the debugger raise, just click on Proceed > > There you will get a BlockCannotReturn: Block Cannot Return > > I attach PharoDebug.log in the issue tracker. > > Cheers > > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

May 27, 2010