pythoncard-users

[Pythoncard-users] PythonCard presentation at OSDC 2005

[Andy T. <an...@ha...>]

Yesterday I gave a presentation at the Australian Open Source Developers 
   Conference in Melbourne.

It was remarkably similar to Kevin's presentations at PyCon and OSCON 
earlier this year. What I managed to do was concentrate on demonstrating 
the power of PythonCard and kept my slides [1] to a minimum.

I did, however, produce a paper [2] to be included in the conference 
proceedings. This is a fairly comprehensive description of the history, 
structure and form of PythonCard. I'd like to put this on the project 
web site but would like some feedback about where it should sit and what 
I should cut or add.

All contributions are welcome.

[1] http://www.halfcooked.com/presentations/osdc/presentation.html
[2] http://www.halfcooked.com/presentations/osdc/pythoncard.html

Regards,
Andy
-- 
--------------------------------------------------------------------------------
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/

Re: [Pythoncard-users] PythonCard presentation at OSDC 2005

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

Andy Todd wrote:

> Yesterday I gave a presentation at the Australian Open Source 
> Developers   Conference in Melbourne.
>
> It was remarkably similar to Kevin's presentations at PyCon and OSCON 
> earlier this year. What I managed to do was concentrate on 
> demonstrating the power of PythonCard and kept my slides [1] to a 
> minimum.
>
> I did, however, produce a paper [2] to be included in the conference 
> proceedings. This is a fairly comprehensive description of the 
> history, structure and form of PythonCard. I'd like to put this on the 
> project web site but would like some feedback about where it should 
> sit and what I should cut or add.

Marvelous !  Thank you.

I found the paper very interesting for the history (some of which I knew 
but some I didn't).
And I learned about the runtime tools of property inspector and 
namespace viewer; I guess I'd seen them before - they're right there and 
obvious in the options dialog - but I hadn't really noticed them. I can 
see I'll be using them - particularly the property inspector - a lot 
from now on.

Nothing seems particularly "missing" to me, so no contribution at the 
moment. (Though I'm going to try to construct a tutorial or walk through 
that uses the run-time tools ....)

-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.13.11/191 - Release Date: 02/12/2005

[Pythoncard-users] runtime property editor issues

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

On Dec 8, 2005, at 7:15 AM, Alex Tweedly wrote:

> Andy Todd wrote:
>
>> Yesterday I gave a presentation at the Australian Open Source 
>> Developers   Conference in Melbourne.
>>
>> It was remarkably similar to Kevin's presentations at PyCon and OSCON 
>> earlier this year. What I managed to do was concentrate on 
>> demonstrating the power of PythonCard and kept my slides [1] to a 
>> minimum.
>>
>> I did, however, produce a paper [2] to be included in the conference 
>> proceedings. This is a fairly comprehensive description of the 
>> history, structure and form of PythonCard. I'd like to put this on 
>> the project web site but would like some feedback about where it 
>> should sit and what I should cut or add.
>
> Marvelous !  Thank you.
>
> I found the paper very interesting for the history (some of which I 
> knew but some I didn't).
> And I learned about the runtime tools of property inspector and 
> namespace viewer; I guess I'd seen them before - they're right there 
> and obvious in the options dialog - but I hadn't really noticed them. 
> I can see I'll be using them - particularly the property inspector - a 
> lot from now on.
>
> Nothing seems particularly "missing" to me, so no contribution at the 
> moment. (Though I'm going to try to construct a tutorial or walk 
> through that uses the run-time tools ....)
>
> -- 
> Alex Tweedly       http://www.tweedly.net

The runtime Property Editor is probably the weakest of the current 
tools and I expect it has quite a few boundary condition bugs that were 
fixed in the resourceEditor. Ideally it would share more code with the 
resourceEditor property editor. I forked the resourceEditor version a 
long time ago since the runtime tool does not allow you to save 
changes, but consequently it hasn't kept up with all the fixes and 
features in the resourceEditor version, which also has callbacks into 
the main resourceEditor logic.

One possibility would be to change the modules for the property editor 
and resourceOutput.py to be part of PythonCard/templates and/or primary 
framework modules. The resourceEditor property editor class and debug 
runtime property editor would then become subclasses of the base 
property editor.

The runtime tool could be given a Save As... button so the current 
state of background could be saved. There might be some reason why that 
isn't a good idea that is currently slipping my mind, but it may also 
be one of those "why doesn't it do that already?" ideas that will make 
PythonCard more powerful for some developers. :-)

ka

Re: [Pythoncard-users] PythonCard presentation at OSDC 2005

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

On Dec 5, 2005, at 3:29 PM, Andy Todd wrote:

> Yesterday I gave a presentation at the Australian Open Source  
> Developers   Conference in Melbourne.
>
> It was remarkably similar to Kevin's presentations at PyCon and OSCON  
> earlier this year. What I managed to do was concentrate on  
> demonstrating the power of PythonCard and kept my slides [1] to a  
> minimum.
>
> I did, however, produce a paper [2] to be included in the conference  
> proceedings. This is a fairly comprehensive description of the  
> history, structure and form of PythonCard. I'd like to put this on the  
> project web site but would like some feedback about where it should  
> sit and what I should cut or add.
>
> All contributions are welcome.
>
> [1] http://www.halfcooked.com/presentations/osdc/presentation.html
> [2] http://www.halfcooked.com/presentations/osdc/pythoncard.html
>
> Regards,
> Andy
> --  
> ----------------------------------------------------------------------- 
> ---------
> From the desk of Andrew J Todd esq - http://www.halfcooked.com/

Wow, very nice job Andy. I expect what we want to do is integrate this  
into the documentation page

http://pythoncard.sourceforge.net/documentation.html

perhaps as a new section Overview before Getting Started. There might  
be a better section name, but it should be clear from the section or  
title of the article that it is a background and overview of PythonCard  
rather than the "jumping in" articles in the Gatting Started section.  
Inserting a few screenshots might not be a bad idea either, since they  
are already on the web site, but that would change the original paper,  
so it is up to you.

What was the response to the paper and presentation at the conference?

ka