boa-constructor-users

Re: [Boa Constr] [wxPython-users] Question on opinions...

[Werner F. B. <wer...@fr...>]

Chris,

On 29/11/2010 00:38, Chris Spencer wrote:
> On Sun, 28 Nov 2010 20:27:16 +0100, "Werner F. Bruhin"
> <wer...@fr...>  wrote:
>> Chris,
>>> IS Riaan doing anything?  Currently?
>> The short answer is yes and I don't have details nor do I think it would
>> be up to me to reveal them here.
>
> Sorry, the thrust of my question is unclear.  Is he doing anything
> WITH BOA currently?  I'm quite willing to believe that other work
> matters are keeping him away.
It was as clear as my answer:).

The "yes" was in relation to Boa.  I.e. I know Riaan has done work on it 
but I don't know details.

That is another reason why I would hope that a switch away from CVS 
would help move things foreward, i.e. Riaan (and others) could work on a 
new branch without causing havoc to the "current" trunk.

Hopefully Riaan will find the 25th hour in a day to respond to all these 
questions/concerns/hopes .....

Werner

Re: [Boa Constr] Boa improvements

[C M <cmp...@gm...>]

> Having some kind of roster of the top few functions that are currently
> pertinent to solving the bug/feature concern that I am working on at
> the time might be helpful (lately I've been just writing them or their
> line # on a piece of paper).
>
> I don't know if this is something that IDEs typically do or if it
> would be useful or not, just throwing it out.

I realized after I wrote this that what I'm describing is basically
the Explore tab, only cut down to a small number of selected functions
or objects.  It's like the Explore's Greatest Hits (of the moment).

Che

Re: [Boa Constr] [wxPython-users] Question on opinions...

[Chris S. <csp...@ci...>]

On Sun, 28 Nov 2010 20:27:16 +0100, "Werner F. Bruhin"
<wer...@fr...> wrote:
>Chris,
>> IS Riaan doing anything?  Currently?
>The short answer is yes and I don't have details nor do I think it would 
>be up to me to reveal them here.

Sorry, the thrust of my question is unclear.  Is he doing anything
WITH BOA currently?  I'm quite willing to believe that other work
matters are keeping him away.

>> RE plug-ins:  Until you mentioned it, I didn't even know Boa HAD the
>> ability to do plug-ins.  I subsequently looked for information on them
>> and found exactly one page on the internet...in German...that
>> describes how they are used....
>> http://www.xing.com/net/python-programmierung/details-programmschnipsel-22580/boa-constructor-plugins-1454660/
>>
>> The documentation INSIDE Boa is nonexistent on the topic of how to do
>> custom controls in the context of a plug-in.
>There is a very short mention in "Extending Boa Constructor" within the 
>Boa help but I don't recall that there is any tutorial how to do things.
>
>Looking at some of the existing plug-in files can be helpful but it 
>would definitely be good to have some tutorial on it and how to add 
>widgets to the Companions.

I never looked at it.  I never saw it's power.  Why?  Because most
plug-ins are disabled on a base BOA install.  Any extensions that we
do for wxPython 2.9 controls should be active on the first startup
(and then it's up to the user to disable them if s/he's still working
with older wxPython versions).

But the more I looked into plug-ins, the more I appreciate how much
can be done with them to keep BOA current without mucking about in the
code base.  In fact...I'm such a believer that I might just download a
clean install from CVS and convert all of my monkey-patches to
plug-ins.

I've been using Boa for near 10 years now...I have NO idea how I
missed this.

>Done as plug-in's or within the core code they should both end up in a 
>formal release but in the short time the plug-in way makes it very easy 
>to share.

Agreed.

>If I understand Phoenix correctly it should be backwards compatible, 
>i.e. I think if Boa fully supports 2.9 I would think it will also 
>support Phoenix.

I don't know.  On one hand I'm hearing that it'll be very backwards
compatible.  Then I see the debates about going unicode-only.  Makes
me twitchy (not the Unicode, since all my code is in Unicode) when
developers change the build process.  It encourages them to say "well,
while we're changing THIS...let's just go over here and change these
other things..."

I still wake up in cold sweat nightmares about the Python 3.x
series...

>Another story will be Python 3.x support - but lets make small steps 
>towards a new release of Boa with at least acceptable 2.9 support.

Agreed.

>
>Werner

Chris.

Re: [Boa Constr] Silent listeners

[C M <cmp...@gm...>]

On Sun, Nov 28, 2010 at 1:19 PM, Sylvain <Syl...@fr...> wrote:
> Hi Werner, Chris and CM,
>
> I am sure they are many people who, like me, very seldom write on the list but
> are very interested in what is happening. And that we will help with our
> means. Probing on different system, translatind help, packaging if we dont have
> the skill for helping in programming.

Thanks, Sylvain.  I hope we can figure out a way to allow a number of
people to pitch in and help out Boa.  I think there's a lot of love
for it out there and deservedly so.  Stay tuned....

Che

Re: [Boa Constr] [wxPython-users] Question on opinions...

[Werner F. B. <wer...@fr...>]

Chris,

On 28/11/2010 17:20, Chris Spencer wrote:
> On Sun, 28 Nov 2010 11:09:22 +0100, "Werner F. Bruhin"
> <wer...@fr...>  wrote:
...
>
>> Yes I am willing to invest even a bit more of my time then I already do
>> into Boa which is still nothing compared to what Riaan is doing.
>
> IS Riaan doing anything?  Currently?
The short answer is yes and I don't have details nor do I think it would 
be up to me to reveal them here.

As mentioned in the other post I have been in contact with him less then 
a week ago and know that he has too much work on his plate to give us a 
very quick feed back on all this.  But I am confident that when he gets 
a moment he will respond in some form to all this.

...
>
> RE plug-ins:  Until you mentioned it, I didn't even know Boa HAD the
> ability to do plug-ins.  I subsequently looked for information on them
> and found exactly one page on the internet...in German...that
> describes how they are used....
> http://www.xing.com/net/python-programmierung/details-programmschnipsel-22580/boa-constructor-plugins-1454660/
>
> The documentation INSIDE Boa is nonexistent on the topic of how to do
> custom controls in the context of a plug-in.
There is a very short mention in "Extending Boa Constructor" within the 
Boa help but I don't recall that there is any tutorial how to do things.

Looking at some of the existing plug-in files can be helpful but it 
would definitely be good to have some tutorial on it and how to add 
widgets to the Companions.
>
> Even if I travel up that learning curve (which, from that Germanic
> tutorial, is simpler than what I have been doing), there are things
> like the properties for dialogs (wx.DIALOG_MODAL, etc) that need to be
> applied to the existing code base.
Agreed.
Also, I'm not sure if I'm a big
> fan of forcing people to install Boa...and then have to manually
> download a plug-in pack and place it in the plug-ins directory.  I'm
> much enamored of the "batteries included" approach.
>
Done as plug-in's or within the core code they should both end up in a 
formal release but in the short time the plug-in way makes it very easy 
to share.
> It's only by the grace of god and Robin's commitment to keeping
> wxPython as backward compatible as humanly possible that allows Boa to
> even be used.  I don't know what is going to happen when Project
> Phoenix is finished.
If I understand Phoenix correctly it should be backwards compatible, 
i.e. I think if Boa fully supports 2.9 I would think it will also 
support Phoenix.

Another story will be Python 3.x support - but lets make small steps 
towards a new release of Boa with at least acceptable 2.9 support.

Werner

Re: [Boa Constr] Removing options for wx.DIALOG_MODAL and wx.DIALOG_MODELESS

[Werner F. B. <wer...@fr...>]

Hi Chris,

On 28/11/2010 16:37, Chris Spencer wrote:
> On Sun, 28 Nov 2010 11:17:26 +0100, "Werner F. Bruhin"
> <wer...@fr...>  wrote:
>> Chris,
>> (just removing wx.DIALOG_MODAL and wx.DIALOG_MODELESS references)
>> Shouldn't changes like this be conditioned by Version?  I.e. if one is
>> on wxPython 2.8 or lower this is still active otherwise not.
>>
>> There is already quite a big of "if wx.VERSION[:2]>= (2, 7):" type code
>> in there.
>>
>>
>> Werner
>
> Oh, absolutely, if I were going to patch the main trunk to BOA.  I was
> just putting that out there for people working with wxPython 2.9 and
> up, not patching BOA itself.
>
> I promise to be careful about versions when I do production-ready BOA
> patches...
>
> For me, I'm okay with pinning a minimum version on BOA so that we
> don't have to support versions of wxPython back to the stone-age,
> which would just bloat Boa with "if-blocks" all over the place.
Agreed, but I think at a minimum 2.8 needs to be support for a long time 
to come.
>
> For me, all of this is academic until AT THE VERY LEAST we set up a
> repository somewhere for new code commits (I'm still pulling for
> Mercurial).
Agreed - lets see if Riaan has a preference.
>
> I'd also like SOME kind of blessing from Riaan.  Even though GPL lets
> us fork this code, I'd hope it'd be done in a way that respects the
> ENORMOUS work of the original author.  His lack of reaction to this
> current turn of events makes me wonder if he's even reading this list
> anymore.
He is.  I have been in touch with him off-list less then a week ago.
>
> I am about 2 weeks away from being able to provide the repository on a
> TEMPORARY basis (to get us started).  I'd say we give Riaan until Dec.
> 15 to give us SOMETHING of a reaction before forking it without him.
> Even THAT makes me feel icky, but progress must be made.
I don't think that this will be an issue as there are plenty of optiones 
for OpenSource projects.  One could stay on SourceForge, they are coming 
out with new stuff and they support all the top source code management 
systems or go with one of the others.  I wouldn't do some temp stuff and 
then move again as this is all just work .....

Werner

[Boa Constr] Silent listeners

[Sylvain <Syl...@fr...>]

Hi Werner, Chris and CM,

I am sure they are many people who, like me, very seldom write on the list but 
are very interested in what is happening. And that we will help with our 
means. Probing on different system, translatind help, packaging if we dont have 
the skill for helping in programming.

About plugins, it is not an issue because end user (with Linux) will use 
packages that automaticaly will place them in the right place. Nothing to do.

Sylvain.

Re: [Boa Constr] [wxPython-users] Question on opinions...

[Chris S. <csp...@ci...>]

On Sun, 28 Nov 2010 11:09:22 +0100, "Werner F. Bruhin"
<wer...@fr...> wrote:
>Could you provide patches for any stuff which is of interest for others? 
>  Me and others can then test things and if they work in our setup ask 
>Riaan to apply it.

As I've indicated, I've monkey-patched BOA so much that I'm having
problems determining what can be safely applied to a base BOA install.
My WinDiff looks like a Christmas tree... :)

