If you describe your app a bit here, I'll bet folks will offer (probably > conflicting ;-) ) suggestions. >
OK, at the risk of proving Chris right: it's an app I started on a couple years ago--which I mention because I *think* I may have mentioned it here back then--and then shelved until recently, when I needed something to try to keep my Python chops in shape. It's similar in concept to wxDesigner, except instead of focusing on providing a GUI to design GUI's (and then producing the code to produce those GUI's for you) it's more general: it has a New->Package command where the user provides the name of the package and a few other details the computer wouldn't be able to guess at, and the app creates the required directory and __init__.py file in it; a new module command where the user provides the name of the module, etc., and the app generates the required .py file; a new import command where the user specifies the file they want the import statements added to and selects the modules they want to import from a drop-down list of installed modules, etc., and the app, in essence, does the typing (properly formatted and syntaxed, of course); a new class command where the user...etc., etc., you get the idea. In other words, the app provides a GUI for the user to specify aspects of Python code the computer can't guess at--identifiers, flow control, etc.--and the app provides all the required boiler-plate "surroundings." The original intended audience was for people for whom extensive keyboarding poses an obstacle to programming, but I imagine it might have broader appeal. So you can see, all I really need is HTML forms to implement pretty standard widgets (text boxes, check boxes, radio buttons, drop-down menus, etc., etc.) something to receive the user's selections when the s/he click's "Submit," a collection of standard "embellishment" methods, and a way to save the result as interpretable source code (i.e., a simple text file). Although I've been thinking of the app in "desktop" terms, I kind of like the idea of leveraging Google's App. Engine (which I didn't know about, so thanks Rohit!): I assume they provide a convenient API to their Drive resource (so that the app could write the code to files thereon and then the user could download as desired). Indeed, it occurs to me that they probably also offer an API to their Code hosting platform, so that the whole thing could be integrated w/ that and, e.g., source control, sharing, etc. Interesting... Thanks all! DG
