[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Wxruby-dev] Request for non-coding assistance
From: |
Curt Hibbs |
Subject: |
RE: [Wxruby-dev] Request for non-coding assistance |
Date: |
Sun, 1 Jun 2003 00:56:29 -0500 |
Thanks Rich for jumping in here and helping out!
Curt
> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden Behalf Of
> Richard Kilmer
> Sent: Saturday, May 31, 2003 5:41 PM
> To: address@hidden
> Subject: Re: [Wxruby-dev] Request for non-coding assistance
>
>
> 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
>
>
- RE: [Wxruby-dev] Request for non-coding assistance,
Curt Hibbs <=