>Have a look at WingIDE free for open source projects otherwise it costs. 
>  I've looked at it a little while ago and still have the evaluation 
>copy on my machine - it is the nicest/best I have seen besides Boa and 
>would be high on my list if ever I switch away from Boa.

I have looked at it.  90% of my coding is on what will become a
commercial product (though someone might have to shoot me and grab my
hard drive to get it released...I'm relentlessly unhappy with my work,
making me spend time niggling over things).  That means I would be
honor bound to pay $179 for what is an impressive code editor.

Or I can use my $20 Textpad license.  And I'm cheap.  I've been using
Textpad since the days of Windows 95 and know its every grotty corner
and hidden feature.  It's a COMFORT thing, rather than a LOGIC thing,
I know.  But there you have it...

>> For debugging, I've never run across a debugger that is more flexible
>> than a print statement.
>Sometimes yes, but that means you already know where your bug is.

Oh, I've become proficient in narrowing down where bugs are using
"print".  In fact, it has gotten to the point that when I do Visual
Studio work (either VB.NET or C#), I am loathe to use the Visual
Studio debugger.

>Instead of print statements you should also look at the Python logging 
>module, that way your print/debug stuff can stay in the code instead of 
>having to add it/remove it etc.

I use the logging module for the work I'm doing.  In the beginning it
was invaluable.  Now it just generates gigabyte-sized debug files that
I delete every few days.  I really must go through my code and put
those logging statements on some sort of hierarchical scale.  Right
now I capture exceptions to a MUCH shorter log file, and that is my
main form of debug logging these days.

>Yes I am willing to invest even a bit more of my time then I already do 
>into Boa which is still nothing compared to what Riaan is doing.

IS Riaan doing anything?  Currently?  I can't tell from his lack of
CVS commits to sourceforge and his non-presence on this list.  To me
it feels like he's moved on in his life.  AND THAT IS HIS RIGHT.  I'm
not complaining about that choice, if it has been made.  But I think
he should communicate where he is with respect to the BOA codebase and
his involvement in it.  There's been no release in 3 years, and no CVS
commits for much of that.

>However it would have to be with Riaan's participation as I don't think 
>this will be feasible without having at least access to his know how.

I agree that it's one hell of a learning curve.  It's one we might
have to travel if Riaan is completely unavailable.  For me it's
either...we have to do this or it won't get done and I'll have to move
away from BOA for my next huge investment of coding time.  Which
probably means moving away from wxPython...since there isn't another
GUI builder that doesn't make me want to put my fist through the
screen.

RE plug-ins:  Until you mentioned it, I didn't even know Boa HAD the
ability to do plug-ins.  I subsequently looked for information on them
and found exactly one page on the internet...in German...that
describes how they are used....
http://www.xing.com/net/python-programmierung/details-programmschnipsel-22580/boa-constructor-plugins-1454660/

The documentation INSIDE Boa is nonexistent on the topic of how to do
custom controls in the context of a plug-in.

Even if I travel up that learning curve (which, from that Germanic
tutorial, is simpler than what I have been doing), there are things
like the properties for dialogs (wx.DIALOG_MODAL, etc) that need to be
applied to the existing code base.  Also, I'm not sure if I'm a big
fan of forcing people to install Boa...and then have to manually
download a plug-in pack and place it in the plug-ins directory.  I'm
much enamored of the "batteries included" approach.

It's only by the grace of god and Robin's commitment to keeping
wxPython as backward compatible as humanly possible that allows Boa to
even be used.  I don't know what is going to happen when Project
Phoenix is finished.

>Werner

Chris.

Re: [Boa Constr] Boa improvements

[C M <cmp...@gm...>]

On Sun, Nov 28, 2010 at 5:24 AM, Werner F. Bruhin <wer...@fr...> wrote:
> Che,
>
> On 27/11/2010 20:03, C M wrote:
> ...
>>
>> This is just throwing something out, but lately I've been thinking
>> that it would be great to have some kind of dropdown or some GUI
>> element that could allow one to have a list of a handful of functions
>> that one could quickly go to in the code.  I use browse to, "back",
>> Ctrl-G and other things, but this would beat all of them, I think.
>> Not sure how hard that would be to implement.
> You mean like ctrl and left mouse click:)?
>
> i.e. having this or similar line in the code:
>
> self.BackupCheck()
>
> Hover over it while holding down "Ctrl" it will change to a hyperlink
> and when you click on it the editor will jump to the "def" of that function.

