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

Re: [Pharo-project] TWM doesn't work without keymappins and keymappings doesn't work

by Mariano Martinez Peck

Thanks Guille for the whole work :) Laurent: let me know when I can use TWM properly with this latest version of keymappings. Thanks guys On Sun, Oct 16, 2011 at 10:11 AM, laurent laffont <laurent.laffont(a)gmail.com > wrote: > >>> >> OK so cmd+w is definitely not a good prefix for TWM shortcuts. Is cmd+m >> better ? >> >> > oups Cmd+m not a good idea :) I struggle to find a good prefix..... > > Laurent. > > > > > >> >> >>> So i installed TWM without keybinding but now I cannot open the settings >>>> window because keymappings is not load. >>>> >>>> Any solution? (install TWM without keymappings or fixing keymappings) >>>> >>> >>> I've done some fixes and improvements to keymapping, and I've created a >>> 2.0 version where: >>> >>> - the collisions below are fixed >>> - keymaps can be configured per morph instance too (not only per class, >>> as the former version) >>> - some little improvements and code cleaning >>> >> >> >> Thanks ! >> >> >> But those things I remarked of TWM should be reviewed :) >>> >>> Or you can Use twm without keymappings and I'll have no more feedback :( >>> >> >> >> TWM without Keymapping is not really interesting. I will produce new >> versions of TWM. >> >> Laurent >> >> >> >>> >>> >>>> >>>> thanks! >>>> >>> >>> Thank you :) >>> >>> Guille >>> >> >> > -- Mariano http://marianopeck.wordpress.com

Oct. 16, 2011

Re: [Pharo-project] Native Windows

by StÃ©phane Ducasse

What is the license of the code? I do not think that newspeak code is MIT. Stef On Oct 16, 2011, at 11:51 AM, Mariano Martinez Peck wrote: > > > On Sun, Oct 16, 2011 at 6:12 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Fri, Oct 14, 2011 at 9:19 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > What are the current options/future-possibilities? > > I was playing with Fffenestri's DisplayHostWindow, which kind of works in > 1.3. What ever happened to that project? What is the status of Mars? Are > there any other avenues? > > > back-porting Vassili Bykov's native window implementation for Newspeak (which runs above a slightly-modified Squeak VM, modified to support Newspeak bytecodes). > > > He is coming to Smalltalks.... I mention this just in case someone wants to discuss with him. > > > > Thanks. > Sean > > -- > View this message in context: http://forum.world.st/Native-Windows-tp3905413p3905413.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > -- > best, > Eliot > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Oct. 16, 2011

Re: [Pharo-project] Native Windows

by Mariano Martinez Peck

On Sun, Oct 16, 2011 at 6:12 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > > > On Fri, Oct 14, 2011 at 9:19 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > >> What are the current options/future-possibilities? >> >> I was playing with Fffenestri's DisplayHostWindow, which kind of works in >> 1.3. What ever happened to that project? What is the status of Mars? Are >> there any other avenues? >> > > > back-porting Vassili Bykov's native window implementation for Newspeak > (which runs above a slightly-modified Squeak VM, modified to support > Newspeak bytecodes). > > He is coming to Smalltalks.... I mention this just in case someone wants to discuss with him. > >> Thanks. >> Sean >> >> -- >> View this message in context: >> http://forum.world.st/Native-Windows-tp3905413p3905413.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > > > -- > best, > Eliot > > -- Mariano http://marianopeck.wordpress.com

Oct. 16, 2011

Re: [Pharo-project] TWM doesn't work without keymappins and keymappings doesn't work

by laurent laffont

> > >> > OK so cmd+w is definitely not a good prefix for TWM shortcuts. Is cmd+m > better ? > > oups Cmd+m not a good idea :) I struggle to find a good prefix..... Laurent. > > >> So i installed TWM without keybinding but now I cannot open the settings >>> window because keymappings is not load. >>> >>> Any solution? (install TWM without keymappings or fixing keymappings) >>> >> >> I've done some fixes and improvements to keymapping, and I've created a >> 2.0 version where: >> >> - the collisions below are fixed >> - keymaps can be configured per morph instance too (not only per class, as >> the former version) >> - some little improvements and code cleaning >> > > > Thanks ! > > > But those things I remarked of TWM should be reviewed :) >> >> Or you can Use twm without keymappings and I'll have no more feedback :( >> > > > TWM without Keymapping is not really interesting. I will produce new > versions of TWM. > > Laurent > > > >> >> >>> >>> thanks! >>> >> >> Thank you :) >> >> Guille >> > >

Oct. 16, 2011

Re: [Pharo-project] TWM doesn't work without keymappins and keymappings doesn't work

by StÃ©phane Ducasse

