[wx-discuss] Hoyle reviews wxWidgets

Kevin Ollivier kevino at theolliviers.com
Mon Mar 6 15:32:51 PST 2006


Hi Robin,

On Mar 6, 2006, at 3:02 PM, Robin Dunn wrote:

> Kevin Ollivier wrote:
>
>> Why not simply create a URL in the overview showing the relevant C+ 
>> + samples? i.e.
>> "For C++ users, see also the following C++ samples: blah, blah"  
>> where blah is a file URL to wxSrc/samples/whatever(/whatever.cpp?)  
>> (or just make a tab for C++)
>> Even better, we can even make this only appear when the wxPython  
>> demo runs inside a wx tree, so we can do something like:
>> cpp_file="wxdir/samples/whatever"
>> if os.path.exists(cpp_file):
>>     # code to show C++ tab or links
>> It's true the samples aren't equivalent, but they'll do what users  
>> need them to - show how to use the class.
>
> The only issue with this is that most of the C++ samples have  
> multiple source files, so we probably would have to restructure the  
> demo to make it easy to see all of them.

Why not just have, at the top of the C++ notebook page, a drop-down  
with a list of .h and .cpp files for the sample? For the widgets C++  
sample, for example, any wxPy class that appears in the Widgets  
sample would display the Widgets sample files in the C++ tab. In  
fact, if the person's environment were configured correctly and wx  
binaries were installed, which an installer could do, we could  
actually have a "Build and Run C++ Sample" button up there to the  
right of the drop-down list, or perhaps at the bottom of the notebook  
page... We'll need to re-direct the compiler/linker output of course,  
and have a prompt display when compiling fails. Not quite head- 
exploding, perhaps, but not coronary-inducing either. ;-) It actually  
would give us results close to what Ryan was talking about in terms  
of editing the samples. :-)

> Probably better from a UI point of view is to just have some C++  
> snippets that can be displayed with each widget in the demo, but  
> then those would have to be maintained separately from the samples  
> and so it could become a mess...

I half think what will happen is that when the wxPython and wx C++  
demos are put side-to-side, people are going to start jumping in and  
synchronizing them, or trying things shown in one in the other.  
Hmmm... thinking more, we could utilize the "Use Modified" and "Use  
Original" options from the wxPython demo too, and allow wx C++ users  
to click a "Make Patch" button to create a patch file that users  
could submit to wx! You know how we're always asking someone to  
modify the minimal sample... ;-)

Thanks,

Kevin

> -- 
> Robin Dunn
> Software Craftsman
> http://wxPython.org  Java give you jitters?  Relax with wxPython!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wx-discuss-unsubscribe at lists.wxwidgets.org
> For additional commands, e-mail: wx-discuss-help at lists.wxwidgets.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: wx-discuss-unsubscribe at lists.wxwidgets.org
For additional commands, e-mail: wx-discuss-help at lists.wxwidgets.org





More information about the wx-discuss mailing list