search for: nqxml

since http://nqxml.sourceforge.net/ also recommends that we switch to use rexml which is shipped with ruby? If there are plans for it but no developers, I might take it up as an exercise to learn the internals of wxruby-swig. Cheers, Phuah Yee Keat

In trying to add wxTextCtrl to wxruby-swig, I''ve been running into a problem with the argument conversion that appears to be a SWIG director bug. It is tied to multiple inheritance, and is related to SWIG specifically making director''s ''initialize'' take a first argument, but because ''initialize'' is static there isn''t a self value

Since I''m setting up my development environment on a new system, I figure now is the time to get rid of one of the extra dependencies: NQXML. It appears that REXML can now parse the whole classes xml file in about 20 seconds on this machine, which is a huge improvement over the many, many minutes it used to take. So I am now updating extract.rb to use REXML instead of NQXML. Hopefully the conversion won''t be too painful....

0.0.5 sure gets the Mac build a lot further. There''s a bug in the wxMac-2.4.2 distribution that I''m running into: wx-config wants to invoke a program in the source directory at link time. That''s ugly in itself, but it tries to use a variable ${top_srcdir} to accomplish this, and it''s apparently empty. It tries to invoke

...g xml file that I mentioned earlier, which itself was (apparently) scraped from the wxWidgets html help files. Several interesting notes: 1. REXML took forever to parse the 2.5 meg xml file. I didn''t want to do stream processing, and hoped to stay with a pure-ruby solution, so I used NQXML. It is somewhat slow, but that''s ok since this doesn''t need to be run very often. It works. 2. The xml file itself is not entirely accurate. I have already discovered one case where it does not match the 2.4.2 html docs. To work around this, the app I wrote to extract .h files...

I just grabbed the latest wxruby-swig from cvs and tried to compile it (without enabling the SWIG step) on my gentoo Linux box. I get: g++ -c -I/usr/lib/wx/include/gtk2-2.4 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -O2 -march=athlon-xp -fPIC -I /usr/lib/ruby/gems/1.8/gems/rake-0.4.8/bin -I /usr/lib/ruby/gems/1.8/gems/rake-0.4.8/lib -I

Was trying to understand more about the internals of wxruby-swig, where does the big chunk of XML comes from? I saw something similiar in Python, is that massaged out of there? The codes produced by extractxml.rb and wxclasses-2.4.2.xml is quite different from the original header files. Just for example the WxDialog class. OnXXX are non-virtual in WxWidgets, but virtual in wxruby-swig

This fixes the rakefile to not require NQXML and SWIG, unless you have a WXRUBY_SWIG environment variable set. It also fixes some of the calendar sample errors, but one remains: stock objects (like the color RED) are still not supported. I tried a couple approaches, but none of them will work. I will have to think of something more creat...

...his is a default in any of the wxWidgets platforms, and will be a major point of contention with new users. To actually do any development with wxruby-swig (add new classes, etc), you need a patched version of SWIG, rake (which won''t work on Ruby 1.6, only 1.8), and in the worst case, NQXML. I know rake still needs some work - it''s confirmed not to work with MSYS, and requires some work in MSVC. Personally, I see this as a real drag in getting volunteer developers. If you can''t figure out the build environment, then you won''t help, end of story. On the ot...

I couldn''t find the original tex document that the author of the xml file converted from. Anyone knows where it is? I am toying with the idea of _not using_ the xml file. Either getting the wx header files thru SWIG (I assume you guys have thought about this before already, any specific problems?), or continue with the template generator in the current wxruby-4.0. The RUBY port of