Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Wed, 11 Jan 2006 23:01:07 +0100 (CET)
From: Giacomo Pati <giacomo@apache.org>
Sender: giacomo@lapgp.otego.com
To: dev@cocoon.apache.org
Subject: Re: Block deployment: working with blocks from a user's point of
 view
In-Reply-To: <43C57CFF.6060308@apache.org>
Message-ID: <Pine.LNX.4.64.0601112257020.29368@lapgp.otego.com>
References: <43C57CFF.6060308@apache.org>
X-GPG-PUBLIC_KEY: 
 http://pks.gpg.cz:11371/pks/lookup?op=get&search=0x2CD749BD98E35590
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV version 0.88,
 clamav-milter version 0.87 on smtp-08.tornado.cablecom.ch
X-Virus-Status: Clean
X-DCC-spamcheck-02.tornado.cablecom.ch-Metrics: smtp-08.tornado.cablecom.ch
 32701; Body=1
	Fuz1=1 Fuz2=1
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

-----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 <reinhard@apache.org>
> Reply-To: dev@cocoon.apache.org
> To: dev@cocoon.apache.org
> 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-----