[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GMG-Devel] Proposal: Allow plugins to hook into account nav

From: Christopher Allan Webber
Subject: Re: [GMG-Devel] Proposal: Allow plugins to hook into account nav
Date: Wed, 28 Nov 2012 13:28:07 -0600
User-agent: mu4e 0.9.9-dev6; emacs

Heya Nathan,

Sorry about the slow reply (okay, there's several emails you sent, sorry
about being slow to reply to all of them :)).

I think this is really important and good... I haven't gotten to look at
the code yet.  The screenshots look promising.

As for plugin stuff, my plan is that in 0.3.3 I'll be plugin'ifying
OpenStreetMap stuff (that was my code plan for 0.3.2 until it became
obvious that I'd be 100% on the campaign :)) and looking personally at
some of how the plugin stuff is structured.  Soooooo... I've marked this
locally in my orgmode to look at your branch again in tandem with
that.... I don't think we'll be able to make any move on this in 0.3.2

On another note, we really ought to have a conversation about "how do
user account things work really?"  We've had a dropdown recently, and
then it went away, and now we seem to have a "dashboard", but we don't
really know what we want I think.

I think we already agree that this is an issue; I'm not sure how to
actually start resolving this.

To that end, I've created a bug for us to clarify design and for now
assigned to Jef:

 - Chris

Nathan Yergler writes:

> Hello all,
> As I've been using the OAuth plugin, I've realized that the
> functionality is currently a little buried. I was thinking that it'd
> be nice if the list of my OAuth clients were easily accessible from my
> account page. It's important that users be able to easily find their
> authorized connections and remove them if they decide a client
> application isn't operating in their best interest, and right now
> that's not the case.
> I was looking at the plugin API, and decided to try and leverage the
> existing hooks for this idea. I'd like to suggest defining a hook as a
> string in tools/ so that plugins and templates can easily
> refer to it, and add a docstring there stipulating what implementers
> are expected to provide. The hook I've implemented, ACCOUNT_PAGES,
> allows plugins to return URLs and labels to be added to the account
> edit page navigation. [For the sake of prototyping, I just added a
> sidebar; if people think this is a reasonable idea, someone else
> should have a look at making sure this looks reasonable and works with
> the adaptive CSS already in place.]
> I've pushed this prototype to a branch in my personal clone; you can
> find the single commit at
> You can find screenshots of how it looks for the edit password page
> and the OAuth connections page at
> At this point I'm curious if other people think this is conceptually a
> good idea, and then feedback on the implementation.
> Thanks,
> _______________________________________________
> devel mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]