Re: [Pythoncard-users] Python/PythonCard: live like HyperCard?

[Geoff C. <gc...@in...>]

First, I should clarify: I come from a general/Revolution background, 
not a HyperCard background (at least not recently). I only used 
HyperCard as an example because it seemed more reasonable to assume 
people on this list were familiar with it, given the PythonCard name. 
As an example of why this is significant, I could care less about 
auto-save, and I never use idle.

That said, I'm still boggled. There's so much information, and 
seemingly no table of contents that allows me to answer the following:

In Revolution, I'm used to:

1. Starting Revolution
2. Creating a new project
3. Laying out the interface for that project
4. Adding code to various elements of that project
5. Interactively testing the project, going back and forth between 
testing and coding because the project runs live.
6. When I'm ready, I select the appropriate options and build the 
project as a standalone application.

Now, what I think I understand is that in PythonCard I:

1. Start the Resource Editor
2. Create a new project
3. Lay out the interface for that project -- at this point no code 
entry is possible and the project is dead.
4. Save the project as a resource file.
5. Open the project in PythonCard -- at this point the interface of the 
project is modifiable, but not savable.
6. Edit the code of the project -- which is one big long list of code.
7. Run the project in some fashion
8. Test the project.
9. Rinse and repeat steps 5-8.
10. When I'm ready, do something or other to build the application. On 
Mac and Unix it will open the console window and I can't stop it.

Is that accurate at all?

regards,

Geoff Canyon
gc...@in...