11 Jun
2014
11 Jun
'14
4:16 p.m.
Exactly this is where we are going. The current solution already offers a
rudimentary browser just to be able to explore the possibilities, but we
want a cooler and simpler to use class browser dedicated to an object.
Given that you already worked in this area, would you be interested in
joining this effort?
Cheers,
Doru
On Tue, Jun 10, 2014 at 2:31 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr>
wrote:
Unless you make the class browser simple and compact enough to be part of
the inspector or the debugger (i.e. really blurring the lines between the
three).
I wonder what it would mean not having to go through the inspector... Or
replacing the code pane in the debugger by the tree + code pane of
AltBrowser.
Oh, I think I'd like that last one :)
Thierry
------------------------------
*De :* moose-dev-bounces(a)iam.unibe.ch [moose-dev-bounces(a)iam.unibe.ch] de
la part de Tudor Girba [tudor(a)tudorgirba.com]
*Envoyé :* mardi 10 juin 2014 10:18
*À :* Moose-related development
*Objet :* [Moose-dev] Re: Cool feature of GTInspector
Hi,
Indeed, a good end goal would be to have the inspector and the debugger
capturing some 60-70% of programming. A class browser is good for
organizing code, but less good for live programming.
Cheers,
Doru
On Sun, Jun 8, 2014 at 2:00 AM, [CH] Aliaksei Syrel <alex(a)syrel.ch> wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
Thank you all for very positive comments :) New pager is very interesting
idea, that was a big pleasure to implement. In short time with the help of
Andrei and Tudor I will try to make another interesting GTInspector feature
real! It's the idea of having a possibility to re-open pane tree while
inspecting a list of similar objects. So if you made a long way deep inside
the object (lots of panes) and start inspecting another object of the same
class as before, inspector will try to redo your previous job of digging
deep inside, wich can heavily save someone's time. And after having such
mechanism it could theoretically be possible to generate Smalltalk code,
based on that way. So maybe someday we can program directly in inspector
switching panes?...
Cheers,
Alex
On Jun 7, 2014 6:57 PM, "Tudor Girba" <tudor(a)tudorgirba.com> wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Cool, isn't it :)
As I mentioned when we introduced the GLMPager, this is a conceptual
improvement over the Miller's columns. But, now that we are at it, did you
try mousing over a bullet that represents a pane that is not visible (you
need the latest version for this) :).
The implementation credits go to the Alex (Aliaksei Syrel) and Andrei.
Doru
On Sat, Jun 7, 2014 at 3:24 AM, Ben Coman <btc(a)openinworld.com> wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Alexandre Bergel wrote:
> Hi!
>
> Serge shown us today how to have three panes in a GTInspector. This
> made my day!
> https://vimeo.com/97507411
>
> Cheers,
> Alexandre
>
>
That was a surprise it was so simple! Very intuitive. Very cool....
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev