I was just reading something about the WindowInfo class in another thread, and it occured to me that I haven't heard anything about code refactoring and improvement of the technical structure that supports NEdit. I am not an NEdit developer, and don't have the time to work on it yet, but it did make me wonder about what efforts are being done to coordinate an effort to ensure that the code-base was clean?
Something that I would expect would be that a particular area of the code would be selected as unfit by some normal coding criteria, and would then be selected to be refactored. This would then be broken up into workable sections which would each be changed and committed at an approximate rate of one section per release. Do the NEdit developers work like this, or do they have any interest in this? Just curious. -- Aaron Hsu <[EMAIL PROTECTED]> | Jabber: [EMAIL PROTECTED] ``Government is the great fiction through which everybody endeavors to live at the expense of everybody else.'' - Frederic Bastiat -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
