PythonCard

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.

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

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

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.