Le 24/04/2015 12:21, [email protected] a écrit :


On Fri, Apr 24, 2015 at 10:48 AM, Thierry Goubier
<[email protected] <mailto:[email protected]>> wrote:

    Le 24/04/2015 10:11, [email protected] <mailto:[email protected]>
    a écrit :



        On Fri, Apr 24, 2015 at 8:38 AM, Esteban Lorenzano
        <[email protected] <mailto:[email protected]>
        <mailto:[email protected] <mailto:[email protected]>>> wrote:

             I disagree… DarkTheme is just for certain tastes, while
        regular one,
             while probably dated, is more “standard”.
             Also, DarkTheme is not ready. yeah, yeah… it works and
        works fine
             most of the time… but not *all* the time (take for example find
             string dialog… I never found the time to fix it, and nobody
             complained so… :P). Finally. we need to adopt SVG icons (in
        my TODO
             list since a couple of months, I will deliver soon, I hope),
             otherwise they do not look good (this is a problem eclipse
        itself
             had it… we are just inheriting it :) )

             But a good question would be: How can we push forward our UI,
             besides using a darker or clearer theme?
             I would like to hear some opinions here :)



        I'd like to have some solution for that "windows popping up
        everywhere"
        thing. AltBrowser has some good ideas.

        In fact I'd like to have AltBrowser and Nautilus together (as in
        additional entries in the "Browse", "Browse Scoped", ..."Alt
        Browse",
        "Alt Browse Scoped")

        Also, having a way to see a class with all the methods in a long
        pane.
        Yeah, Smalltalk is all about short methods but it is hard to explain
        things to people when looking at a ravioli at a time.


    Like the Newspeak browser?


Don't know about that one.

http://bracha.org/hopscotch-wasdett.pdf

Look for the IDE description (i.e. Figure 1). A web browser metaphor, where you can open all elements and edit in place; not that different from what it could be in Self.

I believe it's not as efficient in practice as it could be, for editing code. But for overall viewing, could be very effective.

I toyed with multiple selection in the AltBrowser (i.e. opening multiple edit panes on the right) but never went that way. Maybe merging both could be an idea: Newspeak browser + tree navigation on the left :)



        Navigating hierarchies should be made easier (switching on the
        "hier/flat" button gets tiring).


    This one is difficult to solve.


Maybe a popup with the hierarchy would do (with some keybinding, like C-h)

In AltBrowser, I'm searching around how to do that, so what I have is:

- menu navigation commands (super, first subclass, sibling) with a memory (back), but I'm not satisfied because often what I want is see both at the same time. Back really works well, but maybe with a button on the toolbar (or linked to the back and forward keys on my Chromebook? Not used to that keyboard layout yet)

- What I use most often is: right click on superclass name in the description, choose browse to open a browser on the superclass... Not too bad for what I want. Works for any class name everywhere, which is very convenient.

- I also have a hierarchy command which opens a browser scoped on the hierarchy. For certain types of searches, it can be very convenient (i.e. all callers of printString in the hierarchy...)

But, still: three ways to do the same thing? Clearly could be better.

Thierry


        I need to see how spotter will make this easier anyway. Still
        not using
        it, need to bring all my code to 4.0 before.


    I'm a bit: Spotter is an external tool to the browser. If my
    searches are well answered in the browser, I'll prefer to avoid
    switching back and forth between two GUIs.

    It would be nice to have a closer integration between Browser and
    Spotter. When looking at methods, Spotter and AltBrowser show a very
    similar GUI: context tree on the left (i.e. where is the element in
    the overall scheme), element/work pane on the right. Like all the
    tree-based browsers have done in the past, really (the Star browser,
    the Whisker browser).

    Which makes Spotter a kind of reimplementation of a tree browser
    with object-driven representations on the right... was that a
    project by Alain Plantec in the Squeak days?

    Thierry

        Phil










Reply via email to