cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <acoli...@apache.org>
Subject Re: Cocoon Wiki (was: Re: [CLEANCOON] Let's clean Cocoon and modu larize it . . .)
Date Wed, 07 Aug 2002 12:23:58 GMT
And thats fine.  The wiki is for content generation more than dispersal.  

But I DONT think we should wait for forrest before beginning this. 
 Cocoon's documentation has been
a rotting heap for too long.

-Andy

Ivelin Ivanov wrote:

>I agree with Ulrich to a certain extent.
>Cocoon's core Documentation belongs to the Cocoon main web site.
>Supporting sites are fine for developing new pieces of docs, but they should
>be only refered to as supporting sites, not main sources of information.
>As we've discussed before, hopefully with forrest we will be able to allow
>inline notes to the Cocoon main site,
>similarly to PHP's doc pages.
>
>Ivelin
>
>----- Original Message -----
>From: "Ulrich Mayring" <ulim@denic.de>
>To: <cocoon-dev@xml.apache.org>
>Sent: Wednesday, August 07, 2002 3:40 AM
>Subject: Re: Cocoon Wiki (was: Re: [CLEANCOON] Let's clean Cocoon and modu
>larize it . . .)
>
>
>  
>
>>Piroumian Konstantin wrote:
>>
>>    
>>
>>>Your are wrong saying that Cocoon does not server its own website.
>>>      
>>>
>Cocoon's
>  
>
>>>site is generated using Cocoon's CLI as well as the Forrest site
>>>(http://xml.apache.org/forrest or the recent version:
>>>http://www.krysalis.org/forrest). The reason that the web site is not
>>>      
>>>
>served
>  
>
>>>as a web application is the infrastructure that has no running servlet
>>>engine on the web server.
>>>      
>>>
>>As I said, there are probably good reasons. But from a marketing point
>>of view it is still a show-stopper.
>>
>>    
>>
>>>Cocoon can be used to implement a Wiki application, isn't it? The other
>>>thing is that nobody had did it yet.
>>>      
>>>
>>And people wonder: why not? Why are there Wiki implementations in JSP,
>>but none for Cocoon? If it were easy to do, surely someone could slap
>>something together right now.
>>
>>    
>>
>>>For lighter tasks a lighter tool is the best, but when you have a
>>>      
>>>
>complex
>  
>
>>>web application/site with customizable/personalizable content and
>>>      
>>>
>layout,
>  
>
>>>where you will need multimedia output of the same content etc. then
>>>      
>>>
>you'll
>  
>
>>>hardly be happy to do it using JSP even with its XML and Tiles like
>>>      
>>>
>taglibs.
>  
>
>>So, Cocoon is positioned as being only for large and complex websites?
>>
>>Ulrich
>>
>>--
>>Ulrich Mayring
>>DENIC eG, Systementwicklung
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>>For additional commands, email: cocoon-dev-help@xml.apache.org
>>
>>    
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>  
>




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


Mime
View raw message