[Kde-bindings] JSmoke architectural questions

[Sven Aßmann]

Hello @All

i have reviewed a few lines of code from the jsmoke project from git.kde.org, 
and now i have questions about the architecture of the jsmoke project and 
about a design question for the new phpsmoke project.

1. Is it right that the main core (jsmokeruntime) build the baselevel without 
concrete bindings to any module?

2. the concrete modules are structures under "bindings" and are some kind of 
plugins (QScriptExtensionPlugin)?

3. what about the loading of the plugins, is this doing at runtime by 
something like an "import" derective in the qtscript (i'm know not much about 
qtscript)?

4. is this seperation into plugins only a nice special way because this 
mechanism is enabled by the qt framework itself for qtscript?

conclusion

i'm not sure if i can restructure the php bindings project like this, because 
then i have to write an own loading mechanism for the php smoke runtime, that 
allow to import so little nice plugins for any kind of binding into the php 
language.
in fact php 5.3 support namespaces und imports (or in cpp usings), so it would 
be an really nice benefit if we can do things like this:

<?php
namespace QtGui\QTextEdit;
namespace QtGui\QDockWidget;

?>

Think forward and cut off all stuff before php 5.3?

What think you about this? 

Regards Sven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-bindings/attachments/20101027/ed29e4c2/attachment.sig>