org.forgerock / org.forgerock.openidm

12 Dec, 2011

1 commit

09 Dec, 2011

12 commits

07 Dec, 2011

1 commit

06 Dec, 2011

4 commits

05 Dec, 2011

8 commits

02 Dec, 2011

2 commits

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
     

30 Nov, 2011

2 commits

  • 9158d56e   Many line changes, mainly editorial differences. ... Browse Dir » 
    I did comment out the note about disabling the reconciliation sample, because the config file had "enabled":false when I looked after installing today.

By the way, if you want external URLs to open in a new tab, you can use xlink:show="new" on the <link>.

git-svn-id: https://svn.forgerock.org/openidm/trunk@549 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    mark
     
  • 0447f5cf   Add syntax highlighting for doc sources ... Browse Dir » 
    Notice that you get syntax highlighting by adding a language attribute, such as language="javascript", to block elements that preserve whitespace like <programlisting> or <screen>.

I'm not particularly proud of the colors defined in src/main/docbkx-stylesheets/html/coredoc.xsl.
Perhaps someone less aesthetically challenged could fix that.

git-svn-id: https://svn.forgerock.org/openidm/trunk@547 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    mark
     

29 Nov, 2011

2 commits

  • 3e34b507   When I try the current nightly of 2.0.0-SNAPSHOT, I need to authenticate in orde… ... Browse Dir » 
    …r to create or read managed user JSON.

git-svn-id: https://svn.forgerock.org/openidm/trunk@543 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    mark
     
  • 35991700   Partial fix for COMMWEB-35: Allow inter-document links in core doc sources ... Browse Dir » 
    This works around http://code.google.com/p/docbkx-tools/issues/detail?id=36
allowing links that work in the HTML, and look like this in the source:

refer to the chapter on <link xlink:href="admin-guide#chap-troubleshooting"
xlink:role="http://docbook.org/xlink/role/olink"><citetitle
>Troubleshooting</citetitle></link> in the <citetitle>Administration
Guide</citetitle>.

As the olinkdb files are not currently built for other formats, the
xlink:role="http://docbook.org/xlink/role/olink" links are
ignored during output generation.

git-svn-id: https://svn.forgerock.org/openidm/trunk@542 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    mark
     

21 Nov, 2011

2 commits

18 Nov, 2011

1 commit

05 Nov, 2011

2 commits

04 Nov, 2011

1 commit

02 Nov, 2011

1 commit