[Boa Constr] Re: [wxPython] Boa Status?

[Riaan B. <riaan@e.co.za>]

Hi Gordon, 

Gordon Williams wrote:
> 
> I was wondering when the next release of Boa was going to be.  There appears
> to be things added to the CVS every couple of weeks.

The functionality for the next release is basically complete, there are
just a few issues/bugs left and things like updating the Docs.
You tripped over one of the issues, I use popen3 to run external 
programs but there are some problems. I hope to switch to wxProcess
asap.

> I tried the latest CVS version and it looks really great with a lot of new
> features from what I remember from looking at it before.  This is going to
> be a nice tool for creating applications using wxPython in a logical and
> consistent way.
> 
> I had a few problems though, and was prevented from finishing the tutorial
> by a crash.  I hope the notes below are of help.
> 
> Regards,
> 
> Gordon Williams
> 
> Boa Bugs
> 
> When going through the tutorial.
> CVS 2000/11/29
> W95, wxPython 2.2.2, python 2.0
> 
> 0) The font in the editor source window is very large and I don't see an
> easy way to change it.  Some clarification is needed in the .cfg
> preferences to make it easier.  It currently looks like a 16 pt. font with
> only 16 lines shown.

You can now edit this at the bottom of PrefsMSW.py (or PrefsGTK for
Linux)
Change the 'size' entry in the faces dictionary.
I hoped to add an interface to configure the fonts and colour but have 
not yet gotten round to it.

> 
> 1) After wxApp and wxFrame created.  Unable to run.  Computer freezes.
>  You can run the wxApp file outside Boa and the frame comes up OK.

I strongly suspect popen3 on Win95.

> 
> 2) Creating Menu. "Edit the name of the first wxMenu to call it mnuFile."
>    This shows an error dialog with "Invalid name for Python object".

Ouch, thanks for catching this one. 
Fixed now, change PropEdit.PropertyEditors.NameConstrPropEdit.getValue
line 578 from:
                for c in value:
to:
                for c in value[1:-1]:

> 3) After making the menus and trying to save the changes using
> the Post button on the Editor, Boa crashes with
> 
> PYTHON executed an invalid instruction in
> module <unknown> at 0000:0180aef8.

I can't reproduce this, but Boa now has a crash tracing facility for
these trying moments. Run Boa with command line option -T and make
it crash. Start it up again, open Boa.py and select 

Edit->View trace log as Traceback

After crunching through the log file a traceback frame should open.
A file named Boa.trace.stack will also be saved in the Boa directory,
please mail or post me this file.

> 
> I tried this twice and got the same crash both times.
> 
> 4) One small thing that would be nice is to change the naming convention
> from "OnMnuhelpitems0Menu" to "OnMnuhelpAboutMenu" for the "About" menu
> item.  That way we don'ts have to remember that item0 is really About.

Remember that you can safely rename event names to whatever you want
by manually changing it in the code (EVT_* binding and On* method name).

Nicer event names are now on the todo list.
It not completely straightforward tho, menu captions != python
identifiers.

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net