Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 34621 invoked from network); 4 May 2005 01:53:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 May 2005 01:53:16 -0000 Received: (qmail 96394 invoked by uid 500); 4 May 2005 01:55:04 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 96354 invoked by uid 500); 4 May 2005 01:55:04 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 96329 invoked by uid 99); 4 May 2005 01:55:04 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=HTML_40_50,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from mailgwvw01.freelance.com (HELO mailgwvw01.freelance.com) (207.234.129.118) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 03 May 2005 18:55:03 -0700 Received: from mailgwvw02.freelance.com (mailgwvw02.freelance.com [207.234.129.52]) by mailgwvw01.freelance.com (8.12.3/8.12.3) with ESMTP id j441rarq004640 for ; Wed, 4 May 2005 03:53:36 +0200 Received: from [10.0.0.101] ([200.88.145.117]) by mailgwvw02.freelance.com (Lotus Domino Release 5.0.12) with ESMTP id 2005050403523518:4977 ; Wed, 4 May 2005 03:52:35 +0200 Subject: Fwd: [Myfaces-develop] New feature suggestion : Edit mode From: Sylvain Vieujot To: dev@myfaces.apache.org Date: Tue, 03 May 2005 21:52:41 -0400 Message-Id: <1115171561.10577.101.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-4) X-MIMETrack: Itemize by SMTP Server on mailgw01/Freelance(Release 5.0.12 |February 13, 2003) at 05/04/2005 03:52:35 AM, Serialize by Router on mailgw01/Freelance(Release 5.0.12 |February 13, 2003) at 05/04/2005 03:52:37 AM, Serialize complete at 05/04/2005 03:52:37 AM Content-Type: multipart/alternative; boundary="=-JzPYD8C68Ij6JMZpyFCD" X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_20_30, HTML_FONTCOLOR_UNSAFE,HTML_MESSAGE autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mailgwvw01.freelance.com X-Virus-Scanned: ClamAV 0.84/866/Tue May 3 21:02:33 2005 on mailgwvw01.freelance.com X-Virus-Status: Clean X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --=-JzPYD8C68Ij6JMZpyFCD Content-Transfer-Encoding: 7bit Content-Type: text/plain Quite sometimes ago, we discussed on adding an editMode attribute the meaningful x: components. The explanation for this is in the forwarded email discussion bellow. To summarize what it's about : renders as the standard input box renders as an x:outputText I now need those features, and would like to implement them (have them implemented). So, I would like to check everyone still agrees with this. Thanks, Sylvain. Subject: Re: [Myfaces-develop] New feature suggestion : Edit mode Date: Fri, 30 Jul 2004 10:51:39 -0400 One more precision : I didn't dig into the role based access -- used in disabled for example -- right now. Maybe we have to think for one minute about the integration of this with editMode. As of now, I think it works well : editMode == true => standard behavior editMode == false => renders as output anyway. But as I'm not sure I fully understand the MyFaces roles right now, maybe I'm wrong or there is something smarter to do. Sylvain. On Fri, 2004-07-30 at 10:12, Sylvain Vieujot wrote: > Yes, that's it. > > I also think that the editmode attribute is better (in fact editMode > as I think this is the convention, like for actionListener). > > Thanks for your feedback. > > Sylvain. > > On Fri, 2004-07-30 at 03:22, Manfred Geiler wrote: > > > Hi, > > Just a short summarize of your suggestion, so that I'm sure that I got > > it right: > > - we indroduce a new attribute "edit" (or "editmode") for all extended > > input components (x: tags) > > - default value of this attribute is true > > - value of true does not change rendering > > - value of false renders an output (normal html text) instead of an > > input (html input tag) > > > > Ok, her is my vote: > > +1 for such an attribute > > +.4 for name "edit" > > +.6 for name "editmode" > > > > Regards, > > Manfred > > > > > > Sylvain Vieujot wrote: > > > *Feedback requested on implementing a new edit attribute for the x: tags : > > > * > > > I used to program a lot with Notes/Domino, and Domino has a very nice > > > feature : > > > You design a form, and the you use it either in read or edit mode. > > > In read mode, you just see the fields contents (i.e. h:outputText in > > > JSF), and in edit mode, you have the corresponding input field (i.e. > > > h:inputText(area) in JSF). > > > > > > This is a very useful feature that really help to quicken the development. > > > In JSF right now, as far as I know, you either have to design 2 forms : > > > one for read mode, and one for edit mode, or (especially if the access > > > can be different for each field) like here : > > > > > > > > > > > > > > > I think it would be way easier to add an *edit* attribute to the x: > > > tags, that would reduce the upper code to : > > > > > > > > > > > > For sure, you can use the disabled attribute, but here, you wouldn't > > > have the text in a disabled box, but you would see it clear which is > > > much nicer. > > > For the x:dateInput tag that I just did, it would also look nicer to see > > > a clean text with the date/time instead of all the input fields/combo boxes. > > > For the x:fileUpload also, it would allow to display the file name and > > > maybe render the file in case the edit attribute is set to false. > > > > > > In the current MyFaces exemples, for the dataTable.jsf example, if you > > > want to edit all the countries, you also have to design a new form. > > > I think with an edit attribute, we could avoid the countryTableForm.jsf, > > > and have only one form. > > > > > > I also need a wiki style input tag where in edit mode, you enter text > > > with wiki like formating, and in read mode, you just see the formated text. > > > In such cases, the edit (or whatever we choose to name it) attribute is > > > mandatory. > > > > > > So, my question is : > > > Would you agree that we implement a standard edit attribute for all the > > > x: tags where it's relevant ? > > > > > > And as you might guess, I think it would really be a big plus for > > > MyFaces as it would dramatically improve and simplify some developments. > > > > > > Thanks for your feedback. > > > > > > Sylvain. > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > > one more big change to announce. We are now OSTG- Open Source Technology > > Group. Come see the changes on the new OSTG site. www.ostg.com > > _______________________________________________ > > Myfaces-develop mailing list > > Myfaces-develop@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/myfaces-develop --=-JzPYD8C68Ij6JMZpyFCD Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=utf-8 Quite sometimes ago, we discussed on adding an editMode attribute the meaningful x: components.
The explanation for this is in the forwarded email discussion bellow.

