pythoncard-users — PythonCard Users and Developers

[Pythoncard-users] Custom Event Handlers in 0.8

[Phil E. <ph...@li...>]

I've been using a custom event handler in one of my PythonCard apps, as 
follows:

    wx.EVT_LEFT_UP(self.components.versionString, self.on_multiSelect)

I've changed this to:

    wxEVT_LEFT_UP(self.components.versionString, self.on_multiSelect)

the on_multiSelect() function doesn't do anything earth shattering:

    def on_multiSelect(self, event):
        if event.controlDown: self.need2Add = 1

The flag that's being set is dealt with elsewhere in the code.

I get an exception thrown when starting the program:

Traceback (most recent call last):
  File "./pimp.py", line 59, in on_initialize
    wxEVT_LEFT_UP(self.components.versionString, self.on_multiSelect)
TypeError: 'int' object is not callable

The migration guide tells me I should post event binding issues to the mailing 
list, so here I am... :-)





-- 

Regards

Phil Edwards
Brighton, UK

Re: [Pythoncard-users] List problem in 0.8

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

At 09:44 25/08/2004 -0700, Kevin Altis wrote:

>Well the old way was to use a selection or selected attribute and 
>sometimes one of those did dual-duty by checking the input arg on 'set' 
>which allowed you to pass in a string or integer, but of course the 'get' 
>version could only return one type. To make matters worse, not all the 
>components used the attribute names in the same way. This was just one of 
>those issues that existed from some of the earliest versions of the 
>prototype and I kept putting off making all the components consistent. I 
>would have to go back and look at every component and compare them to the 
>0.8 components to document all the variations and frankly I would rather 
>fix bugs or add new functionality.

>I think the short story is that if you were using a method or attribute 
>related to selection or selected then you should probably just be using 
>selection or stringSelection now and you have to look at your source and 
>resource files to update them.

I don't think there's any need to document each of the changes - but the 
relevant paragraph in the migration guide needs to be a bit simpler for 
those who (like me) didn't necessarily fully understand what they had 
before (i.e. we had copied an example or another bit of code).

The migration guide mentioned the 'selected' and 'selection' attributes 
needing to be changed - so it maybe wasn't obvious that GetSelectionIndex( 
) and GetSelection() would also need to be changed.

How about ....
>The Choice, ComboBox, List, RadioGroup components were updated to use
>'selection' and 'stringSelection' attributes instead of
>mixed-capability 'selected' and 'selection' attributes. If you were
>using these attributes previously, you will have to update both your
>source and resource files.
.... add ....
The correct way to get the result of a selection now is to use either the 
attribute 'selection' to retrieve the integer index, or 'stringSelection' 
for the text value; if you previously used functions such as GetSelection() 
or GetSelectionIndex() these need to be changed to use the attributes directly.

>What I think I will do is turn the migration_guide.txt file into HTML 
>using the reStructuredText format and stick that on the main documentation 
>page so fewer people miss it.

That will definitely be a good thing, but in this case both Adrian and I 
had read the migration guide and didn't appreciate the import of what it 
was telling us.

-- Alex.

Re: [Pythoncard-users] List problem in 0.8

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

On Aug 25, 2004, at 9:20 AM, Alex Tweedly wrote:

>  Kevin, I must have read that paragraph a dozen times in trying to=20
> answer Adrian's question - and I just didn't "get it", and I'm not=20
> sure I do yet.
>
>  Could I suggest adding an additional paragraph that says (IF this is=20=

> correct)
>
>  So for example,
> =A0=A0=A0=A0=A0=A0 0.7 and earlier=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 0.8
>  =A0 list.getSelectionIndex()=A0=A0=A0=A0=A0=A0=A0=A0 list.selection
>  =A0 list.getSelection()=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
list.stringSelection
>  =A0 list.selection=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
 list.selection
> etc. if more are needed to clarify it.
>
Well the old way was to use a selection or selected attribute and=20
sometimes one of those did dual-duty by checking the input arg on 'set'=20=