Hi guillermo I would like to push Keymapping in the core. Do you think that it is ready? Like that we could remove the hardcoded way. Stef > > > On Sat, Oct 15, 2011 at 9:47 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys. I was trying to use TWM in Pharo 1.3 release. TWM brings with keymappings, which breaks the shortcuts of my image. > > The main problem here is that it's not integrated with current tools (i.e. OB). If you just load Keymapping you will have an image where: > - lots of shortcuts are hardcoded > - some shortcuts like OB's are handled with it's own and specific way/framework > > Having keymapping living with those, introduces a third way of handling shortcuts (yeap, it's not good enough, but It's not easy to remove all the old code in a row ). So, the following problems happens: > > - first of all, there are shortcuts collisions. If a morph handles cmd + a and its owner handles cmd + a, cmd + b, the owner morph will never handle the shortcut because it was handled by it's child first. > - second. It's hard to keep track and find every hardcoded shortcut :). And furthermore, this leads in the fact that I cannot easily analyse shortcuts collisions between keymapping and hardcoded shortcuts. > > So, how does Keymapping live with that by now? > 1) a keyEvent reaches a morph > 2) the morph delegates the handling in keymapping (bubbling until the world instance). > 3) if keymapping does not handle the shortcut, It is delegated to the old-hardcoded shortcuts (so the original behavior is still there yet) > > All this is just to understand what is happening and where the errors come from :P > > For example, after installing keymappings I cannot close windows anymore with cmd + w or I cannot run tests from the browser using cmd + t. > > So far, I've found those two collisions in keymapping 1.9 and one more in keymapping+TWM: > > 1) Cmd+w was defined for TextEditor for delete backword. > > Esteban already complained about this, so I've changed it in 2.0 for Cmd + Backspace > This shortcut was taken from SimpleEditor, in #initializeCmdKeyShortcuts. I don't know if it should be there or not. > > 2) Cmd+t from omnibrowser was colliding with some global shortcuts I defined in the initial versions of keymapping to play opening a test runner, a browser, a monticello browser. > > I've fixed it removing the global shortcuts by now (because I'm not conviced the key combinations are nice). > > 3) When loading TWM + Keymapping, I realized the cmd+w was not working again. Wandering, I found that the TWM shortcuts were defined for a lot of morphs, in this way, causing a little of trouble: > > {PasteUpMorph. SystemWindow. SmalltalkEditor. TextEditor. PluggableTextMorph} do: [:aClass| > aBuilder > attachShortcutCategory: self shortcutCategory > to: aClass. > ]. > > But replacing it by > > aBuilder > attachShortcutCategory: self shortcutCategory > to: PasteUpMorph. > > should be working the same way :/. > Laurent, did you have any problems when not attaching the categories in this way?. > > Also: TWM by default has a lot of (cmd+w, ...) mappings colliding with the window cmd+w shortcut. So the window shortcut or the TWM ones are to be sacrificed :P. > > > So i installed TWM without keybinding but now I cannot open the settings window because keymappings is not load. > > Any solution? (install TWM without keymappings or fixing keymappings) > > I've done some fixes and improvements to keymapping, and I've created a 2.0 version where: > > - the collisions below are fixed > - keymaps can be configured per morph instance too (not only per class, as the former version) > - some little improvements and code cleaning > > But those things I remarked of TWM should be reviewed :) > > Or you can Use twm without keymappings and I'll have no more feedback :( > > > thanks! > > Thank you :) > > Guille

Oct. 16, 2011

Re: [Pharo-project] TWM doesn't work without keymappins and keymappings doesn't work

by laurent laffont

Hi Guillermo, thanks a lot for these informations. 3) When loading TWM + Keymapping, I realized the *cmd+w* was not working > again. Wandering, I found that the TWM shortcuts were defined for a lot of > morphs, in this way, causing a little of trouble: > > {PasteUpMorph. SystemWindow. SmalltalkEditor. TextEditor. > PluggableTextMorph} do: [:aClass| > aBuilder > attachShortcutCategory: self shortcutCategory > to: aClass. > ]. > > But replacing it by > > aBuilder > attachShortcutCategory: self shortcutCategory > to: PasteUpMorph. > > should be working the same way :/. > Laurent, did you have any problems when not attaching the categories in > this way?. > I think I've done that because TWM shortcuts are not handled when the focus is on a TextEditor, because of the cmd+w collision. Also: TWM by default has a lot of *(cmd+w, ...)* mappings colliding with the > window *cmd+w* shortcut. So the window shortcut or the TWM ones are to be > sacrificed :P. > > OK so cmd+w is definitely not a good prefix for TWM shortcuts. Is cmd+m better ? > So i installed TWM without keybinding but now I cannot open the settings >> window because keymappings is not load. >> >> Any solution? (install TWM without keymappings or fixing keymappings) >> > > I've done some fixes and improvements to keymapping, and I've created a 2.0 > version where: > > - the collisions below are fixed > - keymaps can be configured per morph instance too (not only per class, as > the former version) > - some little improvements and code cleaning > Thanks ! But those things I remarked of TWM should be reviewed :) > > Or you can Use twm without keymappings and I'll have no more feedback :( > TWM without Keymapping is not really interesting. I will produce new versions of TWM. Laurent > > >> >> thanks! >> > > Thank you :) > > Guille >

Oct. 16, 2011

Re: [Pharo-project] TWM doesn't work without keymappins and keymappings doesn't work

by Guillermo Polito

