grouper-dev - RE: subject picker UI component
Subject: Grouper Developers Forum
List archive
- From: Chris Hyzer <>
- To: Grouper Dev <>
- Subject: RE: subject picker UI component
- Date: Wed, 17 Feb 2010 00:01:45 -0500
- Accept-language: en-US
- Acceptlanguage: en-US
Hey, It is done, here is a doc: https://spaces.internet2.edu/display/GrouperWG/Grouper+subject+picker https://bugs.internet2.edu/jira/browse/GRP-376 Maybe Im the only one who is excited about this J I need this related to how Penn will use the Grouper-KualiRice
integration, since if you want to do a simple workflow, and pick a person (e.g.
your supervisor needs to approve, but there isn’t a list of everyone’s
supervisors, so the initiator picks their supervisor), there is no way to do
that with Rice edoclite. This is also an option to use this in the Grouper UI itself, and
it can be an example for other similar UI components (e.g. a Group picker, or a
privilege picker, etc). Let me know any comments. Thanks, Chris From: Chris Hyzer
[mailto:] Hey, I briefly mentioned this before, and have started working on
it. This is a screen that allows external applications to grouper (or grouper
itself), to have a subject picker in the grouper ui. Initially I would like to
use this in Kuali workflow edoclite, but it could be used anywhere. This is the design, let me know any feedback.
There is a button on the application
which lets the user select a user. (see screenshot #1)
<script> function
grouperSubjectSelected(elementName,subjectId,subjectDescription,
pickerResultSubject) { subjectDescription =
escapeHtml(subjectDescription); subjectId = escapeHtml(subjectId); document.getElementById(elementName
+ "DescriptionSpanId").innerHTML =
subjectDescription; if (elementName
== 'subject1') {
document.getElementById(elementName + "IdSpanId").innerHTML
= subjectId; } else
if (elementName == 'subject2') {
document.getElementById(elementName + "IdSpanId").value
= subjectId; } else
{ alert("ERROR: Cant find elementName: " +
elementName); } } /** convert input into a non-null
string */ function
escapeHtml(input) { input = input.replace(/&/g, "&"); input = input.replace(/</g, "<"); input = input.replace(/>/g, ">"); return input; } </script> 6. You see the
application screen change (see attachment #4), probably a label on the screen
and a hidden field for the subject id or whatever. The
config options will have defaults for all subject pickers, and you can
customize for each one. All the text, the way the subjects are displayed,
the CSS, what is returned to the calling application, which sources are
searched, which group the results must be in, which group the user must be in,
etc. I picture the configs to be on the classpath or in a directory
(specified in media.properties). If you do nothing, no subject pickers
will be enabled, you need to add a config file for one to be used. There
isnt really a way to know which app the subject picker is used from, this is
how internet applications work. I
think in general s subject picker is more of an IdM thing, and not a
group thing, but since you can control which group the user and results need to
be in, it is related to group management (and for institutions where there isnt
an IdM equivalent). It is a downside that the application relies on the
Grouper UI being available... Also, the browser support list
of the Grouper UI will limit the calling application. Anyways,
let me know your thoughts or if anyone might be able to use this. Thanks, Chris |
- subject picker UI component, Chris Hyzer, 02/11/2010
- Re: [grouper-dev] subject picker UI component, Tom Barton, 02/12/2010
- RE: subject picker UI component, Chris Hyzer, 02/17/2010
Archive powered by MHonArc 2.6.16.