Re: [Pythoncard-users] Added MDI support to Pythoncard (was MDI - childwindows within a window)

[Peter D. <pyd...@gm...>]

On Sat, Apr 2, 2011 at 1:11 PM, Kael Fischer <kae...@gm...> wrote:
> Python card is great.
>
> But I  caution people stating out on large computationally or database
> intensive projects that while pythoncard makes the easy stuff very
> easy, it makes that hard stuff harder.  Note that even using wxPython
> getting the process-based and thread-based multitasking working
> properly can be hard and is essential in any program that uses the
> cpu, disk and network intensively and still needs wx to be responsive,
> draw progress bars, etc.
>
> I'm warning about big data here (for a GUI anyway): trees with
> 1000's-10,000's of nodes, grid data stores with ~1M cells.
>
> I've written some cool programs in python card, but they never scaled well.

I used PythonCard for a few projects, and was impressed by how easy it
was to put together a simple app. But I know exactly what you mean
about scaling. And while I don't do heavy database apps, I do have to
save settings, configurations, etc., and this was a very manual
process in PythonCard.

After I discovered Dabo a few years ago, I have only used PythonCard
occasionally, and each time I find myself missing Dabo. It's a much
cleaner wrapper around wxPython, and it comes with data binding built
in. And to get back to the subject, MDI forms have been a part of Dabo
since the beginning.

Dabo is still being actively developed, and its user base is growing
all the time. You should definitely give it a try (and no, they don't
pay me to say this! I'm just a big fan!). http://dabodev.com

-- 

# p.d.