Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Student projects/Admin page cleanup.

Student projects/Admin page cleanup: Difference between revisions

From MoodleDocs
mNo edit summary
 
(42 intermediate revisions by the same user not shown)
Line 1: Line 1:
<strike>I'm currently working on porting the settings to XML and putting together the new index.php admin page. Please use the talk page to leave me any comments, I'll be checking it regularly.</strike>
This just in: no XML! The new format will be PHP/OO-based. New code to come soon. (Till then, take a look at the [[Student projects/Admin page cleanup/Reorg|Reorg]] page, which still contains useful data.)
{| style="color:black; border: 2px solid red; width: 100%; height: 20px;"
{| style="color:black; border: 2px solid red; width: 100%; height: 20px;"
| <center>'''Before looking at source code, please run [http://betaserv.vkm.ca:82/moodle/source_code_update.php this] script to update .phps files'''</center>
| <center>'''Source code now available on CVS (web access [http://moodle.cvs.sourceforge.net/moodle/moodle/ here])'''
Please note the statuses on this page are out of date. For the latest issues and bugs, check the [http://tracker.moodle.org/ Moodle bugtracker]</center>
|}
|}


Line 10: Line 7:
== Key Project Tasks ==
== Key Project Tasks ==


* <strike>'''(done)''' [[Student projects/Admin page cleanup/XML file format|Design XML DTD]]</strike> '''(done)''' [[Student projects/Admin page cleanup/OO format|Design OO format for admin]]
* <strike>'''(done)''' [[Student projects/Admin page cleanup/XML file format|Design XML DTD]]</strike> '''(done)''' [http://betaserv.vkm.ca:82/moodlemindmaps/moodle_admin_classes.png Design OO format for admin]
* '''(almost done -- 3 issues remaining)''' [[Student projects/Admin page cleanup/Admin block|Design new admin block]]
* '''(almost done -- 2 issues remaining)''' [[Student projects/Admin page cleanup/Admin block|Design new admin block]]
* '''(in progress)''' [[Student projects/Admin page cleanup/Reorg|Reorganize and port Moodle admin settings to OO structure]]
* '''(done)''' [[Student projects/Admin page cleanup/Reorg|Reorganize and port Moodle admin settings to OO structure]]
* '''(almost done -- 3+ issues remaining)''' [[Student projects/Admin page cleanup/Admin subpages|Code script for displaying and accepting input from new admin interface]]
* '''(done, except for possible bugs)''' [[Student projects/Admin page cleanup/Admin subpages|Code script for displaying and accepting input from new admin interface]]
* '''(almost done -- 2 issues remaining)''' [[Student projects/Admin page cleanup/Bookmarks|Build a per-user bookmarking system for admin settings]]
* '''(done)''' [[Student projects/Admin page cleanup/Bookmarks|Build a per-user bookmarking system for admin settings]]
* '''(not yet started)''' [[Student projects/Admin page cleanup/User management interface|Redo the user management interface]]
* '''(done)''' [[Student projects/Admin page cleanup/Upgrade|Code the necessary PHP to highlight changed settings after an upgrade]] (see admin/upgradesettings.php)
* '''(not yet started)''' [[Student projects/Admin page cleanup/Upgrade|Code the necessary PHP to highlight changed settings after an upgrade]]


== Random Notes ==
== Remaining Issues ==


* <strike>I mentioned (in my proposal) using XML to store the hierarchy. I still think this is ideal (after all, XML seems to lend itself to hierarchical data), but I think there are a few ways to expand this. Notably, along with the settings, we can store
* <strike>Find a good way to mark settings that are set on initial install</strike>
# whether a setting should appear on the initial (installation) config page (granted, this'll require a rewrite or modification of the initial config page)
* <strike>Find a good way to display settings that are added (or set to default values) during an upgrade</strike>
# if a new setting has been set to the default because of an upgrade, then we can have a config page that appears when upgrading which shows only the flagged, new variables (i.e. those that were set to defaults)</strike>
* <strike>Figure out how user_is_editing() should work in admin/pagelib.php</strike>
* Site settings and editor settings could be grouped together (but I won't jumble up settings between the two of them; they'll just have the same parent in the hierarchy).
* <strike>Specify the $paramtype for all admin_setting_configtext objects and children</strike>
* Logs and Site Files sections look good as-is... probably won't make very many changes there
* Specify the $role for all admin_externalpage and admin_settingpage objects
* Will try to improve on course administration interface (ideas to come soon)
* Specify explicit $precedence values for all admin_externalpage, admin_settingpage, and admin_category objects
* (Sort of) redo the user management interface so that we can get rid of the "Assign Teachers", "Assign Admins", etc. options on the main admin page (i.e. have a single link to a "User Management Interface" and do everything else from there.
* Fix non-language-specific strings, and add required langfile strings
* Group Modules, Filters, and Blocks (and other 16 types of plugins) under a top-level category called Plug-Ins (similar to the way it's done on [http://moodle.org/mod/data/view.php?id=6009 moodle.org])
* <strike>Work out a way to handle gd_version</strike>
* <strike>Will probably use the PHP SimpleXML extension for reading XML files; variable data will be stored in current locations, not in XML, thus no XML changes will be made by PHP</strike>
* Consider adding icons and/or custom names for admin bookmarks
* Fix icons in admin_2 block to be theme-dependent
* Find out if admin_2 block can be set up as an HTML list (and still work with Javascript)
* Fix admin/pagelib.php to include admin_2 and admin_bookmarks as default blocks
* For the course management section, allow view-only-mode? (i.e. the mode in which you don't edit categories)
* Work out which files can be safely removed from the admin dir
* See if we can eliminate the old admin block (bear in mind it's still used on course pages)


== Links ==
== Links ==
Line 34: Line 36:
* Get back to the [[Student_projects | Student Projects]] listing.
* Get back to the [[Student_projects | Student Projects]] listing.
* You can get my official SoC app [http://vkm.ca/?s=soc2006-moodle-app here].
* You can get my official SoC app [http://vkm.ca/?s=soc2006-moodle-app here].
* My sample moodle setups are <strike>[http://demoserv.vkm.ca:822/moodle here for 1.5]</strike> and [http://betaserv.vkm.ca:82/moodle here for 1.6].
* My sample moodle setups are <strike>[http://demoserv.vkm.ca:822/moodle here for 1.5]</strike>, <strike>[http://betaserv.vkm.ca:82/moodle here for 1.6]</strike> and [http://betaserv.vkm.ca:82/moodle17/moodle here for 1.7 beta].
* A beta hierarchy script (actually, a PHP hierarchy object) that I created for this is available [http://demoserv.vkm.ca:822/temp.php here].
* [http://betaserv.vkm.ca:82/moodle/blocks/HOWTO.html Useful link] for me to learn about module programming.


[[Category:Developer]]
[[Category:Developer]]
[[Category:Project]]
[[Category:Project]]

Latest revision as of 04:39, 21 September 2006

Source code now available on CVS (web access here) Please note the statuses on this page are out of date. For the latest issues and bugs, check the Moodle bugtracker


Key Project Tasks

Remaining Issues

  • Find a good way to mark settings that are set on initial install
  • Find a good way to display settings that are added (or set to default values) during an upgrade
  • Figure out how user_is_editing() should work in admin/pagelib.php
  • Specify the $paramtype for all admin_setting_configtext objects and children
  • Specify the $role for all admin_externalpage and admin_settingpage objects
  • Specify explicit $precedence values for all admin_externalpage, admin_settingpage, and admin_category objects
  • Fix non-language-specific strings, and add required langfile strings
  • Work out a way to handle gd_version
  • Consider adding icons and/or custom names for admin bookmarks
  • Fix icons in admin_2 block to be theme-dependent
  • Find out if admin_2 block can be set up as an HTML list (and still work with Javascript)
  • Fix admin/pagelib.php to include admin_2 and admin_bookmarks as default blocks
  • For the course management section, allow view-only-mode? (i.e. the mode in which you don't edit categories)
  • Work out which files can be safely removed from the admin dir
  • See if we can eliminate the old admin block (bear in mind it's still used on course pages)

Links