I started to do this in HTML, thinking that would be useful in
constructing the real pages, but every time I try this, I feel like
smashing my computer! :>) HTML is a perfect example of design-by-
committee. So anyway, what you see is nicely formatted by Microsoft
Word, and the HTML will be impossible to re-use. Whoever actually
implements these pages will have to start fresh anyway.
--
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.
On Mon, Apr 12, 2010 at 9:58 PM, Andrew Harrington
<anharr...@gmail.com> wrote:
> David,
> Files are not working at the pywhip google group. Is that where you meant?
>
David is referring to PyKata home page.
Regards,
Eliseo.
Actually, I can delete PyWhip from App Engine, but I think it might be
useful to keep it for experimentation. I've put a notice at the top of
the home page, directing users to PyKata.org.
> David, nice ideas with flags for comments. I'm not sure how the
> teacher is specifying categories. I would not depend on them just
> corresponding to your general ones. If there are not too many
> problems, an entry for each problem might make sense, with a number of
> false attempts and whether it was finally solved.
Categories, and the problems selected in each category, will be
determined by our teachers. At first, this can be just having them edit
a template, which we will upload to the website. Later, we can think
about automation, so teachers can make changes without involving us.
Depending on how many teachers get involved, we may not need that much
automation. If it is just a few, and they are spending a substantial
amount of time creating content, it won't be much more for them to learn
SVN, and they can update the website themselves.
I like your idea of having a summary display of all problems for a
selected student, with details on number of failed attempts, etc. This
could be a three-step "drill down" - click the students name to get a
summary of all problems that student has worked on. Click an individual
problem, and see all his work, including failed attempts.
By the way, our files have been restored at
http://groups.google.com/group/pywhip/files. I tried uploading
T_report.htm, but it looks like that didn't work!! There is still not
even an acknowledgment from Google that there is a problem, and I see
continued furor on
http://groups.google.com/group/is-something-broken/topics.
I think our best bet for important files is to just keep them in our SVN
repository at http://code.google.com/p/pykata/w/list. This works for
text and code, but not for HTML, like the mockup page I just did. I
will post those pages to our website with links at
http://code.google.com/p/pykata/. If someone has a better solution to
this problem, please let me know.
Andrew Harrington wrote:
We need to change the pyWhip page to just point to PyKata! We can't get rid of pyWhip, but we can change it.
I would like to suggest adding visualizations for progress of each
student in the Teacher Report ( using Google Visualization API ). Lets
say when a student name is clicked, student data about problems solved
vs problems attempted in each category, progress on pyKata, recent
trends in submission, etc along with the problems solved and profile
could be displayed. It will consume almost nothing on the quota part
( a query is already being made for data, the same data would be fed
to the API and the Google generated chart would be displayed ) and the
reports generated would be better for analysis.
regards,
Abhishek Anand
On Apr 14, 11:48 am, Abhishek Mishra <ideam...@gmail.com> wrote:
> Hi David,
>
> The table looks great, we could even link the numbers to list of questions
> attempted in that category (if needed), so that the teacher could navigate
> to that area in "one click" :)
>
> Ah even I tried uploading the same html, seems weird... I removed the two
> meta tags and tried uploading... poof! it shows the html code from google
> groups. Anyways... it doesn't seem to be working.
> Lets put it in SVN and we could have a *"blue prints"* page on the wiki