Getting a control to expand on only one axis

Hi to all Reviewers and readers. Sorry for the long hiatus in
preparing the draft of the new BoxSizer Tutorial wiki page (s).
The first 4 pages are ready for testing and general review. The main
page is:

    [BoxSizerFromTheGroundUp](http://wiki.wxpython.org/BoxSizerFromTheGroundUp)

I am starting a new thread specifically for the purpose of

communication during the review of the wiki pages. Please reply to
this post in that thread: It is titled:

    BoxSizerFromTheGroundUp wiki page development

The first post will be the contents of this post.

Development Status:

The first 4 pages are ready for testing and general review. The

first page is rather long, but I haven’t figured out how to break it
up and still show complete demos. It’s no wonder that so many people
have difficulty with with it being as complicated as it is.

The 5th page is half finished at this point. Writing is going

quickly to my own amazement. I anticipate only one more page unless
I’ve overlooked some important feature that I’m not aware.

All corrections and suggestions are welcome. **      Please be

constructive with your comments.** Keep in mind that much of the
“official” BoxSizer documentation (not tutorials) seems to be
haphazardly thrown together as afterthoughts. So, I’ve had to make
guesses about some specific parameters.

I have to say that there needs to be a wiki page on       constructing

wiki pages ! The documentation that is there is OK, but
there’s no guide concerning “how to get things done” when creating a
page. Also, the documentation clearly states that code blocks
will use a monospaced font . This is clearly wrong and
disappointing. The way I tend to write code is by aligning
sequential lines of similar call parameters by their columns. This
style makes it very easy to identify which parameters have changed
and which remain the same. This appearance is much more difficult
using a kerned (variable width) font. Otherwise, I’ve finally got
the hang of editing in an efficient manner.

Ray Pasco

Ray,

I’ve reviewed the first page and attached same as a PDF.
Haven’t tried to run the code.

My comments are in yellow between ** and **.

My suggested changes, caught typos, etc. are in yellow or yellow with strikethrough.

I’ll get to the other pages soon.

I do note that one thing you haven’t (yet) covered is sizer
nesting inside a panel inside a panel. wx.EXPAND comes into play there, too.

Al

BoxSizerFromTheGroundUp.pdf (248 KB)

···

From: wxpython-users@googlegroups.com
[mailto:wxpython-users@googlegroups.com] On Behalf Of Ray Pasco
Sent: Tuesday, September 28, 2010 12:46 AM
To: Wxpython Users
Subject: [wxPython-users] Getting a control to expand on only one axis

Hi to all Reviewers and
readers. Sorry for the long hiatus in preparing the draft of the new
BoxSizer Tutorial wiki page
(s). The first 4 pages are ready for testing and
general review. The main page is:
BoxSizerFromTheGroundUp
I am starting a new thread specifically for the purpose of communication during
the review of the wiki pages. Please reply to this post in that
thread: It is titled:
BoxSizerFromTheGroundUp wiki page development
The first post will be the contents of this post.
Development Status:
The first 4 pages are ready for testing and general review. The first page is
rather long, but I haven’t figured out how to break it up and still show
complete demos. It’s no wonder that so many people have difficulty with with it
being as complicated as it is.
The 5th page is half finished at this point. Writing is going quickly to my own
amazement. I anticipate only one more page unless I’ve overlooked some
important feature that I’m not aware.
All corrections and suggestions are welcome. Please be constructive with
your comments.
Keep in mind that much of the “official” BoxSizer
documentation (not tutorials) seems to be haphazardly thrown together as
afterthoughts. So, I’ve had to make guesses about some specific parameters.

I have to say that there needs to be a wiki page on constructing wiki pages
! The documentation that is there is OK, but there’s no guide concerning
“how to get things done” when creating a page. Also, the
documentation clearly states that code blocks will use a monospaced font.
This is clearly wrong and disappointing. The way I tend to write code is by
aligning sequential lines of similar call parameters by their columns. This
style makes it very easy to identify which parameters have changed and which
remain the same. This appearance is much more difficult using a kerned
(variable width) font. Otherwise, I’ve finally got the hang of editing in an
efficient manner.

Ray Pasco


To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en

part 2,3,4,5

Al

ControlsPadding.pdf (119 KB)

ControlsResizing.pdf (196 KB)

NestedBoxSizers.pdf (201 KB)

DivideAndConquer.pdf (92.4 KB)

···

From: wxpython-users@googlegroups.com
[mailto:wxpython-users@googlegroups.com] On Behalf Of Al Mansur
Sent: Wednesday, September 29, 2010 12:51 PM
To: wxpython-users@googlegroups.com
Subject: RE: [wxPython-users] Getting a control to expand on only one
axis

Ray,

I’ve reviewed the first page and attached same as a PDF.
Haven’t tried to run the code.

My comments are in yellow between ** and **.

My suggested changes, caught typos, etc. are in yellow or yellow with strikethrough.

I’ll get to the other pages soon.

I do note that one thing you haven’t (yet) covered is sizer
nesting inside a panel inside a panel. wx.EXPAND comes into play there, too.

Al

From: wxpython-users@googlegroups.com
[mailto:wxpython-users@googlegroups.com] On Behalf Of Ray Pasco
Sent: Tuesday, September 28, 2010 12:46 AM
To: Wxpython Users
Subject: [wxPython-users] Getting a control to expand on only one axis

Hi to all Reviewers and
readers. Sorry for the long hiatus in preparing the draft of the new BoxSizer
Tutorial wiki page
(s). The first 4 pages are ready for testing and general
review. The main page is:
BoxSizerFromTheGroundUp
I am starting a new thread specifically for the purpose of communication during
the review of the wiki pages. Please reply to this post in that
thread: It is titled:
BoxSizerFromTheGroundUp wiki page development
The first post will be the contents of this post.
Development Status:
The first 4 pages are ready for testing and general review. The first page is
rather long, but I haven’t figured out how to break it up and still show
complete demos. It’s no wonder that so many people have difficulty with with it
being as complicated as it is.
The 5th page is half finished at this point. Writing is going quickly to my own
amazement. I anticipate only one more page unless I’ve overlooked some
important feature that I’m not aware.
All corrections and suggestions are welcome. Please be constructive with
your comments.
Keep in mind that much of the “official” BoxSizer
documentation (not tutorials) seems to be haphazardly thrown together as
afterthoughts. So, I’ve had to make guesses about some specific parameters.

I have to say that there needs to be a wiki page on constructing wiki pages
! The documentation that is there is OK, but there’s no guide concerning
“how to get things done” when creating a page. Also, the
documentation clearly states that code blocks will use a monospaced font.
This is clearly wrong and disappointing. The way I tend to write code is by
aligning sequential lines of similar call parameters by their columns. This
style makes it very easy to identify which parameters have changed and which
remain the same. This appearance is much more difficult using a kerned
(variable width) font. Otherwise, I’ve finally got the hang of editing in an
efficient manner.

Ray Pasco


To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en


To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en

From: wxpython-users@googlegroups.com
[On Behalf Of Al Mansur
Sent: Wednesday, September 29, 2010 12:51 PM

I've reviewed the first page and attached same as a PDF. Haven't tried to
run the code.

My comments are in yellow between ** and **.

My suggested changes, caught typos, etc. are in yellow or yellow with
strikethrough.

I'll get to the other pages soon.

Thank you very much for the detailed editing.

I do note that one thing you haven't (yet) covered is sizer nesting inside a
panel inside a panel. wx.EXPAND comes into play there, too.

Al

A great suggestion ! I'll see what I can whip up and add. Besides,
more kinds of controls used will make the tutorial visually more
interesting.

Thanks for all your suggestions.

Ray