Re: [Pythoncard-users] Revival of Pythoncard

[<kc1...@ya...>]

In an open-source project, "Dead" is when others "perceived" that you are d=
ead.  As I indicated earlier, this would help driving skillful programmers =
away - in search of more "interesting", more "alive" projects.=0A=0AWhile i=
t's all nice and good that we are productive *today*, we certainly can use =
more skillful contribution to the project=0A=0A=0A=0A-----Original Message-=
----=0AFrom: =0Ap...@li... =0A[mailto:p=
yth...@li...] On Behalf Of Sean =0AK. Frie=
se=0ASent: Tuesday, December 05, 2006 5:10 PM=0ATo: =0APycard mailing list=
=0ASubject: Re: [Pythoncard-users] Revival of =0APythoncard=0A=0A=0A> Hello=
,=0A>    I am a High School student =0Aat Yorktown High School and i worked=
=0A> extensively all my junior year with =0APythoncard. This year i wanted =
to=0A> continue my studies but my teacher =0Aseems to believe that Pythonca=
rd is =0A> dead. However, i will not give in =0Ato that message and i hope =
for a=0A> response that basically says that =0APythoncard is not dead yet=
=0A>=0A> Please prove me =0Aright.=0A=0A=0ADefine "dead".=0A=0AIt appears a=
s though you'd like to know =0Awhether or not Pythoncard will somehow "disa=
ppear", or be incapable of handling =0Aa large project you might cook up so=
me time down the road.  I wouldn't worry =0Aabout either, personally.  Pyth=
oncard offers one of the most accessible GUI =0Adevelopment layers for, in =
my opinion, the best language.  I wouldn't let your =0Ateacher's comment sw=
ay you from something you've become attached to for your own =0Areasons.  T=
hat is, after all, one of the great things about Python.  There are =0Amany=
 resources available to approach any problem using Python.  Selecting the =
=0Aone that is right for you is entirely up to you and your comfort level a=
lone. =0A=0A=0AYou'll find several resources on the web today that have eit=
her been =0Acompletely abandoned, or have not had many updates within the p=
ast year.  This =0Adoes *not* mean that resource is "dead".  Perhaps it is =
just that Pythoncard is =0Acapable and stable as it stands and does not req=
uire consistent updates.  What =0Ayou might want to ask yourself is whether=
 or not Pythoncard is the right =0Asolution for you *today*.  Since you've =
used it throughout your junior year in =0AHigh School, it would appear it h=
as worked for you in its current state.  =0APersonally, I've used Pythoncar=
d, along with the ever popular StandaloneBuilder =0Afor a while now, and I'=
ve not come across a scenario where I needed to look =0Aelsewhere.  There a=
re other alternatives to Pythoncard that sit upon the =0AwxPython framework=
 ("wax" is one of them).  Since I approach my solutions in a =0Amore "Pytho=
ncard" fashion, Pythoncard makes sense to me.  If it didn't, I =0Awouldn't =
use it.  I have no immediate need for components outside of what is =0Acurr=
ently available, and Pythoncard is indeed quite stable. =0A=0AI've used =0A=
Pythoncard for odd niche eLearning development applications and I'm still a=
mazed =0Aat how fast I'm able to throw them together using Pythoncard.  I p=
icked up =0APythoncard at first for prototyping applications only - Some bi=
g, some small.  =0AI've since used it exclusively for all of my application=
 development.  The =0Aavailability of "helper apps", like StandaloneBuilder=
, are just pure icing on =0Athe cake.  I've used platforms far more "active=
", such as .NET in the past, and =0AI must say that the time and overhead o=
f implementing the identical project in =0APythoncard has been far less for=
 me. =0A=0AIn the end, it is about choosing =0Awhat is right for both you a=
nd the problem at hand.  For my needs, Pythoncard is =0Athe right fit.=0A=
=0A=0A-- =0ARegards,=0ASean K. Friese [ skf...@gm...]=0A=0A =0A--=0AJ=
ohn Henry=0A=0A