22 Feb, 2013
1 commit
-
…f clickable elements, some refactoring https://bugster.forgerock.org/jira/browse/OPENIDM-1174 git-svn-id: https://svn.forgerock.org/openidm/trunk@1999 d98387aa-ee2c-4292-a9e6-504d2a719fd3
19 Nov, 2012
1 commit
-
http://sources.forgerock.org/cru/CR-902 git-svn-id: https://svn.forgerock.org/openidm/trunk@1581 d98387aa-ee2c-4292-a9e6-504d2a719fd3
15 Nov, 2012
1 commit
-
http://sources.forgerock.org/cru/CR-891 This also includes global rename of _query-id to _queryId and _query-expression to _queryExpression. Note for documenters: there are several changes expected to be made soon; review the code review (linked above) and note Andi's comments git-svn-id: https://svn.forgerock.org/openidm/trunk@1531 d98387aa-ee2c-4292-a9e6-504d2a719fd3
12 Nov, 2012
1 commit
-
Updates for UI: Corrected policy, max security answer attempts, task/workflow updates. http://sources.forgerock.org/cru/CR-862 git-svn-id: https://svn.forgerock.org/openidm/trunk@1485 d98387aa-ee2c-4292-a9e6-504d2a719fd3
02 Nov, 2012
2 commits
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@1413 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
Merging in changes from UI branch to trunk git-svn-id: https://svn.forgerock.org/openidm/trunk@1412 d98387aa-ee2c-4292-a9e6-504d2a719fd3
13 Mar, 2012
1 commit
-
The refactoring affects path names to HTML content. Examples: Before http://openam.forgerock.org/doc/admin-guide/OpenAM-Admin-Guide.html#configure-authn-chains http://opendj.forgerock.org/doc/admin-guide/OpenDJ-Admin-Guide.html#chap-account-lockout http://openidm.forgerock.org/doc/integrators-guide/OpenIDM-Integrators-Guide.html#security-bootstrap After http://openam.forgerock.org/doc/admin-guide/index.html#configure-authn-chains http://opendj.forgerock.org/doc/admin-guide/index.html#chap-account-lockout http://openidm.forgerock.org/doc/integrators-guide/index.html#security-bootstrap git-svn-id: https://svn.forgerock.org/openidm/trunk@1024 d98387aa-ee2c-4292-a9e6-504d2a719fd3
20 Feb, 2012
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@976 d98387aa-ee2c-4292-a9e6-504d2a719fd3
08 Feb, 2012
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@938 d98387aa-ee2c-4292-a9e6-504d2a719fd3
07 Feb, 2012
1 commit
-
Cannot get docbook.css.source to look for anything outside the stylesheet .zip downloaded by Maven git-svn-id: https://svn.forgerock.org/openidm/trunk@930 d98387aa-ee2c-4292-a9e6-504d2a719fd3
11 Jan, 2012
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@771 d98387aa-ee2c-4292-a9e6-504d2a719fd3
03 Jan, 2012
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@718 d98387aa-ee2c-4292-a9e6-504d2a719fd3
30 Dec, 2011
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@708 d98387aa-ee2c-4292-a9e6-504d2a719fd3
09 Dec, 2011
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@594 d98387aa-ee2c-4292-a9e6-504d2a719fd3
02 Dec, 2011
1 commit
-
…e works appears to have changed since the doc was last updated git-svn-id: https://svn.forgerock.org/openidm/trunk@556 d98387aa-ee2c-4292-a9e6-504d2a719fd3
01 Dec, 2011
1 commit
-
The idea is that when you break long lines in <screen> at a space character, the reader can double-click to collapse folded lines to a single line for easy copying into a terminal window, and then double-click again to refold the lines for easy reading. Line continuations with \ would allow folded lines to be used directly, at least on *n*x, and also be syntactically correct. Yet, its harder to edit a command that used \ to continue lines. The JavaScript expects line continuations where continued lines start with a space. Lines without initial spaces do not get collapsed. For example: <screen>$ curl --user admin:admin -X PUT -d '{ "name":"joe", "firstname":"joe", "lastname":"smith", "email":"joe@abc.com", "userPassword":"11111111"}' http://localhost:8080/openidm/managed/user/joe {"_rev":"0","_id":"joe"}</screen> Shows up as: $ curl --user admin:admin -X PUT -d '{ "name":"joe", "firstname":"joe", "lastname":"smith", "email":"joe@abc.com", "userPassword":"11111111"}' http://localhost:8080/openidm/managed/user/joe {"_rev":"0","_id":"joe"} And then when you double-click: $ curl --user admin:admin -X PUT -d '{ "name":"joe", "firstname":"joe", "lastname":"smith", "email":"joe@abc.com", "userPassword":"11111111"}' http://localhost:8080/openidm/managed/user/joe {"_rev":"0","_id":"joe"} And vice versa. There's no doubt cleanup to do in the core doc sources to take advantage of this. git-svn-id: https://svn.forgerock.org/openidm/trunk@551 d98387aa-ee2c-4292-a9e6-504d2a719fd3
25 May, 2011
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@211 d98387aa-ee2c-4292-a9e6-504d2a719fd3