[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-edu-devel
Subject:    Re: [kde-edu-devel] And so it begins (libkdeedu)
From:       Scott Wheeler <wheeler () kde ! org>
Date:       2002-05-30 13:15:18
[Download RAW message or body]

On Thursday 30 May 2002 01:42 pm, Eva Brucherseifer wrote:

> KDEEdu is more than just language apps. Shouldn't if have a more specific 
> name 
> then including the voc aspect?
> 
> What about 
> KEduVocData

Yes that would probably work.  There is some question at this point is whether 
or not this lib will be mostly for vocabulary data, but it seems that things 
are going that way.  

Question:  Is there anyone out there that has developed or is developing an 
application that would benefit from the data model that the vocabulary apps 
are using?  i.e. a set of text values that represent an "entry" and a set of 
those entries that represent a "list"?

Ok now, thinking about it, I think the way to go would be to define a set of 
classes that work with kvtml that are specific to vocabulary.  If at some 
point we decide that a more generalized approach would be useful, we could 
port those classes to the generalized solution and use the "vocabulary" 
classes as a wrapper to the more general classes.  How does that sound?
 
> Also it might be interesting to have a seperate lib for voc apps, so I'd 
> call 
> it "libkeduvoc". Math apps might also want to have a lib and would be quite 
> bad to link all the voc stuff into a math app.
> A lib "libkedu" should only contain things, that _all_ edu apps can use, 
> such 
> as a score system, etc.

Hmm.  I disagree here.  I see why it would be useful to have separate sets of 
classes, but I don't see why they should be in separate libs.  For example Qt 
is one library, kdeui is just one library, etc.  Again, this is open for 
debate but I don't see a reason to build several libraries except where there 
are linking issues (for instance there are potential advantages to not having 
to link to classes that contain GUI items).  What do you see as the benefit 
of these not being in the same library?

At any rate this should give us some good things to talk about at LinuxTag!

-Scott

_______________________________________________
kde-edu-devel mailing list
kde-edu-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-edu-devel
[prev in list] [next in list] [prev in thread] [next in thread]