[PLIP-Advisories] Re: [Plone] #9311: Clean up of user related actions UI
#9311: Clean up of user related actions UI -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: closed Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: wontfix Keywords: | -+-- Changes (by esteele): * status: assigned = closed * resolution: = wontfix Comment: This PLIP has been rejected for merging into Plone 4.0 The final vote was: Alec Mitchell 0 David Glick 0 Erik Rose -1 Laurence Rowe - Matthew Wilkes - Ross Patterson -1 The Framework Team felt that the product was not finished enough to be merged at this time. I'd encourage you to resubmit this PLIP for a 4.x branch if you feel it appropriate. Thank you for your hard work. -- Ticket URL: http://dev.plone.org/plone/ticket/9311#comment:21 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9311: Clean up of user related actions UI
#9311: Clean up of user related actions UI -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by rossp): Seems incomplete as is. FWT vote: -1 for merging -- Ticket URL: http://dev.plone.org/plone/ticket/9311#comment:20 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9311: Clean up of user related actions UI
#9311: Clean up of user related actions UI -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by robgietema): Updated review at: http://svn.plone.org/svn/plone/buildouts/plone- coredev/branches/4.0/plips/plip9311-review-robgietema.txt -- Ticket URL: http://dev.plone.org/plone/ticket/9311#comment:19 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9311: Clean up of user related actions UI
#9311: Clean up of user related actions UI -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by esteele): Your PLIP has passed the Framework team's initial review. Feel free to discuss any suggested changes either here in the PLIP ticket or on the mailing lists. Final deadline for this PLIP is set for September 30. -- Ticket URL: http://dev.plone.org/plone/ticket/9311#comment:18 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9311: Clean up of user related actions UI
#9311: Clean up of user related actions UI -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by cjohansen): Tested with FAE (http://fae.cita.uiuc.edu/). Accessibility of Add Portlets control poor. The problem is the use of the onChange JavaScript event trigger in the select / element: select name=:action onchange=this.form.submit() To make applications accessible, they must be navigable by keyboard alone. Using the keyboard to navigate this select element fires the onChange trigger when using the arrow keys. I effect, the user can never get past the first choice in an option list. A fix is to remove the onChange event trigger and add a button to execute the selected option. -- Ticket URL: http://dev.plone.org/plone/ticket/9311#comment:17 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9311: Clean up of user related actions UI
#9311: Clean up of user related actions UI -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by dokter): Ready for review. -- Ticket URL: http://dev.plone.org/plone/ticket/9311#comment:15 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9311: Clean up of user related actions UI
#9311: Clean up of user related actions UI -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Description changed by dokter: Old description: '''Proposer:''' Duco Dokter[[BR]] '''Seconder:''' Alexander Limi, David Convent[[BR]] [[BR]] == Motivation == The user admin related actions, from the perspective of the user itself, are scattered over the user interface. The following ''actions'' are available: * access to the dashboard, * user data * preferences * personal preferences * profile (author info) * user folder * change password The several configuration sets are not uniform: name and email address are part of preferences for example, but are clearly user data, as opposed to wysiwyg editor setting or skin preference. Also, the personal bar is really in the way of the overall design. == Assumptions == It is hard for users to determine exactely what access to use to get to a specific setting. == Proposal Implementation == User related actions are moveed to new package '''plone.app.users'''. What should be available to the user is: * public profile, based on tiles. The user can determine what to show to the public, for instance a 'recently added' tile, or an overview of specific user data. * preferences, where a user can set favorite editor, skin, etc. * user data, where a user can administer personal data, like email address, surname, etc. * dashboard * change password * user folder In the UI, there should only be a maximum of three accessors: 1. a clickable login name, that takes the user to his/her dashboard 2. ''Account'', that takes the user to user the, config panel. This panel provides three tabs: user data, preferences and change password. 3. ''My stuff'', in case a user has a personal folder. Also, the user can set his/her start page for the site in the preferences. This should be the page the user is directed to after login. Default is the plone start page. Other options are dashboard, my stuff, etc. The personal bar will be moved to the top of the page, to remove it from overall design, and give it a clear place. The user data and preferences will be implemented using the same back-end as in the current situation, only the way to navigate there will be changed, and the forms will be implemented using zope.forms, located in tabs in an overall user admin screen. == Deliverables == Personal bar moved to top, user data and preferences clearly separated, less entry points for user functionality, unit tests for all forms. Other than that, localization and unit tests are largely in place, but need to be adapted to the new situation and moved to plone.app.users. Documentation will be altered and moved whereever necessary. == Risks == The new design is a deviation from the current situation; migration to Plone 4 will require adaptation of users to the new way of accessing functionality. == Participants == Duco Dokter, dokter Kees Hink, khink Kim Chee Leong, kcleong David Convent, davconvent == Progress == Some of the work has been done at the Baarn 2009 sprint New description: '''Proposer:''' Duco Dokter[[BR]] '''Seconder:''' Alexander Limi, David Convent[[BR]] [[BR]] == Motivation == The user admin related actions, from the perspective of the user itself, are scattered over the user interface. The following ''actions'' are available: * access to the dashboard, * user data * preferences * personal preferences * profile (author info) * user folder * change password The several configuration sets are not uniform: name and email address are part of preferences for example, but are clearly user data, as opposed to wysiwyg editor setting or skin preference. Also, the personal bar is really in the way of the overall design. == Assumptions == It is hard for users to determine exactely what access to use to get to a specific setting. == Proposal Implementation == User related actions are moveed to new package '''plone.app.users'''. What should be available to the user is: * public profile, based on tiles. The user can determine what to show to the public, for instance a 'recently added' tile, or an overview of specific user data. * preferences, where a user can set favorite editor, skin, etc. * user data, where a user can administer personal data, like email address, surname, etc. * dashboard * change password * user folder In the UI, there should only be a maximum of three accessors: 1. a clickable login name, that takes the user to his/her dashboard 2. ''Account'', that takes the user to user the, config panel. This
[PLIP-Advisories] Re: [Plone] #9311: Clean up of user related actions UI
#9311: Clean up of user related actions UI -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Changes (by dokter): * status: new = assigned -- Ticket URL: http://dev.plone.org/plone/ticket/9311#comment:12 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9311: Clean up of user related actions UI
#9311: Clean up of user related actions UI -+-- Reporter: dokter |Owner: Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9311#comment:10 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
