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 2013/05/23 11:41:19 UTC
svn commit: r1485630 -
/isis/site/trunk/content/applib-guide/applib-guide-intro.md
Author: danhaywood
Date: Thu May 23 09:41:18 2013
New Revision: 1485630
URL: http://svn.apache.org/r1485630
Log:
more on the applib markdown
Modified:
isis/site/trunk/content/applib-guide/applib-guide-intro.md
Modified: isis/site/trunk/content/applib-guide/applib-guide-intro.md
URL: http://svn.apache.org/viewvc/isis/site/trunk/content/applib-guide/applib-guide-intro.md?rev=1485630&r1=1485629&r2=1485630&view=diff
==============================================================================
--- isis/site/trunk/content/applib-guide/applib-guide-intro.md (original)
+++ isis/site/trunk/content/applib-guide/applib-guide-intro.md Thu May 23 09:41:18 2013
@@ -4,35 +4,36 @@ Title: Apache Isis Programming Model
These conventions are together known as the *Apache Isis Programming Model*. The Apache Isis Application Library - or AppLib - constitutes those elements of the programming model that are declarative (such as annotations and interfaces). It also contains the `DomainObjectContainer` interface, which is normally injected into your domain objects and represents the only point of coupling from your domain into the framework.
-This guide to the programming model breaks into three main parts:
+This guide to the programming model breaks into three main parts: how-tos, supporting features, and reference on annotations etc.
-How-tos
--------
+##How-tos
- * [How-to write Domain Entities](./how-tos/000-about.html)
+* [How-to write Domain Entities](./how-tos/000-about.html)
- * [Domain Services, Repositories and Factories](./domain-services/000-about.html)
+* [Domain Services, Repositories and Factories](./domain-services/000-about.html)
- * [Value Types](./value-types/000-about.html)
+* [Value Types](./value-types/000-about.html)
-Supporting Features
--------------------
+##Supporting Features
- * [Clock, Fixtures, etc](./supporting-features/000-about.html)
+* [Clock, Fixtures, etc](./supporting-features/000-about.html)
-Reference
----------
+##Reference
- * [Recognized Methods and Prefixes](./reference/Recognized-Methods-and-Prefixes.html)
- * [Recognized Annotations](./reference/recognized-annotations/000-about.html)
- * [DomainObjectContainer interface](./reference/DomainObjectContainer.html)
- * [Security](./reference/Security.html)
- * [Applib Utility Classes](./reference/Utility.html)
- * [Applib Events](./reference/Event.html)
+* [Recognized Methods and Prefixes](./reference/Recognized-Methods-and-Prefixes.html)
+* [Recognized Annotations](./reference/recognized-annotations/000-about.html)
-Remarks
--------
+* [DomainObjectContainer interface](./reference/DomainObjectContainer.html)
+
+* [Security](./reference/Security.html)
+
+* [Applib Utility Classes](./reference/Utility.html)
+
+* [Applib Events](./reference/Event.html)
+
+
+### Remarks
To a large extent the conventions of the programming
model can be described as 'intentional' - they convey an intention as to
how domain objects, their properties and behaviours, are to be made