Carlos Sanchez wrote: > I think you are going too far for the start, is good to have the use > cases and the overall idea, but as soon as you get to the > implementation you will find things that you didn't thought about > before. > Certainly - there will be minor tweaks and changes. I'm not doing a full design up front, just enough of the architecture and public interfaces to be confident that all of the use cases are possible to implement, and also to figure out what (if any) core Piotr and I share. Incidentally, comparing two graphs and being able to persist (load and save) have driven my design more than anything else, and my plans were different before I considered those. > About the UI as long as you have the global idea of how it should work > then when you start with it you'll be able to refine and improve it. > It really shouldn't be a standalone application but something that can > be reused in an IDE, applet, ... Make sure you use a standard format I'm planning both a full application and an applet. Both will control a core graph display "widget" inside a JFrame. Is there a particular container class or are there other design restrictions that you have in mind?
> for the data so it can be reused easily, for instance I thing Prefuse > uses the GraphML format. I'd start with the base functionality as > first milestone (no interactive UI) and when that's finished think > about the next steps Good idea - Prefuse does have a builtin reader and writer for GraphML, and it would seem that they set all of the custom properties in the Node objects, so this should be quite possible for the XML sources and sinks. > > On 5/19/07, Peter Kolbus <[EMAIL PROTECTED]> wrote: >> As a Google Summer of Code participant, this summer I'll be working on a >> dependency graphing plugin, with Carlos as mentor. See >> http://docs.codehaus.org/display/MAVEN/Dependency+Graphing for >> background. >> >> What follows is my design so far - my understanding of the use cases, an >> overview of the UI elements, and the beginnings of the class design. >> >> Questions: >> * Is the list of use cases complete - is there anything that should be >> added or removed? > > use cases look right to me > >> * Does the UI seem appropriate for the tasks? > > see my comments at the begining. > >> * (for Piotr) Should this be integrated with your work on static diagram >> generation? If so, how well do my plans match up with yours? > > definitely, you both have to work together and with the rest of the > people in the project, you can split the functionality as you wish, > but the core libraries for the same functionality must be shared. > >> >> I'll put this on the wiki once I get some sleep. >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
