This is the Third Edition of Indexed Database API.īecame a W3C Recommendation on 8 January 2015.īecame a W3C Recommendation on 30 January 2018. This document is governed by the 2 November 2021 W3C Process Document. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group that page also includes instructions for disclosing a patent. This document was produced by a group operating under the W3C Patent Policy. It is inappropriate to cite this document as other than work in progress. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. Publication as a Working Draft does not imply endorsement by W3C and its Members. Please use GitHub issues Historical discussions can be found in the archives. This document was published by the Web Applications Working Group as a Working Draft using the Recommendationįeedback and comments on this specification are welcome. This document is intended to become a W3C Recommendation. This document was published by the Web Applications Working Group as a Working Draft. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at. So the top of our section describes the status of this document at the time of its publication. The class should also define a class variable $type, which again should use the same name - in our example, we'd give it the value 'tastiness'.
For example, if we're creating a new data type called "Tastiness", we want to create our plugin in a folder "tastiness" and the PHP class should be data_field_tastiness. Your class's name should match the subfolder you have created. This is very important - the class "data_field_base" (defined in /moodle/mod/data/lib.php, by the way) defines some of the core behaviours without which your field will not work. If you look at the file "" for the URL field type you'll see that the class is named "data_field_url" and it is a subclass of "data_field_base". You will see icons for all the other fields in this directory. To add an icon for your field you need to include this file in 'mod/data/pix/field/'. icon.gif - the icon to be displayed along with the field, as a visual cue to the teacher about what sort of data is stored in this field.All of the normal field types keep their language definitions in the general language file ('mod/data/lang/en/data.php'), but I recommend keeping your language strings separate where you can. You will need to create the same file structure as the other field types ('mod/data/field/url/lang/en/'). datafield_url.php - contains the language strings used in the url field type.version.php - contains version information about the field type.mod.html - contains a HTML "fragment" defining how the form fields will appear when the teacher is adding/editing an instance of the field.- the most important file, this defines a PHP class which defines the majority of the data field's behaviour.The best way to get an understanding of the plugin architecture is to look at an existing field type - I recommend you look at the URL field type, stored in /moodle/mod/data/field/url. What to do (what info to store) when the teacher submits the field-add/edit form.What form fields to output when the teacher is adding/editing an instance of the field.What to do (what info to store) when someone submits the record-add/edit form.What form fields to output when people are adding/editing a record in the database.What HTML to output when people are looking at a record in the database.
#CREATE LINK IN IDATABASE CODE#
Inside this folder will be PHP code telling Moodle:
To create a new field type in Moodle we need to create a new folder in /moodle/mod/data/field. "wiki page" - people see a drop-down list containing the names of pages in your wiki, and can choose which page this particular entry refers to Basic concepts "library reference number" - people can enter a number into the field, and this is automatically turned into a direct link to your library webpages Module-specific field types e.g. "Protein PDB code" - people can enter the PDB code for a protein, and then the display could (for example) include a 3D viewer for the protein structure, or link out to molecular databases. For example, you might like to create:ĭiscipline-specific field types e.g. Moodle's Database module has some predefined field types (text, date, URL, picture, etc), but you can customise this to create new field types.
0 kommentar(er)
