Re-launch of PyKata
David MacQuigg
ahead and changed the name (cloned the project) in Google Code and
Google App Engine. I'll leave the name as is in Google Groups, since
the public doesn't see that. The new links are:
http://pykata.appspot.com
http://code.google.com/p/pykata
Sean Lennon, one of Andy Harrington's students, is making great
progress getting up to speed on App Engine, and I think he will make a
real contribution to our website development. Meanwhile, I would like
to go ahead with getting some content in the current website. I held
off before, on the theory that we need to finish the website before
getting a lot of content. I think that was a mistake, and got people
thinking the project was going nowhere.
We should assume the website will get done, one way or another. Let's
get some interesting exercises and help files to show, even if the
website is less than perfect. We can re-organized these items later.
You may notice I changed the colors of the PyKata logo. I like bold,
bright colors, better than the soft pastels we had in PyWhip. Our
group should decide on this, however, so it's not just my personal
preference.. I've also eliminated the slogan "Keep on crackin' it",
which used to appear as a title on our web pages. I'm thinking of
posting a contest on [edu-sig] looking for the best logo and slogan.
The new website does not yet have the exercises copied over from the
old website. Turns out that like "renaming" a project, this is yet
another thing Google does not make easy. We will probably need to do
this with our own code, and that may be actually a good thing, as it
could be part of an enhancement we have already discussed.. Andy
suggested that we have a simple way to upload numerous exercises,
without having to use the web form on each one. We can do this with
an "import" command, written as a mirror for our "export" command.
The intermediate data format should be executable Python code, with
tags allowing the import command to put each block in the appropriate
section of the stored data.
My time is really tight this semester, but I'll do what I can to keep
this project moving forward.
-- Dave
Richard Guenther
http://codingbat.blogspot.com/
http://codingbat.com/python
Since everyone on [edu-sig] seems to like the name PyKata, I've gone
ahead and changed the name (cloned the project) in Google Code and
Google App Engine...........
Richard Guenther
Math and Computer Science
Skyline High School
Longmont, CO
Andrew Harrington
Andy
--
You received this message because you are subscribed to the Google Groups "PyWhip" group.
To post to this group, send email to pyw...@googlegroups.com.
To unsubscribe from this group, send email to pywhip+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pywhip?hl=en.
--
Andrew N. Harrington
Director of Academic Programs
Computer Science Department
Loyola University Chicago
512B Lewis Towers (office)
Snail mail to Lewis Towers 416
820 North Michigan Avenue
Chicago, Illinois 60611
http://www.cs.luc.edu/~anh
Phone: 312-915-7982
Fax: 312-915-7998
g...@cs.luc.edu for graduate administration
u...@cs.luc.edu for undergrad administration
aha...@luc.edu as professor
David MacQuigg
Javabat problems to Python, but Nick wanted to do it himself. He is
ahead of us now on website development, but in the end, I think we
will be ahead on content. One person just can't do it all. That is
the great advantage of open-source. Let's get moving!!
The one thing I really like about CodingBat is the one-to-one
comparison of Java to Python. That will get a lot of Java programmers
introduced to Python, and perhaps lower some barrier down the road
when we are trying to introduce Python in the curriculum. If anyone
sees a better, more elegant translation than what Nick has done, let
him know. He was quite generous in letting us use some of his
problems when we got started.
I'm looking forward to a friendly competition.
Andrew Harrington
Nick's authoring and topic:value tagging is rather well worked out. It exactly parallels my ideas, and then gives a specific implementation. He has a nice description of a simplified scheme for html. The idea for a permanent code for each problem makes sense. Then we can move them around if we just keep a mapping.
With our emphasis on open access, one thing occurs to me that is built into a Wiki: historical versions. This stuff is supposed to be given a creative commons license. I believe we then have a duty to keep it (Jeff??). What about the situation where A creates Prog1, B likes it and uses it with a reference, and then A changes Prog1 or essentially deletes it from our site. Do we have an obligation (or desire) to have the original version of Prog1 accessible for B's use?
Andy
--
You received this message because you are subscribed to the Google Groups "PyWhip" group.
To post to this group, send email to pyw...@googlegroups.com.
To unsubscribe from this group, send email to pywhip+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pywhip?hl=en.
David MacQuigg
graduating in May, and is not eligible for the Summer of Code. Before
we make a big push to get another student, I would like to make sure
PyKata shows the level of interest we have from teachers. It is OK if
the HTML is screwed up. A web developer will know that is fixable.
The biggest problem is that I am not able to transfer the exercises
from PyWhip to PyKata without showing myself as author.
If you are still interested in this project, please log on to both
http://pywhip.appspot.com/problems and http://pykata.appspot.com/problems
and transfer your problems to the new website. It will only take a
few minutes using cut-and-paste.