which allowed you to pass in a string or integer, but of course the=20
'get' version could only return one type. To make matters worse, not=20
all the components used the attribute names in the same way. This was=20
just one of those issues that existed from some of the earliest=20
versions of the prototype and I kept putting off making all the=20
components consistent. I would have to go back and look at every=20
component and compare them to the 0.8 components to document all the=20
variations and frankly I would rather fix bugs or add new=20
functionality.

I think the short story is that if you were using a method or attribute=20=

related to selection or selected then you should probably just be using=20=

selection or stringSelection now and you have to look at your source=20
and resource files to update them.

What I think I will do is turn the migration_guide.txt file into HTML=20
using the reStructuredText format and stick that on the main=20
documentation page so fewer people miss it.

ka

Re: [Pythoncard-users] List problem in 0.8

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

On Aug 25, 2004, at 3:57 AM, Alex Tweedly wrote:

> At 08:37 25/08/2004 +0100, Adrian Smith wrote:
>
>> However the second problem I have yet to resolve.
>> I use .list.getSelectionIndex() which was fine in 0.7.3.1 but now the
>> program falls over at that point saying
>>
>> AttributeError: 'List' object has no attribute 'getSelectionIndex'
>>
>> I had a look at the components doc but it still says use 
>> getSelectionIndex.
>>
>> What is the new variation of this command?
>
> I don't have a 0.7.3 on here any more to check completely, but I'm 99% 
> sure if should be
> list.GetSelection()
>
That is the wxPython method name and that is what getSelectionIndex 
used to wrap. PythonCard now uses the attributes selection for the 
integer index and stringSelection for the string selection. These are 
defined in the ContainerMixin class in components/list.py.

 From the migration_guide.txt:
"""
selection and stringSelection Attributes
The Choice, ComboBox, List, RadioGroup components were updated to use 
'selection' and 'stringSelection' attributes instead of 
mixed-capability 'selected' and 'selection' attributes. If you were 
using these attributes previously, you will have to update both your 
source and resource files.
"""

In addition, though you can use selection for manipulating a live 
component, the spec for the components above only defines 
stringSelection, so that is all you can use in the resourceEditor, not 
the integer index. I thought it would be too confusing to users to 
support both and have to provide some sort of conflict negotiation when 
the integer and string index didn't match.

ka

Re: [Pythoncard-users] List problem in 0.8

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

At 08:37 25/08/2004 +0100, Adrian Smith wrote:

>Hi,
>Its great to see a new version out but its causing a little problem. I have
>read the migrate documentation but I am still getting a problem or two.
>I at first could not load my app in pythoncard resource editor, it just
>failed to load even when I cut it down to nothing just a basic minimal.

The migration guide describes this - though it might perhaps have given it 
more emphasis. All existing resource files need to be edited (in a text 
editor) to replace "stack" by "application". (Depending on your text 
editor, remember to save as "text only")

Details in the migration guide in the section on "Resource File Changes"

>However the second problem I have yet to resolve.
>I use .list.getSelectionIndex() which was fine in 0.7.3.1 but now the
>program falls over at that point saying
>
>AttributeError: 'List' object has no attribute 'getSelectionIndex'
>
>I had a look at the components doc but it still says use getSelectionIndex.
>
>What is the new variation of this command?

I don't have a 0.7.3 on here any more to check completely, but I'm 99% sure 
if should be
list.GetSelection()

-- Alex Tweedly.

[Pythoncard-users] List problem in 0.8

[Adrian S. <Adr...@pe...>]

Hi,
Its great to see a new version out but its causing a little problem. I have
read the migrate documentation but I am still getting a problem or two.
I at first could not load my app in pythoncard resource editor, it just
failed to load even when I cut it down to nothing just a basic minimal. The
only way I could get it to open in PythonCard was to create a new minimal
and then add all the components by copy and paste from the old rsrc file to
the new one through pythonwin.
However the second problem I have yet to resolve.
I use .list.getSelectionIndex() which was fine in 0.7.3.1 but now the
program falls over at that point saying

