Idea: User-Installed Nautilus Package Group

I've often wanted to know which packages I had personally installed in an image (i.e. non-kernel). Our one-level-deep package nesting makes the full list unnavigable, so how about a Nautlius group where all new packages get included automatically? We could clear it out prior to release et voila!

What do you think?

Le 03/09/2016 à 17:06, Sean P. DeNigris a écrit :
> I've often wanted to know which packages I had personally installed in an
> image (i.e. non-kernel). Our one-level-deep package nesting makes the full
> list unnavigable, so how about a Nautlius group where all new packages get
> included automatically? We could clear it out prior to release et voila!
>
> What do you think?

I have a recent packages category in AltBrowser which works like that.
Limited to the last ten entries, but maybe could be limitless instead.

Another benefit, when you teach newcomers:

- A constant, direct path in the browser to the last package created(*)
or loaded in the image. 3 times out of four, students misread the
package name they are supposed to create, and finding it for them in
Nautilus is a pain.

Thierry

(*) The old system browser used to have such a constant path: last
package in the list of packages. This feature is no more in Nautilus. I
reintroduced it in AltBrowser.

> On 3 Sep 2016, at 17:06, Sean P. DeNigris <[hidden email]> wrote:
>
> I've often wanted to know which packages I had personally installed in an
> image (i.e. non-kernel). Our one-level-deep package nesting makes the full
> list unnavigable, so how about a Nautlius group where all new packages get
> included automatically? We could clear it out prior to release et voila!
>
> What do you think?

+1

There was a smart group with all recent packages and nobody used them.
So if you want to add a group with the functionality you need go ahead.

What we could do is

     mark all the present packages

     only display a diff after loading.

I would like to have a different group behavior such as only showing the
classes I want to see.

But this is work. First what is really annoying to me is the fact that
when I'm in hierarchy I cannot select a package

to switch to the view package. This is the first thing I want to fix.

Stef

EstebanLM wrote

+1

I will not open an issue because I don't have time to work on it right now and suspect it will languish and be closed (not complaining), so I will add it way down on my personal todo list and I leave opening an issue to anyone actually willing to do the work.