Jesse Ross wrote: > I've been trying to work on some new mockups, and wanted to get some > opinions before I show them. I'm running into an issue regarding > tagging and presenting objects. Let's assume that we have a flat > object space, and that we can apply tags to objects to be able to > automatically sort them into groups. Let's also assume that we have > projects, and projects can include objects of different types and > with different tags. Thus, while tags and projects can both be used > for grouping and organizing objects, tags create system-generated > views (the system adds the contents), and projects are user-generated > views (the user adds the contents). > > Because tags and projects both occupy a similar role (as views on > collections of objects), should a user be able to tag a project? If > so, can I, as a user, have both an object tagged 'design' and a > project tagged 'design'? And if I do a search on 'design', do I get > both the objects and projects in my results list? Additionally, what > should this results list look like? Should it be, in essence, a new > project (meaning that all tag groups are really just system-generated > projects)? If it is represented in a similar fashion as a project, we > would end up with a project within a project... something we don't want.
The results would be shown in a "sieve panel" I think. It's supposed to be a refined search. i.e. You keep honing down options until you find what you want. You would then add the object to your project, or just open the object. The sieve should act as a system wide "open panel". This is one of the bright spots of the object centric approach. You open the object THEN choose what service to browse/edit it with, and can change the service midway. In an application centric environment you must close one application and open the object in another in order to brows/edit it in a different way. Also my opinion is that projects should be a collection of links to actual objects, NOT a list of objects generated from tags UNLESS the user tells it to (i.e. "smart project" or "sieve project"). The user can decide whether to directly manipulate the object or just the link with the use of two sets of commands: create/delete for the object and add/remove for the project's reference. > Any feedback would be much appreciated. I can handle that. :) Just my humble totally unbiased opinion. Isaiah Beerbower _______________________________________________ Etoile-discuss mailing list [EMAIL PROTECTED] https://mail.gna.org/listinfo/etoile-discuss
