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

List:       kde-devel
Subject:    Re: Parts vs plugins and extending non-gui portions of an application.
From:       Anatoli Gorchetchnikov <anatoli () cns ! bu ! edu>
Date:       2001-06-18 21:25:46
[Download RAW message or body]

I might be wrong, but so far I've chosen KParts for general 
frameworks (model of visual system or model of goal driven 
navigation) and KPart::Plugins to contain the particular neural 
implementation of the model (which would be algorithm in your 
case). Seems quite flexible so far. And AFAIK Plugins are only 
kept in memory when you actually use them, so you don't waste 
resources. 

On Monday 18 June 2001 04:50 pm, Ian Reinhart Geiser wrote about 
"Parts vs plugins and extending non-gui portions of an 
application.":
> Greetings,
> 	I have a question reguarding KParts.  I have an application
> that I wish to add some functionality to that is not gui
> oriented.  I would like this to happen via a plugin because I
> wish to keep expanding on this area of the applications
> features.  They are a library of different math algorythms.
>
> My question is "Is a KPart the right tool for the job, or
> should I use a different plugin system?"  All of the docs I
> have ever seen on KParts seem GUI oriented so I am not sure of
> where to go from here.  I have started writeing some code
> arround the examples of how to use KParts and it really seems
> as if I may be doing it wrong.
>
> Can anyone offer advice on this subject.
>
> Thanks
> -ian reinhart geiser

-- 
WBR,

TAnGorN
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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