[kplato] RDBMS for Kplato

[Chris Clarke]

On Tuesday 19 June 2001 11:28, Thomas Zander wrote:

> On Tue, Jun 19, 2001 at 02:26:59PM +0300, Jyry Kuukkanen wrote:
> > Wouldn't it make more sense to break this project into three sections:
> >
> > 1) User interface related (web/Local GUI/...)
> > 2) Application functions (create project, allocate resourses etc.)
> > 3) Database connectivity
>
> He, you seem to be a programmer ;)
> That is a standard programming model, where a programmer builds the
> parts seperately so its a lot easier to bugfix and build new front-ends.
>
> The default would be to have it like this
> 1) internal data model. A number of classes that represent the different
>    things (where things are everything from a project to a user to
>     a contractor)
> 2) build saving loading and interactions INTO the data objects. I.e.
>    a project can save itself as an xml-stream. Just a stream, someone
>    else decides what to do with this.
> 3) Build a Gui on top of this, view seperated from logic. Is a programming
>    technique thought around the world today ;)

I'd like to add:

0) Define the general functionality

to this list.  In the discussions to date t has become evident that the 
different disciplines here use different vocabularies and different needs, 
not to mention people's vision of the product differs depending on what level 
of program management they're in.

This layout makes perfect sense from the programming point of view and seems 
to be the direction we're heading (if you trace back through enough of the 
emails it is eventually possible to maybe infer that fact :-)  

Cheers,
Chris.

-- 
Chris Clarke
security@cfourconsulting.com
http://cfourconsulting.com