-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 11 Jan 2006, Reinhard Poetz wrote:

Date: Wed, 11 Jan 2006 22:47:43 +0100
From: Reinhard Poetz <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Block deployment: working with blocks from a user's point of view


As mentioned in a mail a couple of days ago, I've started to work on the block deployment mechanism. This forced me to think a lot about how I (and hopefully others) want to develop Cocoon 2.2 applications.

Great! Count me in.

I wrote two tutorials that guide a developer step by step through the process of

 - creating a block[1] and
 - creating a web application that uses blocks[2].

I'll have a look at it.

At the time of writing this, the functionality described in both documents has only been implemented partly. Nevertheless I publish them at this early stage in order to get feedback from you to make the first contact with Cocoon 2.2 as simple as possible.

Ok, I was wondering when I saw the commit mail what those hard coded dependencies would be all about in the Mojo. :-)

This should also give everybody the chance of getting involved without
having to dig into the code (though I would be more than pleased if somebody does).

I have also committed the IDE and build tool independant block deployer[3] and a skeleton for the block deployer mojos[4] that will wrap the general block deployer.

[1] http://cocoon.zones.apache.org/daisy/documentation/g2/796.html
[2] http://cocoon.zones.apache.org/daisy/documentation/g2/797.html
[3] http://svn.apache.org/repos/asf/cocoon/whiteboard/deployer/
[4] http://svn.apache.org/repos/asf/cocoon/whiteboard/deployer-maven-plugin/

I'll look into those as well (but not this night ;-)

Thanks and Ciao

- -- Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD4DBQFDxYAkLNdJvZjjVZARAqUiAJjUPu5BUzTQ8Mg9ieCkMHdNcakmAJ9gdokg
wMGCKUf2aQkS/9UmV8aiJw==
=S8Qf
-----END PGP SIGNATURE-----

Reply via email to