Development:Comments 2.0: Difference between revisions
From MoodleDocs
| Line 49: | Line 49: | ||
| | | | ||
| Some plugin specific item id (eg. forum post, blog entry or assignment submission) | | Some plugin specific item id (eg. forum post, blog entry or assignment submission) | ||
|- | |||
| comment_area | |||
| int(10) | |||
| | |||
| a comment should belong to a comment area | |||
|- | |- | ||
| timecreated | | timecreated | ||
| int(10) | |||
| | |||
| | |||
|- | |||
| timemodified | |||
| int(10) | | int(10) | ||
| | | | ||
Revision as of 02:26, 11 May 2009
Objectives
The goals of comments 2.0:
- Manage comments centrally
- Use a consistent approach for all comments throughout Moodle
- Easily integrate comments 2.0 with existing modules
Overview
The comments 2.0 provides APIs to:
- Add comments
- Update comments
And provides an ajax interface to allow adding comments on a floating DIV.
Comments database table
| Field | Type | Default | Info |
|---|---|---|---|
| id | int(10) | auto-incrementing | The unique ID for this comment. |
| user_id | int(10) | who wrote this comment | |
| parent_id | int(10) | the ID for parent comment | |
| contextid | int(10) | The context id defined in context table - identifies the instance of plugin owning the comment. | |
| itemid | int(10) | Some plugin specific item id (eg. forum post, blog entry or assignment submission) | |
| comment_area | int(10) | a comment should belong to a comment area | |
| timecreated | int(10) | ||
| timemodified | int(10) | ||
| content | text | content of comment |
Mockup
See also
- MDL-19118 - Comments 2.0 issue
