Note: You are currently viewing documentation for Moodle 2.8. Up-to-date documentation for the latest stable version of Moodle may be available here: Ratings 2.0.

Development talk:Ratings 2.0: Difference between revisions

From MoodleDocs
(New page: # I think it would be clearer to move the userid column later in the database table, to just before timecreated. # What value will be in the userid field if one user sets one rating, then...)
 
No edit summary
Line 1: Line 1:
# I think it would be clearer to move the userid column later in the database table, to just before timecreated.
# I think it would be clearer to move the userid column later in the database table, to just before timecreated.
# What value will be in the userid field if one user sets one rating, then a different user changes it?
# What value will be in the userid field if one user sets one rating, then a different user changes it?
# I think the content column would be easier to understand if you called it 'comment'.
# I think the content column would be easier to understand if you called it 'comment'.
# Is there any way of knowing which scale the rating is against, other than by asking the plugin? Have you considered a scaleid column in the table?
# Is there any way of knowing which scale the rating is against, other than by asking the plugin? Have you considered a scaleid column in the table?
# class rating really should be split into class rating for the back-end, and care_rating_renderer for the GUI.
# class rating really should be split into class rating for the back-end, and care_rating_renderer for the GUI.
# Why do plugins need to implement so many callbacks to use ratings?
# Why do plugins need to implement so many callbacks to use ratings?
# You say the interface won't be changed, but that AJAX could be implemented in future. Well, forum already has AJAX rating!
# You say the interface won't be changed, but that AJAX could be implemented in future. Well, forum already has AJAX rating!
# Manual grading in the quiz have never been handled in the same ways as rating elsewhere, for good reasons. However, you might like to look at how manual grading of quiz questions works.


--[[User:Tim Hunt|Tim Hunt]] 11:03, 20 January 2010 (UTC)
--[[User:Tim Hunt|Tim Hunt]] 11:03, 20 January 2010 (UTC)

Revision as of 11:05, 20 January 2010

  1. I think it would be clearer to move the userid column later in the database table, to just before timecreated.
  2. What value will be in the userid field if one user sets one rating, then a different user changes it?
  3. I think the content column would be easier to understand if you called it 'comment'.
  4. Is there any way of knowing which scale the rating is against, other than by asking the plugin? Have you considered a scaleid column in the table?
  5. class rating really should be split into class rating for the back-end, and care_rating_renderer for the GUI.
  6. Why do plugins need to implement so many callbacks to use ratings?
  7. You say the interface won't be changed, but that AJAX could be implemented in future. Well, forum already has AJAX rating!
  8. Manual grading in the quiz have never been handled in the same ways as rating elsewhere, for good reasons. However, you might like to look at how manual grading of quiz questions works.

--Tim Hunt 11:03, 20 January 2010 (UTC)