Hmm, that is what I was calling "browse to" above, and I use it all
the time--but now that I check, "browse to" is listed as Ctrl-Return.
Then what is the real "browse to", since if I use Ctrl-Return it
doesn't seem to do anything?

Whatever Ctrl-click is called, it is very handy.  But it is necessary
to use "Back" to go back to where you just were, but oftentimes I will
be poking around in other functions or places in the code and will
introduce new places where "back" will bring me to...and I'll find
myself forgetting the point of where I was or what the goal was.
Having some kind of roster of the top few functions that are currently
pertinent to solving the bug/feature concern that I am working on at
the time might be helpful (lately I've been just writing them or their
line # on a piece of paper).

I don't know if this is something that IDEs typically do or if it
would be useful or not, just throwing it out.

Che

Re: [Boa Constr] Removing options for wx.DIALOG_MODAL and wx.DIALOG_MODELESS

[Chris S. <csp...@ci...>]

On Sun, 28 Nov 2010 11:17:26 +0100, "Werner F. Bruhin"
<wer...@fr...> wrote:
>Chris,
>(just removing wx.DIALOG_MODAL and wx.DIALOG_MODELESS references)
>Shouldn't changes like this be conditioned by Version?  I.e. if one is 
>on wxPython 2.8 or lower this is still active otherwise not.
>
>There is already quite a big of "if wx.VERSION[:2] >= (2, 7):" type code 
>in there.
>
>
>Werner

Oh, absolutely, if I were going to patch the main trunk to BOA.  I was
just putting that out there for people working with wxPython 2.9 and
up, not patching BOA itself.

I promise to be careful about versions when I do production-ready BOA
patches...

For me, I'm okay with pinning a minimum version on BOA so that we
don't have to support versions of wxPython back to the stone-age,
which would just bloat Boa with "if-blocks" all over the place.

For me, all of this is academic until AT THE VERY LEAST we set up a
repository somewhere for new code commits (I'm still pulling for
Mercurial).

I'd also like SOME kind of blessing from Riaan.  Even though GPL lets
us fork this code, I'd hope it'd be done in a way that respects the
ENORMOUS work of the original author.  His lack of reaction to this
current turn of events makes me wonder if he's even reading this list
anymore.

I am about 2 weeks away from being able to provide the repository on a
TEMPORARY basis (to get us started).  I'd say we give Riaan until Dec.
15 to give us SOMETHING of a reaction before forking it without him.
Even THAT makes me feel icky, but progress must be made.

Chris.

Re: [Boa Constr] Boa improvements

[Werner F. B. <wer...@fr...>]

Che,

On 27/11/2010 20:03, C M wrote:
...
>
> This is just throwing something out, but lately I've been thinking
> that it would be great to have some kind of dropdown or some GUI
> element that could allow one to have a list of a handful of functions
> that one could quickly go to in the code.  I use browse to, "back",
> Ctrl-G and other things, but this would beat all of them, I think.
> Not sure how hard that would be to implement.
You mean like ctrl and left mouse click:)?

i.e. having this or similar line in the code:

self.BackupCheck()

Hover over it while holding down "Ctrl" it will change to a hyperlink 
and when you click on it the editor will jump to the "def" of that function.

Werner

Re: [Boa Constr] Removing options for wx.DIALOG_MODAL and wx.DIALOG_MODELESS

[Werner F. B. <wer...@fr...>]

Chris,

On 27/11/2010 18:32, Chris Spencer wrote:
> wx.DIALOG_MODAL and wx.DIALOG_MODELESS have been removed as of
> wxPython 2.9.  It is dangerous (and unnecessary) to leave them in Boa
> Constructor.  Therefore, in the file FrameCompanions.py, replace...
>
> class DialogDTC(FramesConstr, BaseFrameDTC):
>      dialogLayout = True
>
>      def __init__(self, name, designer, frameCtrl):
>          BaseFrameDTC.__init__(self, name, designer, frameCtrl)
>          self.windowStyles = ['wx.DIALOG_MODAL', 'wx.DIALOG_MODELESS',
>                'wx.CAPTION', 'wx.DEFAULT_DIALOG_STYLE',
> 'wx.RESIZE_BORDER',
>                'wx.THICK_FRAME', 'wx.STAY_ON_TOP',
> 'wx.DIALOG_NO_PARENT',
>                'wx.SYSTEM_MENU', 'wx.CLOSE_BOX']\
>                + self.windowStyles
>
> with...
>
> class DialogDTC(FramesConstr, BaseFrameDTC):
>      dialogLayout = True
>
>      def __init__(self, name, designer, frameCtrl):
>          BaseFrameDTC.__init__(self, name, designer, frameCtrl)
>          self.windowStyles = [
>                'wx.CAPTION', 'wx.DEFAULT_DIALOG_STYLE',
> 'wx.RESIZE_BORDER',
>                'wx.THICK_FRAME', 'wx.STAY_ON_TOP',
> 'wx.DIALOG_NO_PARENT',
>                'wx.SYSTEM_MENU', 'wx.CLOSE_BOX']\
>                + self.windowStyles
>
> (just removing wx.DIALOG_MODAL and wx.DIALOG_MODELESS references)
Shouldn't changes like this be conditioned by Version?  I.e. if one is 
on wxPython 2.8 or lower this is still active otherwise not.

