Hey Rich,
I got parse_wxdoc working, but I have one possible problem, and one
feature request. It's already way better than what I was planning to
have to do, so you've already saved me time.
The first file I tried was window. Generally it looks good, but I see
that ClientToScreen isn't listed. I haven't yet looked at the tex file
to try to figure it out.
The feature request is: Would it be possible to list the Python
signatures where they exist? I plan to match the Python implementation
where it differs from C++. One example is window's ClientToScreen call.
Do you think it would be difficult to include the Python alternatives
as
extra text associated with the method? Then, they could be printed out
below the C++ version, with an extra tab to set them off. That would be
really great.
Thanks!
Kevin
On Sat, 2003-05-31 at 15:41, Richard Kilmer wrote:
OK...so here you go. It was a bit nasty to parse out some of the
destructors and stuff...but here the jist of it. I have a file
(attached) named 'parse_wxdoc.rb'. Drop it in the doc/latex/wx dir.
It actually builds an object structure:
WxClass
name
constructors (array of WxMethods)
methods (array of WxMethods)
WxMethod
return_type
name
params (array of WxParams)
WxParam
ptype
pname
If you run with a parameter "ruby parse_wxdoc.rb frame.tex" it will
output the class/methods+params. If you just run this file with "ruby
parse_wxdoc.rb" it will iterate over all of the .tex files and try and
parse them. There is a whole slew it cannot parse (and it lists
those), but it gets the majority of them. It then outputs the
class/methods+params. Its easy from this point to generate whatever
you want insofar as a format goes.
Let me know if this works for you.
Best,
Rich
_______________________________________________
Wxruby-dev mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/wxruby-dev