[kplato] Moving Forward

[Steven Hatfield]

On Saturday 30 June 2001 08:18 pm, Chris Clarke wrote:
> 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?

Please, use the GPL. I'd hate to see your work get used by some corporation 
somewhere, sold for money of which you would get none.

>
> 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?

C++ is the language to use, if this is a KDE2 application. Java is nice for 
servlets and applets, but unless you plan on making this a skinable app, go 
with C++. Java based windowing apps look like crap, imho.

>
> 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.

Just my .02.. have a great Sunday :)
-Steven