Re: [Ktechlab-devel] test-cases using KDevelop::Core

[Julian B. <ju...@sv...>]

On Monday 19 April 2010 13:04:06 P Zoltan wrote:
> On Thu, 15 Apr 2010 21:33:45 +0200, P Zoltan <zol...@gm...>
> 
> wrote:
> >   Then getting the model is currently not possible. Not a big problem,
> > 
> > can be fixed with the interfaces.
> 
>   We need a new interface, becausethe circuitdocument is subclassed from
> KDevelop::KPartDocument. Instead I'd suggest:
> CircuitDocument <- IComponentDocument <- Kdevelop::KPartDocument.
Ah, now I got your point.. You are right, of course.

> >   So one way to do this might be:
> > create an ISimulatorController. It contains a list of registered
> > component types and the factories associated with them, and also a list
> > of document types and document simulator factories.
> > When a new document is created, it creates a new document simulator with
> > the document type (great, now we will again have document.type()), and
> > attaches the simulator to the document model. Then the document
> > simulator on each model change can rebuild the structure formed by the
> > models. Also, when a given time elapses, the document simulator runs a
> > step in simulation.
> 
>   Inheriting from the Core is not a solution, because the Core is created
> in kdevplatform. The way to go is with a ISimulationController singleton.
Indeed, I tried implementing the shell on our own, this really isn't, what we 
want ;) I reverted this some month ago. If we really need additional methods, 
we should discuss it with KDevelop people and get these directly into 
KDevPlatform.

> >   The problem with this solution is I don't know how will be
> > kdevplatform/kde able to load a needed plugin if a component residing in
> > some now loaded plugin is needed.
> 
> This is still a problem. Maybe load them from the SimuationController at
> document attachment?
Let's discuss that in IRC, I will join in a minute.

bye then
julian