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

Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy

by Tudor Girba

It works. Toon, am I wrong? Cheers, Doru On 6 Apr 2011, at 13:18, StÃ©phane Ducasse wrote: > > On Apr 6, 2011, at 1:08 PM, Tudor Girba wrote: > >> Hi, >> >> Indeed, it would be great to have a Debugger model. Toon produced one in the context of the Glamorous Toolkit. Perhaps it would be good if we merged it in the Core. > > As soon as it works I want that in the core :) > imagine a model not mixed with UI concerned :) > Stef > >> >> Cheers, >> Doru >> >> >> On 6 Apr 2011, at 12:54, Michael Roberts wrote: >> >>> Ok. And is the idea to build a new core debugger in this effort? I wanted to check we would only build 1 debugger model; and to know where it is. (I only see one in glamourst source). >>> >>> Thanks >>> Mike >>> >>> On 6 Apr 2011, at 07:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>> It is not. >>>> The idea is to have a default browser and set of tools that we can use >>>> in bare core image and that are not based on toolBuilder or stringHolder. >>>> After if Glamour produces a nice IDE then we can load it and use it. >>>> In addition benjamin is fixing a lot of problems in default widgets like multiple selection, >>>> hilighting.... >>>> >>>> Stef >>>> >>>>> Hi, how does it relate to glamourost? >>>>> >>>>> thanks, >>>>> Mike >>>>> >>>>> On Tue, Apr 5, 2011 at 7:57 PM, StÃ©phane Ducasse >>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>> >>>>>> On Apr 5, 2011, at 5:31 PM, Alexandre Bergel wrote: >>>>>> >>>>>>> Hi Guys, >>>>>>> >>>>>>> Maybe I missed part of the discussion, but what is Nautilus? >>>>>> >>>>>> A new browser :) >>>>>> Supporting >>>>>> - groups >>>>>> - package >>>>>> - declarative menus >>>>>> - environment selection >>>>>> - scoped actions >>>>>> - soon refactoring >>>>>> >>>>>> but right now a bit too slow because of the HUGGGGGGEEEEEE trees build by TreeMorphTreeMorph >>>>>> >>>>>>> Squeaksource simply says "A new browser" >>>>>>> >>>>>>> Cheers, >>>>>>> Alexandre >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> -- >> www.tudorgirba.com >> >> "Being happy is a matter of choice." >> >> >> >> > > -- www.tudorgirba.com "We are all great at making mistakes."

April 6, 2011

Re: [Pharo-project] Issue 3966 in pharo: String>>lines misses tests

by pharo＠googlecode.com

Comment #2 on issue 3966 by stephane...(a)gmail.com: String>>lines misses tests http://code.google.com/p/pharo/issues/detail?id=3966 tx!

April 6, 2011

Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy

by StÃ©phane Ducasse

On Apr 5, 2011, at 2:32 PM, Fernando Olivero wrote: > Hi Ben, i was thinking about the discussion of the menus: > > Since you are using menu pragma builder, and have explicit views for > each tool, then the CodeHolder hierarchy is no longer needed. Because > the specialized views get the behavior for answering the actions in > the menus (which currently is spread across the StringHolder > hierarchy). I would say yes but I will let ben replied with more depth if necessary. > So this is the main reason why you simple need a pluggable text model, > for the model of the views. And a pluggable TextModel (or StringHolder > in Pharo) would suffice? Is this correct? > > Thanks, > Fernando >

April 6, 2011

Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy

by Geert Claes