On Sat, Oct 15, 2011 at 9:47 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi guys. I was trying to use TWM in Pharo 1.3 release. TWM brings with > keymappings, which breaks the shortcuts of my image. The main problem here is that it's not integrated with current tools (i.e. OB). If you just load Keymapping you will have an image where: - lots of shortcuts are hardcoded - some shortcuts like OB's are handled with it's own and specific way/framework Having keymapping living with those, introduces a third way of handling shortcuts (yeap, it's not good enough, but It's not easy to remove all the old code in a row ). So, the following problems happens: - first of all, there are shortcuts collisions. If a morph handles *cmd + a * and its owner handles *cmd + a, cmd + b*, the owner morph will never handle the shortcut because it was handled by it's child first. - second. It's hard to keep track and find every hardcoded shortcut :). And furthermore, this leads in the fact that I cannot easily analyse shortcuts collisions between keymapping and hardcoded shortcuts. So, how does Keymapping live with that by now? 1) a keyEvent reaches a morph 2) the morph delegates the handling in keymapping (bubbling until the world instance). 3) if keymapping does not handle the shortcut, It is delegated to the old-hardcoded shortcuts (so the original behavior is still there yet) All this is just to understand what is happening and where the errors come from :P For example, after installing keymappings I cannot close windows anymore > with cmd + w or I cannot run tests from the browser using cmd + t. So far, I've found those two collisions in keymapping 1.9 and one more in keymapping+TWM: 1) Cmd+w was defined for TextEditor for delete backword. Esteban already complained about this, so I've changed it in 2.0 for *Cmd + Backspace* This shortcut was taken from SimpleEditor, in *#initializeCmdKeyShortcuts*. I don't know if it should be there or not. 2) Cmd+t from omnibrowser was colliding with some global shortcuts I defined in the initial versions of keymapping to play opening a test runner, a browser, a monticello browser. I've fixed it removing the global shortcuts by now (because I'm not conviced the key combinations are nice). 3) When loading TWM + Keymapping, I realized the *cmd+w* was not working again. Wandering, I found that the TWM shortcuts were defined for a lot of morphs, in this way, causing a little of trouble: {PasteUpMorph. SystemWindow. SmalltalkEditor. TextEditor. PluggableTextMorph} do: [:aClass| aBuilder attachShortcutCategory: self shortcutCategory to: aClass. ]. But replacing it by aBuilder attachShortcutCategory: self shortcutCategory to: PasteUpMorph. should be working the same way :/. Laurent, did you have any problems when not attaching the categories in this way?. Also: TWM by default has a lot of *(cmd+w, ...)* mappings colliding with the window *cmd+w* shortcut. So the window shortcut or the TWM ones are to be sacrificed :P. So i installed TWM without keybinding but now I cannot open the settings > window because keymappings is not load. > > Any solution? (install TWM without keymappings or fixing keymappings) > I've done some fixes and improvements to keymapping, and I've created a 2.0 version where: - the collisions below are fixed - keymaps can be configured per morph instance too (not only per class, as the former version) - some little improvements and code cleaning But those things I remarked of TWM should be reviewed :) Or you can Use twm without keymappings and I'll have no more feedback :( > > thanks! > Thank you :) Guille

Oct. 16, 2011

Re: [Pharo-project] Native Windows

by Eliot Miranda

On Fri, Oct 14, 2011 at 9:19 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > What are the current options/future-possibilities? > > I was playing with Fffenestri's DisplayHostWindow, which kind of works in > 1.3. What ever happened to that project? What is the status of Mars? Are > there any other avenues? > back-porting Vassili Bykov's native window implementation for Newspeak (which runs above a slightly-modified Squeak VM, modified to support Newspeak bytecodes). > Thanks. > Sean > > -- > View this message in context: > http://forum.world.st/Native-Windows-tp3905413p3905413.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- best, Eliot

Oct. 16, 2011

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

by Tudor Girba

Hi, Btw, you can download a ready-made image with the GlamorousToolkit from: http://ci.moosetechnology.org/job/glamorous-toolkit-latest-dev/lastSuccessf… Cheers, Doru On 15 Oct 2011, at 23:32, Tudor Girba wrote: > Hi, > > On 15 Oct 2011, at 23:13, StÃ©phane Ducasse wrote: > >> >> 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. > > Actually it is not broken. Something else is broken by loading an older version somewhere in the Moose configuration. I did not have time yet. > >>>> 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. > > I know how they work. I was actually referring to the actual code :). It is such a big mess to deal with the explosion of combinations. > > Doru > > >>> 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." >>> >>> >>> >>> >>> >> >> > > -- > www.tudorgirba.com > > "One cannot do more than one can do." > > > -- www.tudorgirba.com "Obvious things are difficult to teach."

Oct. 15, 2011

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

by Tudor Girba

Hi, On 15 Oct 2011, at 23:13, StÃ©phane Ducasse wrote: > > 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. Actually it is not broken. Something else is broken by loading an older version somewhere in the Moose configuration. I did not have time yet. >>> 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. I know how they work. I was actually referring to the actual code :). It is such a big mess to deal with the explosion of combinations. Doru >> 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." >> >> >> >> >> > > -- www.tudorgirba.com "One cannot do more than one can do."

Oct. 15, 2011