Plugin Development Use Cases > Add a Page to the Admin Theme

Hi, I hope this is the appropriate spot for this.

If there could be code samples in http://omeka.org/codex/Plugin_Use_Cases/Add_a_Page_to_the_Admin_Theme , it would be very helpful.

It still appears to be a little incomplete right now; e.g. It instructs one to create a controller in CustomAdminPage/controllers/
IndexController.php , but doesn't give the code for that.

I was looking at it because I see from looking at plugins that the general format for controllers is something like

Class MyPlugin_IndexController extends Omeka_Controller_AbstractActionController
{
public function indexAction()
{
indexAction()
{
//...
}
//...
}
}

But I'm still confused on how one associates user-accessible URIs with views defined by the PHP files in the SomePlugin/views/[admin|public|shared] folders.

Also, it might make sense to move the plugin development docs now located at http://omeka.org/codex/Plugin_Use_Cases/[pagename] to http://omeka.org/codex/Plugin_Development_Use_Cases/[pagename] , both to be consistent with the referring page http://omeka.org/codex/Plugin_Development_Use_Cases and because it clarifies that the pages are about plugin development , not general plugin use.

Thanks.

Ok, for my part, I figured out the rest from http://omeka.org/codex/MVC_Pattern_and_URL_Paths_in_Omeka . Still, it would be good for others if the http://omeka.org/codex/Plugin_Use_Cases/Add_a_Page_to_the_Admin_Theme page had the code. I'd add it, but registration for Wiki editing appears to be disabled. (Understandable -- I assume spammers and/or vandals were a problem.)