There is already quite a big of "if wx.VERSION[:2] >= (2, 7):" type code 
in there.


Werner

Re: [Boa Constr] [wxPython-users] Question on opinions...

[Werner F. B. <wer...@fr...>]

Hi Chris,

On 27/11/2010 17:44, Chris Spencer wrote:
> On Sat, 27 Nov 2010 10:33:36 +0100, werner<wb...@fr...>  wrote:
>> Chris,
>>
>> On 26/11/2010 20:43, Chris Spencer wrote:
>>> On Fri, 26 Nov 2010 10:46:55 +0100, werner<wb...@fr...>   wrote:
>>>> Adding new widgets can be done in two ways, either via the plug-in
>>>> support, see e.g. FlatNotebook-plug-in.py which I think I started and
>>>> Riaan fixed it up so it really worked;-) or via the "companions" support
>>>> see the sub-folder with the same name in Boa.
>>>>
>>>> Werner
>>> And I have used this technique from time to time.  I know how to add
>>> widgets for myself.  But why should everyone replicate my work to get
>>> the additional controls added to wxPython in the past 5 years or so?
>> Totally agree.
>>
>> If you done any as plug-in's can you please post them to the Boa list as
>> those anyone can just drop into the plug-in folder and they would be
>> usable - o.k. they still won't make it into the next release until ....
>
> I'll have to dig into it and see what I can contribute immediately.  I
> run a somewhat heavily modded Boa Constructor, so my code won't be
> plug-n-play.
Could you provide patches for any stuff which is of interest for others? 
  Me and others can then test things and if they work in our setup ask 
Riaan to apply it.
>
>>> Would you not agree that it's better for a small group of people to
>>> add these controls and then release a Boa Constructor version with
>>> them integrated in?
>>>
>>> Frankly, I don't use Boa as a code editor or debugger.  I have other
>>> much more evolved code editors for that.
>> What are you using?  Wing IDE or?
>
> I use Textpad. :)  Every Python editor/debugger I've tried doesn't
> give me the one capability that I crave most of all...splitting the
> same source code into different windows seamlessly.  Also, I like
> coding on a black background with white text (easier on the eyes), and
> you'd be surprised how many code editors don't allow you to change the
> color scheme...
Have a look at WingIDE free for open source projects otherwise it costs. 
  I've looked at it a little while ago and still have the evaluation 
copy on my machine - it is the nicest/best I have seen besides Boa and 
would be high on my list if ever I switch away from Boa.

- allows black on white
- same source file can be viewed worked on in multiple windows
- has a very good debugger
- only hang up I found at the time is that its perspective save/restore 
doesn't yet work on dual monitors, i.e. I would want to move some of its 
toolboxes to my secondary monitor.
>
> For debugging, I've never run across a debugger that is more flexible
> than a print statement.
Sometimes yes, but that means you already know where your bug is.

Instead of print statements you should also look at the Python logging 
module, that way your print/debug stuff can stay in the code instead of 
having to add it/remove it etc.
>
>>>     What I do use Boa for is
>>> it's (as far as I am concerned) unmatched GUI creation ability.
>>>
>>> But it is showing its age.  Rust is creeping in.  And it's not keeping
>>> up with the increasing control density of wxPython.  And I don't think
>>> Riann (for WHATEVER reason) is willing/able to keep maintaining it.
>> I won't speak for Riaan (I am pretty sure he is old enough for that:-) )
>> but I am sure he cares but real live is just getting too much in the way
>> for our liking - i.e. he is very very busy on protects which pay his
>> food and roof etc and just doesn't have enough time to spend on Boa.
>>
>> I don't see anyone beside Riaan who is totally familiar with Boa and so
>> a "restart" without him does not make much sense.  I hope he will react
>> to my post in reaction to this thread on the Boa list.
>
> And he shouldn't have to maintain it for the rest of his life.  That
> is what Open Source is for, so that the community can maintain code as
> necessary when the creator can't.
>
> However, forking the code to another site might be the only option if
> we don't obtain CVS write access to the code on sourceforge.  And my
> favorite source control is Mercurial, because it's in Python. :)  It
> also seems to be gaining a lot of traction in the Open Source world.
>
>>> I've often thought of making my own GUI creation tool, like Visual
>>> Studio's.  The amount of effort to get from zero to useful is beyond
>>> my ability to devote time to it.  However, BOA is 90% there already. I
>>> can spend the time helping to polish it up and bring it current with
>>> wxPython 2.9.
>> We really should take this Boa discussion onto the Boa list before
>> others here get feed up with us.
>
> Done and done.
>
>>> It's sad to see such a fantastic tool become, essentially,
>>> abandonware.
>> I would very much regret if Boa would be totally abandoned.
>
> Me too...especially since it's the best GUI designer out there.
>
> I'm going to re-download the latest CVS and do a little less haphazard
> modding of it so that I can do a proof-of-concept patch for the list.
That would be great.
>
> I would love to have Riann's blessing on this.  Boa is under the GPL
> license, so we could fork without him, but I consider this to be
> extremely rude (which is why I've gritted my teeth for five years).
> However, I'd rather be rude than to see Boa wither on the vine.
Lets give Riaan (two 'a's and one 'n') some time to think about all this.
>
> I'm going to brush up on my Boa internals and see if I can integrate
> the new wx.Button ability to contain an image.  Sort of a "hello
> world" of modding Boa.  I'd also like to add all of the new AGW
> controls.  One of the mods I've done with my hacked-up version of Boa
> is the AquaButton control.  I'd like to do it in a more controlled
> manner this time.
If you do them as plug-ins then they are much easier for others to use 
and I don't think you loose any functionality.
>
> I'd like to know, if I start doing this stuff, will others pick up the
> torch as well and help me.  Due to my own busy life (running a
> business, going to school, and making indie films...yes, you heard
> that right :) ) this effort to revitalize Boa will quickly fall apart
> if it's just me doing it.
>
Yes I am willing to invest even a bit more of my time then I already do 
into Boa which is still nothing compared to what Riaan is doing.

However it would have to be with Riaan's participation as I don't think 
this will be feasible without having at least access to his know how.

Werner

[Boa Constr] Boa improvements

[C M <cmp...@gm...>]

Hi Werner, Chris, and others.

OK, I finally subscribed to the boa email list; for some reason, all
this time I didn't realize it was an email list like the
wxPython-users list (I guess I thought it was only a forum).  I missed
the first day or so of discussion regarding sprucing up Boa, so I'll
just cut and paste it into this new message

