Website:http://tagsea.sourceforge.net
Update Site: http://tagsea.sourceforge.net/update
Like many other Eclipse projects, TagSEA is both an extensible framework as well as a set of exemplary tools. It provides basic tagging infrastructure for Eclipse, as well as concrete implementations for Java Tagging and Resource Tagging. TagSEA uses a concept from wayfinding known as waypoints. A waypoint is a particular location you wish to mark. TagSEA allows you to add tags, metadata and a comment to this waypoint.
Why did we do this? Good question :) We hypothesized that through the use of marking locations in code (or XML, or PDE Forms, or Workbench layout, etc...) , and providing mechanisms to return to these locations, developers could more easily navigate to “common” hot-spots or share interesting places with others. What do you think? Of course this is very new and we are just starting out, but we have all sorts of ideas of where tags could be useful:
- EMF generated code that users are likely to customize
- Places in the GEF framework that “should” be extended for normal operation
- Plugin and manifest files
- Mylar tasks
- Images and other resources for future retrieval
- SWT Snippets or other sample code
- JUnit test cases
TagSEA currently supports hierarchical tags, a tag view, waypoint view and tag refactoring. As I mentioned, we have concrete implementations for Java and Resource files (Web URL and breakpoints are on the way). Where should we go next?
We have a long talk planned at EclipseCon (here) and we are currently throwing around the idea of holding a BoF on IDE's and tagging.
4 comments:
Hi,
(sorry for the deleted post earlier - I pressed buttons I shouldn't have.)
this reminds me of an experiment we did a few years ago which we didn't develop too much but it might be related to tagging.
The details are here: http://www.stateofflow.com/projects/12/subtext
The idea is to provide documentation which could be provided contextually. For example, you could provide documentation for an interface which would be presented whenever the developer opened a class that implemented that interface.
Documentation could be provided by a number of different sources and is presented together.
Do you think this is useful in the context of tagging?
Channing
Channing,
This sounds very useful. We have thrown around the idea of mixing Tags and Actions (somewhat like aspects) to allow certain things to happen based on your tags. I think documentation is an excellent example of this.
As I can see on your picture, you 're look like Ian Bull, who I knew few ares ago (20 already), I just wanted to know what you becomes. If you're the one who live 4 butterfield drive Don Mills, I was you're Nany.If you speak french, will be better for me. my mél : isabelle.durupt@club-internet.fr
Post a Comment