Ron: Yes, I meant to include Dummy.usc(contains a wxRadioBox use case) so there would be something to display in the use case box.
We will need to cross check the wxWidgets against the wxPerl widgets and adjust the ListBox accordingly. And generate a use case for each wxPerl Widget. I can steal a fair number of them from my wxBook Examples(with learning curve applied since their creation date). James On Fri, Jan 29, 2016 at 10:00 AM, Ron Grunwald <ron...@yahoo.com.au> wrote: > Hi James, > > Brilliant concept and a huge effort on your part. Did you intend to attach > the file “Dummy.usc”? > > My slight worry is that because you’re drawing on WxWidgets documentation, > we would need some sort of validation mechanism that ensures that any > particular class or method does in fact exist in Wx. > > Fantastic effort – thank you. > > Cheers, > Ron. > > > On 29/01/16 6:35 AM, "James Lynes" <jmlyne...@gmail.com> wrote: > > Ron, Steve, et. al.: > > I got to thinking a few days ago about how we could leverage the great > mass of documentation already produced by the wxWidgets folks, especially > the member function/method documentation for each widget. > > So, I threw together a proof of concept script(attached) for a wxPerl > Documentation Viewer. Download the wxWidgets html documentation(33mb) and > the attached files and give it a try. Obviously a lot more could be added > to this script and several hundred use case files would need to be > created(and downloaded), but that's a smaller effort than recreating all > the method documentation. > > What say ye? If nothing else, it's another good example program. LOL. > > James > > >