Hi all,
alien.cxx and alien.cxx.templates (unreleased) are getting to the point
where it will soon be feasible to 'rebase' my Qt work on top of them.
The existing binding code uses smoke, however using smoke is not the
only approach; an alternative is binding to Qt directly using
alien.cxx. I see the pros and cons stacking up like this:
smoke pros:
* only one extra library to load
* simple interception of all Qt method calls (useful for subclassing
in factor)
smoke cons:
* requires marshalling of primitive values
* requires smoke (and if smoke disappears or morphs....)
* restricted to smokeified libraries
* dependent on upstream to add methods and classes (unless I learn
more about smoke)
* lousy documentation
alien.cxx pros:
* no indirection through smoke at runtime
* add methods and classes at will from any C++ library
alien.cxx cons:
* generates one C function per method (not sure how much space this
will take)
* no factor-side subclassing until I write alien.cxx.subclass (which
would generate a C++ class which used alien callbacks to implement
its methods)
* I have less Qt experience than the writers of smoke
I'm leaning towards using alien.cxx because a) I'm familar with it and
b) smoke feels hackish in a code-generator ish way; however neither a
nor b are particularly objective and maybe someone with more smoke
experience will disagree.
Air your thoughts and preferences now or forever hold your peace!
Cheers,
Jeremy
------------------------------------------------------------------------------
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk
