On Fri, Oct 16, 2009 at 4:06 AM, Klaas Holwerda <db...@nl.thalesgroup.com> wrote: >>> John Labenski wrote: >>>> >>>> to make them work in both 2.8 and 2.9 since I think they'd be pretty >>>> unreadable by the time I'd be done. >>> >>> Maybe its an idea to make two trees of binding files?? >> >> I will start using SVN, I'm not sure why people like it so much, but >> it seems like the way to go. > > I meant only a seconds version for the bindings directory. > That way things get less fuzzy.
I think wxWidgets 3.0 is due to be out soon enough and there are enough good reasons to start using it. I believe that it is possible to keep the current CVS at SF as 2.8 and make SVN the 2.9 branch. I don't think that there is much to do with 2.8 anymore, it's pretty much a done product so it'll stay that way. > For wxAr2tD i switched to SVN last week. The best thing about SVN is moving > files and directories becomes possible. Also the commit mail is one for > every commit, not per file. I uses as client i use > http://rapidsvn.tigris.org/ which works well. Thanks for your tips on line endings. >> I think we can do away with %class %enum and use class and enum >> followed by { } instead of looking for %endclass and %endenum, change >> %define to #define, but we'll still need #define_string. Basically, >> make it as C/C++ like as possible. Many of the %XXX tags were made to >> catch errors and to be very easy to process. > > But there is things like %rename %operator, but maybe even those can somehow > be defined in the interface files. I see @python things like this in the > interface *.h files. The Python stuff looks easy to skip and we may have to write our own @beginWxLuaOnly sections. The %rename and %operator tags will have to be added too. The best way I can think of doing it is to copy the whole wxWidgets/interface directory to wxLua, edit as appropriate (typically remming out stuff that's not useful in Lua or can't be done), and use it to generate the bindings. When new versions of wxWidgets come out I will have to diff each wxLua file to the corresponding wxWidgets file and copy over the changes to preserve our tags. That's the really time consuming and annoying part. Thanks for the Doxygen sample, XML is ugly. Your idea of providing some interactive docs is compelling, but I'll have to look into the XML more to make sure that does contain enough info and the tags they use don't change and are very systematic. The upshot is that the %operators probably will be nicely parsed (which is hard to do) so we won't need that tag, but we will still need %rename for overloaded functions that take int/double/enum values since Lua treats them all as double so we can't tell what function the user wanted to call. How can we stick that into the interface file so it ends up in the doxygen XML? I'm sure there's a way... The really simple XML parser by Roberto works fine on the XML you posted and it's only a ~50 lines. http://lua-users.org/wiki/LuaXml In the end it's not going to be easy at all since when I last looked briefly at the wxWidgets interface files I found that we have functions in the current wxLua that are not in them so I'll have to compare everything we wrap now with everything we wrap with the interface files and if appropriate send doc patches to wxWidgets. Regards, John ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
