Thanks, I think you have mostly addressed all my queries. The part I am worried about is how tightly things are currently coupled into the Swing library. Although there IS a separation, if we ever think about using some other rendering technique/API, something tells me we will have to work hard. And that is bound to happen sooner or later. (Pls tell me if this is not the case) In fact, since JComponents are quite memory-intensive, this can become a problem very easily with large maps. If a user prefers to keep all his work in one single large map on different branches (as opposed to making new maps out of the larger branches), I have seen Freemind become somewhat hard to handle. It's rendering starts to fail in certain places, certain features no longer work (notably PDF export) etc. This happens at around 4000 visible nodes - a high number for sure, but can easily be reached if someone hits "Expand All" after about a year. So we might actually have to leave JComponent-based rendering sometime soon. I am not suggesting that we do this right now, but we should keep provisions in our designs now so that we can make such changes in a relatively painless way. Just keeping an eye that however we design, removing JComponent dependency should be easy. I do have some ideas now, and I hope to be able to make a rough sketch of necessary plans in a few days time. In the mean time, please suggest if I should change any part of my opinions here.
Reasamp ------------------------------------------------------------------------- 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
