Was trying to think of a way to finally organize the AdminHandler..
and had an AdminThemeHandler opened also...

Then it hit... callbacks.... we use them in rewrite rules, 'handler'
and 'action'...

We merge them array('class','function') and then make a parameter
'callback' accepting an array of arrays:

array(
 'POST' => array('AdminHandler','post_comments'),
 'GET' => array('AdminThemeHandler','display_comments'),
)

Anyhow, thought I'ld mention it hear to get the idea rolling!

On Sep 30, 11:54 am, Arthus Erea <[EMAIL PROTECTED]> wrote:
> I don't think this needs to be high priority, but it should be  
> considered for eventual implementation.
>
> On Sep 30, 2008, at 9:11 AM, Christian Mohn (h0bbel) wrote:
>
>
>
>
>
>
>
> > Agreed.
>
> > I don't really see why we should spend any time on this, at least  
> > not now.
> > There are other more pressing issues that should be taken care of.
>
> > Christian
> > -----Original Message-----
> > From: [email protected] [mailto:habari-
> > [EMAIL PROTECTED] On
> > Behalf Of Owen Winkler
> > Sent: 30. september 2008 14:14
> > To: [email protected]
> > Subject: [habari-dev] Re: Why are admin and installer still distinct  
> > from
> > themes?
>
> > I think this discussion is inappropriate at this time.
>
> > By allowing easy user-supplied admin themes we'd be encouraging a
> > situation where users could quite easily damage their overall  
> > install in
> > many ways, including making their admin inaccessible or causing  
> > discrete
> > components of the admin to fail.
>
> > In addition, nearly the entire admin "theme" relies on specific  
> > methods
> > with the adminhandler, the analog for the admin theme's theme.php.
> > Writing any supplemental admin theme would likely involve rewriting a
> > significant and impractical amount of the handler code.
>
> As I understand it, no you wouldn't.
>
> The same handler would be used for the new admin theme, it would  
> simply use different presentation files.
>
>
>
>
>
> > There are so many other things to do right now to bring Habari into a
> > useful state with the admin that we have, I simply don't see any
> > compelling reason to make this change now, or even provide the  
> > rudiments
> > for it.  It certainly doesn't simplify any other task currently in
> > queue.  Is there some latent user request for this?
>
> > Owen
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to