COmanage Developers List

[Benn Oshrin <>]

This could make sense. One thing to keep in mind is that Cake's 
view/layout functionality could help here, eg not rendering the header 
or footer when in a lightbox view.

We already do something similar for real time matching I think, and we 
already do a page refresh automatically for manual provisioning.

Thanks,

-Benn-

On 3/23/14 4:09 PM, Arlen Johnson wrote:
> One final note:
>
> Since "subsections" (as I refer to them below, meaning email, names, org
> ids, etc) can be visited from a number of different places directly,
> another approach we could take is to edit components from the
> co_people/edit page using a lightbox.
>
> I've used this one previously - it has an MIT license:
> https://github.com/dimsemenov/Magnific-Popup
> http://dimsemenov.com/plugins/magnific-popup/
>
> It provides an "iframe" mode - so we could launch the editing of
> subsections (name, id, etc) into the lightbox easily - mostly by
> simplifying the page down to just the title and form.  When editing is
> done, the user would close the lightbox, and we remain in the same
> context (though we'd likely need to reload the edit page).
>
> This might be a more elegant solution to this problem that avoids much
> refactoring of the "subsections".
>
> Arlen
>
> On 3/23/2014 2:47 PM, Arlen Johnson wrote:
> > When editing subsections of a person (roles, identifiers, org ids,
> > etc), there is no navigation to return to where we were previously.
> > This could take the form of a "back" button, a sidebar menu, or
> > breadcrumbs.  Are there reasons this should not be pursued (in other
> > words, is there some reason that knowing where to go back to is a big
> > issue), and do you have a preference?  We'll want to implement
> > breadcrumbs regardless, but I think using the sidebar consistently as
> > a means of navigation is good.  I'm leaning towards implementing it in
> > these subsections.