wxPython: Should you use a master sizer object?

[John Salerno]

Sorry for posting here again. I tried the wxPython list but I'm not sure
I'm sending to the right email address! It bounced back. Besides, your
opinions are too good to pass up. ;)

My question was:

I was wondering, is it recommended to always have a top-level sizer in
which you place all other sizers, or is it acceptable to have mulitple
sizers that are not grouped together?

[Steve Holden]

Re: wxPython: Should you use a master sizer object?

John Salerno wrote:[color=blue]
> Sorry for posting here again. I tried the wxPython list but I'm not sure
> I'm sending to the right email address! It bounced back. Besides, your
> opinions are too good to pass up. ;)
>
> My question was:
>
> I was wondering, is it recommended to always have a top-level sizer in
> which you place all other sizers, or is it acceptable to have mulitple
> sizers that are not grouped together?[/color]

You should definitely create a master sizer, and then add sub-sizers to it.

regards
Steve
--
Steve Holden +44 150 684 7255 +1 800 494 3119
Holden Web LLC/Ltd http://www.holdenweb.com
Love me, love my blog http://holdenweb.blogspot.com
Recent Ramblings http://del.icio.us/steve.holden

[John Salerno]

Re: wxPython: Should you use a master sizer object?

Steve Holden wrote:[color=blue]
> John Salerno wrote:[color=green]
>> Sorry for posting here again. I tried the wxPython list but I'm not sure
>> I'm sending to the right email address! It bounced back. Besides, your
>> opinions are too good to pass up. ;)
>>
>> My question was:
>>
>> I was wondering, is it recommended to always have a top-level sizer in
>> which you place all other sizers, or is it acceptable to have mulitple
>> sizers that are not grouped together?[/color]
>
> You should definitely create a master sizer, and then add sub-sizers to it.[/color]

Thanks. Also, I just found out that a Frame can't have more than one
sizer in it, meaning if you need multiple sizers you *have* to create a
master sizer first to nest the others. Now it's just a matter of
figuring out *how* to use them! I don't want to fall into the trap of
using them the way you can use the <table> element to lay out a form in
HTML...

[Steve Holden]

Re: wxPython: Should you use a master sizer object?

John Salerno wrote:[color=blue]
> Steve Holden wrote:
>[color=green]
>>John Salerno wrote:
>>[color=darkred]
>>>Sorry for posting here again. I tried the wxPython list but I'm not sure
>>>I'm sending to the right email address! It bounced back. Besides, your
>>>opinions are too good to pass up. ;)
>>>
>>>My question was:
>>>
>>>I was wondering, is it recommended to always have a top-level sizer in
>>>which you place all other sizers, or is it acceptable to have mulitple
>>>sizers that are not grouped together?[/color]
>>
>>You should definitely create a master sizer, and then add sub-sizers to it.[/color]
>
>
> Thanks. Also, I just found out that a Frame can't have more than one
> sizer in it, meaning if you need multiple sizers you *have* to create a
> master sizer first to nest the others. Now it's just a matter of
> figuring out *how* to use them! I don't want to fall into the trap of
> using them the way you can use the <table> element to lay out a form in
> HTML...[/color]

There doesn't seem to be any really usable material to help beginners. A
recursive design approach seems best, breaking down each grouping, but I
have sometimes found it difficult to adapt a design to changes.

Although I'm a big fan of open source I must confess that to solve this
problem I eventually bought a copy of wxDesigner, which while not
perfect does help quite a lot, and allows cut/copy and paste of design
elements.

regards
Steve
--
Steve Holden +44 150 684 7255 +1 800 494 3119
Holden Web LLC/Ltd http://www.holdenweb.com
Love me, love my blog http://holdenweb.blogspot.com
Recent Ramblings http://del.icio.us/steve.holden

[John Salerno]

Re: wxPython: Should you use a master sizer object?

Steve Holden wrote:
[color=blue]
> There doesn't seem to be any really usable material to help beginners. A
> recursive design approach seems best, breaking down each grouping, but I
> have sometimes found it difficult to adapt a design to changes.
>
> Although I'm a big fan of open source I must confess that to solve this
> problem I eventually bought a copy of wxDesigner, which while not
> perfect does help quite a lot, and allows cut/copy and paste of design
> elements.[/color]

Yeah, it would be nice to use something like wxDesigner eventually, but
right now I'd like to learn how to write it all by hand, so I can know
what's going on.

There are a couple of screencasts about using sizers with Dabo that are
helpful, even though it's specific to that designer. It still shows how
to layout nested sizers, for example.

[Morpheus]

Re: wxPython: Should you use a master sizer object?

IIRC the wx dox contain stuff about sizers too. It's definitly worth to get
into this stuff. Once you are used to sizers, you don't want to miss them
anymore.

HTH
Morpheus


"John Salerno" <johnjsal@NOSPA Mgmail.com> wrote in message
news:448b25e4$0 $9428$c3e8da3@n ews.astraweb.co m...[color=blue]
> Steve Holden wrote:
>[color=green]
> > There doesn't seem to be any really usable material to help beginners. A
> > recursive design approach seems best, breaking down each grouping, but I
> > have sometimes found it difficult to adapt a design to changes.
> >
> > Although I'm a big fan of open source I must confess that to solve this
> > problem I eventually bought a copy of wxDesigner, which while not
> > perfect does help quite a lot, and allows cut/copy and paste of design
> > elements.[/color]
>
> Yeah, it would be nice to use something like wxDesigner eventually, but
> right now I'd like to learn how to write it all by hand, so I can know
> what's going on.
>
> There are a couple of screencasts about using sizers with Dabo that are
> helpful, even though it's specific to that designer. It still shows how
> to layout nested sizers, for example.[/color]