First off, I think that if things get polished up, user community
interest can really increase.  E.g., the person who runs ShowMeDo.com,
a major Python and wxPython aficionado, was enthused enough about Boa
to write a blog post about my videos when they went up, and I think
reading his post might be a good thing if we are thinking about how
Boa is perceived.  Note his opening line:  "There are precious few
open-source (OS) GUI builders of any repute but the lack is sorely
felt in the wxPython world."

The blog post is here:
http://blog.showmedo.com/new-showmedo-videos/boa-constructor-wxpython-gui-builder-video-series/

Werner wrote:

> I think a "restart" needs at a minimum:
>
> - new web site, I would suggest a Sphinx (http://sphinx.pocoo.org/)
> type web site, i.e. an introduction/welcome page with links to the
> documentation which in turn also links to any tutorials and videos etc.

No question.  The current website is a major turnoff to new users,
whether they are Python newbies or serious developers.  That, in turn,
seriously cools interest and possible open source contributors to Boa.
 At this point in internet history, it's almost to the point where if
there isn't even a regularly posted-to blog, a project feels
abandoned.   I think a lot can be done without a great deal of effort
to help here.

> - regular releases, I think it needs one at least once a year better
> would be twice a year.  And this means not certainly lots of new
> features but just officially rolling out any fixes done since the last
> one, including adding in the up to date documentation for Python,
> wxPython etc.

Agreed.

> - make it easier for others to contribute (see source code control
> below), document how things are done so maybe others then Riaan can do
> them (e.g. web site, documentation generation, release generation...).

Agreed.

>
> - tutorial on adding a new widget would be really helpful

Yes, definitely.  But, as Chris said, more important is to have a
"batteries included" approach to Boa, such that new users can know
that it remains up-to-date with respect to the latest version of
wxPython.

Adding my own to the wish list:

- Fix the Linux-specific bugs, which are deal-breaking unless one
knows how to work around them.  As Werner knows, I've documented all
of the ones I could find.  Riaan has that list, so I'm not sure if he
managed to fix any of them yet.

- toggling of the IDs (probably even making it the default), so that
wxID_PANEL1BITMAPBUTTON4 becomes simply -1.  I've tried editing the
"Do Not Edit" section of the Boa code and replacing all those with -1
and removing the list of them at the top, and the Designer still
works, so that suggests they are not necessary--though I don't know.

- toggling giving widgets sizes if in some kind of "sizer mode".
Having sizes has gotten me into trouble numerous times.  I don't think
I understand Werner's response about introspection, so some
elaboration would be helpful there.

And

- General bug fixes and enhancements.  I listed 6 bugs in my final
video, and I can think of a number more.  We could prioritize them and
work on the most egregious ones first.

This is just throwing something out, but lately I've been thinking
that it would be great to have some kind of dropdown or some GUI
element that could allow one to have a list of a handful of functions
that one could quickly go to in the code.  I use browse to, "back",
Ctrl-G and other things, but this would beat all of them, I think.
Not sure how hard that would be to implement.

Chris wrote:

> I'd like to know, if I start doing this stuff, will others pick up the
> torch as well and help me.  Due to my own busy life (running a
> business, going to school, and making indie films...yes, you heard
> that right :) ) this effort to revitalize Boa will quickly fall apart
> if it's just me doing it.

I would like to help, for one.  I would think we might be able to get
1-2 other people from users or wxPython people.  We can at least try
and see if it could work.

Che

[Boa Constr] Removing options for wx.DIALOG_MODAL and wx.DIALOG_MODELESS

[Chris S. <csp...@ci...>]

wx.DIALOG_MODAL and wx.DIALOG_MODELESS have been removed as of
wxPython 2.9.  It is dangerous (and unnecessary) to leave them in Boa
Constructor.  Therefore, in the file FrameCompanions.py, replace...

class DialogDTC(FramesConstr, BaseFrameDTC):
    dialogLayout = True

    def __init__(self, name, designer, frameCtrl):
        BaseFrameDTC.__init__(self, name, designer, frameCtrl)
        self.windowStyles = ['wx.DIALOG_MODAL', 'wx.DIALOG_MODELESS',
              'wx.CAPTION', 'wx.DEFAULT_DIALOG_STYLE',
'wx.RESIZE_BORDER',
              'wx.THICK_FRAME', 'wx.STAY_ON_TOP',
'wx.DIALOG_NO_PARENT',
              'wx.SYSTEM_MENU', 'wx.CLOSE_BOX']\
              + self.windowStyles

with...

class DialogDTC(FramesConstr, BaseFrameDTC):
    dialogLayout = True

    def __init__(self, name, designer, frameCtrl):
        BaseFrameDTC.__init__(self, name, designer, frameCtrl)
        self.windowStyles = [
              'wx.CAPTION', 'wx.DEFAULT_DIALOG_STYLE',
'wx.RESIZE_BORDER',
              'wx.THICK_FRAME', 'wx.STAY_ON_TOP',
'wx.DIALOG_NO_PARENT',
              'wx.SYSTEM_MENU', 'wx.CLOSE_BOX']\
              + self.windowStyles

(just removing wx.DIALOG_MODAL and wx.DIALOG_MODELESS references)

Re: [Boa Constr] [wxPython-users] Question on opinions...

[Chris S. <csp...@ci...>]

On Sat, 27 Nov 2010 10:33:36 +0100, werner <wb...@fr...> wrote:
>Chris,
>
>On 26/11/2010 20:43, Chris Spencer wrote:
>> On Fri, 26 Nov 2010 10:46:55 +0100, werner<wb...@fr...>  wrote:
>>> Adding new widgets can be done in two ways, either via the plug-in
>>> support, see e.g. FlatNotebook-plug-in.py which I think I started and
>>> Riaan fixed it up so it really worked;-) or via the "companions" support
>>> see the sub-folder with the same name in Boa.
>>>
>>> Werner
>> And I have used this technique from time to time.  I know how to add
>> widgets for myself.  But why should everyone replicate my work to get
>> the additional controls added to wxPython in the past 5 years or so?
>Totally agree.
>
>If you done any as plug-in's can you please post them to the Boa list as 
>those anyone can just drop into the plug-in folder and they would be 
>usable - o.k. they still won't make it into the next release until ....

I'll have to dig into it and see what I can contribute immediately.  I
run a somewhat heavily modded Boa Constructor, so my code won't be
plug-n-play.

>> Would you not agree that it's better for a small group of people to
>> add these controls and then release a Boa Constructor version with
>> them integrated in?
>>
>> Frankly, I don't use Boa as a code editor or debugger.  I have other
>> much more evolved code editors for that.
>What are you using?  Wing IDE or?

I use Textpad. :)  Every Python editor/debugger I've tried doesn't
give me the one capability that I crave most of all...splitting the
same source code into different windows seamlessly.  Also, I like
coding on a black background with white text (easier on the eyes), and
you'd be surprised how many code editors don't allow you to change the
color scheme...

For debugging, I've never run across a debugger that is more flexible
than a print statement.

