org.forgerock / org.forgerock.openidm

22 Apr, 2015

1 commit

21 Apr, 2015

2 commits

17 Apr, 2015

1 commit

16 Apr, 2015

2 commits

15 Apr, 2015

1 commit

07 Apr, 2015

1 commit

01 Apr, 2015

1 commit

10 Mar, 2015

1 commit

02 Nov, 2012

2 commits

13 Mar, 2012

1 commit

  • 2daf53af   New feature COMMWEB-37: Provide maven plugin for core documentation ... Browse Dir » 
    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
    mark
     

20 Feb, 2012

1 commit

08 Feb, 2012

1 commit

07 Feb, 2012

1 commit

26 Jan, 2012

1 commit

11 Jan, 2012

1 commit

03 Jan, 2012

1 commit

30 Dec, 2011

1 commit

09 Dec, 2011

1 commit

02 Dec, 2011

1 commit

01 Dec, 2011

1 commit

  • 745881bd   Introduce line unfolding and refolding in <screen> output for HTML ... Browse Dir » 
    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
    mark
     

25 May, 2011

1 commit