Menu
▾
▴
pythoncard-users
|
From: ralph h. <1st...@1I...> - 2004-04-28 15:58:43
|
Even though I am still a newbie as well and am currently developing a pythoncard application I will take a stab. As far as "running live" it is not a service. Pythoncard is a set of libraries that are "imported" into your script at development. When you run the script, it imports the PythonCard objects as the script is interpreted. Python is an interpreted language. In essence it is as "live" as your scripts are. --- Geoff Canyon <gc...@in...> wrote: Forgive the newby question, but I didn't see the answer to this on the web site(s): HyperCard runs live -- you never have to run because it is always running, even as you change properties and set scripts. Is this possible in Python/PythonCard? 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! |
|
From: ralph h. <1st...@1I...> - 2004-04-29 13:02:43
|
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! |
|
From: Kevin A. <al...@se...> - 2004-04-29 15:00:47
|
On Apr 29, 2004, at 7:29 AM, RANDY BURNS wrote: > There are some simple single user databases that are written in Python=20= > or Perl. > These are a bit more than what I think of as a "flat file" databases,=20= > and allow you to tie an associative array to a database. If you used=20= > one of those and thought the persistancy interface through early on in=20= > the process, I think it=A0 would be pretty easy for someone to convert=20= > this tool to SQL databases early in the process. > =A0 > >What I do know is possible and will probably do first is make a > >flatfileDatabase environment app which has some of the features of a > >full PythonCard environment. This is probably analogous to FileMaker=20= > or > >MS Access. The database app is started and then you can open, use, > >design, etc. various database templates which will all get some > >capabilities from the database app environment. The same thing would=20= > be > >possible for SQL databases, but I'll do it for flatfileDatabase = first. > >If anyone else is interested, let me know and maybe work will get = done > >on it before 1.0 is finished. > The flatfileDatabase module currently support pickle, XML, and MetaKit.=20= It should be relatively easy to have it support PySQLite and Gadfly.=20 But the other framework stuff is a higher priority item for me, so I=20 don't plan to spend any time on it until the other stuff is done,=20 unless someone else takes ownership and just needs a bit of input and=20 clarification from me on how particular bits work. ka |
|
From: Andy T. <an...@ha...> - 2004-05-05 10:00:34
|
Kevin Altis wrote: > On Apr 29, 2004, at 7:29 AM, RANDY BURNS wrote: > >> There are some simple single user databases that are written in Python >> or Perl. >> These are a bit more than what I think of as a "flat file" databases, >> and allow you to tie an associative array to a database. If you used >> one of those and thought the persistancy interface through early on in >> the process, I think it would be pretty easy for someone to convert >> this tool to SQL databases early in the process. >> >> >What I do know is possible and will probably do first is make a >> >flatfileDatabase environment app which has some of the features of a >> >full PythonCard environment. This is probably analogous to FileMaker or >> >MS Access. The database app is started and then you can open, use, >> >design, etc. various database templates which will all get some >> >capabilities from the database app environment. The same thing would be >> >possible for SQL databases, but I'll do it for flatfileDatabase first. >> >If anyone else is interested, let me know and maybe work will get done >> >on it before 1.0 is finished. >> > The flatfileDatabase module currently support pickle, XML, and MetaKit. > It should be relatively easy to have it support PySQLite and Gadfly. But > the other framework stuff is a higher priority item for me, so I don't > plan to spend any time on it until the other stuff is done, unless > someone else takes ownership and just needs a bit of input and > clarification from me on how particular bits work. > > ka > > I've already done most of the legwork, gadflyDatabase.py inherits from flatfileDatabase.py and replaces the file based interface with a DB-API one. Adding support for SQLite shouldn't be much more work. Regards, Andy -- -------------------------------------------------------------------------------- From the desk of Andrew J Todd esq - http://www.halfcooked.com/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X