Re: Nautilus Package Tree

> I think the tree nodes should be based on name-matching and not only per-package
I should've appended: "as a compromise for the time being"...

In 4.0, imagine this killer combination:
- Declare high-level logical categories a la AltBrowser (e.g. UI). This really nails the 7+/-2 sweet spot

- For external projects, query the Metacello configurations to find out exactly what packages belong to which project and group accordingly; they could also declare AltBrowser categories

But until then, I think this is already an improvement:

The screenshot is of two overlapping Nautilus browsers. The one on the left is the current implementation. The one on the right adds top-level categories. The key thing to notice is the scroll bar:
        almost 10 pages to deal with currently  vs. 3-4 with top level categories.
Notice also that the icons make it clear what is an actual package.

The other important thing to remember is that power users are most likely going to use Spotlight or the filter bar. This is really more for exploration and education.

Cheers,
Sean

Screen Shot 2014-01-23 at 9.00.40 PM.png (246K) <http://forum.world.st/attachment/4738896/0/Screen%20Shot%202014-01-23%20at%209.00.40%20PM.png>
Screen Shot 2014-01-23 at 8.50.28 PM.png (200K) <http://forum.world.st/attachment/4738896/1/Screen%20Shot%202014-01-23%20at%208.50.28%20PM.png>

Sean,

I find this very interesting.

Le 24/01/2014 03:11, Sean DeNigris a écrit :
Querying the metacello configuration is a great idea... Then, when
loading a package, I could refer to a configuration and a group as a way
to classify them?

AltBrowser is currently not very good at loading a large set of packages
(for example, seaside) and recreate higher-level categories on the fly.
The code to move from:
        |
        - Platform-Core
to :
        |
        - Platform
                |
                + Core
                + Tests
(i.e. creation of a higher level Platform category node) upon loading or
creation of Platform-Tests can be a bit tricky, especially when
computing the level of tree refreshing needed.

You gave me another idea: in AltBrowser, there is an API for filtering
the tree contents based on the environment (i.e. scoped browsing, if a
tree node model is not in the environment, it isn't displayed in the
tree). Now I could add more categories (based on the configurations
loaded, for example), and, if empty, they would not appear in the tree.
However, adding packages would put them in the right place.

Cool. Lots of things to try :)

Thanks,

Thierry

--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Hi Sean,

I got a simple version of your configuration querying idea working.

Regards,

Thierry

Le 24/01/2014 03:11, Sean DeNigris a écrit :
>  > I think the tree nodes should be based on name-matching and not only
> per-package
> I should've appended: "as a compromise for the time being"...
>
> In 4.0, imagine this killer combination:
> - Declare high-level logical categories a la AltBrowser (e.g. UI). This
> really nails the 7+/-2 sweet spot
> - For external projects, query the Metacello configurations to find out
> exactly what packages belong to which project and group accordingly;

--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Le 03/04/2014 01:03, Igor Stasenko a écrit :
> cool
> +1
>
> but that means we need a resident configs in image, which IMO is a plus.
> right now we don't.

You can cope with a pre-existing classification for stuff already in the
image, and configs for the additional stuff. Works. A touch is the
ability to customize and save your classification.

It would be very nice to see it working from one of the unloaded images
(with configs to reload all the additional stuff).

Thierry
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Igor Stasenko wrote

cool

Yes, very!