> Hello,
> I am a High School student at Yorktown High School and i worked
> extensively all my junior year with Pythoncard. This year i wanted to
> continue my studies but my teacher seems to believe that Pythoncard is
> dead. However, i will not give in to that message and i hope for a
> response that basically says that Pythoncard is not dead yet
>
> Please prove me right.
Define "dead".
It appears as though you'd like to know whether or not Pythoncard will
somehow "disappear", or be incapable of handling a large project you might
cook up some time down the road. I wouldn't worry about either,
personally. Pythoncard offers one of the most accessible GUI development
layers for, in my opinion, the best language. I wouldn't let your teacher's
comment sway you from something you've become attached to for your own
reasons. That is, after all, one of the great things about Python. There
are many resources available to approach any problem using Python.
Selecting the one that is right for you is entirely up to you and your
comfort level alone.
You'll find several resources on the web today that have either been
completely abandoned, or have not had many updates within the past year.
This does *not* mean that resource is "dead". Perhaps it is just that
Pythoncard is capable and stable as it stands and does not require
consistent updates. What you might want to ask yourself is whether or not
Pythoncard is the right solution for you *today*. Since you've used it
throughout your junior year in High School, it would appear it has worked
for you in its current state. Personally, I've used Pythoncard, along with
the ever popular StandaloneBuilder for a while now, and I've not come across
a scenario where I needed to look elsewhere. There are other alternatives
to Pythoncard that sit upon the wxPython framework ("wax" is one of them).
Since I approach my solutions in a more "Pythoncard" fashion, Pythoncard
makes sense to me. If it didn't, I wouldn't use it. I have no immediate
need for components outside of what is currently available, and Pythoncard
is indeed quite stable.
I've used Pythoncard for odd niche eLearning development applications and
I'm still amazed at how fast I'm able to throw them together using
Pythoncard. I picked up Pythoncard at first for prototyping applications
only - Some big, some small. I've since used it exclusively for all of my
application development. The availability of "helper apps", like
StandaloneBuilder, are just pure icing on the cake. I've used platforms far
more "active", such as .NET in the past, and I must say that the time and
overhead of implementing the identical project in Pythoncard has been far
less for me.
In the end, it is about choosing what is right for both you and the problem
at hand. For my needs, Pythoncard is the right fit.
--
Regards,
Sean K. Friese [skf...@gm...]
|
