|
From: Dieter W. <di...@wi...> - 2003-07-07 19:14:32
|
To all, I think it is time to do something about the GUI development, so that we make best use of our most limited resource time. My proposal is to: 1. remove the GUI code from the library codebase 2. make the GUI implementation an independent module 3. target a standalone "Addressbook" implementation starting from the current codebase; this could be: a) a demonstration app (proof-of-concept?) b) a test app for the library 4. derive/work on reusable "components" and see whether we can provide another module with GUI-Components, the App from 3 could be still a testbed also for this components. 5. Put somebody (Tony?) in charge of the GUI App module This proposal is based on following arguments: 1. From what I have heard so far, I doubt that we will be really able to create a useful one-for-all addressbook "component": a) because many projects want to impose their own look and feel b) because many projects want to manage their set of properties, probably even derived models 2. The separation will help to keep the codebases maintainable: a) because I foresee growth (calendar, task, notes, bookmarks ?) b) because we can act, work and release rather independently Comments and suggestions are welcome. Regards, Dieter |