AttributeError: 'List' object has no attribute 'getSelectionIndex'

I had a look at the components doc but it still says use getSelectionIndex.

What is the new variation of this command?
Thanks
Adrian Smith

Re: [Pythoncard-users] PythonCard 0.8 issues (was Re: #pythoncard irc channel on freenode)

[Steven D'A. <st...@cy...>]

On Tue, Aug 24, 2004 at 10:05:31AM +0100, XXXXXXXXXXX wrote:
> On Tue, 24 Aug 2004 11:24:24 +1000, Steven D'Aprano wrote:
> 
> >> Now why you'd want to locate the image somewhere other than the current
> >> directory I couldn't say...
> >
> >Easy: if you have more than, oh, half a dozen images in your application,
> >you probably want to dump them all in an image subdirectory rather than
> >clutter up your main directory.
> 
> I would have thought that you'd use the image component rather than the
> background image property for that sort of thing. Saying that, maybe the
> image component has the same limitation.

Yes, but you might want to store the background image in the same 
directory as the rest of the image files.



-- 
Steven D'Aprano 
Operations Manager 
Cybersource Pty Ltd, ABN 13 053 904 082 
Level 4, 10-16 Queen St, Melbourne VIC 3000 
Tel: +61 3 9621 2377   Fax: +61 3 9621 2477 
Web: http://www.cybersource.com.au 

Re: [Pythoncard-users] Resource Editor Problem

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

On Aug 24, 2004, at 8:53 AM, Phil Edwards wrote:

> First problem I've come across since upgrading everything, although I 
> think
> this was also a problem on 0.7.x...Platform is Mandrake Linux 10, 
> Python
> 2.3.3, wxPythonGTK2-py2.3-2.5.2.7 installed from RPM and 
> Pythoncard-0.8.1 out
> of CVS.
>
> I can't select list components in the resource editor. I'm not seeing 
> any
> mouseEnter, mouseLeave or mouseMove events being generated when 
> running with
> the '-m' command line option.
>
> I haven't done any further investigation yet, can anyone confirm this 
> on
> another Linux install?
>
Do you see any mouse events for a List component in the other samples? 
If not, I wonder if the underlying wx.ListBox on GTK has those events?

ka

Re: [Pythoncard-users] PythonCard 0.8 issues (was Re: #pythoncard irc channel on freenode)

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

>> 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...
>
> Yep, I should probably change the code to save a relative path so you 
> could select a file and then have it be something like 
> images/testo.jpg. I'll ponder that for the various places Image is 
> used. I'm pretty sure relative paths already work, but there is  no 
> attempt to break apart the path and then rejoin it so slashes are 
> converted to backslashes, etc.
>
>> 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.
>
> Yes it could. I just need to change a few lines so that the current 
> color is passed in as the name arg to the colorDialog. Good one! I'll 
> look at this along with the image path issue above tomorrow.

I've added a relativePath function (swiped from the Python Cookbook) to 
util.py. The resourceEditor now uses this function for the background 
image, icon, and file attributes for Image and ImageButton. Those 
components now get a File... button and openFileDialog for selecting 
images. I also fixed the default color issue above. I still need to 
experiment with normalizing the relative path to always use forward 
slashes so the paths work on each platform, but I need to do a few more 
tests before checking that in. Anyone working from cvs should let me 
know if I bused anything.

ka

[Pythoncard-users] Resource Editor Problem

[Phil E. <ph...@li...>]

First problem I've come across since upgrading everything, although I think 
this was also a problem on 0.7.x...Platform is Mandrake Linux 10, Python 
2.3.3, wxPythonGTK2-py2.3-2.5.2.7 installed from RPM and Pythoncard-0.8.1 out 
of CVS.

I can't select list components in the resource editor. I'm not seeing any 
mouseEnter, mouseLeave or mouseMove events being generated when running with 
the '-m' command line option.

I haven't done any further investigation yet, can anyone confirm this on 
another Linux install?

-- 

Regards

Phil Edwards
Brighton, UK

Re: [Pythoncard-users] PythonCard 0.8 issues (was Re: #pythoncard irc channel on freenode)

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

At 12:11 24/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. :-)
> >
> >I point the finger at the guy in the other country ;-)
>
>Yes - I think he's running the new spellchecker component across all his
>other dialogs at this very moment ;-)

Sadly, the typos were in my first dialog, so it didn't take long to check 
the other.

But I now have the sample program working, and found one other typo in 
PythonCard menus (repeated in four places).

The program (getSpell) is available at www.tweedly.net/Python
btw - I used a GridBagSizer so it can be an example of that too ...

-- Alex.

Re: [Pythoncard-users] PythonCard 0.8 issues (was Re: #pythoncard irc channel on freenode)

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On Mon, 23 Aug 2004 23:53:37 -0700, Kevin Altis wrote:
>>
>> 1) Documentation - the on-line stuff is duplicated in the PythonCard/
>> <snip>
>
>Tis true, but it is because you can generate those files yourself. This 
>has been covered a few times before on the list, but it definitely 
>needs to be highlighted better. Anyway, open up the widgets sample and 
>select Create Component Docs... <snip>

Wahaay! Thanks for that. Worked great on Windows.

Unfortunately OS X's permissions made things a bit trickier. I had to run
the widgets sample with 'sudo' to get to the blit exception (otherwise I
got a folder permissions error, presumably trying to add stuff to the
framework directory). I also ended up using TextWrangler to save
widgets.py with admin permission (I guess I could have used 'sudo vi' or
something, but I'm happier using the GUI). One thing I've noticed with
codeEditor is that it doesn't alert you to read-only/permission issues -
it just fails to save without letting you know.

>> 2) Typo - in the resource editor when you duplicate a component the
>> offset widgets are spelt wrong - "Offest Horizontally", etc. :-)
>
>I point the finger at the guy in the other country ;-)

