Lennard de Rijk <ljvderijk@gmail.com> [Mon, 10 Aug 2009 15:37:12 -0700] rev 2745
Made the specific SurveyTakeForm used in a View part of params.
This fixes the Grade question not showing up on the preview and view record pages.
Lennard de Rijk <ljvderijk@gmail.com> [Mon, 10 Aug 2009 15:28:42 -0700] rev 2744
Removed the grade_choices keyword argument from GradeSurveyTakeForm.
This is because this class already assumes very specific things about the grade_choices keyword argument. Therefore it is now a constant inside this class.
Lennard de Rijk <ljvderijk@gmail.com> [Mon, 10 Aug 2009 15:14:29 -0700] rev 2743
Enable the project management page to be visited for project in other statusses.
This enables org admins to easily view Survey results for projects that have failed.
Sverre Rabbelier <sverre@rabbelier.nl> [Sun, 09 Aug 2009 21:00:32 -0700] rev 2742
Added tag v0-5-20090809 for changeset 107bec037dda
Sverre Rabbelier <srabbelier@gmail.com> [Sun, 09 Aug 2009 20:59:15 -0700] rev 2741
Set new Melange version number to 0-5-20090809 in app.yaml.template.
Lennard de Rijk <ljvderijk@gmail.com> [Sun, 09 Aug 2009 13:42:31 -0700] rev 2740
Added project title and student name to the ProjectSurvey take page.
This required some reodering of the Survey take template and also a renamed setH
elpAndStatus to _setSurveyTakeContext.
Lennard de Rijk <ljvderijk@gmail.com> [Sun, 09 Aug 2009 13:03:47 -0700] rev 2739
Added capability to update a single GradingRecord on the edit page.
Mario Ferraro <fadinlight@gmail.com> [Sat, 08 Aug 2009 18:42:22 +0100] rev 2738
Upgrade to jQuery library to 1.3.2 version.
This will allow us to use also the new Event object (for example
for publish/subscribe pattern) along with some plugins
(like Colorbox) which work only with newer (>=1.3) jQuery versions.
Some further testing is suggested.
Daniel Hans <Daniel.M.Hans@gmail.com> [Fri, 07 Aug 2009 02:06:33 +0200] rev 2737
List of countries is actually alphabetically sorted.
Daniel Hans <Daniel.M.Hans@gmail.com> [Fri, 07 Aug 2009 01:27:24 +0200] rev 2736
Argument store added to updateEntityProperties.
This argument determines if an entity should be stored in the data model after its properties are updated.
It may be useful, for example, along with tasks (Task Queue API). One may want to make some modifications to an entity during execution of a task, but the developer is sure that at least one new task, which also wants to modify the entity, will be queued, so he or she can just update the entity without saving the changes to the data model, set the entity in memcache and the following task (which is to be executed very shortly) is to retrive the current entity from the memcache (without any expensive calls to the actual data model).