> Actually my question was about how extensions would communicate with each > other should that be necessary, I used rendering merely as an example.
In general assume extension A depends on operations and properties declared in extension I, e.g. an attribute extension wants that the node displays an attribute icon. For this purpose it could use a public method of the controller of the icon extension IconController#setStateIcon(MindMapNode node, ImageIcon icon). The icon controller itself could be obtained from the ModeController e.g. by ModeController.get(IconController.class) . If you had define another example, I could use it either. >> they essential task of the rendering component is the rendering of the >> effects in the right order, > How are we ensuring that the different extended components do not overlap > each other? Is this automatically taken care of by LayoutManagers? How could differently extended components overlap? I do not understand you. Yes, layout managers are responsible for overlap free node placement. > I just went through the NodeView class. I'm not sure if you'd agree, but > seemed like a good place to start refactoring :) I am not sure if refactoring should START with refactoring of the viewers. I would start with the models. But you are welcome to put your ideas on the table. I am looking forward to know them. Dimitry ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Freemind-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freemind-developer
