On Feb 24, 2012, at 7:02 PM, S Krish wrote:
> I love Pharo's ability to mould/ twist in spare time something that is
> imminently usable..
>
> Just playing around over an hour plus, I find this tree view grouping
> more convinient than current browsers in giving a coherent view that
> easily extends:
>
> All editable code text morphs, spreading over to mutliple worlds one
> can traverse too if needed. or appears on tab anyways for each group.
>
> a) Package, Class, Category , Hierarchy levels.
>
> b) Senders, implementors ..
>
> c) Arbitrary groups of methods if one desires to..
>
> Can also include some class definition info bubble/ reduce noise
> through some more optimization to make it optimized
>
> ... we can have a little customizations too to get a good grip of the
> whole as well as the part.
>
> But I agree, Gaucho / Code Bubbles are nice, but I am afraid fo
> fragmented view it will still represented. May be each will have
> little twist of his predilictions and cannot be highly generalized.
>
>
> On 2/24/12, Igor Stasenko <
siguctua@gmail.com> wrote:
>> On 24 February 2012 00:18, Matias Garcia Isaia <
mgarciaisaia@gmail.com>
>> wrote:
>>> On Thu, Feb 23, 2012 at 5:08 PM, Mariano Martinez Peck
>>> <
marianopeck@gmail.com> wrote:
>>>> Nooo!!! he comes from Java!! he starts with index 0. Kill him!!! �;)
>>>
>>> Ooops... Time to get a new identity :)
>>>
>>>
>>> On 23 February 2012 19:47, St�phane Ducasse <
stephane.ducasse@inria.fr>
>>> wrote:
>>>> Sure we know.
>>>> And we also know that it requires effort and lot of people are talking.
>>>
>>> I know there's a loooong way to see what CodeBubbles can do, and that
>>> requires to do a big effort, but imagined that some kind of
>>> alternative - I'm not sure that CB is **exactly** what I want (sure
>>> Java-ers want to see **something more** than just a file pimped with
>>> colours, but Smalltalk **allready has** much more than a text file -
>>> have real code) �- could be very less effort-consuming. Making the
>>> current browser (Nautilus? - newbie here :) ) pop a new
>>> �window?�morph? showing a method instead of updating a single pane
>>> (the current one showing method's source) don't seems to be so "far"
>>> away to me.
>>>
>>> Of course that's my point of view, based on what I imagine that could
>>> be. I should spend some time to see how it is implemented, and to see
>>> if it really is that simple, but anyway trust you if you say is a huge
>>> effort...
>>>
>>
>> Well, popping out a new morph every time you clicking around is easy part.
>> The hard part is to make this stuff really consistent and easy to use
>> for navigation and development.
>> It requires far more serious work than just spending 2 hours
>> implementing "bubbling" behavior.
>>
>>>
>>> Cheers :)
>>>
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>>