Geert Claes wrote: > > How does one load Nautilus? I tried by adding the nautilus repository and > using the ConfigurationOf on a clean 1.2 OneClick but I get a DNU > readStream? > Mmm, seems to be a network issue because I get the same message for other stuff :( -- View this message in context: http://forum.world.st/abouth-nautilus-and-the-removal-of-CodeHolder-hierarc… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 6, 2011

Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy

by StÃ©phane Ducasse

On Apr 6, 2011, at 1:08 PM, Tudor Girba wrote: > Hi, > > Indeed, it would be great to have a Debugger model. Toon produced one in the context of the Glamorous Toolkit. Perhaps it would be good if we merged it in the Core. As soon as it works I want that in the core :) imagine a model not mixed with UI concerned :) Stef > > Cheers, > Doru > > > On 6 Apr 2011, at 12:54, Michael Roberts wrote: > >> Ok. And is the idea to build a new core debugger in this effort? I wanted to check we would only build 1 debugger model; and to know where it is. (I only see one in glamourst source). >> >> Thanks >> Mike >> >> On 6 Apr 2011, at 07:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> It is not. >>> The idea is to have a default browser and set of tools that we can use >>> in bare core image and that are not based on toolBuilder or stringHolder. >>> After if Glamour produces a nice IDE then we can load it and use it. >>> In addition benjamin is fixing a lot of problems in default widgets like multiple selection, >>> hilighting.... >>> >>> Stef >>> >>>> Hi, how does it relate to glamourost? >>>> >>>> thanks, >>>> Mike >>>> >>>> On Tue, Apr 5, 2011 at 7:57 PM, StÃ©phane Ducasse >>>> <stephane.ducasse(a)inria.fr> wrote: >>>>> >>>>> On Apr 5, 2011, at 5:31 PM, Alexandre Bergel wrote: >>>>> >>>>>> Hi Guys, >>>>>> >>>>>> Maybe I missed part of the discussion, but what is Nautilus? >>>>> >>>>> A new browser :) >>>>> Supporting >>>>> - groups >>>>> - package >>>>> - declarative menus >>>>> - environment selection >>>>> - scoped actions >>>>> - soon refactoring >>>>> >>>>> but right now a bit too slow because of the HUGGGGGGEEEEEE trees build by TreeMorphTreeMorph >>>>> >>>>>> Squeaksource simply says "A new browser" >>>>>> >>>>>> Cheers, >>>>>> Alexandre >>>>> >>>>> >>>>> >>>> >>> >>> >> > > -- > www.tudorgirba.com > > "Being happy is a matter of choice." > > > >

April 6, 2011

Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy

by StÃ©phane Ducasse

On Apr 6, 2011, at 12:54 PM, Michael Roberts wrote: > Ok. And is the idea to build a new core debugger in this effort? I wanted to check we would only build 1 debugger model; and to know where it is. (I only see one in glamourst source). yes we want to join forces with glamour: one model several tools. > > Thanks > Mike > > On 6 Apr 2011, at 07:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> It is not. >> The idea is to have a default browser and set of tools that we can use >> in bare core image and that are not based on toolBuilder or stringHolder. >> After if Glamour produces a nice IDE then we can load it and use it. >> In addition benjamin is fixing a lot of problems in default widgets like multiple selection, >> hilighting.... >> >> Stef >> >>> Hi, how does it relate to glamourost? >>> >>> thanks, >>> Mike >>> >>> On Tue, Apr 5, 2011 at 7:57 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> On Apr 5, 2011, at 5:31 PM, Alexandre Bergel wrote: >>>> >>>>> Hi Guys, >>>>> >>>>> Maybe I missed part of the discussion, but what is Nautilus? >>>> >>>> A new browser :) >>>> Supporting >>>> - groups >>>> - package >>>> - declarative menus >>>> - environment selection >>>> - scoped actions >>>> - soon refactoring >>>> >>>> but right now a bit too slow because of the HUGGGGGGEEEEEE trees build by TreeMorphTreeMorph >>>> >>>>> Squeaksource simply says "A new browser" >>>>> >>>>> Cheers, >>>>> Alexandre >>>> >>>> >>>> >>> >> >> >

April 6, 2011

Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy

by StÃ©phane Ducasse

Because once people are dependent and drug addict then they will spend time fixing it :) No seriously this is mega hyper hyper important that we get - solid scalable listMorph and treeMorph So the best way is to stress it. The second answer is that nautilus is cool and needs tree :) >>>> but right now a bit too slow because of the HUGGGGGGEEEEEE trees build by TreeMorphTreeMorph >>> yes, maybe MorphTreeMorph is not the good tree to use here. >>> why not use a simpler one ? >> or try with LazyMorphTreeMorph even it should be improved. (it should be changed to build the list in background). > > That would be super cool :) > > Doru > > >>> Alain >>> >>>>> Squeaksource simply says "A new browser" >>>>> >>>>> Cheers, >>>>> Alexandre >>>> >>>> >>> >>> >>> >> >> > > -- > www.tudorgirba.com > > "Presenting is storytelling." > >

