Requirements

• Modules needs to be able to inject their own HTML and/or form fields into any other modules (or core) config page
• Modules needs to be able to inject their own JavaScript? within the <script></script> section (excluding form validation)
• Standard form validation functions (JavaScript?) but provide a way to allow custom form validation
• Need to be able to specific which Section the HTML/form field will appear under (e.g. Extension Options, Recording Options) within a config page (e.g. users, devices, conferences)
• Need some basic control over positioning
  • Page Header (i.e. above the various Sections)
  • Section (e.g. 'Extension Options, 'Recording Options')
  • Page Footer (i.e. below the various Sections)
  • Include a Sort Order (-10 to 10) for sorting within this, default to 0 if not specified. All 'core' should be -5 to appear earlier. Items within the same sort order are sorted alphabetically.

Discusssion

Q: Any questions ?

• Perphas we should use PEAR's QuickForm for this, and an array to define all the elements on a page. That way, it doesn't really matter where elements come from, they all just get added to the array. The array is then passed to a build function, that builds a Quickform from it and displays it on the page. Callbacks can be used to process everything.
• I think this is big enough change that I'm changing it to milestone:3.0