You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2017/04/03 23:29:57 UTC
[43/59] [abbrv] [partial] isis-site git commit: ISIS-1521: deletes
content-OLDSITE
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/custom-representations.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/custom-representations.md b/content-OLDSITE/components/viewers/restfulobjects/custom-representations.md
deleted file mode 100644
index af0da71..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/custom-representations.md
+++ /dev/null
@@ -1,95 +0,0 @@
-Title: Custom Representations
-
-[//]: # (content copied to _user-guide_extending_restfulobjects-viewer)
-
-{note
-This API should be considered beta, as it may change in the future in response to emerging requirements
-}
-
-The Restful Objects viewer implements the [Restful Object spec](http://restfulobjects.org), meaning that it:
-
-* defines a well-defined set of endpoint URLs as resources
-* generates a well-defined set of (JSON) representations when these resources are accessed.
-
-There are, however, a number of other "standards" for defining representations, among these:
-
-* [HAL](http://stateless.co/hal_specification.html) (Mike Kelly)
-* [Collection+JSON](http://amundsen.com/media-types/collection/) (Mike Amundsen)
-* [Siren](https://github.com/kevinswiber/siren) (Kevin Swiber)
-* [JSON API](http://jsonapi.org/) (Steve Klabnik)
-* [Hyper+JSON](https://github.com/cainus/hyper-json-spec) (Gregg Cainus)
-* [JSON-LD](https://www.w3.org/TR/json-ld/) (W3C)
-* [Hydra](http://www.markus-lanthaler.com/hydra/) (Markus Lanthaler)
-
-A good discussion about the relative merits of several of these different hypermedia formats can be found [here](https://groups.google.com/forum/#!msg/api-craft/NgjzQYVOE4s/EAB2jxtU_TMJ).
-
-While Isis' Restful Objects viewer only has "out-of-the-box" support for the representations defined in the Restful Objects spec,
-it is possible to plugin a custom representation generator that can produce any arbitrary representation.
-
-## API
-
-The API to implement is the `RepresentationService` API:
-
- import javax.ws.rs.core.Response;
- import org.apache.isis.applib.annotation.Programmatic;
- import org.apache.isis.core.metamodel.adapter.ObjectAdapter;
- import org.apache.isis.viewer.restfulobjects.rendering.RendererContext;
- import org.apache.isis.viewer.restfulobjects.rendering.domainobjects.*;
-
- public interface RepresentationService {
-
- @Programmatic
- Response objectRepresentation(
- Context rendererContext,
- ObjectAdapter objectAdapter);
-
- @Programmatic
- Response propertyDetails(
- Context rendererContext,
- ObjectAndProperty objectAndProperty,
- MemberReprMode memberReprMode);
-
- @Programmatic
- Response collectionDetails(
- Context rendererContext,
- ObjectAndCollection objectAndCollection,
- MemberReprMode memberReprMode);
-
- @Programmatic
- Response actionPrompt(
- Context rendererContext,
- ObjectAndAction objectAndAction);
-
- @Programmatic
- Response actionResult(
- Context rendererContext,
- ObjectAndActionInvocation objectAndActionInvocation,
- ActionResultReprRenderer.SelfLink selfLink);
-
- public static interface Context extends RendererContext {
- ObjectAdapterLinkTo getAdapterLinkTo();
- }
- }
-
-Restful Objects' out-of-the-box support for Restful Objects spec uses this same API, specifically `RepresentationServiceForRestfulObjects` (in the `org.apache.isis.viewer.restfulobjects.rendering.service` package).
-
-Each of these methods provides:
-* a `RendererContext`, providing access to request-specific context (eg HTTP headers), session-specific context (eg authentication) and global context (eg configuration settings)
-* an object representing the information to be rendered, eg `ObjectAdapter`, `ObjectAndProperty`, `ObjectAndCollection` etc
-* for members, whether the representation is in read/write mode (`MemberReprMode`)
-
-## Configuring
-
-Implement the service and register in `WEB-INF/isis.properties`, eg:
-
- isis.services=...,\
- com.mycompany.myservice.RepresentationServiceForMyRestApi,
- ...
-
-This will replace the default representation.
-
-## See also
-
-If all that is required is a very simple representations (of objects), see [here](simplified-object-representation.html).
-
-Or, it is also possible to simply suppress certain elements; see [here](suppressing-elements-of-the-representations.html).
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/event-serializer-rospec.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/event-serializer-rospec.md b/content-OLDSITE/components/viewers/restfulobjects/event-serializer-rospec.md
deleted file mode 100644
index 426059d..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/event-serializer-rospec.md
+++ /dev/null
@@ -1,42 +0,0 @@
-Title: Event Serializer for the RO Spec
-
-[//]: # (content copied to _user-guide_isis-addons-modules)
-
-The [Publishing Service](../../../reference/services/publishing-service.html) enables Isis to publish action invocations and also changes of domain objects to third party systems.
-
-One of the APIs defined by this service is the `EventSerializer`, such that the event can be rendered into different formats. The Restful Objects viewer provides an implementation of this API, serializing the the provided `EventPayload` into the form specified by the [Restful Objects spec](http://restfulobjects.org). The serializer itself is part of the `org.apache.isis.viewer:isis-viewer-restfulobjects-rendering` module.
-
-For example, this is the JSON generated on an action invocation:
-
- 
-
-while this is the object change JSON:
-
- 
-
-
-If you configure the default [PublishingService](../../../reference/services/publishing-service.html) along with the `RestfulObjectsSpecEventSerializer` (part of [isis-module-publishing](https://github.com/isisaddons/isis-module-publishing)), then you should see JSON being written to your console.
-
-
-### Registering and Configuring the Serializer
-
-To register the serializer with Isis, add the following to `isis.properties`:
-
-<pre>
-isis.services=<i>...other services...</i>,\
- org.apache.isis.viewer.restfulobjects.rendering.eventserializer.RestfulObjectsSpecEventSerializer
-</pre>
-
-In addition, the `baseUrl` to use in hyperlinks must be specified, also in `isis.properties`; for example:
-
-<pre>
-isis.viewer.restfulobjects.RestfulObjectsSpecEventSerializer.baseUrl=https://myapp.mycompany.com:8080/restful/.
-</pre>
-
-If no `baseUrl` is specified, then the default URL is `http://localhost:8080/restful/`.
-
-{note
-Because the `baseUrl` will be different in production vs development, you will probably want to [configure Isis](../../../reference/configuration-files.html) to pick up its configuration file
-from an external directory.
-}
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/honor-ui-hints.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/honor-ui-hints.md b/content-OLDSITE/components/viewers/restfulobjects/honor-ui-hints.md
deleted file mode 100644
index 1178221..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/honor-ui-hints.md
+++ /dev/null
@@ -1,24 +0,0 @@
-Title: Honor UI Hints
-
-[//]: # (content copied to _user-guide_restful-objects-viewer)
-
-{note
-These configuration settings should be considered beta, and are likely to change in the future in response to emerging requirements.
-}
-
-By default the representations generated by Restful Objects ignore any Isis metamodel hints referring to the UI.
-In particular, if a collection is annotated then `Render(EAGERLY)` then the contents of the collection are *not*
-eagerly embedded in the object representation.
-
-However, this behaviour can be overridden.
-
-## Global Configuration
-
-Configuring the Restful Objects viewer to honor UI hints globally is done using the
-following property (typically added to `WEB-INF/viewer_restfulobjects.properties`):
-
- isis.viewer.restfulobjects.honorUiHints=true
-
-## Per request
-
-This is not currently supported (though may be in the future).
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/images/action-invocation-published-to-stderr.png
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/images/action-invocation-published-to-stderr.png b/content-OLDSITE/components/viewers/restfulobjects/images/action-invocation-published-to-stderr.png
deleted file mode 100644
index b0b3ca8..0000000
Binary files a/content-OLDSITE/components/viewers/restfulobjects/images/action-invocation-published-to-stderr.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/images/changed-object-published-to-stderr.png
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/images/changed-object-published-to-stderr.png b/content-OLDSITE/components/viewers/restfulobjects/images/changed-object-published-to-stderr.png
deleted file mode 100644
index f894d8d..0000000
Binary files a/content-OLDSITE/components/viewers/restfulobjects/images/changed-object-published-to-stderr.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/pretty-printing.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/pretty-printing.md b/content-OLDSITE/components/viewers/restfulobjects/pretty-printing.md
deleted file mode 100644
index 0cd07d6..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/pretty-printing.md
+++ /dev/null
@@ -1,8 +0,0 @@
-Title: Pretty Printing
-
-[//]: # (content copied to _user-guide_restful-objects-viewer)
-
-The JSON representations generated by the Restful Objects viewer are in compact form if the
-[deployment type](../../../reference/deployment-types.html) is SERVER (ie production), but will automatically be
-"pretty printed" (in other words indented) if the deployment type is PROTOTYPE.
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/release-notes/about.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/release-notes/about.md b/content-OLDSITE/components/viewers/restfulobjects/release-notes/about.md
deleted file mode 100644
index 1fcd4ee..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/release-notes/about.md
+++ /dev/null
@@ -1,9 +0,0 @@
-Title: Release Notes
-
-As of 1.6.0, the Restful Objects viewer is part of Isis Core.
-
-- [isis-viewer-restfulobjects-2.3.0](isis-viewer-restfulobjects-2.3.0.html) (for isis-core-1.5.0)
-- [isis-viewer-restfulobjects-2.2.0](isis-viewer-restfulobjects-2.2.0.html) (for isis-core-1.4.0)
-- [isis-viewer-restfulobjects-2.1.0](isis-viewer-restfulobjects-2.1.0.html) (for isis-core-1.3.0)
-- [isis-viewer-restfulobjects-2.0.0](isis-viewer-restfulobjects-2.0.0.html) (for isis-core-1.2.0)
-- [isis-viewer-restfulobjects-1.0.0](isis-viewer-restfulobjects-1.0.0.html)
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-1.0.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-1.0.0.md b/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-1.0.0.md
deleted file mode 100644
index 8d61b03..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-1.0.0.md
+++ /dev/null
@@ -1,17 +0,0 @@
-Title: isis-viewer-restfulobjects-1.0.0
-
-<h2> Improvement
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-194'>ISIS-194</a>] - Allow JSON viewer to work with object stores other than the in-memory objectstore.
-</li>
-</ul>
-
-
-<h2> Bug
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-256'>ISIS-256</a>] - NullPointerReference exceptions when attempting to persist an object
-</li>
-</ul>
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.0.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.0.0.md b/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.0.0.md
deleted file mode 100644
index ff5aadc..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.0.0.md
+++ /dev/null
@@ -1,21 +0,0 @@
-Title: viewer-restfulobjects-2.0.0
-
-<h2> New Feature
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-323'>ISIS-323</a>] - Provide the capability to publish events, either changed objects or invoked actions
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-410'>ISIS-410</a>] - RO viewer support @Render(EAGERLY) for collections
-</li>
-</ul>
-
-<h2> Improvement
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-233'>ISIS-233</a>] - implement restfulobjects-viewer up to RO spec 1.0.0
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-362'>ISIS-362</a>] - Upgrade to JMock 2.6.0
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-387'>ISIS-387</a>] - Enhance PublishingService and AuditingService for created and deleted objects (as well as just updated objects).
-</li>
-</ul>
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.1.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.1.0.md b/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.1.0.md
deleted file mode 100644
index 60a738c..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.1.0.md
+++ /dev/null
@@ -1,42 +0,0 @@
-Title: viewer-restfulobjects-2.1.0
-
-
-<h2> New Feature
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-553'>ISIS-553</a>] - Provide view model support, as sketched out in the Restful Objects spec
-</li>
-</ul>
-
-
-<h2> Improvement
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-411'>ISIS-411</a>] - Enhance RO to allow EAGER rendering of properties (as well as collections)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-509'>ISIS-509</a>] - Tidy up and rationalize Util classes in core (and all dependents)
-</li>
-</ul>
-
-
-
-<h2> Bug
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-318'>ISIS-318</a>] - Restful Objects viewer returning 500 instead of 400 when given bad input
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-413'>ISIS-413</a>] - RO representation of entities with a null LocalDate failing with an ClassCastException
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-464'>ISIS-464</a>] - Some trivial cleanup
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-479'>ISIS-479</a>] - Properties not getting updated as per 14.2 in RO Spec
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-481'>ISIS-481</a>] - Quickstart RO viewer - some links are broken
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-496'>ISIS-496</a>] - Quickstart RO viewer - a link is broken
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-526'>ISIS-526</a>] - Action Resource Parameters representation
-</li>
-</ul>
-
-
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.2.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.2.0.md b/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.2.0.md
deleted file mode 100644
index 2e8dc0b..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.2.0.md
+++ /dev/null
@@ -1,9 +0,0 @@
-Title: viewer-restfulobjects-2.2.0
-
-<h2> Task
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-695'>ISIS-695</a>] - Tidy-up tasks for Isis 1.4.0 release
-</li>
-</ul>
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.3.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.3.0.md b/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.3.0.md
deleted file mode 100644
index 39eede0..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/release-notes/isis-viewer-restfulobjects-2.3.0.md
+++ /dev/null
@@ -1,9 +0,0 @@
-Title: viewer-restfulobjects-2.3.0
-
-<h2> Task
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-792'>ISIS-792</a>] - Tidy-up tasks for Isis 1.5.0 release
-</li>
-</ul>
-
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/simplified-object-representation.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/simplified-object-representation.md b/content-OLDSITE/components/viewers/restfulobjects/simplified-object-representation.md
deleted file mode 100644
index 0b5cb6f..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/simplified-object-representation.md
+++ /dev/null
@@ -1,75 +0,0 @@
-Title: Simplified Object Representation
-
-[//]: # (content copied to _user-guide_restful-objects-viewer)
-
-> Enabling these settings makes the representations non-standard with respect to the [Restful Object spec](http://restfulobjects.org).
-
-
-{note
-These configuration settings should be considered beta, and are likely to change in the future in response to emerging requirements
-}
-
-The representations specified by the [Restful Object spec](http://restfulobjects.org) are very rich in hypermedia
-controls and metadata, intended to support a wide variety of possible REST clients. As described [here](suppressing-elements-of-the-representations.html), it is possible to suppress various elements of these representations.
-Even then, though, the representations may be too complex for some bespoke REST clients that require a very "flat"
-object representation.
-
-The Restful Objects viewer therefore supports generating a much simpler representation of objects.
-
-## Global Configuration
-
-Configuring the Restful Objects viewer globally to generate the simple object representation is done using the
-following property (typically added to `WEB-INF/viewer_restfulobjects.properties`):
-
- isis.viewer.restfulobjects.objectPropertyValuesOnly=true
-
-This generates a representation such as:
-
- {
- "title" : "Buy milk due by 2014-10-27",
- "domainType" : "TODO",
- "instanceId" : "L_0",
- "members" : {
- "description" : "Buy milk",
- "category" : "Domestic",
- "subcategory" : "Shopping",
- "complete" : false,
- "versionSequence" : 1,
- "relativePriority" : 2,
- "dueBy" : "2014-10-27",
- "cost" : "0.75",
- "notes" : null,
- "attachment" : null,
- "doc" : null
- },
- "links" : [
- {
- "rel" : "self",
- "href" : "http://localhost:8080/restful/objects/TODO/L_0",
- "method" : "GET",
- "type" : "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
- "title" : "Buy milk due by 2014-10-27"
- },
- {
- "rel" : "describedby",
- "href" : "http://localhost:8080/restful/domain-types/TODO",
- "method" : "GET",
- "type" : "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
- }
- ],
- "extensions" : {
- "oid" : "TODO:L_0"
- },
- }
-
-
-## Per request
-
-This is not currently supported (though may be in the future).
-
-## See also
-
-Rather than returning a completely different representation for objects, it is also possible to simply suppress certain elements;
-see [here](suppressing-elements-of-the-representation.html).
-
-On the other hand, if complete control over all representations is required, see [here](custom-representations.html).
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/suppressing-elements-of-the-representations.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/suppressing-elements-of-the-representations.md b/content-OLDSITE/components/viewers/restfulobjects/suppressing-elements-of-the-representations.md
deleted file mode 100644
index a202835..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/suppressing-elements-of-the-representations.md
+++ /dev/null
@@ -1,49 +0,0 @@
-Title: Suppressing Elements of the Representations
-
-[//]: # (content copied to _user-guide_restful-objects-viewer)
-
-> Enabling these settings makes the representations non-standard with respect to the [Restful Object spec](http://restfulobjects.org).
-> In the future the spec may be updated to allow such extensions.
-
-
-{note
-These configuration settings should be considered beta, and are likely to change in the future in response to emerging requirements
-}
-
-The representations specified by the [Restful Object spec](http://restfulobjects.org) are very rich in hypermedia
-controls and metadata, intended to support a wide variety of possible REST clients. However, if an application is
-providing its REST API only for a small well-defined set of REST clients, then it is possible to suppress (remove)
-various elements of these representations.
-
-## Global Configuration
-
-Suppressing of elements can be done using globally using the following properties (typically added to
-`WEB-INF/viewer_restfulobjects.properties`):
-
- isis.viewer.restfulobjects.suppressDescribedByLinks=true
- isis.viewer.restfulobjects.suppressUpdateLink=true
- isis.viewer.restfulobjects.suppressMemberId=true
- isis.viewer.restfulobjects.suppressMemberLinks=true
- isis.viewer.restfulobjects.suppressMemberExtensions=true
- isis.viewer.restfulobjects.suppressMemberDisabledReason=true
-
-where, respectively, these suppress:
-
-* "describedby" links (on all representations)
-* "update" link (on object representation)
-* "id" json-prop for object members (on object representation and member detail representations)
-* "links" json-prop for object members (on the object representation and member detail representations)
-* "extensions" json-prop for object members (on the object representation and member detail representations)
-* "disabledReason" json-prop for object members (on the object representation and member detail representations)
-
-The defaults for all of these is false, meaning that the hypermedia/metadata is NOT suppressed.
-
-## Per request
-
-This is not currently supported (though may be in the future).
-
-## See also
-
-If even simpler representations (of objects) are required, see [here](simplified-object-representation.html).
-
-If complete control over all representations is required, see [here](custom-representations.html).
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/restfulobjects/using-chrome-tools.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/restfulobjects/using-chrome-tools.md b/content-OLDSITE/components/viewers/restfulobjects/using-chrome-tools.md
deleted file mode 100644
index ef156d1..0000000
--- a/content-OLDSITE/components/viewers/restfulobjects/using-chrome-tools.md
+++ /dev/null
@@ -1,8 +0,0 @@
-Title: Interacting with the REST API using Chrome Plugins
-
-[//]: # (content copied to _user-guide_restful-objects-viewer)
-
-The screencast below shows how to explore the Restful API using Chrome plugins/extensions, and how we use them to write end-2-end (TCK) tests for the Restful Objects viewer.
-
-<iframe width="840" height="472" src="//www.youtube.com/embed/_-TOvVYWCHc" frameborder="0" allowfullscreen></iframe>)
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/scimpi/about.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/scimpi/about.md b/content-OLDSITE/components/viewers/scimpi/about.md
deleted file mode 100644
index e81228b..0000000
--- a/content-OLDSITE/components/viewers/scimpi/about.md
+++ /dev/null
@@ -1,19 +0,0 @@
-Title: Scimpi viewer
-
-{note
-This component has been retired. The source is in mothballed/component/viewer/dnd.
-}
-
-The scimpi module provides a webapp viewer that out-of-the-box provides a similar interface to that provided by the [HTML viewer](../html/about.html).
-
-However, unlike the HTML viewer it allows the user interface to be extensively customized.
-
-### Customization
-
-Scimpi works by searching for a specific page to render the domain object, eg `Customer.shtml` to render a `Customer` object. If none is found, it always falls back to a generic page, which can render any object.
-
-Customization therefore is accomplished by providing a specific page. The elements of this page can be any of the tags that Scimpi understands.
-
-### Releases
-
-- See [release notes](release-notes/about.html).
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/scimpi/release-notes/about.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/scimpi/release-notes/about.md b/content-OLDSITE/components/viewers/scimpi/release-notes/about.md
deleted file mode 100644
index 9464b5c..0000000
--- a/content-OLDSITE/components/viewers/scimpi/release-notes/about.md
+++ /dev/null
@@ -1,7 +0,0 @@
-Title: Release Notes
-
-<!--
-- [isis-xxx-yyy-1.0.0](isis-xxx-yyy-1.0.0.html)
--->
-
-While incubating, this component was released as part of core. There have been no releases of this component since Isis graduated out of the incubator.
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/about.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/about.md b/content-OLDSITE/components/viewers/wicket/about.md
deleted file mode 100644
index f363ca1..0000000
--- a/content-OLDSITE/components/viewers/wicket/about.md
+++ /dev/null
@@ -1,15 +0,0 @@
-Title: Wicket viewer
-
-[//]: # (content copied to _user-guide_xxx)
-
-The wicket viewer provides a customizable webapp for an Isis domain model, implemented using the [Apache Wicket](http://wicket.apache.org) web framework.
-
-## Releases
-
-- See [release notes](release-notes/about.html).
-
-## Further reading
-
-The [main documentation page](../../../documentation.html#wicket-viewer) lists the pages available for the Wicket viewer.
-
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/application-menu-layout.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/application-menu-layout.md b/content-OLDSITE/components/viewers/wicket/application-menu-layout.md
deleted file mode 100644
index c58ff1a..0000000
--- a/content-OLDSITE/components/viewers/wicket/application-menu-layout.md
+++ /dev/null
@@ -1,152 +0,0 @@
-Title: Application menu layout (1.8.0)
-
-[//]: # (content copied to _user-guide_wicket-viewer)
-
-The actions of domain services are made available as an application menu bar. By default each domain service
-corresponds to a single menu on this menu bar, with its actions as the drop-down menu items. This is rarely exactly
-what is required, however. The `@MemberOrder` and `@DomainServiceLayout` annotations can be used to rearrange the
-placement of menu items.
-
-The screenshots below are taken from [Estatio](http://github.com/estatio/estatio), and open source estate management
-application built using Apache Isis.
-
-## @DomainServiceLayout
-
-Menus for domain services can be placed either on a primary, secondary or tertiary menu bar.
-
-<img src="images/application-menu-layout-menus.png" width="800"></img>
-
-Within a single top-level menu (eg "Fixed Assets") there can be actions from multiple services. The Wicket viewer
-automatically adds a divider between each:
-
-<img src="images/application-menu-dividers.png" width="300"></img>
-
-In the example above the top-level menu combines the actions from the `Properties`, `Units` and `FixedAssetRegistrations`
-services. The `Properties` service is annotated:
-
- @DomainServiceLayout(
- named="Fixed Assets",
- menuBar = DomainServiceLayout.MenuBar.PRIMARY,
- menuOrder = "10.1"
- )
- public class Properties ... { ... }
-
-while the `Units` service is annotated:
-
- @DomainServiceLayout(
- named="Fixed Assets",
- menuBar = DomainServiceLayout.MenuBar.PRIMARY,
- menuOrder = "10.2"
- )
- public class Units ... { ... }
-
-and similarly `FixedAssetRegistrations` is annotated:
-
- @DomainServiceLayout(
- named="Fixed Assets",
- menuBar = DomainServiceLayout.MenuBar.PRIMARY,
- menuOrder = "10.3"
- )
- public class FixedAssetRegistrations ... { ... }
-
-Note that in all three cases the value of the `named` attribute and the `menuBar` attribute is the same: "Fixed Assets"
-and PRIMARY. This means that all will appear on a "Fixed Assets" menu in the primary menu bar.
-
-Meanwhile the value of `menuOrder` attribute is significant for two reasons:
-
-* first, for these three services on the same ("Fixed Assets") top-level menu, it determines the relative order of their
- sections (`Properties` first, then `Units`, then `FixedAssetRegistrations`)
-* second, it determines the placement of the top-level menu itself ("Fixed Assets") with respect to other top-level
- menus on the menu bar.
-
-To illustrate this latter point, the next top-level menu on the menu bar, "Parties", is placed after "Fixed Assets"
- because the `menuOrder` of the first of its domain services, namely the `Parties` service, is higher than that for
- "Fixed Assets":
-
- @DomainServiceLayout(
- named="Parties",
- menuBar = DomainServiceLayout.MenuBar.PRIMARY,
- menuOrder = "20.1"
- )
- public class Parties ... { ... }
-
-Note that only the `menuOrder` of the *first* domain service is significant in placing the menus along the menu bar;
-thereafter the purpose of the `menuOrder` is to order the menu services sections on the menu itself.
-
-## Ordering of a service's actions within a menu
-
-For a given service, the actions within a section on a menu is determined by the `@MemberOrder` annotation. Thus, for
-the `Units` domain service, its actions are annotated:
-
- public class Units extends EstatioDomainService<Unit> {
-
- @MemberOrder(sequence = "1")
- public Unit newUnit( ... ) { ... }
-
- @MemberOrder(sequence = "2")
- public List<Unit> findUnits( ... ) { ... }
-
- @ActionLayout( prototype = true )
- @MemberOrder(sequence = "99")
- public List<Unit> allUnits() { ... }
- ...
- }
-
-Note that the last is also a prototype action (meaning it is only displayed in SERVER_PROTOTYPE (=Wicket Development) mode).
-In the UI it is rendered in italics.
-
-(It is possible to override this place of a given action by specifying `@MemberOrder(name="...")` where the name is
-that of a top-level menu. Prior to 1.8.0 this was the only way of doing things, as of 1.8.0 its use
-is not recommended).
-
-## Tertiary menubar
-
-The tertiary menu bar consists of a single unnamed menu, rendered underneath the user's login, top right. This is
-intended primarily for actions pertaining to the user themselves, eg their account, profile or settings:
-
-<img src="images/application-menu-tertiary.png" width="200"></img>
-
-Domain services' actions can be associated with the tertiary menu using the same `@DomainServiceLayout` annotation. For
-example, the `updateEpochDate(...)` and `listAllSettings(...)` actions come from the following service:
-
- @DomainServiceLayout(
- menuBar = DomainServiceLayout.MenuBar.TERTIARY,
- menuOrder = "10.1"
- )
- public class EstatioAdministrationService ... {
-
- @MemberOrder(sequence = "1")
- public void updateEpochDate( ... ) { ... }
-
- @MemberOrder(sequence = "2")
- public List<ApplicationSetting> listAllSettings() { ... }
- ...
- }
-
-Because the number of items on the tertiary menu is expected to be small and most will pertain to the current user, the
-viewer does *not* place dividers between actions from different services on the tertiary menu.
-
-## Isis Add-on modules
-
-Some of the Isis add-ons modules also provide services whose actions appear in top-level menus.
-
-The [security](http://github.com/isisaddons/isis-module-security)'s module places its domain service menus in three
-top-level menus:
-
-* its `ApplicationUsers`, `ApplicationRoles`, `ApplicationPermission`, `ApplicationFeatureViewModels` and
- `ApplicationTenancies` domain services are all grouped together in a single "Security" top-level menu, on the
- SECONDARY menu bar
-
-* its `SecurityModuleAppFixturesService` domain service, which allows the security modules' fixture scripts to be run,
- is placed on a "Prototyping" top-level menu, also on the SECONDARY menu bar
-
-* its `MeService` domain service, which provides the `me()` action, is placed on the TERTIARY menu bar.
-
-Meanwhile the [devutils](http://github.com/isisaddons/isis-module-devutils) module places its actions - to download layouts and
-so forth - on a "Prototyping" top-level menu, on the SECONDARY menu bar.
-
-
-Currently there is no facility to alter the placement of these services. However, their UI can be suppressed <!--either-->
-using security<!-- or (more sophisticatedly) a [vetoing subscriber](../../../more-advanced-topics/vetoing-subscriber.html)-->.
-
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/bookmarks.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/bookmarks.md b/content-OLDSITE/components/viewers/wicket/bookmarks.md
deleted file mode 100644
index 6164686..0000000
--- a/content-OLDSITE/components/viewers/wicket/bookmarks.md
+++ /dev/null
@@ -1,70 +0,0 @@
-Title: Bookmarks
-
-[//]: # (content copied to _user-guide_wicket-viewer)
-
-The Wicket viewer supports the bookmarking of both domain objects and [safe](../../../reference/recognized-annotations/ActionSemantics.html) (query-only) actions.
-
-Domain objects, if bookmarkable, can be nested.
-
-Bookmarking is automatic; whenever a bookmarkable object/action is visited, then a bookmark is created. To avoid the number of bookmarks from indefinitely growing, bookmarks that have not been followed after a whle are automatically removed (an MRU/LRU algorithm). The number of bookmarks to preserve can be configured.
-
-##Screenshots
-
-> these have not yet been updated for the new look-n-feel introduced in 1.8.0
-
-#### Simple List
-
-The following screenshot, taken from [Isisaddons example todoapp](https://github.com/isisaddons/isis-app-todoapp) (not ASF) shows how the bookmarks are listed in a sliding panel.
-
-<a href="images/bookmarks/bookmarked-pages-panel.png"><img src="images/bookmarks/bookmarked-pages-panel-940.png"/></a>
-
-(screenshot of v1.4.0)
-
-Note how the list contains both domain objects and an action ("not yet complete").
-
-#### Nested bookmarks
-
-The following screenshot, taken from the [Estatio](https://github.com/estatio/estatio) application, shows a variety of different bookmarked objects.
-
-<a href="images/bookmarks/bookmarked-pages-panel-estatio.png"><img src="images/bookmarks/bookmarked-pages-panel-estatio-940.png"/></a>
-
-Some - like Property, Lease and Party - are root nodes. However, LeaseItem is bookmarkable as a child of Lease, and LeaseTerm is bookmarkable only as a child of LeaseItem. This parent/child relationship is reflected in the layout.
-
-##Domain Code
-
-To indicate a class is bookmarkable, use the [@Bookmarkable](../../../reference/recognized-annotations/Bookmarkable.html] annotation:
-
- @Bookmarkable
- public class Lease { ... }
-
-To indicate a class is bookmarkable but only as a child of some parent bookmark, specify the bookmark policy:
-
- @Bookmarkable(BookmarkPolicy.AS_CHILD)
- public class LeaseItem { ... }
-
-To indicate that a safe (query only) action is bookmarkable, again use the `@Bookmarkable` annotation:
-
- public class ToDoItem ... {
- ...
- @Bookmarkable
- @ActionSemantics(Of.SAFE)
- public List<ToDoItem> notYetComplete() { ... }
- ...
- }
-
-##User Experience
-
-The sliding panel appears whenever the mouse pointer hovers over the thin blue tab (to the left of the top header region).
-
-Alternatively, `alt+[` will toggle open/close the panel; it can also be closed using `Esc` key.
-
-####Related functionality
-
-The [recent pages](./recent-pages.html) also lists recently visited pages, selected from a drop-down.
-
-##Configuration
-
-By default, the bookmarked pages panel will show a maximum of 15 'root' pages. This can be overridden using a property (in `isis.properties`), for example:
-
- isis.viewer.wicket.bookmarkedPages.maxSize=20
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/brand-logo.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/brand-logo.md b/content-OLDSITE/components/viewers/wicket/brand-logo.md
deleted file mode 100644
index 91a97f0..0000000
--- a/content-OLDSITE/components/viewers/wicket/brand-logo.md
+++ /dev/null
@@ -1,56 +0,0 @@
-Title: Brand Logo (1.8.0)
-
-[//]: # (content copied to _user-guide_wicket-viewer)
-
-By default the Wicket viewer will display the application name top-left in the header menu. This can be changed to
-display a png logo instead.
-
-##Screenshots
-
-The screenshot below shows the Isis addons example [todoapp](https://github.com/isisaddons/isis-app-todoapp/) (not ASF) with a 'brand logo' image in its header:
-
-
-
-A custom brand logo (typically larger) can also be specified for the signin page:
-
-
-
-
-##Configuration
-
-In the application-specific subclass of `IsisWicketApplication`, bind:
-
-* a string with name "brandLogoHeader" to the URL of a header image. A size of 160x40 works well.
-* a string with name "brandLogoSignin" to the URL of a image for the sign-in page. A size of 400x100 works well.
-
-For example:
-
- @Override
- protected Module newIsisWicketModule() {
- final Module isisDefaults = super.newIsisWicketModule();
-
- final Module overrides = new AbstractModule() {
- @Override
- protected void configure() {
- ...
- bind(String.class).annotatedWith(Names.named("brandLogoHeader")).toInstance("/images/todoapp-logo-header.png");
- bind(String.class).annotatedWith(Names.named("brandLogoSignin")).toInstance("/images/todoapp-logo-signin.png");
- ...
- }
- };
-
- return Modules.override(isisDefaults).with(overrides);
- }
-
-
-If the logo is hosted locally, add to the relevant directory (eg `src/main/webapp/images`). It is also valid for the
-URL to be absolute.
-
-You may also wish to tweak the `css/application.css`. For example, a logo with height 40px works well with the following:
-
- .navbar-brand img {
- margin-top: -5px;
- margin-left: 5px;
- }
-
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/configuring-the-about-page.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/configuring-the-about-page.md b/content-OLDSITE/components/viewers/wicket/configuring-the-about-page.md
deleted file mode 100644
index d943977..0000000
--- a/content-OLDSITE/components/viewers/wicket/configuring-the-about-page.md
+++ /dev/null
@@ -1,102 +0,0 @@
-Title: Configuring the About page
-
-[//]: # (content copied to _user-guide_wicket-viewer)
-
-Isis' Wicket viewer has an About page that, by default, will provide a dump of the JARs that make up the webapp. This page will also show the manifest attributes of the WAR archive itself, if there are any. One of these attributes may also be used as the application version number.
-
-## Screenshot
-
-Here's what the About page looks like with this configuration added:
-
-<img src="images/about-page.png" width="800"></img>
-
-Note that the `Build-Time` attribute has been used as the version number. The Wicket viewer is hard-coded to search for specific attributes and use as the application version. In order, it searches for:
-
-* `Implementation-Version`
-* `Build-Time`
-
-If none of these are found, then no version is displayed.
-
-## Configuration
-
-_This configuration is included within the [simpleapp archetype](../../../intro/getting-started/simpleapp-archetype.html)._
-
-#### Adding attributes to the WAR's manifest
-
-Add the following to the webapp's `pom.xml` (under `<build><plugins>`):
-
- <plugin>
- <groupId>org.codehaus.mojo</groupId>
- <artifactId>build-helper-maven-plugin</artifactId>
- <version>1.5</version>
- <executions>
- <execution>
- <phase>validate</phase>
- <goals>
- <goal>maven-version</goal>
- </goals>
- </execution>
- </executions>
- </plugin>
-
- <plugin>
- <artifactId>maven-war-plugin</artifactId>
- <configuration>
- <archive>
- <manifest>
- <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
- </manifest>
- <manifestEntries>
- <Build-Time>${maven.build.timestamp}</Build-Time>
- <Build-Number>${buildNumber}</Build-Number>
- <Build-Host>${agent.name}</Build-Host>
- <Build-User>${user.name}</Build-User>
- <Build-Maven>Maven ${maven.version}</Build-Maven>
- <Build-Java>${java.version}</Build-Java>
- <Build-OS>${os.name}</Build-OS>
- <Build-Label>${project.version}</Build-Label>
- </manifestEntries>
- </archive>
- </configuration>
- <executions>
- <execution>
- <phase>package</phase>
- <goals>
- <goal>war</goal>
- </goals>
- <configuration>
- <classifier>${env}</classifier>
- </configuration>
- </execution>
- </executions>
- </plugin>
-
-If you then build the webapp from the Maven command line (`mvn clean package`), then the WAR should contain a `META-INF/MANIFEST.MF` with those various attribute entries.
-
-#### Exporting the attributes into the app
-
-The manifest attributes are provided to the rest of the application by way of the Wicket viewer's integration with Google Guice.
-
-In your subclass of `IsisWicketApplication`, there is a method `newIsisWicketModule()`. In this method you need to bind an `InputStream` that will read the manifest attributes. This is all boilerplate so you can just copy-n-paste:
-
- @Override
- protected Module newIsisWicketModule() {
-
- ...
-
- final Module simpleappOverrides = new AbstractModule() {
- @Override
- protected void configure() {
- ...
- bind(InputStream.class)
- .annotatedWith(Names.named("metaInfManifest"))
- .toProvider(Providers.of(
- getServletContext().getResourceAsStream("/META-INF/MANIFEST.MF")));
- }
- };
-
- ...
-
- }
-
-And with that you should be good to go!
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/custom-pages.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/custom-pages.md b/content-OLDSITE/components/viewers/wicket/custom-pages.md
deleted file mode 100644
index e4b995f..0000000
--- a/content-OLDSITE/components/viewers/wicket/custom-pages.md
+++ /dev/null
@@ -1,128 +0,0 @@
-Title: Custom Pages
-
-[//]: # (content copied to _user-guide_extending_wicket-viewer)
-
-The Wicket viewer allows you to customize the GUI in several (progressively more sophisticated) ways:
-
-* through CSS (see [here](./how-to-tweak-the-ui-using-css-classes.html))
-* through Javascript snippets (eg JQuery) (see [here](./how-to-tweak-the-ui-using-javascript.html))
-* by replacing elements of the page using the `ComponentFactory` interface (see [here](./customizing-the-viewer.html))
-* by providing new pages (described below)
-
-In the vast majority of cases customization should be sufficient by [replacing elements of a page](./customizing-the-viewer.html). However, it is also possible to define an entirely new page for a given page type.
-
-## Page Types
-
-Isis defines eight page types (see the `org.apache.isis.viewer.wicket.model.models.PageType` enum):
-
-<table class="table table-bordered table-hover">
- <tr>
- <th>
- Page type
- </th>
- <th>
- Renders
- </th>
- </tr>
- <tr>
- <th>
- SIGN_IN
- </th>
- <td>
- The initial sign-in page
- </td>
- </tr>
- <tr>
- <th>
- HOME
- </th>
- <td>
- The home page, displaying either the welcome message or dashboard
- </td>
- </tr>
- <tr>
- <th>
- ABOUT
- </th>
- <td>
- The about page, accessible from link top-right
- </td>
- </tr>
- <tr>
- <th>
- ENTITY
- </th>
- <td>
- Renders a single entity or view model
- </td>
- </tr>
- <tr>
- <th>
- STANDALONE_COLLECTION
- </th>
- <td>
- Page rendered after invoking an action that returns a collection of entites
- </td>
- </tr>
- <tr>
- <th>
- VALUE
- </th>
- <td>
- After invoking an action that returns a value type (though not URLs or Blob/Clobs, as these are handled appropriately automatically).
- </td>
- </tr>
- <tr>
- <th>
- VOID_RETURN
- </th>
- <td>
- After invoking an action that is `void`
- </td>
- </tr>
- <tr>
- <th>
- ACTION_PROMPT
- </th>
- <td>
- (No longer used).
- </td>
- </tr>
-</table>
-
-
-
-
-
-## `PageClassList` interface
-
-The `PageClassList` interface declares which class (subclass of `org.apache.wicket.Page` is used to render for each of these types. For example, Isis' `WicketSignInPage` renders the signin page. To specify a different page class, create a custom subclass of `PageClassList`:
-
- @Singleton
- public class MyPageClassList extends PageClassListDefault {
-
- protected Class<? extends Page> getSignInPageClass() {
- return MySignInPage.class;
- }
- }
-
-## Registering the Custom `PageClassList`
-
-This updated `PageClassList` implementation is then registered by adjusting the Guice bindings (part of Isis' bootstrapping) in your custom subclass of `IsisWicketApplication`:
-
- public class MyAppApplication extends IsisWicketApplication {
- @Override
- protected Module newIsisWicketModule() {
- final Module isisDefaults = super.newIsisWicketModule();
- final Module myAppOverrides = new AbstractModule() {
- @Override
- protected void configure() {
- ...
- bind(PageClassList.class).to(MyPageClassList.class);
- ...
- }
- };
-
- return Modules.override(isisDefaults).with(myAppOverrides);
- }
- }
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/customizing-the-viewer.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/customizing-the-viewer.md b/content-OLDSITE/components/viewers/wicket/customizing-the-viewer.md
deleted file mode 100644
index 1c56a42..0000000
--- a/content-OLDSITE/components/viewers/wicket/customizing-the-viewer.md
+++ /dev/null
@@ -1,141 +0,0 @@
-Title: Customizing the Viewer
-
-[//]: # (content copied to _user-guide_extending_wicket-viewer)
-
-The Wicket viewer allows you to customize the GUI in several (progressively more sophisticated) ways:
-
-* through CSS (see [here](./how-to-tweak-the-ui-using-css-classes.html))
-* through Javascript snippets (eg JQuery) (see [here](./how-to-tweak-the-ui-using-javascript.html))
-* by replacing elements of the page using the `ComponentFactory` interface (described below)
-* by providing new pages (see [here](./custom-pages.html))
-
-Replacing elements of the page (the technique described here) is the most powerful general-purpose way to customize the look-n-feel of the viewer. Examples at [Isis Add-ons](http://www.isisaddons.org) include the [gmap3](isisaddons/isis-wicket-gmap3.html), [calendar](isisaddons/isis-wicket-fullcalendar2.html), [excel download](isisaddons/isis-wicket-excel.html) and [charting](isisaddons/isis-wicket-wickedcharts.html) integrations.
-
-## Replacing Components (elements of the page)
-
-The pages generated by Isis' Wicket viewer are built up of numerous elements,
-from fine-grained widgets for property/parameter fields, to much larger components that take responsibility for rendering an entire entity entity, or a collection of entities. Under the covers these are all implementations of the the Apache Wicket `Component` API. The larger components delegate to the smaller, of course.
-
-
-#### How the Wicket viewer selects components
-
-Components are created using Isis' `ComponentFactory` interface, which are registered in turn through the `ComponentFactoryRegistrar` interface. Every
-component is categorizes by type (the `ComponentType` enum), and Isis uses this to determine which `ComponentFactory` to use. For example, the `ComponentType.BOOKMARKED_PAGES` is used to locate the `ComponentFactory` that will build the bookmarked pages panel.
-
-Each factory is also handed a model (an implementation of `org.apache.wicket.IModel`) appropriate to its `ComponentType`; this holds the data to be rendered. For example, `ComponentType.BOOKMARKED_PAGES` is given a `BookmarkedPagesModel`, while `ComponentType.SCALAR_NAME_AND_VALUE` factories are provided a model of type of type `ScalarModel` .
-
-In some cases there are several factories for a given `ComponentType`; this is most notably the case for `ComponentType.SCALAR_NAME_AND_VALUE`. After doing a first pass selection of candidate factories by `ComponentType`, each factory is then asked if it `appliesTo(Model)`. This is an opportunity for the factory to check the model itself to see if the data within it is of the appropriate type.
-
-Thus, the `BooleanPanelFactory` checks that the `ScalarModel` holds a boolean, while the `JodaLocalDatePanelFactory` checks to see if it holds `org.joda.time.LocalDate`.
-
-There will typically be only one `ComponentFactory` capable of rendering a particular `ComponentType`/`ScalarModel` combination; at any rate, the framework stops as soon as one is found. (*There is one exception to this design, discussed below in the next section "Additional Views of Collections"*).
-
-#### How to replace a component
-
-This design (the [chain of responsibility](http://en.wikipedia.org/wiki/Chain-of-responsibility_pattern) design pattern) makes it quite straightforward to change the rendering of any element of the page. For example, you might switch out Isis' sliding bookmark panel and replace it with one that presents the bookmarks in some different fashion.
-
-First, you need to write a `ComponentFactory` and corresponding `Component`. The recommended approach is to start with the source of the `Component` you want to switch out. For example:
-
- public class MyBookmarkedPagesPanelFactory
- extends ComponentFactoryAbstract {
-
- public MyBookmarkedPagesPanelFactory() {
- super(ComponentType.BOOKMARKED_PAGES);
- }
-
- @Override
- public ApplicationAdvice appliesTo(final IModel<?> model) {
- return appliesIf(model instanceof BookmarkedPagesModel);
- }
-
- @Override
- public Component createComponent(final String id, final IModel<?> model) {
- final BookmarkedPagesModel bookmarkedPagesModel = (BookmarkedPagesModel) model;
- return new MyBookmarkedPagesPanel(id, bookmarkedPagesModel);
- }
- }
-
-and
-
- public class MyBookmarkedPagesPanel
- extends PanelAbstract<BookmarkedPagesModel> {
- ...
- }
-
-Here `PanelAbstract` ultimately inherits from `org.apache.wicket.Component`.
-Your new `Component` uses the information in the provided model (eg `BookmarkedPagesModel`) to know what to render.
-
-Next, you will require a custom implementation of the `ComponentFactoryRegistrar` that registers your custom `ComponentFactory` as a replacement:
-
- @Singleton
- public class MyComponentFactoryRegistrar extends ComponentFactoryRegistrarDefault {
-
- @Override
- public void addComponentFactories(ComponentFactoryList componentFactories) {
- super.addComponentFactories(componentFactories);
- componentFactories.add(new MyBookmarkedPagesPanelFactory());
- }
- }
-
-This will result in the new component being used instead of (that is, discovered prior to) Isis' default implementation.
-
-> Previously this page suggested using "replace" rather than "add"; however this has unclear semantics for some component types; see [ISIS-996](https://issues.apache.org/jira/browse/ISIS-996).
-
-Finally (as for other customizations), you need to adjust the Guice bindings in your custom subclass of `IsisWicketApplication`:
-
- public class MyAppApplication extends IsisWicketApplication {
- @Override
- protected Module newIsisWicketModule() {
- final Module isisDefaults = super.newIsisWicketModule();
- final Module myAppOverrides = new AbstractModule() {
- @Override
- protected void configure() {
- ...
- bind(ComponentFactoryRegistrar.class)
- .to(MyComponentFactoryRegistrar.class);
- ...
- }
- };
-
- return Modules.override(isisDefaults).with(myAppOverrides);
- }
- }
-
-
-
-## Additional Views of Collections
-
-As explained above, in most cases Isis' Wicket viewer will search for the first `ComponentFactory` that can render an element, and use it. In the case of (either standalone or parented) collections, though, Isis will show all available views.
-
-For example, out-of-the-box Isis provides a table view, a summary view (totals/sums/averages of any data), and a collapsed view (for `@Render(LAZILY)` collections). These are selected by clicking on the toolbar by each collection.
-
-Additional views though could render the objects in the collection as a variety of ways. Indeed, some third-party implementations already exist:
-
- * [excel integration](https://github.com/isisaddons/isis-wicket-excel) (collection as a downloadable excel spreadsheet)
- * [google maps v3 integration](https://github.com/isisaddons/isis-wicket-gmap3) (render any objects with a location on a map)
- * [wicked charts integration](https://github.com/isisaddons/isis-wicket-wickedcharts) (barchart of any data)
- * [full calendar integration](https://github.com/isisaddons/isis-wicket-fullcalendar2) (render any objects with date properties on a calendar)
-
-Registering these custom views is just a matter of adding the appropriate Maven module to the classpath. Isis uses the JDK `ServiceLoader` API to automatically discover and register the `ComponentFactory` of each such component.
-
-If you want to write your own alternative component and auto-register, then include a file `META-INF/services/org.apache.isis.viewer.wicket.ui.ComponentFactory` whose contents is the fully-qualified class name of the custom `ComponentFactory` that you have written.
-
-Wicket itself has lots of components available at its [wicketstuff.org](http://wicketstuff.org) companion website; you might find some of these useful for your own customizations.
-
-### Adding a Custom Object View (eg a Dashboard)
-
-One further use case in particular is worth highlighting; the rendering of an entire entity. Normally entities this is done using `EntityCombinedPanelFactory`, this being the first `ComponentFactory` for the `ComponentType.ENTITY` that is registered in Isis default `ComponentFactoryRegistrarDefault`.
-
-You could, though, register your own `ComponentFactory` for entities that is targeted at a particular class of entity - some sort of object representing a dashboard, for example. It can use the `EntityModel` provided to it to determine the class of the entity, checking if it is of the appropriate type. Your custom factory should also be registered before the `EntityCombinedPanelFactory` so that it is checked prior to the default `EntityCombinedPanelFactory`:
-
- @Singleton
- public class MyComponentFactoryRegistrar extends ComponentFactoryRegistrarDefault {
- @Override
- public void addComponentFactories(ComponentFactoryList componentFactories) {
- componentFactories.add(new DashboardEntityFactory());
- ...
- super.addComponentFactories(componentFactories);
- ...
- }
- }
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/customizing-the-welcome-page.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/customizing-the-welcome-page.md b/content-OLDSITE/components/viewers/wicket/customizing-the-welcome-page.md
deleted file mode 100644
index 3770760..0000000
--- a/content-OLDSITE/components/viewers/wicket/customizing-the-welcome-page.md
+++ /dev/null
@@ -1,33 +0,0 @@
-Title: Customizing the Welcome Page
-
-[//]: # (content copied to _user-guide_wicket-viewer)
-
-It's possible to customize the application name, welcome message and about message can also be customized. This is done by adjusting the Guice bindings (part of Isis' bootstrapping) in your custom subclass of `IsisWicketApplication`:
-
- public class MyAppApplication extends IsisWicketApplication {
- @Override
- protected Module newIsisWicketModule() {
- final Module isisDefaults = super.newIsisWicketModule();
- final Module myAppOverrides = new AbstractModule() {
- @Override
- protected void configure() {
- ...
- bind(String.class)
- .annotatedWith(Names.named("applicationName"))
- .toInstance("My Wonderful App");
- bind(String.class)
- .annotatedWith(Names.named("welcomeMessage"))
- .toInstance(readLines("welcome.html"));
- bind(String.class)
- .annotatedWith(Names.named("aboutMessage"))
- .toInstance("My Wonderful App v1.0");
- ...
- }
- };
-
- return Modules.override(isisDefaults).with(myAppOverrides);
- }
- }
-
-Here the `welcome.html` file is resolved relative to `src/main/webapp`.
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/disabling-modal-dialogs.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/disabling-modal-dialogs.md b/content-OLDSITE/components/viewers/wicket/disabling-modal-dialogs.md
deleted file mode 100644
index 0f821b2..0000000
--- a/content-OLDSITE/components/viewers/wicket/disabling-modal-dialogs.md
+++ /dev/null
@@ -1,11 +0,0 @@
-Title: Disabling Modal Dialogs
-
-[//]: # (content copied to _user-guide_wicket-viewer_configuration_properties)
-
-By default the Isis Wicket viewer uses a modal dialog for action parameters.
-Before this feature was implemented (prior to 1.4.0), Isis rendered action parameters
-on its own page. This old behaviour can be re-enabled using:
-
- isis.viewer.wicket.disableModalDialogs=true
-
-Note that action pages are still used for bookmarked actions.
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/dynamic-layouts.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/dynamic-layouts.md b/content-OLDSITE/components/viewers/wicket/dynamic-layouts.md
deleted file mode 100644
index 3eb360d..0000000
--- a/content-OLDSITE/components/viewers/wicket/dynamic-layouts.md
+++ /dev/null
@@ -1,145 +0,0 @@
-Title: Dynamic Layouts
-
-[//]: # (content copied to _user-guide_wicket-viewer_layout_dynamic-object-layout)
-
-Because Isis implements the [naked objects pattern](http://en.wikipedia.org/wiki/Naked_objects), the domain objects are rendered in the UI based only metadata gleaned from the domain classes themselves. Traditionally this metadata has been specified [statically](./static-layouts.html), using annotations. However, it is also possible to specify it using a JSON file. This brings the advantage that the layout can be refreshed dynamically, without recompiling/redeploying the app.
-
-## <a name="screencast"></a>Screencast
-
-How to layout properties and collections dynamically, in the Wicket viewer.
-
-<iframe width="530" height="354" src="http://www.youtube.com/embed/zmrg49WeEPc" frameborder="0" allowfullscreen></iframe>
-
-
-## JSON layout file
-
-The JSON layout file for class `Xxx` takes the name `Xxx.layout.json`, and resides in the same package as the class.
-The format of the file is:
-
- {
- "columns": [ // list of columns
- {
- "span": 6, // span of the left-hand property column
- "memberGroups": { // ordered map of member (property) groups
- "General": { // member group name
- "members": {
- "description": { // property, no associated actions, but with UI hint
- "propertyLayout": {
- "typicalLength": 50 // UI hint for size of field (no longer used in ISIS 1.8.0)
- }
- },
- "category": {},
- "complete": { // property, with associated actions
- "propertyLayout": {
- "describedAs": "Whether this todo item has been completed"
- },
- "actions": {
- "completed": {
- "actionLayout": {
- "named": "Done", // naming UI hint
- "cssClass": "x-highlight" // CSS UI hint
- }
- },
- "notYetCompleted": {
- "actionLayout": {
- "named": "Not done"
- }
- }
- }
- }
- },
- "Misc": {
- "members": {
- "notes": {
- "propertyLayout": {
- "multiLine": 5 // UI hint for text area
- }
- },
- "versionSequence": {}
- }
- }
- }
- }
- },
- {
- "span": 6, // span of the middle property column
- "memberGroups": { ... }
- },
- {
- "span": 0 // span of the right property column (if any)
- },
- {
- "span": 6,
- "collections": { // ordered map of collections
- "dependencies": { // collection, with associated actions
- "collectionLayout": {
- "paged": 10, // pagination UI hint
- "render": "EAGERLY" // lazy-loading UI hint
- },
- "actions": {
- "add":{},
- "delete": {}
- },
- },
- "similarItems": {} // collection, no associated actions
- }
- }
- ],
- "actions": { // actions not associated with any member
- "delete": {},
- "duplicate": {
- "actionLayout": {
- "named": {
- "value": "Clone"
- }
- }
- }
- }
- }
-
-Although advisable, it is not necessary to list all class members in this file. Any members not listed with be
-ordered according either to annotations (if present) or fallback/default values.
-
-Note also that the layout file may contain entries for
-[contributed associations and actions](../../../more-advanced-topics/how-to-01-062-How-to-decouple-dependencies-using-contributions.html);
-this allows each contributee classes to define their own layout for their contributions, possibly overriding any
-static metadata on the original domain service contributor.
-
-## Downloading an initial layout file
-
-The fastest way to get started is to use the [Developer Utilities Service](../../../reference/services/developer-utilities-service.html) to download the layout file (derived from any existing static metadata defined by annotations).
-
-## Picking up new metadata
-
-When running in [prototype/development mode](../../../reference/deployment-type.html), the Wicket viewer automatically rebuilds the metamodel for each class as it is rendered.
-
-> Conversely, do note that the Wicket viewer will *not* pick up new metadata if running in production/server mode.
-
-## Required updates to the dom project's pom.xml
-
-If using the `.layout.json` files, these must be compiled and available in the CLASSPATH. When using an IDE such as Eclipse+M2E, any `.layout.json` files in `src/main/java` or `src/main/resources` will be part of the CLASSPATH automatically. However, unless the `pom.xml` is changed, these will not be part of the compiled WAR.
-
-Therefore, make sure the following is added to the dom project's `pom.xml`:
-
- <resources>
- <resource>
- <filtering>false</filtering>
- <directory>src/main/resources</directory>
- </resource>
- <resource>
- <filtering>false</filtering>
- <directory>src/main/java</directory>
- <includes>
- <include>**</include>
- </includes>
- <excludes>
- <exclude>**/*.java</exclude>
- </excludes>
- </resource>
- </resources>
-
-If using an Isis [archetype](../../../intro/getting-started/simple-archetype.html), then the POM is already correctly configured.
-
-## Static vs Dynamic Layouts
-
-As mentioned above, it is also possible to [specify the layout semantics statically](./static-layouts.html) using annotations. There's a <a href="static-layouts.html#pros-and-cons">discussion on that page</a> as to the pros and cons of static vs dynamic layouts.
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/file-upload-download.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/file-upload-download.md b/content-OLDSITE/components/viewers/wicket/file-upload-download.md
deleted file mode 100644
index 8066f1c..0000000
--- a/content-OLDSITE/components/viewers/wicket/file-upload-download.md
+++ /dev/null
@@ -1,73 +0,0 @@
-Title: File upload/download
-
-[//]: # (content copied to _user-guide_wicket-viewer_features)
-
-The Isis application library provides the [Blob](../../../reference/value-types.html) type (binary large objects) and
-[Clob](../../../reference/value-types.html) type (character large object), each of which also includes metadata about the data (specifically the filename and mime type).
-
-A class can define a property using either of these types, for example:
-
- private Blob attachment;
-
- @javax.jdo.annotations.Persistent(defaultFetchGroup="false")
- @javax.jdo.annotations.Column(allowsNull="true")
- public Blob getAttachment() {
- return attachment;
- }
-
- public void setAttachment(final Blob attachment) {
- this.attachment = attachment;
- }
-
-The `Blob` and `Clob` types can also be used as parameters to actions.
-
-##Screenshots
-
-The following screenshots are taken from the Isis addons example [todoapp](https://github.com/isisaddons/isis-app-todoapp) (not ASF):
-
-#### View mode, empty
-
-`Blob` field rendered as attachment (with no data):
-
-<a href="images/file-upload-download/010-attachment-field.png"><img src="images/file-upload-download/010-attachment-field-940.png"/></a>
-
-(screenshot of v1.4.0)
-
-#### Edit mode
-
-Hit edit; 'choose file' button appears:
-
-<a href="images/file-upload-download/020-edit-choose-file.png"><img src="images/file-upload-download/020-edit-choose-file-940.png"/></a>
-
-(screenshot of v1.4.0)
-
-#### Choose file
-
-Choose file using the regular browser window:
-
-<a href="images/file-upload-download/030-choose-file-using-browser.png"><img src="images/file-upload-download/030-choose-file-using-browser-520.png"/></a>
-
-#### Blob metadata
-
-Chosen file is indicated:
-
-<a href="images/file-upload-download/040-edit-chosen-file-indicated.png"><img src="images/file-upload-download/040-edit-chosen-file-indicated-940.png"/></a>
-
-#### Image rendered
-
-Back in view mode (ie once hit OK) if the `Blob` is an image, then it is shown:
-
-<a href="images/file-upload-download/050-ok-if-image-then-rendered.png"><img src="images/file-upload-download/050-ok-if-image-then-rendered-940.png"/></a>
-
-#### Download
-
-`Blob` can be downloaded:
-
-<a href="images/file-upload-download/060-download.png"><img src="images/file-upload-download/060-download-940.png"/></a>
-
-#### Clear
-
-Back in edit mode, can choose a different file or clear (assuming property is not mandatory):
-
-<a href="images/file-upload-download/070-edit-clear.png"><img src="images/file-upload-download/070-edit-clear-940.png"/></a>
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/hints-and-copy-url.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/hints-and-copy-url.md b/content-OLDSITE/components/viewers/wicket/hints-and-copy-url.md
deleted file mode 100644
index 787a58f..0000000
--- a/content-OLDSITE/components/viewers/wicket/hints-and-copy-url.md
+++ /dev/null
@@ -1,63 +0,0 @@
-Title: Copy URL and Hints
-
-[//]: # (content copied to _user-guide_wicket-viewer_features)
-
-While the user can often copy the URL of a domain object directly from the browser's address bar, the Wicket viewer also allows the URL of domain objects to be easily copied from a dialog.
-
-More interestingly, this URL can also contain hints capturing any sorting or page numbering, or hiding/viewing of collections. End-users can therefore share these URLs as a form of deep linking into a particular view on a domain object.
-
-The copy URL and hinting is automatic.
-
-##Screenshots
-
-(screenshots of v1.4.0)
-
-#### Copy URL
-
-The following screenshot, taken from the link:https://github.com/estatio/estatio[Estatio] application, shows the copy URL button (top right):
-
-<a href="images/copy-link/010-copy-link-button.png"><img src="images/copy-link/010-copy-link-button-940.png"/></a>
-
-Clicking on this button brings up a dialog with the URL preselected:
-
-<a href="images/copy-link/020-copy-link-dialog.png"><img src="images/copy-link/020-copy-link-dialog-940.png"/></a>
-
-The URL in this case is something like:
-
- http://localhost:8080/wicket/entity/org.estatio.dom.lease.Lease:L_0
-
-The user can copy the link (eg `ctrl+C`) into the clipboard, then hit `OK` or `Esc` to dismiss the dialog.
-
-#### Hints
-
-Using the viewer the user can hide/show collection tables, can sort the tables by header columns:
-
-<a href="images/copy-link/030-hints.png"><img src="images/copy-link/030-hints-940.png"/></a>
-
-Also, if the collection spans multiple pages, then the individual page can be selected.
-
-Once the view has been customised, the URL shown in the copy URL dialog is in an extended form:
-
-<a href="images/copy-link/040-copy-link-with-hints.png"><img src="images/copy-link/040-copy-link-with-hints-940.png"/></a>
-
-The URL in this case is something like:
-
-<pre>
-http://localhost:8080/wicket/entity/org.estatio.dom.lease.Lease:L_0?hint-1:collectionContents-view=3&hint-1:collectionContents:collectionContents-3:table-DESCENDING=value&hint-1:collectionContents:collectionContents-3:table-pageNumber=0&hint-2:collectionContents-view=0&hint-2:collectionContents:collectionContents-2:table-pageNumber=0&hint-3:collectionContents-view=2&hint-3:collectionContents:collectionContents-2:table-pageNumber=0&hint-4:collectionContents-view=3&hint-4:collectionContents:collectionContents-3:table-ASCENDING=exerciseDate&hint-4:collectionContents:collectionContents-3:table-pageNumber=0&hint-5:collectionContents-view=0&hint-5:collectionContents:collectionContents-3:table-pageNumber=0
-</pre>
-
-#### Copy URL from title
-
-When the user invokes an action on the object, the URL (necessarily) changes to indicate that the action was invoked. This URL is specific to the user's session and cannot be shared with others.
-
-A quick way for the user to grab a shareable URL is simply by clicking on the object's title:
-
-<a href="images/copy-link/050-title-url.png"><img src="images/copy-link/050-title-url-940.png"/></a>
-
-
-##User Experience
-
-The copy URL dialog is typically obtained by clicking on the icon.
-
-Alternatively, `alt+]` will also open the dialog. It can be closed with either `OK` or the `Esc` key.
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/how-to-auto-refresh-page.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/how-to-auto-refresh-page.md b/content-OLDSITE/components/viewers/wicket/how-to-auto-refresh-page.md
deleted file mode 100644
index eed599d..0000000
--- a/content-OLDSITE/components/viewers/wicket/how-to-auto-refresh-page.md
+++ /dev/null
@@ -1,25 +0,0 @@
-title: How to auto-refresh an (entity) page (1.8.0)
-
-[//]: # (content copied to _user-guide_wicket-viewer_customisation)
-
-This requirement from the users mailing list:
-
-_Suppose you want to build a monitoring application, eg for an electricity grid. Data is updated in the background (eg via the
-Restful Objects REST API)... what is needed is the ability to show an entity that includes a [map](http://github.com/isisaddons/isis-wicket-gmap3), and have it auto-refresh every 5 seconds or so._
-
-First, update the domain object to return custom CSS:
-
- public class MyDomainObject {
- ...
- public String cssClass() {return "my-special-auto-updating-entity"; }
- ...
- }
-
-Then, use javascript in `webapp/src/main/webapp/scripts/application.js` to reload:
-
- $(function() {
- if ($(".my-special-auto-updating-entity").length) {
- setTimeout(function() {document.location.reload();}, 5000); // 1000 is 5 sec
- }
- });
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/how-to-tweak-the-ui-using-css-classes.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/how-to-tweak-the-ui-using-css-classes.md b/content-OLDSITE/components/viewers/wicket/how-to-tweak-the-ui-using-css-classes.md
deleted file mode 100644
index 83c94b5..0000000
--- a/content-OLDSITE/components/viewers/wicket/how-to-tweak-the-ui-using-css-classes.md
+++ /dev/null
@@ -1,131 +0,0 @@
-title: Tweaking the UI using CSS classes
-
-[//]: # (content copied to _user-guide_wicket-viewer_customisation)
-
-The Wicket viewer allows you to customize the GUI in several (progressively more sophisticated) ways:
-
-* through CSS (described below)
-* through Javascript snippets (eg JQuery) (see [here](./how-to-tweak-the-ui-using-javascript.html))
-* by replacing elements of the page using the `ComponentFactory` interface (see [here](./customizing-the-viewer.html))
-* by providing new pages (see [here](./custom-pages.html))
-
-The most straight-forward way to customize the Wicket viewer's UI is to use CSS, and is described here.
-
-## Customizing the CSS
-
-The HTML generated by the Wicket viewer include plenty of CSS classes so that you can easily target the required elements as required. For example, you could use CSS to suppress the entity's icon alongside its title. This would be done using:
-
- .entityIconAndTitlePanel a img {
- display: none;
- }
-
-These customizations should generally be added to `src/main/webapp/css/application.css`; this file is included by default in every webpage served up by the Wicket viewer.
-
-## Targetting individual members
-
-For example, the `ToDoItem` object of the Isis addons example [todoapp](https://github.com/isisaddons/isis-app-todoapp/) (not ASF) has a `notes` property. The HTML for this will be something like:
-
- <div>
- <div class="property ToDoItem-notes">
- <div class="multiLineStringPanel scalarNameAndValueComponentType">
- <label for="id83" title="">
- <span class="scalarName">Notes</span>
- <span class="scalarValue">
- <textarea
- name="middleColumn:memberGroup:1:properties:4:property:scalarIfRegular:scalarValue"
- disabled="disabled"
- id="id83" rows="5" maxlength="400" size="125"
- title="">
- </textarea>
- <span>
- </span>
- </span>
- </label>
- </div>
- </div>
- </div>
-
-
-The `src/main/webapp/css/application.css` file is the place to add application-specific styles. By way of an example, if (for some reason) we wanted to completely hide the notes value, we could do so using:
-
- div.ToDoItem-notes span.scalarValue {
- display: none;
- }
-
-You can use a similar approach for collections and actions.
-
-
-### Targetting members through a custom CSS style
-
-The above technique works well if you know the class member to target, but you might instead want to apply a custom style to a set of members. For this, you can use the `@CssClass`.
-
-For example, in the `ToDoItem` class the following annotation (indicating that this is a key, important, property) :
-
- @CssClass("x-key")
- public LocalDate getDueBy() {
- return dueBy;
- }
-
-would generate the HTML:
-
- <div>
- <div class="property ToDoItem-dueBy x-key">
- ...
- </div>
- </div>
-
-This can then be targeted, for example using:
-
- div.x-key span.scalarName {
- color: red;
- }
-
-
-Note also that instead of using `@CssClass` annotation, you can also specify the CSS style using a [dynamic layout](./dynamic-layouts.html) JSON file:
-
- ...
- "dueBy": {
- "propertyLayout": {
- "cssClass": "x-key"
- }
- },
- ...
-
-
-### Application-specific 'theme' class
-
-The application name (as defined in the `IsisWicketApplication` subclass) is also used (in sanitized form) as the CSS class in a `<div>` that wraps all the rendered content of every page.
-
-For example, if the application name is "ToDo App", then the `<div>` generated is:
-
- <div class="todo-app">
- ...
- </div>
-
-You can therefore use this CSS class as a way of building your own theme for the various elements of the wicket viewer pages.
-
-## Using a different CSS file
-
-If for some reason you wanted to name the CSS file differently (eg `stylesheets/myapp.css`), then adjust the Guice bindings (part of Isis' bootstrapping) in your custom subclass of `IsisWicketApplication`:
-
- public class MyAppApplication extends IsisWicketApplication {
- @Override
- protected Module newIsisWicketModule() {
- final Module isisDefaults = super.newIsisWicketModule();
- final Module myAppOverrides = new AbstractModule() {
- @Override
- protected void configure() {
- ...
- bind(String.class)
- .annotatedWith(Names.named("applicationCss"))
- .toInstance("stylesheets/myapp.css");
- ...
- }
- };
-
- return Modules.override(isisDefaults).with(myAppOverrides);
- }
- }
-
-As indicated above, this file is resolved relative to `src/main/webapp`.
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/how-to-tweak-the-ui-using-javascript.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/how-to-tweak-the-ui-using-javascript.md b/content-OLDSITE/components/viewers/wicket/how-to-tweak-the-ui-using-javascript.md
deleted file mode 100644
index ad4bf11..0000000
--- a/content-OLDSITE/components/viewers/wicket/how-to-tweak-the-ui-using-javascript.md
+++ /dev/null
@@ -1,40 +0,0 @@
-Title: Tweaking the UI using Javascript
-
-[//]: # (content copied to _user-guide_wicket-viewer_customisation)
-
-The Wicket viewer allows you to customize the GUI in several (progressively more sophisticated) ways:
-
-* through CSS (see [here](./how-to-tweak-the-ui-using-css-classes.html))
-* through Javascript snippets (eg JQuery) (described below)
-* by replacing elements of the page using the `ComponentFactory` interface (see [here](./customizing-the-viewer.html))
-* by providing new pages (see [here](./custom-pages.html))
-
-Customizing the viewer using Javascript is discouraged, however, as there is no formal API that such custom JS can target. Instead, consider implementing the customization server-side, using the `ComponentFactory` interface (described [here](./customizing-the-viewer.html)).
-
-## Customizing using Javascript snippets
-
-The Wicket viewer ships with embedded JQuery, so this can be leveraged (eg to run some arbitrary JQuery on page load).
-
-This is done by adjusting the Guice bindings (part of Isis' bootstrapping) in your custom subclass of `IsisWicketApplication`:
-
- public class MyAppApplication extends IsisWicketApplication {
- @Override
- protected Module newIsisWicketModule() {
- final Module isisDefaults = super.newIsisWicketModule();
- final Module myAppOverrides = new AbstractModule() {
- @Override
- protected void configure() {
- ...
- bind(String.class)
- .annotatedWith(Names.named("applicationJs"))
- .toInstance("scripts/application.js");
- ...
- }
- };
-
- return Modules.override(isisDefaults).with(myAppOverrides);
- }
- }
-
-Currently only one such `.js` file can be registered.
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/images/about-page.png
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/images/about-page.png b/content-OLDSITE/components/viewers/wicket/images/about-page.png
deleted file mode 100644
index ae5dfc8..0000000
Binary files a/content-OLDSITE/components/viewers/wicket/images/about-page.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/images/application-menu-dividers.png
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/images/application-menu-dividers.png b/content-OLDSITE/components/viewers/wicket/images/application-menu-dividers.png
deleted file mode 100644
index dcb415d..0000000
Binary files a/content-OLDSITE/components/viewers/wicket/images/application-menu-dividers.png and /dev/null differ
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/components/viewers/wicket/images/application-menu-layout-menus.pdn
----------------------------------------------------------------------
diff --git a/content-OLDSITE/components/viewers/wicket/images/application-menu-layout-menus.pdn b/content-OLDSITE/components/viewers/wicket/images/application-menu-layout-menus.pdn
deleted file mode 100644
index 01453f7..0000000
Binary files a/content-OLDSITE/components/viewers/wicket/images/application-menu-layout-menus.pdn and /dev/null differ