Alan,
Gtk2 may require a bit of a different approach in the way objects are
constructed and so on. Doing it straight on, similar to Gtk1 won't let
us take advantage of optimizations and extendibility features. I plan to
sit down and write up a plan of attack before PHP Con..
That should be feasible - not much of the current code has been altered much, so far:
- added gobject to the inheritence tree
- fleshed out signal connect with closures.
- got my h2defs.php to parse all .h files from gtk2 perfectly(I hope).
- added xxx.defs.defaults (to set defaults)
- moved xxx.defs.extra (for additional defs not generated from headers)
- commented out GtkArgs->php args code.
Looking at the general requirements for Gtk2 -
a) defs file creation / overrides
b) signals/callbacks + GtkArg->GValue conversions
c) changing the base code to use GObject, rather than GtkObject. (and ?? examine how the objects/ze store stuff works)
I was tempted to leave the last bit alone for the moment anyway.. - The idea being it's nice to have a working testbed for any new Object design..
I was thinking of maybe attacking b) depending on timescale - I didnt think there was too much overlap in those areas.. eg. changing the object model may not affect too much of the existing code anyway..?
Regards
Alan
-Andrei
I love deadlines. I like the whooshing sound they make as they fly by.
-- Douglas Adams
--
Can you help out?
Need Consulting Services or Know of a Job?
http://www.akbkhome.com