Yes - I think he's running the new spellchecker component across all his
other dialogs at this very moment ;-)

>> 3) Image path - this follows on from an observation I made recently. 
>> <snip>
>
>Yep, I should probably change the code to save a relative path so you 
>could select a file and then have it be something like 
>images/testo.jpg. I'll ponder that for the various places Image is 
>used. I'm pretty sure relative paths already work, but there is  no 
>attempt to break apart the path and then rejoin it so slashes are 
>converted to backslashes, etc.

I can't speak for anyone else, but I'm in no hurry for this. 

>
>> 4) Colour...oops...Color picker - could this open with the property's
>> current value? 
>> <snip>
>
>Yes it could. I just need to change a few lines so that the current 
>color is passed in as the name arg to the colorDialog. Good one! I'll 
>look at this along with the image path issue above tomorrow.
>

Thanks.

Neil

Re: [Pythoncard-users] PythonCard 0.8 issues (was Re: #pythoncard irc channel on freenode)

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

At 23:53 23/08/2004 -0700, Kevin Altis wrote:

>On Aug 23, 2004, at 3:32 PM, XXXXXXXXXXX wrote:
>
>>2) Typo - in the resource editor when you duplicate a component the
>>offset widgets are spelt wrong - "Offest Horizontally", etc. :-)
>
>I point the finger at the guy in the other country ;-)

Yeah - I thought about claiming it was a UK spelling variant, like colo(u)r !!
Fortunately, I realized in time that Neil also had a UK address, so I 
didn't try that.

But I am going to implement (for my own purposes), some easy way to extract 
all label and text values, so I can push them into a spell-checker - if it 
comes out nice, I'll make it a Pythoncard sample.

-- Alex.

