From: Ludovic C. <lud...@ho...> - 2003-07-02 17:30:25
|
Christian Heller wrote: >Scope: >- It seems to be very quiet in your mailing list. Did you all give up >or continue to contribute to the Free Software Community? >- Did you encounter design problems in Scope? If yes, then which? >What can we all learn from it? >- If the design turned out to be incomplete: What should be changed? >- If the project has stopped: Did you try to find a similar project to >bring in your knowledge and continue your work? > > The mailing list is quiet for now but the development is active. In fact we are now working on a major 2.0 release with a lot of refactoring in the core classes. Yes, there were design problems in Scope 1.0 ;-( First, the public API was starting to grow a lot after i tried to add validation and security in the framework. Then, to add this functionality, i had to mess up a lot in the internals of Scope, because there was no plugable design. What i have learnt from this is: - to build a framework, think about the user: try to hide as much complexity from him, and put in the public API only what he needs to actually use, and put the classes used internally in a separate framework-impl.jar - before adding new functionality, think about your object model, and redesign it if necessary to have a plugable architecture in the areas where you want to add the functionality - use the XP best practices: write only the code that you need right now, write the unit tests before writing the classes (or at the same time), refactor early and often, write stories to define clearly what to do next. and i din't find a project like scope that provides a MVC framework for Swing applications (except the framework in ResMedicinae that forked from Scope 1.0). Ludovic Claude |