pythoncard-users

[Pythoncard-users] Re: Pythoncard-users digest, Vol 1 #777 - 9 msgs

[jamesr <cir...@gm...>]

Hi - new voice on this list.. I am James in Maryland and having been
sucking up python card for about a month, to my great advantage. I
specialize in usuability issues, graphic design, and code like a crazy
monkey. (Take it all with grain of salt..)

The multiple layout windows i briefly read about above may be overkill
- but a widget that 'encapsulates' other widgets could be handy in
this case. A vaguish suggestion - a 'Group' Widget that takes as it
items a list of other widget names. Setting an attribute of this
widget changes the attributes (if they have it) of all listed widgets
connected to it  Immediately, I would use this to change the
visibility of groups of widgets with one call, but an ability to add
or subtract (relatively) from the position x and y from a group of
objects would be very handy too, as well as font or color. Anyone else
think of a use for this?

again, generally i'd use it to hide and show groups of widgets that
support different functionality in one window.

thanks, james, circlecycle'AT'gmail'dot'com

On Mon, 23 Aug 2004 20:41:08 -0700,
pyt...@li...
<pyt...@li...> wrote:
> Send Pythoncard-users mailing list submissions to
>         pyt...@li...
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/pythoncard-users
> or, via email, send a message with subject or body 'help' to
>         pyt...@li...
> 
> You can reach the person managing the list at
>         pyt...@li...
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Pythoncard-users digest..."
> 
> Today's Topics:
> 
>    1. Fwd: planned resourceEditor changes (Kevin Altis)
>    2. Re: #pythoncard irc channel on freenode (XXXXXXXXXXX)
>    3. Re: #pythoncard irc channel on freenode (Alex Tweedly)
>    4. Re: #pythoncard irc channel on freenode (Kevin Altis)
>    5. PythonCard 0.8 issues (was Re:  #pythoncard irc channel on freenode) (XXXXXXXXXXX)
>    6. Re: #pythoncard irc channel on freenode (XXXXXXXXXXX)
>    7. Multicolumn Lists (Tony Maniaci)
>    8. Re: PythonCard 0.8 issues (was Re:
>        #pythoncard irc channel on freenode) (Alex Tweedly)
> 
> --__--__--
> 
> Message: 1
> Date: Mon, 23 Aug 2004 10:45:03 -0700
> From: "Kevin Altis" <al...@se...>
> To: "pythoncard-Users" <pyt...@li...>
> Subject: [Pythoncard-users] Fwd: planned resourceEditor changes
> 
> --Apple-Mail-24--988212964
> Content-Transfer-Encoding: 7bit
> Content-Type: text/plain;
>         charset=US-ASCII;
>         format=flowed
> 
> I should have started this discussion on the list in the first place,
> but Alex is the only other person that has been working on
> resourceEditor changes, so I initially emailed him offlist. Feel free
> to chime in with ideas and comments.
> 
> I've already checked in the function wrappers for all the custom
> dialogs as well as changes to the Property Editor so that the user
> doesn't have to click the Update button to change an attribute. The
> auto-updating will be optional in the future, settable via a menu item
> in the Options menu.
> 
> If you are using PythonCard from cvs, you can keep up as changes are
> made. Unless a critical framework or tool bug pops up in 0.8 that
> requires a quick fix release, I expect the next version will be 0.8.1
> out sometime in late September or early October. The more feedback
> people give on 0.8, the easier it will be to focus on which items to do
> for 0.8.1.
> 
> Also see the to do lists on the wiki.
> 
> ka
> 
> Begin forwarded message:
> 
> > From: "Alex Tweedly" <al...@tw...>
> > Date: August 22, 2004 7:46:57 AM PDT
> > To: "Kevin Altis" <al...@se...>, "Alex Tweedly"
> > <al...@tw...>
> > Subject: Re: planned resourceEditor changes
> >
> > At 19:37 21/08/2004 -0700, Kevin Altis wrote:
> >
> >> Now that 0.8 is out I want to move forward with a number of
> >> resourceEditor changes. Since you've been working on the code I
> >> thought you might be interested in some of these. Obviously, if you
> >> would like to see some other changes, then it is good to know that
> >> I'm planning on mucking around and changing things.
> >>
> >> First of all, I keep debating back and forth on whether to support
> >> closeField and select (choice) and mouseClick (checkbox) for updating
> >> components instead of requiring the user to press the Update button.
> >> It is easy to support, so this might be a good choice for turning on
> >> with a preference and in the event handler just calling the update
> >> command to avoid much code change.
> >
> > What's the argument against doing this ?  Would anyone prefer to need
> > to press Update ?
> >
> >> 1. make sure all the custom dialogs are done with function wrappers
> >> for cleanliness sake
> >> 2 . switch to util.runScript
> >> 3. Refactor all the code ...  self.layoutWindow.
> >> 4. Move all the code for moving and dragging the components to a new
> >> layout class and module. It is probably possible to refactor a large
> >> number of the component manipulation commands so they all move to the
> >> new layout class.
> >
> > They sound good - the component manipulation stuff is a bit hard to
> > follow right now.
> >
> >> 4a. Make sure the layoutWindow displays the real menubar, that
> >> dialogs don't have extra vertical space like they do today because of
> >> the forced menubar, show statusbar, etc. if needed.
> >
> > Sounds good - though to be hones, not something I've had a problem
> > with.
> >
> >> 5. Assuming all of the above goes well, then it is time to start
> >> adding some new functionality. The next items are just ideas.
> >>
> >> 6. Add group selection functionality to all more than one item to be
> >> selected, then do alignment operations such as align left, align top,
> >> etc. as well as group moves. Setting attributes via the property
> >> editor would likely need to be disabled.
> >
> > Do you see groups as anything other than a mechanism of the
> > resourceEditor ? (i.e. like Revolution groups ?  or simply a way to
> > make move/alignment/distribution more convenient)
> >
> >> 8. Support multiple layout windows. This would be another refactor of
> >> item 3. I'm actually a bit hesitant about this change due to the
> >> confusion it might cause.
> >
> > Not sure I see a need for this.
> >
> >> 9. Add a palette for the components rather than having a menu of
> >> components. The palette doesn't have to be just bitmaps, it could be
> >> a wx.ListCtrl with the first column being an icon (if available) and
> >> the second column is the component name. Since the layoutWindow will
> >> be separate from the main window and menubar it might be best to roll
> >> the propertyEditor and palette into one main window? I haven't
> >> thought a lot about this.
> >
> > Palette of components sounds good - especially if you know someone who
> > can devise / draw suitable icons. Whether through a palette, or simply
> > from menu, I'd like to see automatic graphic positioning of newly
> > added components (not for copy/paste or edit/duplicate, just newly
> > created one). So when you select say Add/Button, it switches to a
> > different cursor type and allows you to press/drag/release to position
> > and size the button in one operation.  Given a palette, this can be
> > "sticky" after a doubleclick.
> >
> >> That's enough for now. Other ideas or things you think are pressing
> >> issues?
> >
> > Two pressing issues - but maybe too big for now .....
> >
> > 1. Sizer / geometry management.
> >
> > Haven't got a good handle on how this might be done - still playing
> > with sizers to see what's possible in wx.  But this is the biggest
> > missing feature, in IMHO, in the whole of PythonCard.
> >
> > (Well, maybe an integrated debugger is a bigger feature - but this is
> > certainly the biggest one with any connection to the resourceEditor).
> >
> > 2. Undo.
> >
> > This can be a can of worms, but it would be really nice. Not sure if
> > it's possible (or necessary) to make absolutely everything undo-able,
> > but at least simple component moves, adds, deletes?, and text edits.
> >
> > -- Alex.
> 
> --Apple-Mail-24--988212964
> Content-Transfer-Encoding: 7bit
> Content-Type: text/enriched;
>         charset=US-ASCII
> 
> I should have started this discussion on the list in the first place,
> but Alex is the only other person that has been working on
> resourceEditor changes, so I initially emailed him offlist. Feel free
> to chime in with ideas and comments.
> 
> I've already checked in the function wrappers for all the custom
> dialogs as well as changes to the Property Editor so that the user
> doesn't have to click the Update button to change an attribute. The
> auto-updating will be optional in the future, settable via a menu item
> in the Options menu.
> 
> If you are using PythonCard from cvs, you can keep up as changes are
> made. Unless a critical framework or tool bug pops up in 0.8 that
> requires a quick fix release, I expect the next version will be 0.8.1
> out sometime in late September or early October. The more feedback
> people give on 0.8, the easier it will be to focus on which items to
> do for 0.8.1.
> 
> Also see the to do lists on the wiki.
> 
> ka
> 
> Begin forwarded message:
> 
> <excerpt><bold><color><param>0000,0000,0000</param>From:
> </color></bold>"Alex Tweedly" <<al...@tw...>
> 
> <bold><color><param>0000,0000,0000</param>Date: </color></bold>August
> 22, 2004 7:46:57 AM PDT
> 
> <bold><color><param>0000,0000,0000</param>To: </color></bold>"Kevin
> Altis" <<al...@se...>, "Alex Tweedly" <<al...@tw...>
> 
> <bold><color><param>0000,0000,0000</param>Subject: </color>Re: planned
> resourceEditor changes
> 
> </bold>
> 
> At 19:37 21/08/2004 -0700, Kevin Altis wrote:
> 
> <excerpt>Now that 0.8 is out I want to move forward with a number of
> resourceEditor changes. Since you've been working on the code I
> thought you might be interested in some of these. Obviously, if you
> would like to see some other changes, then it is good to know that I'm
> planning on mucking around and changing things.
> 
> First of all, I keep debating back and forth on whether to support
> closeField and select (choice) and mouseClick (checkbox) for updating
> components instead of requiring the user to press the Update button.
> It is easy to support, so this might be a good choice for turning on
> with a preference and in the event handler just calling the update
> command to avoid much code change.
> 
> </excerpt>
> 
> What's the argument against doing this ?  Would anyone prefer to need
> to press Update ?
> 
> <excerpt>1. make sure all the custom dialogs are done with function
> wrappers for cleanliness sake
> 
> 2 . switch to util.runScript
> 
> 3. Refactor all the code ...  self.layoutWindow.
> 
> 4. Move all the code for moving and dragging the components to a new
> layout class and module. It is probably possible to refactor a large
> number of the component manipulation commands so they all move to the
> new layout class.
> 
> </excerpt>
> 
> They sound good - the component manipulation stuff is a bit hard to
> follow right now.
> 
> <excerpt>4a. Make sure the layoutWindow displays the real menubar,
> that dialogs don't have extra vertical space like they do today
> because of the forced menubar, show statusbar, etc. if needed.
> 
> </excerpt>
> 
> Sounds good - though to be hones, not something I've had a problem
> with.
> 
> <excerpt>5. Assuming all of the above goes well, then it is time to
> start adding some new functionality. The next items are just ideas.
> 
> 6. Add group selection functionality to all more than one item to be
> selected, then do alignment operations such as align left, align top,
> etc. as well as group moves. Setting attributes via the property
> editor would likely need to be disabled.
> 
> </excerpt>
> 
> Do you see groups as anything other than a mechanism of the
> resourceEditor ? (i.e. like Revolution groups ?  or simply a way to
> make move/alignment/distribution more convenient)
> 
> <excerpt>8. Support multiple layout windows. This would be another
> refactor of item 3. I'm actually a bit hesitant about this change due
> to the confusion it might cause.
> 
> </excerpt>
> 
> Not sure I see a need for this.
> 
> <excerpt>9. Add a palette for the components rather than having a menu
> of components. The palette doesn't have to be just bitmaps, it could
> be a wx.ListCtrl with the first column being an icon (if available)
> and the second column is the component name. Since the layoutWindow
> will be separate from the main window and menubar it might be best to
> roll the propertyEditor and palette into one main window? I haven't
> thought a lot about this.
> 
> </excerpt>
> 
> Palette of components sounds good - especially if you know someone who
> can devise / draw suitable icons. Whether through a palette, or simply
> from menu, I'd like to see automatic graphic positioning of newly
> added components (not for copy/paste or edit/duplicate, just newly
> created one). So when you select say Add/Button, it switches to a
> different cursor type and allows you to press/drag/release to position
> and size the button in one operation.  Given a palette, this can be
> "sticky" after a doubleclick.
> 
> <excerpt>That's enough for now. Other ideas or things you think are
> pressing issues?
> 
> </excerpt>
> 
> Two pressing issues - but maybe too big for now .....
> 
> 1. Sizer / geometry management.
> 
> Haven't got a good handle on how this might be done - still playing
> with sizers to see what's possible in wx.  But this is the biggest
> missing feature, in IMHO, in the whole of PythonCard.
> 
> (Well, maybe an integrated debugger is a bigger feature - but this is
> certainly the biggest one with any connection to the resourceEditor).
> 
> 2. Undo.
> 
> This can be a can of worms, but it would be really nice. Not sure if
> it's possible (or necessary) to make absolutely everything undo-able,
> but at least simple component moves, adds, deletes?, and text edits.
> 
> -- Alex.
> 
> </excerpt>
> --Apple-Mail-24--988212964--
> 
> --__--__--
> 
> Message: 2
> From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> To: "Pythoncard Users" <Pyt...@li...>
> Subject: Re: [Pythoncard-users] #pythoncard irc channel on freenode
> Date: Mon, 23 Aug 2004 21:48:47 +0100
> 
> On Fri, 20 Aug 2004 10:45:58 -0700, Kevin Altis wrote:
> 
> >Just a reminder that I'm still regularly hanging out on the pythoncard
> >irc channel on irc.freenode.net in case anyone cares.
> >
> 
> As somebody supporting an old legacy app, and banging his head against
> the wall trying to get my customers to use these fancy mailing lists and
> web site things I've painstakingly set up, I feel almost obliged to try
> this out so that your efforts at setting it up aren't in vain :-)
> 
> Saying that I've never used irc in my life! I'm even more a newbie with
> it than PythonCard and Python (one month and counting for the latter two).
> 
> I've actually got a few little bugs/enhancement requests to report,
> mainly in the resource editor, that I wouldn't mind others trying to
> duplicate. Is the irc a good mechanism to use, or posting to this mailing
> list?
> 
> Neil
> 
> --__--__--
> 
> Message: 3
> Date: Mon, 23 Aug 2004 22:07:08 +0100
> To: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX,
>  "Pythoncard Users" <Pyt...@li...>
> From: Alex Tweedly <al...@tw...>
> Subject: Re: [Pythoncard-users] #pythoncard irc channel on freenode
> 
> --=======12D33E95=======
> Content-Type: text/plain; x-avg-checked=avg-ok-29AB195; charset=us-ascii; format=flowed
> Content-Transfer-Encoding: 8bit
> 
> At 21:48 23/08/2004 +0100, XXXXXXXXXXX wrote:
> 
> >On Fri, 20 Aug 2004 10:45:58 -0700, Kevin Altis wrote:
> >
> > >Just a reminder that I'm still regularly hanging out on the pythoncard
> > >irc channel on irc.freenode.net in case anyone cares.
> > >
> >
> >As somebody supporting an old legacy app, and banging his head against
> >the wall trying to get my customers to use these fancy mailing lists and
> >web site things I've painstakingly set up, I feel almost obliged to try
> >this out so that your efforts at setting it up aren't in vain :-)
> >
> >Saying that I've never used irc in my life! I'm even more a newbie with
> >it than PythonCard and Python (one month and counting for the latter two).
> >
> >I've actually got a few little bugs/enhancement requests to report,
> >mainly in the resource editor, that I wouldn't mind others trying to
> >duplicate. Is the irc a good mechanism to use, or posting to this mailing
> >list?
> 
> I'd suggest posting them to this list. IRC can be a good place to discuss
> them if needed, but it's worth having them described on the mailing list so
> that everyone can see them even if they don't happen to be on irc at the
> right time.
> 
> Of course, sometimes irc will give you an almost immediate answer - but
> even then it's good to post a summary to the list to make the knowledge
> more available to others.
> 
> -- Alex.
> 
> --=======12D33E95=======--
> 
> --__--__--
> 
> Message: 4
> Date: Mon, 23 Aug 2004 14:02:35 -0700
> From: "Kevin Altis" <al...@se...>
> To: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> Cc: "Pythoncard Users" <Pyt...@li...>
> Subject: Re: [Pythoncard-users] #pythoncard irc channel on freenode
> 
> On Aug 23, 2004, at 1:48 PM, XXXXXXXXXXX wrote:
> 
> > On Fri, 20 Aug 2004 10:45:58 -0700, Kevin Altis wrote:
> >
> >> Just a reminder that I'm still regularly hanging out on the pythoncard
> >> irc channel on irc.freenode.net in case anyone cares.
> >>
> >
> > As somebody supporting an old legacy app, and banging his head against
> > the wall trying to get my customers to use these fancy mailing lists
> > and
> > web site things I've painstakingly set up, I feel almost obliged to try
> > this out so that your efforts at setting it up aren't in vain :-)
> >
> > Saying that I've never used irc in my life! I'm even more a newbie with
> > it than PythonCard and Python (one month and counting for the latter
> > two).
> >
> > I've actually got a few little bugs/enhancement requests to report,
> > mainly in the resource editor, that I wouldn't mind others trying to
> > duplicate. Is the irc a good mechanism to use, or posting to this
> > mailing
> > list?
> >
> > Neil
> >
> 
> Questions should generally go to the list, but feel free to ask over on
> the irc channel as well. If you are using Windows, mIRC is a pretty
> popular irc client. Over on Mac OS X I recommend Colloquy.
> 
> http://www.irchelp.org/
> 
> http://www.mirc.com/
> 
> http://www.colloquy.info/
> 
> The server is irc.freenode.net and the channel is #pythoncard. You
> don't type the leading # when joining the channel.
> 
> http://freenode.net/
> 
> Finally, if you've found a bug or behavior problem, then I suggest
> upgrading to wxPython 2.5.2.7 and PythonCard 0.8 and following the
> migration guide to update your code to see if that fixes the problem.
> 
> ka
> 
> --__--__--
> 
> Message: 5
> From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> To: "Pythoncard Users" <Pyt...@li...>
> Date: Mon, 23 Aug 2004 23:32:57 +0100
> Subject: [Pythoncard-users] PythonCard 0.8 issues (was Re:  #pythoncard irc channel on freenode)
> 
> On Mon, 23 Aug 2004 22:07:08 +0100, Alex Tweedly wrote:
> 
> >
> >I'd suggest posting them to this list. IRC can be a good place to discuss
> >them if needed, but it's worth having them described on the mailing list so
> >that everyone can see them even if they don't happen to be on irc at the
> >right time.
> >
> 
> OK, here are a few minor things I've discovered running 0.8 following my
> upgrade to the latest versions of everything on Friday. Let's see if
> anybody else can replicate these or agree/disagree. I think I've checked
> all the to-do and known bug lists, but if not please don't shout - I'm a
> newbie!
> 
> Unless I say otherwise, assume this applies to the OS X and Win32 versions...
> 
> 1) Documentation - the on-line stuff is duplicated in the PythonCard/
> docs/html directory, but if I try to click on a link to any of the
> component descriptions they're not there. The components directory is
> missing. Not a huge problem when I have ADSL, but the one time I was
> network-less I tried using the docs and discovered this.
> 
> 2) Typo - in the resource editor when you duplicate a component the
> offset widgets are spelt wrong - "Offest Horizontally", etc. :-)
> 
> 3) Image path - this follows on from an observation I made recently. When
> you select an image in the background dialog you can use the file browser
> to track it down, but in the resource file the path is never stored and
> therefore the image fails to load unless it's in the same directory as
> the resource file.
> 
> Now why you'd want to locate the image somewhere other than the current
> directory I couldn't say...
> 
> 4) Colour...oops...Color picker - could this open with the property's
> current value? At the moment it always starts with black. Just makes it
> easier to make a minor color shift and makes the OS X color picker look
> better when it opens.
> 
> Nothing earth-shattering, I admit, but a start.
> 
> Neil
> 
> --__--__--
> 
> Message: 6
> From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> To: "Pythoncard Users" <Pyt...@li...>
> Subject: Re: [Pythoncard-users] #pythoncard irc channel on freenode
> Date: Mon, 23 Aug 2004 23:33:00 +0100
> 
> On Mon, 23 Aug 2004 14:02:35 -0700, Kevin Altis wrote:
> 
> >Questions should generally go to the list, but feel free to ask over on
> >the irc channel as well. If you are using Windows, mIRC is a pretty
> >popular irc client. Over on Mac OS X I recommend Colloquy.
> >
> 
> Thanks. Since it's getting late this side of the pond I'll put the issues
> in my next email rather than try and get irc working (I will try and use
> it eventually). Then when I wake up tomorrow morning I can be braced for
> the replies ;-)
> 
> >
> >Finally, if you've found a bug or behavior problem, then I suggest
> >upgrading to wxPython 2.5.2.7 and PythonCard 0.8 and following the
> >migration guide to update your code to see if that fixes the problem.
> 
> Sorry, I should have pointed out that I'm already running these versions
> - I upgraded on Friday on OS X and NT 4. Both went without a hitch. The
> OS X version seems to running quite a bit faster than before (starting
> the editors in particular), though I did have to restart my machine today
> so maybe that's responsible.
> 
> Neil
> 
> --__--__--
> 
> Message: 7
> To: Pythoncard users <pyt...@li...>
> From: Tony Maniaci <tma...@tr...>
> Date: Mon, 23 Aug 2004 16:33:14 -0700
> Subject: [Pythoncard-users] Multicolumn Lists
> 
> Hi,
> 
> Is there a way to set a multicolumn list editable?
> 
> --__--__--
> 
> Message: 8
> Date: Tue, 24 Aug 2004 00:47:55 +0100
> To: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX,
>  "Pythoncard Users" <Pyt...@li...>
> From: Alex Tweedly <al...@tw...>
> Subject: Re: [Pythoncard-users] PythonCard 0.8 issues (was Re:
>   #pythoncard irc channel on freenode)
> 
> --=======75153FE8=======
> Content-Type: text/plain; x-avg-checked=avg-ok-29AB195; charset=us-ascii; format=flowed
> Content-Transfer-Encoding: 8bit
> 
> At 23:32 23/08/2004 +0100, XXXXXXXXXXX wrote:
> 
> >2) Typo - in the resource editor when you duplicate a component the
> >offset widgets are spelt wrong - "Offest Horizontally", etc. :-)
> 
> Gee, I can't have run that more than what - 400, 500 times ?
> 
> Fix on its way into CVS as I type ... please don't add "spellchecker" to
> your list of suggestions :-)
> 
> Thanks,
> -- Alex.
> 
> --=======75153FE8=======--
> 
> --__--__--
> 
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users
> 
> End of Pythoncard-users Digest
>

