Hi Grant,
it will be the same component - an HtmlInputText in the MyFaces
ext-package, all that was going to change was an additional attribute
on the component and the rendering of the component. Component stays
the same!
Kalle's suggestion would be leading to a whole new bunch of components
- still there would be one fixed underlying component.
so there is no difference in this aspect.
regards,
Martin
On 5/10/05, Grant Smith <[EMAIL PROTECTED]> wrote:
> Before casting a vote, I would like to seek clarity on one issue this seems
> to raise:
>
> If the displayValueOnly attibute is set, does the underlying component
> change ? for example, if I have:
>
> <x:someComponent
> binding="#{someBean.methodReturningComponent}"/>
>
> And I directly manipulate the underlying component with
> someBean.methodReturningComponent(). If I add the new
> displayValueOnly, will I still be able to directly manipulate the same
> underlying component, or will that component now be something different ?
> I'm thinking it WILL be different, but I would like clarity on that.
>
> Thanks,
> Grant.
>
> Martin Marinschek wrote:
> +1 from me...
>
> regards,
>
> Martin
>
> On 5/10/05, Thomas Spiegl <[EMAIL PROTECTED]> wrote:
>
>
> +1 using Myfaces extended components
> +1 add an interface similar to UserRoleAware
> +1 adding displayValueOnly attribute
>
> What's about matching style & styleClass attributes
> (displayValueOnlyStyleClass, displayValueOnlyStyle)? Should we add
> those attributes as well?
> +1 from me
>
> regards, thomas
>
> On 5/10/05, Sylvain Vieujot <[EMAIL PROTECTED]> wrote:
>
>
> I don't want to over user the voting process, but I feel this issue should
> be sorted.
> I apologize for the ones that would be bothered by this, and here is the
> new feature I propose to vote on :
>
> - Add an interface similar to UserRoleAware, that some x: components would
> implement.
>
> - Add the matching attribute (no name decided yet, but let's use
> displayValueOnly).
> By default, displayValueOnly is false, and the components behaves as they
> do today.
> When displayValueOnly is true, no input widget is rendered. Only the text
> corresponding to the component's value is displayed.
>
> Examples :
> For inputText, inputTextarea, inputHtml, the text is displayed as if it
> where rendered by an outputText (with proper escape).
> For radio buttons, check boxes, combo boxes & list boxes, only the selected
> values are displayed.
> For inputDate, the date is rendered
>
> As suggested by Manfred, please remember that a negative binding vote on a
> *feature addition* proposal means: showstopper, that prevents the whole
> community from getting a (perhaps) valuable contribution. A -1 voter should
> at least present an alternative solution and should be willing to implement
> it himself
>
> Here is my +1 for this.
>
> Thanks,
>
> Sylvain.
>
> .
>
>
>
>
