Is more-than-one-level deep planned?
I love the idea, but I'm not finding the current implementation particularly
useful.
I want to reiterate that I think the tree nodes should be based on
name-matching and not only per-package. For example:
> MyProject
>X Core
- Support
- Announcements
X Tests
X Platform
The icons (simulated by X's above) serve to distinguish what is a package
and what is not.
Especially for new users who will be overwhelmed, at the top level of the
system, when one is not working on MyProject, seeing a single MyProject node
is the right thing:
#1:
> Keymapping
> MyProject
> NativeBoost
instead of the current (even when collapsed):
#2:
> Keymapping-Core
Keymapping-KeyCombinations
Keymapping-Pragmas
Keymapping-Settings
Keymapping-Tests
Keymapping-Tools-Spec
> MyProject-Core
> MyProject-Tests
MyProject-Platform
> NativeBoost-Core
> NativeBoost-Examples
> NativeBoost-Mac
> NativeBoost-Pools
> NativeBoost-Tests
> NativeBoost-Unix
> NativeBoost-Win32
#1 captures the feel of the system from a birds eye view, but even with only
3 high-level concept spaces, #2 is already double human RAM.
The fact that there is a MyProject-Tests package, which is only separate so
that it can be unload in production, and that there is a MyProject-Platform
that needs to be a separate package so that we can support both Squeak and
Pharo, is irrelevant and distracting from that point of view.
With the current tree-root per package, there are over 250 top-level nodes.
This has not made understanding and navigating the system any more sane.
Maybe the use of pattern matching as make-believe packages for so long has
made us wary of the technique, but let's use each tool where it's
appropriate.
-----
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Nautilus-Package-Tree-tp4738887.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
