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