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

Michael Roberts mike at mjr104.co.uk
Wed Apr 6 12:54:54 CEST 2011


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 at 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 at 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
>>> 
>>> 
>>> 
>> 
> 
> 



More information about the Pharo-project mailing list