2009/4/7 Matt Read <[email protected]>: > > With the release of 0.6, I'd like to propose a complete overhaul of the > adminhandler, and the entire admin area, code. Right now the entire > thing is a mess of hundrends of methods scattered throughout the > adminhandler class, which each handle different things for different > admin pages. And each page handles things differently form others. I'd > like to standardize the entire thing to provide a common logic for all > the admin pages, and ajaxy stuff, to do things.
I'm definitely in favour of cleaning up the admin handler. [snip] > Parent AdminPage: > https://trac.habariproject.org/habari/browser/branches/adminhandler/htdocs/system/admin/classes/adminpage.php > > AdminHandler: > https://trac.habariproject.org/habari/browser/branches/adminhandler/htdocs/system/classes/adminhandler.php > > and an example AdminPageDashboard: > https://trac.habariproject.org/habari/browser/branches/adminhandler/htdocs/system/admin/classes/dashboardadminpage.php It may be that other handlers become similarly monolithic in the future. I think putting things in /admin may lose us flexibility and cause problems in the future. What about moving the handlers to /system/handlers/{admin,user,atom,etc}.php, and have handler-specific things in a subdirectory, /system/handlers/admin/dashboard.php, for example ? -- Michael C. Harris, School of CS&IT, RMIT University http://twofishcreative.com/michael/blog IRC: michaeltwofish #habari --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