Re: [Pythoncard-users] Re: Pythoncard-users digest, Vol 1 #777 - 9 msgs

[Kevin A. <al...@se...>]

On Aug 23, 2004, at 11:58 PM, jamesr wrote:

> Hi - new voice on this list.. I am James in Maryland and having been
> sucking up python card for about a month, to my great advantage. I
> specialize in usuability issues, graphic design, and code like a crazy
> monkey. (Take it all with grain of salt..)
>
> The multiple layout windows i briefly read about above may be overkill
> - but a widget that 'encapsulates' other widgets could be handy in
> this case. A vaguish suggestion - a 'Group' Widget that takes as it
> items a list of other widget names. Setting an attribute of this
> widget changes the attributes (if they have it) of all listed widgets
> connected to it  Immediately, I would use this to change the
> visibility of groups of widgets with one call, but an ability to add
> or subtract (relatively) from the position x and y from a group of
> objects would be very handy too, as well as font or color. Anyone else
> think of a use for this?
>
> again, generally i'd use it to hide and show groups of widgets that
> support different functionality in one window.
>
> thanks, james, circlecycle'AT'gmail'dot'com

If you want to do something like this today I suggest making a list of 
the component names that you can then do an operation on. For 
example...

group = ['btnOne', 'btnTwo', 'fldOne', 'someList']
for c in group:
     self.components[c].visible = False