To summarize what it's about :
<x:inputText ... editMode="true"> renders as the standard input box
<x:inputText ... editMode="false"> renders as an x:outputText

I now need those features, and would like to implement them (have them implemented).
So, I would like to check everyone still agrees with this.

Thanks,

Sylvain.

Subject: Re: [Myfaces-develop] New feature suggestion : Edit mode
Date: Fri, 30 Jul 2004 10:51:39 -0400
One more precision :
I didn't dig into the role based access -- used in disabled for example -- right now.
Maybe we have to think for one minute about the integration of this with editMode.

As of now, I think it works well :
editMode == true => standard behavior
editMode == false => renders as output anyway.

But as I'm not sure I fully understand the MyFaces roles right now, maybe I'm wrong or there is something smarter to do.

Sylvain.

On Fri, 2004-07-30 at 10:12, Sylvain Vieujot wrote:
Yes, that's it.

I also think that the editmode attribute is better (in fact editMode as I think this is the convention, like for actionListener).

Thanks for your feedback.

Sylvain.

On Fri, 2004-07-30 at 03:22, Manfred Geiler wrote: 
Hi,
Just a short summarize of your suggestion, so that I'm sure that I got 
it right:
- we indroduce a new attribute "edit" (or "editmode") for all extended 
input components (x: tags)
- default value of this attribute is true
- value of true does not change rendering
- value of false renders an output (normal html text) instead of an 
input (html input tag)

Ok, her is my vote:
+1 for such an attribute
+.4 for name "edit"
+.6 for name "editmode"

Regards,
Manfred


Sylvain Vieujot wrote:
> *Feedback requested on implementing a new edit attribute for the x: tags :
> *
> I used to program a lot with Notes/Domino, and Domino has a very nice 
> feature :
> You design a form, and the you use it either in read or edit mode.
> In read mode, you just see the fields contents (i.e. h:outputText in 
> JSF), and in edit mode, you have the corresponding input field (i.e. 
> h:inputText(area) in JSF).
> 
> This is a very useful feature that really help to quicken the development.
> In JSF right now, as far as I know, you either have to design 2 forms : 
> one for read mode, and one for edit mode, or (especially if the access 
> can be different for each field) like here :
> 
> <h:inputText value="#{order.client}" size="50" rendered="#{editMode.edit}"/>
> <h:outputText value="#{order.client}" rendered="#{! editMode.edit}"/>
> 
> I think it would be way easier to add an *edit* attribute to the x: 
> tags, that would reduce the upper code to :
> 
> <x:inputText value="#{order.client}" size="50" *edit*="#{editMode.edit}"/>
> 
> For sure, you can use the disabled attribute, but here, you wouldn't 
> have the text in a disabled box, but you would see it clear which is 
> much nicer.
> For the x:dateInput tag that I just did, it would also look nicer to see 
> a clean text with the date/time instead of all the input fields/combo boxes.
> For the x:fileUpload also, it would allow to display the file name and 
> maybe render the file in case the edit attribute is set to false.
> 
> In the current MyFaces exemples, for the dataTable.jsf example, if you 
> want to edit all the countries, you also have to design a new form.
> I think with an edit attribute, we could avoid the countryTableForm.jsf, 
> and have only one form.
> 
> I also need a wiki style input tag where in edit mode, you enter text 
> with wiki like formating, and in read mode, you just see the formated text.
> In such cases, the edit (or whatever we choose to name it) attribute is 
> mandatory.
> 
> So, my question is :
> Would you agree that we implement a standard edit attribute for all the 
> x: tags where it's relevant ?
> 
> And as you might guess, I think it would really be a big plus for 
> MyFaces as it would dramatically improve and simplify some developments.
> 
> Thanks for your feedback.
> 
> Sylvain.


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Myfaces-develop mailing list
Myfaces-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/myfaces-develop
--=-JzPYD8C68Ij6JMZpyFCD--