Re: [Pythoncard-users] PythonCard 0.8 issues (was Re: #pythoncard irc channel on freenode)

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On Tue, 24 Aug 2004 11:24:24 +1000, Steven D'Aprano wrote:

>> Now why you'd want to locate the image somewhere other than the current
>> directory I couldn't say...
>
>Easy: if you have more than, oh, half a dozen images in your application,
>you probably want to dump them all in an image subdirectory rather than
>clutter up your main directory.

I would have thought that you'd use the image component rather than the
background image property for that sort of thing. Saying that, maybe the
image component has the same limitation.

>Or, if you want to implement something like skins, one set of images to a
>directory.

Ah...never thought of that one...good point.

Neil

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

[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] PythonCard 0.8 issues (was Re: #pythoncard irc channel on freenode)

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

On Aug 23, 2004, at 3:32 PM, XXXXXXXXXXX wrote:

> 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.

Tis true, but it is because you can generate those files yourself. This 
has been covered a few times before on the list, but it definitely 
needs to be highlighted better. Anyway, open up the widgets sample and 
select Create Component Docs... under the File menu, choose the 
PythonCard/docs/html/framework directory. Then you'll see that some 
idiot left the old 2.5.1.5 Blit API call in the code and so it throws 
an exception. Doh! So, then you get to "patch" your copy of widgets.py 
by changing line 374 from:

                 memdc.Blit((0, 0), w.size, dc, (0, 0))

to:

                 memdc.BlitPointSize((0, 0), w.size, dc, (0, 0))

Now try Create Component Docs... again and you should have your own 
copy, complete with widgets based on whatever platform you're running.

> 2) Typo - in the resource editor when you duplicate a component the
> offset widgets are spelt wrong - "Offest Horizontally", etc. :-)

I point the finger at the guy in the other country ;-)

> 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...

Yep, I should probably change the code to save a relative path so you 
could select a file and then have it be something like 
images/testo.jpg. I'll ponder that for the various places Image is 
used. I'm pretty sure relative paths already work, but there is  no 
attempt to break apart the path and then rejoin it so slashes are 
converted to backslashes, etc.

> 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.

Yes it could. I just need to change a few lines so that the current 
color is passed in as the name arg to the colorDialog. Good one! I'll 
look at this along with the image path issue above tomorrow.

> Nothing earth-shattering, I admit, but a start.
>
> Neil

Hey, it is comments like these that keep the project moving forward!

ka

Re: [Pythoncard-users] PythonCard 0.8 issues (was Re: #pythoncard irc channel on freenode)

[Steven D'A. <st...@cy...>]

On Mon, Aug 23, 2004 at 11:32:57PM +0100, XXXXXXXXXXX wrote:

> 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...

Easy: if you have more than, oh, half a dozen images in your application,
you probably want to dump them all in an image subdirectory rather than
clutter up your main directory.

Or, if you want to implement something like skins, one set of images to a
directory.



-- 
Steven D'Aprano 
Operations Manager 
Cybersource Pty Ltd, ABN 13 053 904 082 
Level 4, 10-16 Queen St, Melbourne VIC 3000 
Tel: +61 3 9621 2377   Fax: +61 3 9621 2477 
Web: http://www.cybersource.com.au 

Re: [Pythoncard-users] PythonCard 0.8 issues (was Re: #pythoncard irc channel on freenode)

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

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.

[Pythoncard-users] Multicolumn Lists

[Tony M. <tma...@tr...>]

Hi,

Is there a way to set a multicolumn list editable?

Re: [Pythoncard-users] #pythoncard irc channel on freenode

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

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

[Pythoncard-users] PythonCard 0.8 issues (was Re: #pythoncard irc channel on freenode)

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

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

Re: [Pythoncard-users] #pythoncard irc channel on freenode

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

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

Re: [Pythoncard-users] #pythoncard irc channel on freenode

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

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.

Re: [Pythoncard-users] #pythoncard irc channel on freenode

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

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