Will hive this off to a new package.. rather than tacking it to the PackageTreeExample.

My primary prototype involved a SimpleMorphicView.. which I hived off.. but on my image this combined with TabbedPane is a great time saver in navigations..

This is particularly helpful in keyboard navigation�down/ right��key usage flipping through methods.. �down the whole tree. Also�have a crude / workable find class/ selector too that can open the relevant tree node..�

Sketching out some regular use cases I have: like
* �group methods in a right side multi text tree pane view kind of a two pane view..
* �class browser that opens two paned: instance and class side by side.. , implementors/ senders / references in similar views.
* drop in the variables/ class definition also in to this tree traversal to make it bit more complete..
* Create / Define class.. with a simple dialog.. akin to VW..
* Hook up minimal refectoring: move/ copy methods .. accessors..�
* Normal browseIt continues to work.. as an when required for System/ OB Browser.. or in future the Nautilus..

Inline expand text view/ other extended button actions, will help make it more than adequate. Just good enough for what I see is my personal predilictions.. Of

*********************
if we want specific..packages to open:

MorphicViewNewPackageBrowser new packageNames: { 'Morphic' } ; open

On Sun, Feb 26, 2012 at 10:22 PM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
thanks :)

Stef

On Feb 26, 2012, at 5:08 PM, S Krish wrote:

> Hopefully this should be good to play on a Pharo 1.3 image.
>
> It does not work, as expected, in Pharo 1.4 image.. as
>
> MorphTreeColumn>>
> � rowMorphFor: aNode
>
> "the rowMorphGetSelector defaults to nil in Pharo 1.3.. !. but is a block Pharo 1.4.. can hack this to see the same effect.."
>
> I have a hacked.. version for Pharo 1.4 .. but let me figure out the wirings of MorphTreeColumn better to share it for 1.4
>
>
> On Sat, Feb 25, 2012 at 9:59 PM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
> can you send the code that we play with it because I would like to learn how you do that.
>
> Stef
>
> 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.
> >>
> >>
> > <Pharo_CodeBrowser01.JPG>
>
>
>
> <PackageTree-Browser-Experiment-skrish.5.mcz>