Return-Path: 
 <lenya-dev-return-457-apmail-cocoon-lenya-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-lenya-dev-archive@cocoon.apache.org
Received: (qmail 2734 invoked by uid 500); 9 Jun 2003 16:01:49 -0000
Mailing-List: contact lenya-dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Post: <mailto:lenya-dev@cocoon.apache.org>
List-Help: <mailto:lenya-dev-help@cocoon.apache.org>
List-Unsubscribe: <mailto:lenya-dev-unsubscribe@cocoon.apache.org>
List-Subscribe: <mailto:lenya-dev-subscribe@cocoon.apache.org>
Reply-To: "Lenya Developers List" <lenya-dev@cocoon.apache.org>
Delivered-To: mailing list lenya-dev@cocoon.apache.org
Received: (qmail 2671 invoked from network); 9 Jun 2003 16:01:49 -0000
Message-ID: <3EE4AF5D.5060304@wyona.org>
Date: Mon, 09 Jun 2003 18:01:33 +0200
From: Michael Wechner <michael.wechner@wyona.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
 rv:1.4a) Gecko/20030401
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Lenya Developers List <lenya-dev@cocoon.apache.org>
Subject: Re: [RT] Generate doctype selection for creator
References: <bbq9nt$r2o$1@main.gmane.org> <3EE4788C.1060908@wyona.org>
 <bc1ttc$597$1@main.gmane.org>
In-Reply-To: <bc1ttc$597$1@main.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Andreas Hartmann wrote:

<snip />

>
>>
>> I disagree on the combobox, because each creator (depending on the 
>> "new doctype") can have
>> very specific parameters to pass along.
>
>
> OK, so you think there is no way to make the creator generic? 

No I don't think so. I rather think there are certain generic pieces and 
some
creators can be covered by them, but I think we need the API to enable
derivations.

Please see
http://demo.wyona.org/lenya/docs/xdocs/create-resource.html

>
>
> I have to do more brainstorming on this (just random thoughts ...)
> E.g., maybe we could use an AntTask-based creator:
>
> - a target for every document type with the needed property definitions
> - the task is parameterized with the target (this is already
>   implemented)
> - for every creator type there is Java code that generates the
>   appropriate parameter values from the page envelope, config files etc.
> - this way, the sub-menu generation could be automatized
>
>>> Another possiblity would be to filter the menu
>>> (or add a sub-menu)
>>
>>
>> The sub-menu is the way to go. It was actually always intended like 
>> this,
>> but nobody ever wrote a "Menu-JavaScript" with submenus. It is also 
>> reflecting common UI experience.
>
>
> +1
>
> Maybe we could even use CSS for menu generation?
> http://www.meyerweb.com/eric/css/edge/menus/demo.html 


That's really nice. We only have to make sure that the CSS is working on 
our target browsers and platforms (which we need to define ;-)

Thanks

Michael

>
>
> Andreas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
>
>



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