I don't like the idea of reducing unnecessary complication, especially when it comes to the user themes directory.
I don't know about you, but the URL 'user/themes/user/foo' seems ripe for confusion... My question is: why? What practical aim does this serve to users to justify this added confusion? What would be the problem with simply putting the admin and installer themes in system/themes/admin – I think we can safely assume nobody is going to name a theme "admin" – and if they do we should probably assume it is meant as a replacement for the admin interface. On Sep 29, 2008, at 9:25 PM, Andrew da Silva wrote: > > Clutter in AdminHandler got me thinking... > > Since admin and installer are themes, why are they still in > independent folders? > > Sure, admin and installer in system/themes could be troublesome, but > would it? > We control what goes in system/themes... no risk of overwriting. > Only problem I can foresee is user/themes/admin and installer... > > In the end, I think we should remove those two folders from system, it > makes no sense anymore. > > If installer is considered "administration" material, maybe we could > create... > > system/themes/admin/installer > system/themes/admin/default > system/themes/user/k2 > system/themes/user/mzingi > system/themes/user/charcoal > > And replicate in the user folder.. > > user/themes/admin/... > user/themes/user/... > > This way Habari would mainly be an API completely customizable from A > to Z... > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
