I wish the flowpeople (I'm not one), would clean up after themselves... Right now I'm trying to move fpnode into flowparts to make things a bit more orderly. (use "svn mv" to move files around.)
With great respect to the previous refactoring done on my behalf of the Node heirarchy, there are still many problems that need to be examined and refactored. There is a great deal of code in ecnode that should be in Node or, maybe, connector. Kdevolp's show class heirarchy shows what's going on now... For testing purposes, it would be awesome to be able to instantiate abstract itemDocuments and ICNdocuments. Basically, the problem is we have two types of nodes, nodes attached to CNItems and nodes that are floating on connectors. So the heirarchy should be something vaguely like: NODE -> NodeWithItem. Then, separately: AbstractWireJunction Then, inheriting from Node and abstract wire junction: JunctionNode and then inheriting from NodeWithItem and abstract wire junction: PinNode I think this will further improve the ratio of variables that exist in a given object to those that are actually required to make that object work, and allow code all over the place to be leaner and less buggy. Also, I'm coming across lots and lots of "fail silently" code that I'm taking out to help us further reduce the number of glitches... -- New president: Here we go again... Chemistry.com: A total rip-off. Powers are not rights. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Ktechlab-devel mailing list Ktechlab-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ktechlab-devel
