Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 51404 invoked by uid 500); 14 Feb 2002 13:06:05 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 51393 invoked from network); 14 Feb 2002 13:06:04 -0000 Date: Thu, 14 Feb 2002 19:06:03 +0600 From: Andrew Answer X-Mailer: The Bat! (v1.53d) Reply-To: Andrew Answer Organization: FTC X-Priority: 3 (Normal) Message-ID: <277072669.20020214190603@ftc.ru> To: Torsten Curdt Subject: Re: [PROPOSAL] cocoon-action In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Feb 2002 13:06:03.0697 (UTC) FILETIME=[5B528A10:01C1B558] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello Torsten, +1! As Russian user i'm also join to initiative. Separate flying button text and internal Cocoon millstone - it's a good idea. Your new syntax look not so bad. Try it. >*************Original message************* > From: Torsten Curdt > To: cocoon-dev@xml.apache.org > Date: Thursday, February 14, 2002, 6:46:19 PM > Subject: [PROPOSAL] cocoon-action > the latest dicussion revealed a i18n problem with the cocoon-action. > Let's say we have a simple action-set > > > > > This action-set can be used in HTML as follows > > > Now here is the problem: the value attribute is the key for the action set > as well as the caption of the input button. Now think of a i18n site. The > HTML should look like for locale "de": > > > But the action-set has still english keys. So you would need an action-set > per lanuage. This is IMHO really *BAD*!!!!!!! > So I propose to change this as follows: > locale en: > > locale de: > > ...so there is no i18n dependency. AAAND while changing this I'd also like > to add a way to pass another parameter to the action: > > This would make an MultiAction very easy to implement! :) But I'm sure > there are other use-cases as well... > So I'd like to deprecate the old "cocoon-action" syntax (but still support > it) and like to introduce the new syntax. > [prefix][delimitter][actionkey]{[delimitter][paramtervalue]} > | | | | | > | | | | +-optional: > | | | | will be passed as action > | | | | parameter named (e.g. > | | | | [prefix]-paramter) > | | | | > | | | +------- introduce the parametervalue > | | | (e.g. '/') > | | | > | | +------------------- the key of action (the value > | | attribute of the current impl) > | | > | +------------------------------- (e.g. '-' or ':') > | > +----------------------------------------- prefix (e.g. again 'cocoon-action') > What do guys think? > -- > Torsten > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org >*************Original message************* Best regards, Andrew Answer A.Nuzhdov@ftc.ru --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org