Re: [Ktechlab-devel] kdevplatform and document types

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

On Sunday 18 July 2010 20:52:46 Zoltan Padrah wrote:
> Hi,
> 
> 2010/7/18 Alan Grimes <ag...@sp...>
> 
> > chrome://messenger/locale/messengercompose/composeMsgs.properties:
> > 
> > 
> > I think ppl are going a bit crazy with plugins. =\
> > 
> > The basic circuit elements should be built-in, if anything.
> 
> For the end user, it won't matter if the running code resides in the main
> executable or in a shared library. If everything works  as expected, the
> user wouldn't even know about the plugin system.
> For the developer, in my opinion it's better to have a modular program, in
> order to avoid the mess that happened in ktechlab 0.3 series.
+1 Circuit-related things should be in the circuit plugin or some "friend"-
plugin. May be, there are people, that want to use KTechLab only for 
developing code for their MCUs and don't want to simulate anything within a 
circuit, at all. I know, this is future, but we should definitively be aware 
of that and it doesn't make a big difference to build it into a plugin or the 
main application.

> > Also, there should be a 1 simulator per project rule because a large
> > circuit might be split among several documents with the intention of
> > simulating the entire thing coherently, a microcomputer for example.
> 
> Simulating a circuit spanning on multiple documents should be possible, by
> using subcircuits and external connectors ;)
Yes, but I agree to have only one clock (simulator) for a project. This could 
have multiple circuits, of course.

bye then
julian