[kplato] Moving Forward

[Chris Clarke]

Hey,

Since it's been a while since I've seen any serious traffic on this list, I'd 
say that our initial requirements discussion seems to be over.  Sounds like 
this means we can start getting into the details.

There seem to be two major areas that we should concentrate on now (IMO).  
The first is deciding on some of the design constraints that we've put off.  
Specifically, deciding on the following:

1) License: The general consensus seemed to be GPL, but there were a couple 
of dissenting opinions.  Can we have a vote on what the most popular choice 
is?

2) Language of development: There seemed to be a debate between C++ and Java. 
 My personal opinion is for C++, because I think its easiest to work with the 
KDE libraries.  How about a vote on this one?

As for the other big debate, over RDMBS, it looks like KDE is well on its way 
to solving this problem so I think we can hold off for a while yet.

On the details front there are currently two sets of psedo-code available, 
the data dictionary on the kplato site, and the header files created by John 
Lamb at http://www.btinternet.com/~uyea/ 

I think it's about time to start integrating these, and work on defining the 
primitive operations for our classes.  Anybody want to volunteer to start?

Of course, this is just my engineering minded way of moving forward -- if 
other people want things done (better defined use cases?) feel free to speak 
up.

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