[kplato] RDBMS for Kplato

[Thomas Zander]

On Tue, Jun 19, 2001 at 04:30:45PM -0500, Jim Sabatke wrote:
> "x" IMHO, would be a spreadsheet type listing of when each task will be 
> completed, when the project will be completed, and the probability that 
> the project will be completed on-time.   Also, how many resources will 
> be used and who is assigned to which tasks.
> 
> This should all be visible from the standard input form that we have 
> been discussing so far.


Naturally, this is the right way. Sorry for not making that known ;)
The software design I had in mind was doing this from a higher level
then you propose. In other words, this was on my mind reading and 
distilling the data-desing earlier.

The point I get from your email, Jim, is that this is the way the first
GUI should work. I agree that you are probably a lot better at defining
that then I can, so I assume you are right!

To let this all come together I want to ask you if the information
gathering step can store _all_ its information in the data structures
discussed before. 
see http://lists.kde.org/?l=kplato&m=99291419515904&w=2

This datastructure will list all possible data, but it will not always 
be needed to fill all this from the GUI.

We software people are just creating a structure that will store
everything, and be resillient enough to be used for a completely 
different set of managers. ;)
 
-- 
Thomas Zander                                            zander@earthling.net
The only thing worse than failure is the fear of trying something new