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

[ralph h. <1st...@1I...>]

My experience.  

I wrote some very large enterprise systems in DataFlex about 25 years ago.  Some are still in production today.  During the course of the last 6 years I have evaluated various 4GLs (Progress, FileMaker, Lotus Approach), IDEs (Microsoft .NET, J2EE, Omnis, Revelation, etc) and development environments that are both highly scalable and platform-independent.  BTW I never really figured out Revelation as I didn't have time.

When I first came across Python I was skeptical.  Having written standalone GUIs with Java and C++ I wanted something capable of the RAD model (not just fluff).  When I first downloaded PythonCard it was after I download Boa Constructor and wxGlade.  Both of these are good GUI designers but PythonCard was the first that I saw with true a WYSIWYG capability.  The fact that it separates the GUI from the actual programming wasn't readily apparent to me to be an advantage.

The MySQLDB integration was so simple and with the help of this community I have rewritten about 90% of the original functionality and added new features that I did in DataFlex (a 4GL) with 60% less code.

When I am ready to migrate to a prod/Qa environment, I simply copy the .py file to .pyw which prevents the user from seeing the console window.  I don't know if py2exe would make it load quicker.  The look and feel is impressive and I can create 1 form where before I created several.


PythonCard is a nice work!

--- Geoff Canyon <gc...@in...> wrote:
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...



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Pythoncard-users mailing list
Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/pythoncard-users


_____________________________________________________________
 
 
 
=======================================
    www.StrictlyEmail.com ...our name says it all!