You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@cocoon.apache.org by da...@cocoon.zones.apache.org on 2007/05/06 19:24:59 UTC
[DAISY] Updated: Modularize Cocoon apps (Using blocks)
A document has been updated:
http://cocoon.zones.apache.org/daisy/documentation/1291.html
Document ID: 1291
Branch: main
Language: default
Name: Modularize Cocoon apps (Using blocks) (previously $$ Using blocks)
Document Type: Cocoon Document (unchanged)
Updated on: 5/6/07 5:24:37 PM
Updated by: Reinhard Pötz
A new version has been created, state: publish
Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name: (unchanged)
Size: 793 bytes (previous version: 358 bytes)
Content diff:
<html>
<body>
--- <p class="warn">The leading $$ characters at the beginning of document name mean
--- that the document is skipped when exported by the Daisy export plugin.</p>
+++ <p>In the basic tutorial
+++ <a href="http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1159.html">"Your
+++ first Cocoon application using Maven 2"</a> you have created your first block.
+++ Cocoon 2.2 introduced the concept of blocks because it should help you to split
+++ your application into smaller parts. This increases the maintainability and
+++ reusability by orders of magnitude.</p>
--- <p class="fixme">Add a second block and use the first one from within it.</p>
+++ <p>In this tutorial you will</p>
--- <p class="fixme">Use a postable source from the first pipeline to transform
--- something.</p>
+++ <ol>
+++ <li>create a second block</li>
+++ <li>connect one block with another one</li>
+++ <li>use a pipeline fragement available in one block from within another block
+++ </li>
+++ </ol>
+++ <h1>Create a second block</h1>
+++
+++ <p class="fixme">TBD</p>
+++
+++ <h1>Connect block2 to block1</h1>
+++
+++ <p class="fixme">TBD</p>
+++
+++ <h1>Use a pipeline fragment</h1>
+++
+++ <p class="fixme">TBD</p>
+++
</body>
</html>