> On 24 May 2016, at 04:00, Sean P. DeNigris <[email protected]> wrote: > > Also, not new to Pharo 5.0, but thinking as a new user... Nautilus presents > the system as an overwhelming mess of top level packages. I guess this is > because we're showing packages, which are a dependency/SCM artifact, instead > of capturing/representing logical domain relations. There are so many > packages that start with e.g. System. It is not relevant to the user that > they are packaged separately, unless one is hacking that library. These > should all be collapsed under a top-level System node.
I do agree with this, but we need to find a way to do it… But we need to think how to do it. My main idea is to offer “views” (always configurable in settings so power users can take what they want), something like: - using manifests, we can add tagging of packages. For instance, Nautilus can be tagged #browser, Monticelo #vcs, #versionControl, etc… so we can offer searchs… and even offer a nautlus a view “by tag”… - another view can be “hide system packages”: user does not need to directly see many of those packages, so we could filter them (I would also use a property in manifests for this) Another thing, not related to views but possible and easy to implement (but not to complete, of course) I want to add is the possibility of package comments (also using the manifest) so we can offer a high level view (often a class does not explains what a package is, like Renraku… that can be a nice (?, no idea what it does means) fantasy name, but it does not offer any explanation of what it is for). I think this two ideas can make the environment a lot better… what do you think? Esteban
