Hello,
Sean Lamb wrote:
> Tomsrtbt, and leaves the user at the command line. Like the database
> access layer, we need to build in a screen functionality layer that will
> enable the user to plugin modules for whatever screen library is in use,
> be it curses, Qt, Motif or whatever.
I am working on this now. I have made some kind of design,
and I am trying this out with a simple (dummy) application.
The idea is static modules. So you choose your modules at compile time,
so that the main module register the choosen modules with some '#ifdef'
The rest of the code does not need these '#ifdefs' constructions ...
So what are these modules ?
- the GUI (ofcourse)
- import and export modules
- tools modules
- the datamodel itself. (one model can keep all info in memory, the other
retrieves from dbase
what is needed)
> this from scratch. I was hoping to have a prototype over the summer but
> got caught up in my honeydo list ("honey, do this for me...") and a
and I got married ...
> Now, I have a question for the list...
> Are there any listers who are experienced in designing and building the
> two abstraction layers that I've described above?
I am trying to get this v 0.0 application ready as soon as possible.
Kind regards,
Geert
--
----------------------------------------------------------------------
- Geert Vantienen http://chat.sesuadra.org/ -
----------------------------------------------------------------------
_______________________________________________
Genes-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/genes-devel
