RE: [Pythoncard-users] six blind men describe the beast

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

> From: Rowland Smith
>
> > is not designed to run inside a web browser
>
>
> Definitely.  If someone wants to write a tool that generates a web app
> from PythonCard, that's great, but it's not something we want to take on

In case anyone is confused, this does not mean you can't generate HTML,
design a templating system, content management system, etc. from a
PythonCard app that you've written. It does mean that there wouldn't be an
automatic export/conversion from PythonCard layouts and Python code to HTML
and JavaScript for the client-side of a WebApp and generate all the
necessary back-end server code as well. That is just not possible. As far as
layouts, some form of conversion might be doable, the Pyker .hta files Neil
provided hint at what may or may not be possible.

> > support editing programs in standard editors (vi, vim, emacs,
> >    PythonWin, IDLE, etc.) and not be forced to edit in and IDE
>
>
> It's certainly nice to be able to edit code in your favorite editor, but
> for PythonCard to really be useful it's going to need a slick, powerful
> app builder/ide available as soon as possible.  This is something that I
> would like very much to work on.

Yes and no. Even with just a great framework, layout editor, and some
run-time tools, which would just be a better version of the prototype today
that would be a good thing for Python programmers. In fact, given the extra
work needed to do an IDE, VDE, whatever I would probably be happy to stop at
that point for my own programs. However, I also see the need to go beyond
that so I don't mind contributing to the IDE/VDE effort in parallel and as a
way of stressing the framework since I'm assuming most of the IDE/VDE will
be written itself in PythonCard. Certainly without an environment, we won't
be remotely close to "competing against" HyperCard or any commercial
language solution.

Baby steps,

ka