COmanage Developers List

[Benn Oshrin <>]

I'm vaguely remembering that when we discussed this last time we 
concluded that we'd get rid of the Back button and just let the browser 
navigation and new menus solve that problem. However, we were going to 
keep Cancel buttons for forms since it should be obvious how to exit a 
form without committing a change.

Assuming we [still] want to go ahead with that approach, certain forms 
are already smart enough to know where the cancel button should take 
you. For example if you navigate

 My Population > edit a person > Add an Identifier

or

 Organizational Identities > edit a person > Add an Identifier

either way you end up at /registry/identifiers/add. However, the form 
knows from the presence of an orgidentityid parameter or copersonid 
parameter where to send you back to if you click cancel.

So I think the issues are

(1) Not all forms have Cancel buttons, some have Back... change them to 
Cancel
(2) Make sure all Cancel buttons Do The Right Thing regardless of entry flow
(3) Toss all other Back buttons.

How does that sound?

-Benn-

On 6/19/12 8:36 PM, Marie Huynh wrote:
> I think I've found all the broken back links.  Some are forgetting the
> CO, which should be an easy fix.  Some have multiple entry points and
> one hardcoded back button.  We can have multiple "back" buttons that say
> "back to X page" and "back to Y page" and let the user choose one.  We
> could also just use this javascript option that will back up through
> history or make a best guess if javascript is off:
>
> http://www.sightspecific.com/~mosh/WWW_FAQ/back.html
>
> Marie
>
> On Fri, Jun 1, 2012 at 8:05 AM, Marie Huynh 
> <
> <mailto:>>
>  wrote:
>
>     I've attached my notes on what happens when navigating through the
>     dropdown menu and then via links on the following pages.  It's in
>     spreadsheet-form.
>
>     Breadcrumbs are useful when there are many levels that people might
>     want to return to.  Given the existence of the dropdown menu, it's not
>     difficult for users to get to other parts of the site and I don't
>     think this adds anything useful at this time.  I propose we figure out
>     where cancellations/backs should go and if there should be a default
>     in order to fix them.  We'll have to deal with the case of forms that
>     have multiple points of entry - should they cancel out into a more
>     general place(some major landing page) or should we rely on a browser
>     back button?  Alternatively, we could record history for backing up,
>     but that could get ugly.
>
>     Marie
>
>     On Tue, May 29, 2012 at 2:45 PM, Marie Huynh (JIRA)
>     
> <
>  
> <mailto:>>
>  wrote:
>      >
>      >    [
>     
> https://bugs.internet2.edu/jira/browse/CO-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107#comment-17107
>     ]
>      >
>      > Marie Huynh commented on CO-70:
>      > -------------------------------
>      >
>      > http://book.cakephp.org/2.0/en/core-libraries/helpers/html.html
>      >
>      > in the default layout template:
>      > print $this->Html->getCrumbs(' > ', 'Home');
>      >
>      > in each view:
>      > $this->Html->addCrumb('Users', '/users');
>      > $this->Html->addCrumb('Add User', '/users/add');
>      >
>      > for:
>      > Home > Users > Add User
>      >
>      >> Back button inconsistencies
>      >> ---------------------------
>      >>
>      >>                 Key: CO-70
>      >>                 URL: https://bugs.internet2.edu/jira/browse/CO-70
>      >>             Project: COmanage
>      >>          Issue Type: Improvement
>      >>          Components: Registry
>      >>    Affects Versions: COmanage Gears 0.1 (Lump of Clay)
>      >>            Reporter: Benn Oshrin
>      >>            Assignee: Marie Huynh
>      >>            Priority: Major
>      >>              Labels: sprint06
>      >>             Fix For: COmanage Registry 0.6 (Helpful Hexagon)
>      >>
>      >>
>      >> The Back/Cancel buttons on various pages are inconsistent.
>     Standardize, or perhaps just get rid of them.
>      >> - Menu > View My CO Profile > Edit > Back (goes to CO People)
>      >> - Some are emitted via $html->, others $this->Html
>      >
>      > --
>      > This message is automatically generated by JIRA.
>      > If you think it was sent incorrectly, please contact your JIRA
>     administrators:
>     https://bugs.internet2.edu/jira/secure/ContactAdministrators!default.jspa
>      > For more information on JIRA, see:
>     http://www.atlassian.com/software/jira
>      >
>      >