2015-08-17 14:34 GMT+02:00 Dimitris Chloupis <kilon.alios@gmail.com>:
yeap AltBrowser indeed does it, nice , time to give it another try:)
The thing I haven't done yet is turn a category of packages in a RB environment, to scope all commands and searches to that. Ah well, there is allways something to do ;) Thierry
On Mon, Aug 17, 2015 at 12:36 AM Thierry Goubier < thierry.goubier@gmail.com> wrote:
Le 16/08/2015 22:48, Dimitris Chloupis a écrit :
One of the things that annoy me is how many Configurations and Baselines pollute the package space that are of little interest to the user. It would be nice to group them and filter them out of Nautilus unless user asks for them.
This is what AltBrowser does. All configurations are in a category named 'Configurations' and all Baselines are in a category named 'Baselines'. Unless you really search for it, you won't see it.
I really like this new approach great work.
It certainly help.
I have played a bit with extracting info from Configurations to classify automagically, but it doesn't work very well.
Thierry
On Sun, Aug 16, 2015 at 7:34 PM stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Le 16/8/15 17:00, Sean P. DeNigris a écrit : > stepharo wrote >> you get a project (group) with all your packages together ready to work ;) > Cool! I feel more and more that the standard "Package" pane is only useful > for... packaging, and when one takes off the dependency management hat and > puts the user hat on (i.e. most of the time), what you really want there is > a logical view of the system. So I see three use cases: > - Logical view of the system - I guess this was the original intention of > Categories, but has been hijacked by Monticello > - By project - which, as you just showed, we have now, yay! > - By package - the least useful, but primary (up til now), view
Indeed. We will see what we get at the end but may be something like
MyProject AnotherProject System LowLevel
And people will not be overwhelmed by hundreds of nice packages. :)
I think that touching package contents under the assumption that the package list is too long in the UI is the wrong way to look at the problem. Packages are unit of deployment and we need Projects - unit of knowledge. And the UI should shows both depending on the view we want to get.
Stef > > > > ----- > Cheers, > Sean > -- > View this message in context:
http://forum.world.st/Projects-are-slowly-getting-to-live-and-tp4843277p4843...
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > >