Pedagogical Question
David MacQuigg
and insist that all examples be in the doctests. We need to discuss
this now, because it may affect the way we implement our bulkloader.
Take a look at exercise "list123", and compare it to "list123FAIL".
The idea is that we want to establish good habits early. On the other
hand, we don't want to intimidate our very young students. Maybe each
teacher will have a different way of doing this, so I would like to
get some opinions.
Andre Roberge
It is possible to use "view source" and still see the examples. I think examples can potentially clarify greatly what is meant by the problem statement; I would argue they should be shown.
It had been a while since I looked at the site. I just noticed that the editor is not resizable - I think the resize option should be changed and that font size selection should be made available. Some users who have some visual impairment might want to be able to adjust the display.
One might want to modify the code in editarea (as I have done for Crunchy) to have much larger font sizes available. The main reason I did it for Crunchy was to have the code readable when doing presentations (projected on a screen). This is something that one might want to do also for pykata (in which case the toggle full screen option should also be available).
Just a thought....
André
--
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
we don't need to decide which way to go on this. We can leave it to
the author of each exercise. The examples can appear in either or
both places. See the description of the UploadFormat in our code wiki
at http://code.google.com/p/pykata/w/list.
I've added a #-hints: tag to our upload format. This isn't
implemented yet, but we will probably do something like add a "Hints"
button where the student can bring up suggestions like a list of
simpler exercises to practice before this one.
@Andre, We don't have much control over the EditArea widget, other
than toggling it ON or OFF. Maybe we should look for a more versatile
widget. You can zoom in or out using standard controls in your web
browser.
Andre Roberge
Sorry, that's not true. :-) I use EditArea for crunchy and there's
a whole slew of configuration options one might use.
Here's the code used for initializing EditArea on the PyKata site:
<script language="javascript" type="text/javascript">
editAreaLoader.init({
id: "code-area",
syntax: "python",
start_highlight: true,
allow_resize: "no",
font_size: 14,
toolbar: "new_document, |, help",
replace_tab_by_spaces: 4
});
</script>
Just to point out one example, allow_resize is set to "no", and the
tool bar has only two options.
And here's the one used in (an older version of) Crunchy (which I have
on my work computer):
<script type="text/javascript">
editAreaLoader.init({
id: "code_2:3",
font_size: "11",
allow_resize: "both",
allow_toggle: true,
language: "en",
toolbar: "new_document, save, load, |, fullscreen, |, search,
go_to_line, |, undo, redo, |, select_font, |, change_smooth_selection,
highlight, reset_highlight, |, help",
syntax: "python",
start_highlight: true,
load_callback:"my_load_file",
save_callback:"my_save_file",
display: "later",
replace_tab_by_spaces:4,
min_height: 150});</script>
Note that it is initialized so that it can be resized, and that the
toolbar selection includes a "font selector", for example.
David MacQuigg
had all these options. I added the two you suggested, but they aren't
working right. The resize works very slowly on my local server, but not
at all on our website.
Let's continue this discussion in another thread. Or you can file an
enhancement request at http://code.google.com/p/pykata/issues/list, and
we can continue in the comments to that issue.
> Andr�
>
>