>>    What I do use Boa for is
>> it's (as far as I am concerned) unmatched GUI creation ability.
>>
>> But it is showing its age.  Rust is creeping in.  And it's not keeping
>> up with the increasing control density of wxPython.  And I don't think
>> Riann (for WHATEVER reason) is willing/able to keep maintaining it.
>I won't speak for Riaan (I am pretty sure he is old enough for that:-) ) 
>but I am sure he cares but real live is just getting too much in the way 
>for our liking - i.e. he is very very busy on protects which pay his 
>food and roof etc and just doesn't have enough time to spend on Boa.
>
>I don't see anyone beside Riaan who is totally familiar with Boa and so 
>a "restart" without him does not make much sense.  I hope he will react 
>to my post in reaction to this thread on the Boa list.

And he shouldn't have to maintain it for the rest of his life.  That
is what Open Source is for, so that the community can maintain code as
necessary when the creator can't.

However, forking the code to another site might be the only option if
we don't obtain CVS write access to the code on sourceforge.  And my
favorite source control is Mercurial, because it's in Python. :)  It
also seems to be gaining a lot of traction in the Open Source world.

>> I've often thought of making my own GUI creation tool, like Visual
>> Studio's.  The amount of effort to get from zero to useful is beyond
>> my ability to devote time to it.  However, BOA is 90% there already. I
>> can spend the time helping to polish it up and bring it current with
>> wxPython 2.9.
>We really should take this Boa discussion onto the Boa list before 
>others here get feed up with us.

Done and done.

>> It's sad to see such a fantastic tool become, essentially,
>> abandonware.
>I would very much regret if Boa would be totally abandoned.

Me too...especially since it's the best GUI designer out there.

I'm going to re-download the latest CVS and do a little less haphazard
modding of it so that I can do a proof-of-concept patch for the list.

I would love to have Riann's blessing on this.  Boa is under the GPL
license, so we could fork without him, but I consider this to be
extremely rude (which is why I've gritted my teeth for five years).
However, I'd rather be rude than to see Boa wither on the vine.

I'm going to brush up on my Boa internals and see if I can integrate
the new wx.Button ability to contain an image.  Sort of a "hello
world" of modding Boa.  I'd also like to add all of the new AGW
controls.  One of the mods I've done with my hacked-up version of Boa
is the AquaButton control.  I'd like to do it in a more controlled
manner this time.

I'd like to know, if I start doing this stuff, will others pick up the
torch as well and help me.  Due to my own busy life (running a
business, going to school, and making indie films...yes, you heard
that right :) ) this effort to revitalize Boa will quickly fall apart
if it's just me doing it.

>Werner

Chris.

Re: [Boa Constr] Question on opinions...

[Werner F. B. <wer...@fr...>]

On 26/11/2010 11:53, Werner F. Bruhin wrote:
...
>
> Source code control
>
> I really believe that CVS is a big problem here, it's support for
> merges/branches etc is not good.  Windows 7 doesn't have a client which
> is officially maintained .......
>
> I use SVN for my own stuff but frankly wasn't impressed with it's merge
> support, also it is supposed to be getting better.  Will know in a
> couple of weeks when I merge my latest stuff back to the trunk.
>
>   From what I read/hear is that Git, Mercurial and Bazaar are doing a
> much better job in allowing to merge and resync with the base, i.e. to
> support distributed development.
>
> Branches would allow a contributor to make his/her changes in an
> isolated way, anyone could test it (without having to merge/patch) and
> when done it should be easy to create a patch and/or merge back to the
> main trunk or future version.
>
 From what I found it looks like Git would be the "front runner" for a 
change.

The following give I think a good overview on Git and how it compares to 
SVN and others.

http://whygitisbetterthanx.com/
https://git.wiki.kernel.org/index.php/GitSvnComparison

When I get a moment (probably in a week or two) I will look a bit closer 
at Git and actually try it out for my own stuff.

Werner

Re: [Boa Constr] [wxPython-users] Question on opinions...

[werner <wb...@fr...>]

Chris,

On 26/11/2010 20:43, Chris Spencer wrote:
> On Fri, 26 Nov 2010 10:46:55 +0100, werner<wb...@fr...>  wrote:
>> Adding new widgets can be done in two ways, either via the plug-in
>> support, see e.g. FlatNotebook-plug-in.py which I think I started and
>> Riaan fixed it up so it really worked;-) or via the "companions" support
>> see the sub-folder with the same name in Boa.
>>
>> Werner
> And I have used this technique from time to time.  I know how to add
> widgets for myself.  But why should everyone replicate my work to get
> the additional controls added to wxPython in the past 5 years or so?
Totally agree.

If you done any as plug-in's can you please post them to the Boa list as 
those anyone can just drop into the plug-in folder and they would be 
usable - o.k. they still won't make it into the next release until ....
> Would you not agree that it's better for a small group of people to
> add these controls and then release a Boa Constructor version with
> them integrated in?
>
> Frankly, I don't use Boa as a code editor or debugger.  I have other
> much more evolved code editors for that.
What are you using?  Wing IDE or?
>    What I do use Boa for is
> it's (as far as I am concerned) unmatched GUI creation ability.
>
> But it is showing its age.  Rust is creeping in.  And it's not keeping
> up with the increasing control density of wxPython.  And I don't think
> Riann (for WHATEVER reason) is willing/able to keep maintaining it.
I won't speak for Riaan (I am pretty sure he is old enough for that:-) ) 
but I am sure he cares but real live is just getting too much in the way 
for our liking - i.e. he is very very busy on protects which pay his 
food and roof etc and just doesn't have enough time to spend on Boa.

I don't see anyone beside Riaan who is totally familiar with Boa and so 
a "restart" without him does not make much sense.  I hope he will react 
to my post in reaction to this thread on the Boa list.
> I've often thought of making my own GUI creation tool, like Visual
> Studio's.  The amount of effort to get from zero to useful is beyond
> my ability to devote time to it.  However, BOA is 90% there already. I
> can spend the time helping to polish it up and bring it current with
> wxPython 2.9.
We really should take this Boa discussion onto the Boa list before 
others here get feed up with us.
> It's sad to see such a fantastic tool become, essentially,
> abandonware.
I would very much regret if Boa would be totally abandoned.

Werner

Re: [Boa Constr] Question on opinions...

[Werner F. B. <wer...@fr...>]

