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

Re: [Pharo-project] Can this be improved in Glamourous?

by StÃ©phane Ducasse

On Oct 15, 2011, at 10:58 PM, Tudor Girba wrote: > Hi, > > On 15 Oct 2011, at 22:36, Mariano Martinez Peck wrote: > >> Hi Tudor. Today I wanted to give it a try to 'GT-Inspector' 'GT-Playground' hence I did: > > I am happy you decided to give them a try :). But, the Playground is not yet ready :). > >> (ConfigurationOfGlamoroust project version: #bleedingEdge) load: #('GT-Inspector' 'GT-Playground' ). >> >> In a Pharo 1.3 release. To my surprise, it took like half an hour to install, and it even was broken because it installed a different version of refactoring browser that is not working in 1.3. > > This is due to a broken ConfiguraitonOfRB. I would actually be very interested in a fix in this area. what is broken? because I spent one full sprint to fix it. >> So..can I ask.. are all of those projects really needed just for 2 simples things like a cool inspector and a cool workspace? >> do you need Nile, Grease, RefactoringBrowser, EyeSee, Magritte ??? >> can I somehow just load a minimal core for those things I need ? > > These projects are loaded by the full default ConfigurationOfGlamour. The ConfigurationOfGlamour offers groups, but the GlamorousToolikt one does not yet. If someone can tell me how to do something like this, I would be happy to accommodate the solution. in the chapter on metacello groups are explained. I can send you the latest version if you want. > > Cheers, > Doru > > >> Thanks >> >> linear load : >> linear load : baseline-0.1 [ConfigurationOfGlamoroust] >> load : ConfigurationOfGlamour >> atomic load : baseline-0.1 [ConfigurationOfGlamoroust] >> linear load : default [ConfigurationOfGlamour] >> load : ConfigurationOfEyeSee >> linear load : default [ConfigurationOfGlamour] >> load : ConfigurationOfGrease >> linear load : default [ConfigurationOfGlamour] >> load : ConfigurationOfMondrian >> linear load : default [ConfigurationOfGlamour] >> load : ConfigurationOfShout >> atomic load : default [ConfigurationOfGlamour] >> load : CollectionExtensions >> load : Glamour-Announcements >> load : Glamour-Helpers >> load : Glamour-Core >> load : Glamour-Presentations >> load : Glamour-Browsers >> load : Glamour-Tests-Core >> load : Glamour-Morphic-Theme >> load : Glamour-Examples >> load : Glamour-Tools >> load : Glamour-Morphic-Widgets >> load : Glamour-Morphic-Renderer >> load : Glamour-Tests-Morphic >> linear load : default [ConfigurationOfMondrian] >> load : ConfigurationOfProfStef >> linear load : default [ConfigurationOfMondrian] >> load : ConfigurationOfHealthReportProducer >> linear load : default [ConfigurationOfMondrian] >> load : ConfigurationOfShapeST80 >> atomic load : default [ConfigurationOfMondrian] >> atomic load : 0.2-baseline [ConfigurationOfHealthReportProducer] >> load : HealthReportProducer >> load : CollectionExtensions >> load : Nile-Base >> load : Mondrian-ComplexShape >> load : Mondrian-Core >> load : Mondrian-Layouts >> load : Mondrian-Help >> load : Mondrian-Easel >> load : Mondrian-Pharo-Tests >> load : Mondrian-Shapes >> load : Mondrian-Events >> load : Mondrian-Visitor >> load : Mondrian-Util >> load : Mondrian-Normalizers >> load : Mondrian-Example >> load : Mondrian-ShapeVisitor >> load : Mondrian-Pharo-Morphic >> load : Mondrian-Tests >> load : Mondrian-FADELayout >> load : Glamour-Mondrian-Presentations >> load : Glamour-Tests-Mondrian >> atomic load : default [ConfigurationOfEyeSee] >> load : EyeSee-Events >> load : EyeSee-Axis >> load : EyeSee-Tests-Core >> load : EyeSee-Support >> load : EyeSee-Core >> load : Glamour-EyeSee-Presentations >> load : Glamour-Tests-EyeSee >> linear load : 1.0.6.1 [ConfigurationOfGrease] >> load : ConfigurationOfRefactoringBrowser >> linear load : 1.0.6.1 [ConfigurationOfGrease] >> load : Grease-Slime-lr.13 >> load : Magritte-Model >> load : Magritte-Pharo-Model >> load : Magritte-Morph >> load : Glamour-Magritte-Presentations >> load : Magritte-Tests-Model >> load : GT-Playground >> load : GT-Inspector >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- > www.tudorgirba.com > > "Every successful trip needs a suitable vehicle." > > > > >

Oct. 15, 2011

[Pharo-project] [update 1.4] #14196

by StÃ©phane Ducasse

14196 ----- - Issue 4900: CompiledMethod printString. - Fixing FlatListBrowser (not to use third from event but second). - Issue 4912: Float infinity and Float nan should print themselves - Fix users ot tools registry>>browse:selector: to use now Smalltalk tools browser

Oct. 15, 2011

Re: [Pharo-project] Can this be improved in Glamourous?

by Tudor Girba

Hi, On 15 Oct 2011, at 22:36, Mariano Martinez Peck wrote: > Hi Tudor. Today I wanted to give it a try to 'GT-Inspector' 'GT-Playground' hence I did: I am happy you decided to give them a try :). But, the Playground is not yet ready :). > (ConfigurationOfGlamoroust project version: #bleedingEdge) load: #('GT-Inspector' 'GT-Playground' ). > > In a Pharo 1.3 release. To my surprise, it took like half an hour to install, and it even was broken because it installed a different version of refactoring browser that is not working in 1.3. This is due to a broken ConfiguraitonOfRB. I would actually be very interested in a fix in this area. > So..can I ask.. are all of those projects really needed just for 2 simples things like a cool inspector and a cool workspace? > do you need Nile, Grease, RefactoringBrowser, EyeSee, Magritte ??? > can I somehow just load a minimal core for those things I need ? These projects are loaded by the full default ConfigurationOfGlamour. The ConfigurationOfGlamour offers groups, but the GlamorousToolikt one does not yet. If someone can tell me how to do something like this, I would be happy to accommodate the solution. Cheers, Doru > Thanks > > linear load : > linear load : baseline-0.1 [ConfigurationOfGlamoroust] > load : ConfigurationOfGlamour > atomic load : baseline-0.1 [ConfigurationOfGlamoroust] > linear load : default [ConfigurationOfGlamour] > load : ConfigurationOfEyeSee > linear load : default [ConfigurationOfGlamour] > load : ConfigurationOfGrease > linear load : default [ConfigurationOfGlamour] > load : ConfigurationOfMondrian > linear load : default [ConfigurationOfGlamour] > load : ConfigurationOfShout > atomic load : default [ConfigurationOfGlamour] > load : CollectionExtensions > load : Glamour-Announcements > load : Glamour-Helpers > load : Glamour-Core > load : Glamour-Presentations > load : Glamour-Browsers > load : Glamour-Tests-Core > load : Glamour-Morphic-Theme > load : Glamour-Examples > load : Glamour-Tools > load : Glamour-Morphic-Widgets > load : Glamour-Morphic-Renderer > load : Glamour-Tests-Morphic > linear load : default [ConfigurationOfMondrian] > load : ConfigurationOfProfStef > linear load : default [ConfigurationOfMondrian] > load : ConfigurationOfHealthReportProducer > linear load : default [ConfigurationOfMondrian] > load : ConfigurationOfShapeST80 > atomic load : default [ConfigurationOfMondrian] > atomic load : 0.2-baseline [ConfigurationOfHealthReportProducer] > load : HealthReportProducer > load : CollectionExtensions > load : Nile-Base > load : Mondrian-ComplexShape > load : Mondrian-Core > load : Mondrian-Layouts > load : Mondrian-Help > load : Mondrian-Easel > load : Mondrian-Pharo-Tests > load : Mondrian-Shapes > load : Mondrian-Events > load : Mondrian-Visitor > load : Mondrian-Util > load : Mondrian-Normalizers > load : Mondrian-Example > load : Mondrian-ShapeVisitor > load : Mondrian-Pharo-Morphic > load : Mondrian-Tests > load : Mondrian-FADELayout > load : Glamour-Mondrian-Presentations > load : Glamour-Tests-Mondrian > atomic load : default [ConfigurationOfEyeSee] > load : EyeSee-Events > load : EyeSee-Axis > load : EyeSee-Tests-Core > load : EyeSee-Support > load : EyeSee-Core > load : Glamour-EyeSee-Presentations > load : Glamour-Tests-EyeSee > linear load : 1.0.6.1 [ConfigurationOfGrease] > load : ConfigurationOfRefactoringBrowser > linear load : 1.0.6.1 [ConfigurationOfGrease] > load : Grease-Slime-lr.13 > load : Magritte-Model > load : Magritte-Pharo-Model > load : Magritte-Morph > load : Glamour-Magritte-Presentations > load : Magritte-Tests-Model > load : GT-Playground > load : GT-Inspector > > -- > Mariano > http://marianopeck.wordpress.com > -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

Oct. 15, 2011

Re: [Pharo-project] Can this be improved in Glamourous?

by Lukas Renggli

You should consider yourself lucky that Magritte does not pull-in 75 Seaside packages :-) On Saturday, 15 October 2011, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi Tudor. Today I wanted to give it a try to 'GT-Inspector' 'GT-Playground' hence I did: > > (ConfigurationOfGlamoroust project version: #bleedingEdge) load: #('GT-Inspector' 'GT-Playground' ). > > In a Pharo 1.3 release. To my surprise, it took like half an hour to install, and it even was broken because it installed a different version of refactoring browser that is not working in 1.3. > So..can I ask.. are all of those projects really needed just for 2 simples things like a cool inspector and a cool workspace? > do you need Nile, Grease, RefactoringBrowser, EyeSee, Magritte ??? > can I somehow just load a minimal core for those things I need ? > > Thanks > > linear load : > linear load : baseline-0.1 [ConfigurationOfGlamoroust] > load : ConfigurationOfGlamour > atomic load : baseline-0.1 [ConfigurationOfGlamoroust] > linear load : default [ConfigurationOfGlamour] > load : ConfigurationOfEyeSee > linear load : default [ConfigurationOfGlamour] > load : ConfigurationOfGrease > linear load : default [ConfigurationOfGlamour] > load : ConfigurationOfMondrian > linear load : default [ConfigurationOfGlamour] > load : ConfigurationOfShout > atomic load : default [ConfigurationOfGlamour] > load : CollectionExtensions > load : Glamour-Announcements > load : Glamour-Helpers > load : Glamour-Core > load : Glamour-Presentations > load : Glamour-Browsers > load : Glamour-Tests-Core > load : Glamour-Morphic-Theme > load : Glamour-Examples > load : Glamour-Tools > load : Glamour-Morphic-Widgets > load : Glamour-Morphic-Renderer > load : Glamour-Tests-Morphic > linear load : default [ConfigurationOfMondrian] > load : ConfigurationOfProfStef > linear load : default [ConfigurationOfMondrian] > load : ConfigurationOfHealthReportProducer > linear load : default [ConfigurationOfMondrian] > load : ConfigurationOfShapeST80 > atomic load : default [ConfigurationOfMondrian] > atomic load : 0.2-baseline [ConfigurationOfHealthReportProducer] > load : HealthReportProducer > load : CollectionExtensions > load : Nile-Base > load : Mondrian-ComplexShape > load : Mondrian-Core > load : Mondrian-Layouts > load : Mondrian-Help > load : Mondrian-Easel > load : Mondrian-Pharo-Tests > load : Mondrian-Shapes > load : Mondrian-Events > load : Mondrian-Visitor > load : Mondrian-Util > load : Mondrian-Normalizers > load : Mondrian-Example > load : Mondrian-ShapeVisitor > load : Mondrian-Pharo-Morphic > load : Mondrian-Tests > load : Mondrian-FADELayout > load : Glamour-Mondrian-Presentations > load : Glamour-Tests-Mondrian > atomic load : default [ConfigurationOfEyeSee] > load : EyeSee-Events > load : EyeSee-Axis > load : EyeSee-Tests-Core > load : EyeSee-Support > load : EyeSee-Core > load : Glamour-EyeSee-Presentations > load : Glamour-Tests-EyeSee > linear load : 1.0.6.1 [ConfigurationOfGrease] > load : ConfigurationOfRefactoringBrowser > linear load : 1.0.6.1 [ConfigurationOfGrease] > load : Grease-Slime-lr.13 > load : Magritte-Model > load : Magritte-Pharo-Model > load : Magritte-Morph > load : Glamour-Magritte-Presentations > load : Magritte-Tests-Model > load : GT-Playground > load : GT-Inspector > > -- > Mariano > http://marianopeck.wordpress.com > > -- Lukas Renggli www.lukas-renggli.ch

Oct. 15, 2011

[Pharo-project] Can this be improved in Glamourous?

by Mariano Martinez Peck

Hi Tudor. Today I wanted to give it a try to 'GT-Inspector' 'GT-Playground' hence I did: (ConfigurationOfGlamoroust project version: #bleedingEdge) load: #('GT-Inspector' 'GT-Playground' ). In a Pharo 1.3 release. To my surprise, it took like half an hour to install, and it even was broken because it installed a different version of refactoring browser that is not working in 1.3. So..can I ask.. are all of those projects really needed just for 2 simples things like a cool inspector and a cool workspace? do you need Nile, Grease, RefactoringBrowser, EyeSee, Magritte ??? can I somehow just load a minimal core for those things I need ? Thanks linear load : linear load : baseline-0.1 [ConfigurationOfGlamoroust] load : ConfigurationOfGlamour atomic load : baseline-0.1 [ConfigurationOfGlamoroust] linear load : default [ConfigurationOfGlamour] load : ConfigurationOfEyeSee linear load : default [ConfigurationOfGlamour] load : ConfigurationOfGrease linear load : default [ConfigurationOfGlamour] load : ConfigurationOfMondrian linear load : default [ConfigurationOfGlamour] load : ConfigurationOfShout atomic load : default [ConfigurationOfGlamour] load : CollectionExtensions load : Glamour-Announcements load : Glamour-Helpers load : Glamour-Core load : Glamour-Presentations load : Glamour-Browsers load : Glamour-Tests-Core load : Glamour-Morphic-Theme load : Glamour-Examples load : Glamour-Tools load : Glamour-Morphic-Widgets load : Glamour-Morphic-Renderer load : Glamour-Tests-Morphic linear load : default [ConfigurationOfMondrian] load : ConfigurationOfProfStef linear load : default [ConfigurationOfMondrian] load : ConfigurationOfHealthReportProducer linear load : default [ConfigurationOfMondrian] load : ConfigurationOfShapeST80 atomic load : default [ConfigurationOfMondrian] atomic load : 0.2-baseline [ConfigurationOfHealthReportProducer] load : HealthReportProducer load : CollectionExtensions load : Nile-Base load : Mondrian-ComplexShape load : Mondrian-Core load : Mondrian-Layouts load : Mondrian-Help load : Mondrian-Easel load : Mondrian-Pharo-Tests load : Mondrian-Shapes load : Mondrian-Events load : Mondrian-Visitor load : Mondrian-Util load : Mondrian-Normalizers load : Mondrian-Example load : Mondrian-ShapeVisitor load : Mondrian-Pharo-Morphic load : Mondrian-Tests load : Mondrian-FADELayout load : Glamour-Mondrian-Presentations load : Glamour-Tests-Mondrian atomic load : default [ConfigurationOfEyeSee] load : EyeSee-Events load : EyeSee-Axis load : EyeSee-Tests-Core load : EyeSee-Support load : EyeSee-Core load : Glamour-EyeSee-Presentations load : Glamour-Tests-EyeSee linear load : 1.0.6.1 [ConfigurationOfGrease] load : ConfigurationOfRefactoringBrowser linear load : 1.0.6.1 [ConfigurationOfGrease] load : Grease-Slime-lr.13 load : Magritte-Model load : Magritte-Pharo-Model load : Magritte-Morph load : Glamour-Magritte-Presentations load : Magritte-Tests-Model load : GT-Playground load : GT-Inspector -- Mariano http://marianopeck.wordpress.com

Oct. 15, 2011

Re: [Pharo-project] 1.3 and scamper html package; unexpected emergency evaluator

by Schwab,Wilhelm K

Here is my proposed sequence of steps to reproduce the defect: (1) get/unzip 1.3 one-click (2) run it (perhaps on 32 bit Ubuntu Lucid) (3) open a workspace (4) paste the following text: HtmlParser parse:Clipboard default clipboardText readStream. (5) Select the above and Do-it. Note the missing #string send - the code is not expected to work; it should cause a walkback w/o offering to open an emergency evaluator. The above steps give me an error claiming "system error handling failed." Can anyone reproduce it? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Friday, October 14, 2011 4:38 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.3 and scamper html package; unexpected emergency evaluator On Oct 14, 2011, at 10:28 PM, Schwab,Wilhelm K wrote: > Stef, all, > > I am doing some well-intentioned reverse-engineering of a system (aka trying to read uncommented code) and have been looking at some html that it produces. Scamper's parser was helpful some years back, so I looked on SqueakSource and found two HTML packages. I had the validation package installed, so I decided to add the scamper parser package. > > Weirdness #1: I was curious about what was going to happen when I installed a second HTML* package. I did NOT expect the existing package(s) to be replaced :( Didn't save that image. yes package as jst string conventions so ... > > I owe you guys some serious testing on 1.3, so I decided to use the one-click to run the scamper package. My plan was to view source on a locally-produced page, select-all+copy and then pull the text from the clipboard to parse it. I *should* have done this: > > HtmlParser parse:Clipboard default clipboardText string readStream. > > Aside from every other item being an empty HtmlAttributes (probably very correct if a little odd looking), it does pretty much exactly what I had in mind. I said I should have done the above. What I in fact did was > > HtmlParser parse:Clipboard default clipboardText string readStream. > > (the #string send is missing). > > Weirdness #2: It's interesting, because I get a vm error (text all over the main window with an offer to open an emergency evaluator) saying *** System error handling failed ***. > > Hitting any key clears the error and displays a walkback that will open a debugger revealing that #replaceHtmlCharRefs is missing, or so that appears to be the problem. Of course the real problem is that I evaluated the wrong expression, but I should simply get the walkback, not the callstack. Is there something I can do to help unravel the cause of the problem? I used the 1.3 one-click from the web site. I do not know. Indeed it looks like the handler did not took place and we get the emergency something. Would be good to get a simple way to reproduce the behavior. > > Bill > > > >

Oct. 15, 2011

Re: [Pharo-project] MCDirectoryRepository defaultDirectoryName ignored?

by Sean P. DeNigris

Mariano Martinez Peck wrote: > > it seems "ignored" When I created the accessors and setting, the purpose was so that when you add a directory repository via the MC Browser ("+Repository"->directory), the UI would start in this directory. I wanted this because all my local repos are in the same parent directory and it saved me having to navigate there as I added every new repository. This is the only place where it is used. We could: * comment/rename the current functionality to reflect this * or, update the other use cases you describe to use it HTH, Sean -- View this message in context: http://forum.world.st/MCDirectoryRepository-defaultDirectoryName-ignored-tp… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Oct. 15, 2011

[Pharo-project] [update 1.4] #14195

by StÃ©phane Ducasse

14195 ----- -Issue 4899: Using a Pool var in a subclass of a pool user does not refer to the pool when an existing class with the same name exit. Stef and Igor having fun. Part Two. http://code.google.com/p/pharo/issues/detail?id=4899

Oct. 15, 2011

[Pharo-project] [update 1.4] #14194

by StÃ©phane Ducasse

14194 ----- - Issue 4764: New way to display Debbuger. Thanks Benjamin van Ryseghem. http://code.google.com/p/pharo/issues/detail?id=4764 -Issue 4899: Using a Pool var in a subclass of a pool user does not refer to the pool when an existing class with the same name exit. Stef and Igor having fun. Part one. http://code.google.com/p/pharo/issues/detail?id=4899

Oct. 15, 2011

Re: [Pharo-project] [ANN] Fuel release version 1.7

by Mariano Martinez Peck

> Any blog posts with benchmarks comparing different Fuel versions? > > Here you have 2 charts. You help can be seen in Widestring for example. Now dates are a little bit slower to materialize but the serialization is much faster. If you have ideas to speed up Date materialization ;) FLDateCluster. Cheers -- Mariano http://marianopeck.wordpress.com

Oct. 15, 2011