Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <cocoon-dev@xml.apache.org>
Subject: RE: Back from Germany
Date: Wed, 30 Oct 2002 12:40:58 +0100
Message-ID: <GMEBIBHGAOFGJCDPJANDEEAPFJAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
In-reply-to: <CC92E7C2663B1D498A745BD686C45E1F3F2D4C@exch2000.cti2.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="iso-8859-1"

Amir Rosen wrote:
> .
> > > Also, we planned on having a web interface on top of Cocoon for
> > > configurations and for block deployment. Of course, all secured and
> > > possibly to be turned off for production environments.
> > >
> > And this is the part where we spend most time, because this 
> > is the interface
> > to the Cocoon user. This has to be very clear and simple but of course
> > powerfull.
> > And the great thing is, that this web interface will be 
> > developed using
> > Cocoon and it's components. So it is also a good presentation 
> > of Cocoon
> > itself: we can show flow script, svg generation etc.
> > 
> > Carsten
> > 
> 
> So You'll have to install the batik block (and any other block 
> you want to demonstrate)
> in order to configure the cocoon core ?
> 

With the web interface you configure (or manage) your blocks. 
If this interface uses Batik and Batik is a block then this
would mean that the web interface has a dependency to this
block. That's right.
I admit that mentioning SVG above was not a good idea. 
The web interface should work without the requirement of
installing a block.

Carsten

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org