-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> I'm not against the use of XML, but I think that only simple components >> should be written in XML. Others may be written in C/C++, compiled as .so >> and loaded at launch time (or later...). > I fully agree with your last point here. I'm not yet familiar with the > possibilities of the kdelibs here, but I know, there is a strong plugin- > interface to do such things. You are even not bound to a specific language. > Kross is the name of the scripting interface, I'm not sure, if this helps > here. > > The longer I think about it, the more I think, we need a plugin interface > here, to put the computation-stuff for the components into external libraries > that are loaded on demand. These libraries could also contain the > representation of the components, of course. Which libraries are being referred to here? I really hope you guys aren't thinking of compiling .so libs for distribution of component libraries. - --G -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJFdenLstl3vProOARAuXPAJ9kmQQ2roLxvje0oM6XstvNxxAkIQCfYpVw PVAywH2LlrKGSYO8PjYn1Ic= =PaWQ -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ktechlab-devel mailing list Ktechlab-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ktechlab-devel