...could be used to make all the components in the "group" hidden. 
Rather than string names you could just as easily use the actual 
component references, it just depends on what you prefer. If you want 
to make this more generic then use setattr within a function that takes 
the group list, attribute name, and value as parameters.

def groupChange(self, group, attribute, value):
     for name in group:
         setattr(self.components[name], attribute, value)

attribute is a string like 'visible'.

ka

Re: [Pythoncard-users] Re: Pythoncard-users digest, Vol 1 #777 - 9 msgs

[Alex T. <al...@tw...>]

I was reviewing old email (aka "tidying up") and realized I hadn't sent my 
reply to this - so apologies for replying kind o flate.

At 00:28 24/08/2004 -0700, Kevin Altis wrote:

>On Aug 23, 2004, at 11:58 PM, jamesr wrote:
>
>>The multiple layout windows i briefly read about above may be overkill
>>- but a widget that 'encapsulates' other widgets could be handy in
>>this case. A vaguish suggestion - a 'Group' Widget that takes as it
>>items a list of other widget names. Setting an attribute of this
>>widget changes the attributes (if they have it) of all listed widgets
>>connected to it  Immediately, I would use this to change the
>>visibility of groups of widgets with one call, but an ability to add
>>or subtract (relatively) from the position x and y from a group of
>>objects would be very handy too, as well as font or color. Anyone else
>>think of a use for this?
>
>If you want to do something like this today I suggest making a list of the 
>component names that you can then do an operation on. For example...
>
>group = ['btnOne', 'btnTwo', 'fldOne', 'someList']
>for c in group:
>     self.components[c].visible = False
>
>...could be used to make all the components in the "group" hidden. Rather 
>than string names you could just as easily use the actual component 
>references, it just depends on what you prefer. If you want to make this 
>more generic then use setattr within a function that takes the group list, 
>attribute name, and value as parameters.
>
>def groupChange(self, group, attribute, value):
>     for name in group:
>         setattr(self.components[name], attribute, value)
>
>attribute is a string like 'visible'.

The advantage of James's suggestion is that it is a resourceEditor change, 
rather than a code editor change, to add or subtract items from the "group".

So I'll suggest using an invisible component (say a StaticBox -  which 
could more or less surround the relevant components) and store the list of 
component names in its "userdata". The change to the code suggested are 
obvious, but his moves it out to something you change in the resource Editor.

-- Alex.