cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Hartmann" <develo...@cocooncenter.de>
Subject Re: [RT] Configuration front-end
Date Sat, 23 Mar 2002 17:55:01 GMT


*********** REPLY SEPARATOR  ***********

On 23.03.2002 at 11:50 Ivelin Ivanov wrote:

>Pollo has a basic built in support for sitemaps.
>Is the polo developer on this list ?
>

I had a look at this editor, but it is not what I intended.
It's an XML-structure based editor, not a Cocoon-specific one.
But - it works, and it's probably more useful than a text editor :)

Greetings,
Andreas

>
>----- Original Message ----- 
>From: "Stefano Mazzocchi" <stefano@apache.org>
>To: <cocoon-dev@xml.apache.org>
>Sent: Saturday, March 23, 2002 3:59 AM
>Subject: Re: [RT] Configuration front-end
>
>
>> Please, don't send HTML email!!!!
>> 
>> <quoting reason="my email client fucked up somewhere on this email and
>> it's not able to quote it properly">
>> 
>> Hi Cocoon developers,
>>  
>> I just was about to write a litte Sitemap tutorial for cocooncenter when
>> my flat-mate entered the room. He remarked that an editor with an
>> intuitive GUI
>> would make much more sense. If someone who's not absolutely convinced of
>> the
>> "XSLT doctrine" compares Cocoon to another platform - (e. g., Zope?) -
>> the
>> lack of a web-based configuration tool could make a significant
>> difference.
>>  
>> Pro's:
>> - easy and fast configuration
>> - avoid mistakes
>> - get more users
>>  
>> Con's:
>> - needs time :)
>> - Cocoon concepts might change during the next time
>>  
>> So I wondered if it is possible to implement a general Cocoon
>> configuration front-end.
>> In my eyes, it should provide at least the following functionality:
>>  
>> *Functional Requirements*
>>  
>> - good context-sensitive help/documentation
>> - the user doesn't need to know details about the sitemap vocabulary
>> (components, pipelines, ...)
>>  
>> - create/manipulate URI patterns (URI trees?)
>> - assign resources and transformations to the patterns
>> - automatic integration of the necessary components
>> - define transformations that can be used for several URI patterns
>> - "templates" for standard websites and general solutions
>>  
>> *Operational Requirements*
>>  
>> - web access (Applet <-> SOAP <-> Servlet ?)
>> - easy to install
>> - automatic integration in existing Cocoon installation
>>   (adding a pipeline for applet invocation)
>>  
>> So, if you think this might be realizable, maybe it's worth implementing
>> a prototype.
>> 
>> </quote>
>> 
>> I'll personally be interested in seeing such a prototype, but I'm not
>> sure it is realizable with the current architecture (expecially without
>> Cocoon Blocks).
>> 
>> I would wait until we have the Cocoon Blocks and the Flowmap implemented
>> or you might end up to have to rewrite the whole thing again when we do.
>> 
>> -- 
>> Stefano Mazzocchi      One must still have chaos in oneself to be
>>                           able to give birth to a dancing star.
>> <stefano@apache.org>                             Friedrich Nietzsche
>> --------------------------------------------------------------------
>> 
>> 
>> ---------------------------------------------------------------------
>> 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