April 6, 2011

Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph

by StÃ©phane Ducasse

>> > yes, it is a workaround. > take the current implementation as a functional requirement. Good point! Yes igor we want the same, simpler and faster :D > MorphTreeMorph is cool because it can be used for lists, trees and tables, > but I agree, it is badly implemented. > So I fully agree with you, the positioning logic should placed be in the layout managing >> >> I think that MorphTreeMorph can't be efficient for very big lists >> because each row may contain a lot of morphs. >> Yes, but you can use morphs only for those items which are shown on >> screen, while for those which outside >> you don't need to use morphs at all. >> >> The idea is that You could keep in memory all morphs which >> representing the tree, but don't iterate over them >> every time. Just add to submorphs only those which currently visible. > this is the idea behind LazyMorphTreeMorph, Morphs added only when they become visible. >> What could be done is to simplify things even more, so creating a list >> item will be cheaper and skip many initialization, >> unless it is necessary. > yes, thanks a lot Igor! > Cheers > Alain > >>> Cheers >>> Alain >> > >

April 6, 2011

Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy

by Tudor Girba

Hi, Indeed, it would be great to have a Debugger model. Toon produced one in the context of the Glamorous Toolkit. Perhaps it would be good if we merged it in the Core. Cheers, Doru On 6 Apr 2011, at 12:54, Michael Roberts wrote: > Ok. And is the idea to build a new core debugger in this effort? I wanted to check we would only build 1 debugger model; and to know where it is. (I only see one in glamourst source). > > Thanks > Mike > > On 6 Apr 2011, at 07:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> It is not. >> The idea is to have a default browser and set of tools that we can use >> in bare core image and that are not based on toolBuilder or stringHolder. >> After if Glamour produces a nice IDE then we can load it and use it. >> In addition benjamin is fixing a lot of problems in default widgets like multiple selection, >> hilighting.... >> >> Stef >> >>> Hi, how does it relate to glamourost? >>> >>> thanks, >>> Mike >>> >>> On Tue, Apr 5, 2011 at 7:57 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> On Apr 5, 2011, at 5:31 PM, Alexandre Bergel wrote: >>>> >>>>> Hi Guys, >>>>> >>>>> Maybe I missed part of the discussion, but what is Nautilus? >>>> >>>> A new browser :) >>>> Supporting >>>> - groups >>>> - package >>>> - declarative menus >>>> - environment selection >>>> - scoped actions >>>> - soon refactoring >>>> >>>> but right now a bit too slow because of the HUGGGGGGEEEEEE trees build by TreeMorphTreeMorph >>>> >>>>> Squeaksource simply says "A new browser" >>>>> >>>>> Cheers, >>>>> Alexandre >>>> >>>> >>>> >>> >> >> > -- www.tudorgirba.com "Being happy is a matter of choice."

April 6, 2011

Re: [Pharo-project] SmalltalkHub going beta in a week

by Tudor Girba

Phenomenal stuff :). I cannot wait to use it. Will there be a possibility to migrate the existing squeaksource there? Cheers, Doru On 6 Apr 2011, at 13:00, Nicolas Petton wrote: > Hi, > > We've been working on a new code repository & project management > application for Smalltalk with ESUG named SmalltalkHub. > > If everything goes fine, the app should be in public beta in a week. > The source code of SmalltalkHub will be available at the same moment > (the project itself is hosted by SmalltalkHub). > > Here's a screenshot in the meantime. > http://nicolas-petton.fr/2011/04/06/smalltalkhub-beta-in-a-week.html > > Cheers, > Nicolas > -- > Nicolas Petton > http://www.nicolas-petton.fr > > -- www.tudorgirba.com "Being happy is a matter of choice."

April 6, 2011