On 26/11/2010 10:47, werner wrote:
> This is going a bit OT for this list, hope others won't mind.
>
> I copy the Boa list, so specific stuff for Boa should probably move to
> there.
>
> On 26/11/2010 05:43, Chris Spencer wrote:
>> On Thu, 25 Nov 2010 23:08:57 -0500, C M<cmp...@gm...> wrote:
>>> Chris,
>>> What I'm wondering is: would it be possible to round up a a few
>>> people to help push Boa back into the 10s or whatever this decade is
>>> called? In terms of the controls, maybe we could take a look at what
>>> it is missing, determine the procedure for adding a control in, and
>>> divide the labor amongst a group of people over a period of months. I
>>> don't know how hard this is to do, but if it is a matter of a few
>>> hours per control, I would be willing to try a few if I could. Werner
>>> would probably be able to apprise people of what that entails.
>>>
>>> I'd also like to see an option for toggling Boa's creation of widget
>>> IDs, which I find unnecessary and cluttered (and instead assign them
>>> all -1), and another toggling of providing sizes to widgets if one is
>>> in "sizers mode" (which wouldn't affect you, since you don't use
>>> sizers).
>>>
>>> Beyond that, there are probably a lot of fun newer things that could
>>> be included.
>>> Che
>> First off, can you post a link to your tutorials. I've been using Boa
>> for nearly 10 years now (yeesh, I'm old). But I'm always up for
>> learning new things.
>>
>> Second, without "commit" rights on the Boa Constructor repository,
>> we'd HAVE to fork it in order to be able to distribute it. I'd love
>> to get the maintainer's permission to either fork it or get commit
>> rights to it.
>>
>> I'm also willing to put in a fairly decent amount of work to add
>> controls and do some general "fixing up". I wouldn't mind working
>> with others to accomplish this. I'm in agreement that it is the best
>> GUI designer/IDE out there right now, even in it dilapidated state. It
>> would be nice to shine it up and reintroduce it to the world.
>>
>> We could take this to private email. I also would like to know what
>> Werner thinks, since he's the main contact-man on all things Boa, and
>> has been for quite a few years.
> Having used Boa for the last 7 or 8 years for my shareware I would also
> like to see it "restart".
>
> I'll expand on what I think is needed for a "restart" on the Boa list
> later today.

I think a "restart" needs at a minimum:

- new web site, I would suggest a Sphinx (http://sphinx.pocoo.org/) 
type web site, i.e. an introduction/welcome page with links to the 
documentation which in turn also links to any tutorials and videos etc.

- regular releases, I think it needs one at least once a year better 
would be twice a year.  And this means not certainly lots of new 
features but just officially rolling out any fixes done since the last 
one, including adding in the up to date documentation for Python, 
wxPython etc.

- make it easier for others to contribute (see source code control 
below), document how things are done so maybe others then Riaan can do 
them (e.g. web site, documentation generation, release generation...).

- tutorial on adding a new widget would be really helpful


Source code control

I really believe that CVS is a big problem here, it's support for 
merges/branches etc is not good.  Windows 7 doesn't have a client which 
is officially maintained .......

I use SVN for my own stuff but frankly wasn't impressed with it's merge 
support, also it is supposed to be getting better.  Will know in a 
couple of weeks when I merge my latest stuff back to the trunk.

 From what I read/hear is that Git, Mercurial and Bazaar are doing a 
much better job in allowing to merge and resync with the base, i.e. to 
support distributed development.

Branches would allow a contributor to make his/her changes in an 
isolated way, anyone could test it (without having to merge/patch) and 
when done it should be easy to create a patch and/or merge back to the 
main trunk or future version.


I am sure there is more to it but I have to run for now.

Werner

Re: [Boa Constr] [wxPython-users] Question on opinions...

[Tim H. <zut...@gm...>]

Hi

I have been using Boa continuously for at least 8 years. It's great.

I do a lot of application development for appengine, and it actually
could be a good ide for that, along
with plugin support for doing deployments etc.....

I would like to see it move into current 10's ;-) and not wither on the vine.

Forks been mentioned a few times in the past, though nothing came of that.

One of the big advantages is boa is a lot more lightweight that say
eclipse, so I have often run it on low memory
machines running windows.  Also it doesn't have in your face project
management such as eclipse and
and a few of the other python dev environments.

Rgds

Tim

On Fri, Nov 26, 2010 at 5:47 PM, werner <wb...@fr...> wrote:
> This is going a bit OT for this list, hope others won't mind.
>
> I copy the Boa list, so specific stuff for Boa should probably move to
> there.
>
> On 26/11/2010 05:43, Chris Spencer wrote:
>> On Thu, 25 Nov 2010 23:08:57 -0500, C M<cmp...@gm...>  wrote:
>>> Chris,
>>> What I'm wondering is:  would it be possible to round up a a few
>>> people to help push Boa back into the 10s or whatever this decade is
>>> called?  In terms of the controls, maybe we could take a look at what
>>> it is missing, determine the procedure for adding a control in, and
>>> divide the labor amongst a group of people over a period of months.  I
>>> don't know how hard this is to do, but if it is a matter of a few
>>> hours per control, I would be willing to try a few if I could.  Werner
>>> would probably be able to apprise people of what that entails.
>>>
>>> I'd also like to see an option for toggling Boa's creation of widget
>>> IDs, which I find unnecessary and cluttered (and instead assign them
>>> all -1), and another toggling of  providing sizes to widgets if one is
>>> in "sizers mode" (which wouldn't affect you, since you don't use
>>> sizers).
>>>
>>> Beyond that, there are probably a lot of fun newer things that could
>>> be included.
>>> Che
>> First off, can you post a link to your tutorials.  I've been using Boa
>> for nearly 10 years now (yeesh, I'm old).  But I'm always up for
>> learning new things.
>>
>> Second, without "commit" rights on the Boa Constructor repository,
>> we'd HAVE to fork it in order to be able to distribute it.  I'd love
>> to get the maintainer's permission to either fork it or get commit
>> rights to it.
>>
>> I'm also willing to put in a fairly decent amount of work to add
>> controls and do some general "fixing up".  I wouldn't mind working
>> with others to accomplish this.  I'm in agreement that it is the best
>> GUI designer/IDE out there right now, even in it dilapidated state. It
>> would be nice to shine it up and reintroduce it to the world.
>>
>> We could take this to private email.  I also would like to know what
>> Werner thinks, since he's the main contact-man on all things Boa, and
>> has been for quite a few years.
> Having used Boa for the last 7 or 8 years for my shareware I would also
> like to see it "restart".
>
> I'll expand on what I think is needed for a "restart" on the Boa list
> later today.
>
> Werner
>
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> https://lists.sourceforge.net/lists/listinfo/boa-constructor-users
>

Re: [Boa Constr] [wxPython-users] Question on opinions...

[werner <wb...@fr...>]

This is going a bit OT for this list, hope others won't mind.

I copy the Boa list, so specific stuff for Boa should probably move to 
there.

On 26/11/2010 05:43, Chris Spencer wrote:
> On Thu, 25 Nov 2010 23:08:57 -0500, C M<cmp...@gm...>  wrote:
>> Chris,
>> What I'm wondering is:  would it be possible to round up a a few
>> people to help push Boa back into the 10s or whatever this decade is
>> called?  In terms of the controls, maybe we could take a look at what
>> it is missing, determine the procedure for adding a control in, and
>> divide the labor amongst a group of people over a period of months.  I
>> don't know how hard this is to do, but if it is a matter of a few
>> hours per control, I would be willing to try a few if I could.  Werner
>> would probably be able to apprise people of what that entails.
>>
>> I'd also like to see an option for toggling Boa's creation of widget
>> IDs, which I find unnecessary and cluttered (and instead assign them
>> all -1), and another toggling of  providing sizes to widgets if one is
>> in "sizers mode" (which wouldn't affect you, since you don't use
>> sizers).
>>
>> Beyond that, there are probably a lot of fun newer things that could
>> be included.
>> Che
> First off, can you post a link to your tutorials.  I've been using Boa
> for nearly 10 years now (yeesh, I'm old).  But I'm always up for
> learning new things.
>
> Second, without "commit" rights on the Boa Constructor repository,
> we'd HAVE to fork it in order to be able to distribute it.  I'd love
> to get the maintainer's permission to either fork it or get commit
> rights to it.
>
> I'm also willing to put in a fairly decent amount of work to add
> controls and do some general "fixing up".  I wouldn't mind working
> with others to accomplish this.  I'm in agreement that it is the best
> GUI designer/IDE out there right now, even in it dilapidated state. It
> would be nice to shine it up and reintroduce it to the world.
>
> We could take this to private email.  I also would like to know what
> Werner thinks, since he's the main contact-man on all things Boa, and
> has been for quite a few years.
Having used Boa for the last 7 or 8 years for my shareware I would also 
like to see it "restart".

I'll expand on what I think is needed for a "restart" on the Boa list 
later today.

Werner

Re: [Boa Constr] issues appears in my os!

[Werner F. B. <wer...@fr...>]

On 22/10/2010 13:13, benyu wrote:
> Thank your response!
>
> 1. Under the python27\lib\site-package\boa-constructor directory do : 
> python boa.py
> 2. Started the boa without any errors or warnings!
>
> 3. After that, i go on click the help button get flowing error ( in 
> details )
> 18:56:16: Traceback (most recent call last):
> 18:56:16:   File 
> "D:\Python27\Lib\site-packages\boa-constructor\Palette.py", line 224, 
> in OnHelpToolClick     Help.showMainHelp(self.paletteHelpItems['boa'])
> 18:56:16:   File 
> "D:\Python27\Lib\site-packages\boa-constructor\Help.py", line 261, in 
> showMainHelp     
> getHelpController().Display(bookname).ExpandBook(bookname)
> 18:56:16:   File 
> "D:\Python27\Lib\site-packages\boa-constructor\Help.py", line 323, in 
> Display     self.frameX = wxHelpFrameEx(self)
> 18:56:16:   File 
> "D:\Python27\Lib\site-packages\boa-constructor\Help.py", line 425, in 
> __init__     self.indexPanel.GetChildren()[:3]
> 18:56:16:   File 
> "D:\python27\lib\site-packages\wx-2.8-msw-unicode\wx\_core.py", line 
> 8367, in __getitem__     return _core_.WindowList___getitem__(*args, 
> **kwargs)
> 18:56:16: TypeError: in method 'WindowList___getitem__', expected 
> argument 2 of type 'size_t'
Now I remember, this was a problem caused by a change in wxPython 
2.8.4.2 which is fixed in the CVS version of Boa.
>
> 4. The top palette is also empty, so i create the new wx.app from the 
> toolbar of edit as the default way.
>
> 5. Saving the app1.py , form1.py to a certain directory, 
> then running the app1.py ok now (last time is running the form1.py).
>
> i will keep reading the tutorial!
Have fun
Werner

Re: [Boa Constr] issues appears in my os!

[Werner F. B. <wer...@fr...>]

Hi Benyu,

Can you please subscribe to the list on sourceforge, as otherwise it is 
blocked as spam.

On 22/10/2010 06:02, benyu wrote:
> Tow issues appears in my os!
> 1. After starting of the boa-Constructor then click on the help button
> on palette appears the Error:
> TypeError: in method 'windowlist__getitem__',expected argument 2 of type
> 'size_t'
Can you please provide the full traceback on this error.
>
> 2. Whatever type of window,form, or even the app are created, however,
> the palette always show empty where no any items like button,label or
> else like described as the doc or screenshot in boa-constructor site.
Are there no errors when you start Boa?  If you start it using 
pythonw.exe, can you please start it using python.exe (no "w") and let 
us know if there are any errors.
>
>
> 3. Finish the most simple sample by create the form from editor pannel,
> save and run the 'form' program fail with no any message or tips.
>
When you follow e.g. the Boa tutorial "Building your Frist Application" 
what happens after you created App1.py and Frame1.py when you try to run it?
>
> My configuration of python like below:
> OS: windows 7 ultimate
> Python: python2.7
> wxPython:wxPython2.8-win32-unicode-2.8.11.0-py27.exe
> boa-constructor:boa-constructor-0.6.1.src.win32.exe (from sf)
>
> Of course the demo from official   wxPython and other provider runs right!
>
I working with Py2.6 normally and don't see these issues.  I am doing 
some testing with Py 2.7 for none Boa stuff and just tried Boa with Py 
2.7 and I don't see these issues.

I am on Win 7 too but I use the CVS copy of Boa which contains a few 
corrections since 0.6.1 came out but not sure that this would be your 
problem.

Werner

[Boa Constr] issues appears in my os!

[benyu <mn...@gm...>]

Tow issues appears in my os!
1. After starting of the boa-Constructor then click on the help button on
palette appears the Error:
TypeError: in method 'windowlist__getitem__',expected argument 2 of type
'size_t'

2. Whatever type of window,form, or even the app are created, however, the
palette always show empty where no any items like button,label or else like
described as the doc or screenshot in boa-constructor site.


3. Finish the most simple sample by create the form from editor pannel, save
and run the 'form' program fail with no any message or tips.


My configuration of python like below:
OS: windows 7 ultimate
Python: python2.7
wxPython:wxPython2.8-win32-unicode-2.8.11.0-py27.exe
boa-constructor:boa-constructor-0.6.1.src.win32.exe (from sf)

Of course the demo from official   wxPython and other provider runs right!

[Boa Constr] Sizer tutorial

[Grant I. <gra...@sh...>]

Hi all.

I'm using Boa Constructor v.0.6.1 in OpenSuse 11.1 and am following the
tutorial on sizers. I've created the frame, plunked a panel on it, and
plunked the box sizer on the panel as instructed in the tutorial.

The next step to follow is to place a widget on the panel, but whenever
I do, Boa Constructor crashes. Any help would be greatly appreciated!

Grant.