Hi All
Does anyone know if the new AJAX components (Table and Tree) are available
as Drag and Drop components on the Netbeans 6.1 Palette?, If so where are
they hidden...
On Thu, Jun 5, 2008 at 5:42 AM, <users-digest-help_at_woodstock.dev.java.net>
wrote:
>
> users Digest 4 Jun 2008 19:42:25 -0000 Issue 169
>
> Topics (messages 1090 through 1101):
>
> Unable to disable components with JavaScript
> 1090 by: Ryan de Laplante
> 1091 by: Ratnadeep Bhattacharjee
> 1092 by: Dan Labrecque
> 1093 by: Ryan de Laplante
> 1095 by: Ryan de Laplante
> 1100 by: Dan Labrecque
>
> Re: Asynchronously submit and refresh. How to?
> 1094 by: Felipe Jaekel
>
> Rendering issue with Netbeans and Firefox
> 1096 by: Outar, Rob-P63430
>
> JSF 2.0 question
> 1097 by: Ryan de Laplante
> 1101 by: Dan Labrecque
>
> converting jsf tab to woodstock tab
> 1098 by: Rebecca Searls
> 1099 by: Venkatesh Babu
>
> Administrivia:
>
> To subscribe to the digest, e-mail:
> users-digest-subscribe_at_woodstock.dev.java.net
>
> To unsubscribe from the digest, e-mail:
> users-digest-unsubscribe_at_woodstock.dev.java.net
>
> To post to the list, e-mail:
> users_at_woodstock.dev.java.net
>
>
> ----------------------------------------------------------------------
>
>
> ---------- Forwarded message ----------
> From: Ryan de Laplante <ryan_at_ijws.com>
> To: users_at_woodstock.dev.java.net
> Date: Tue, 03 Jun 2008 16:30:41 -0400
> Subject: Unable to disable components with JavaScript
> Hi,
>
> I created a new NetBeans 6.0.1 web project with Visual Web and am trying
> to create a sample application where there are three dropdown lists. As
> the user selects an item in the first list, the second list enables and
> shows data associated with the selection. As the user selects an item
> in the second dropdown list, the third one enables and displays data
> associated with the selection. If the user selects a different item
> from the first dropdown list, the third dropdown list is cleared and
> disabled. I'm using AJAX features to avoid form submits.
>
> I've got this working, except the enable/disable part. I can see the
> components enable/disable when I want to, but then they always revert
> back to enabled immediately after. I've spent a few hours trying
> different things and can't figure it out.
>
> JSP:
>
> in the head section:
>
> <webuijsf:script>
> function init() {
> dropDown2.setProps({disabled: true});
> dropDown3.setProps({disabled: true});
> }
>
> function dropDown1Changed() {
> var dropDown2 =
> document.getElementById('form1:dropDown2');
> dropDown2.setProps({disable: false});
> dropDown2.refresh('form1:dropDown1');
> dropDown2.focus();
>
> var dropDown3 =
> document.getElementById('form1:dropDown3');
> dropDown3.setProps({disabled: true});
> dropDown3.refresh('');
> }
>
> function dropDown2Changed() {
> var dropDown3 =
> document.getElementById('form1:dropDown3');
> dropDown3.setProps({disabled: false});
> dropDown3.refresh('form1:dropDown2');
> dropDown3.focus();
> }
> </webuijsf:script>
>
> Inside the body:
>
> <webuijsf:dropDown binding="#{Page1.dropDown1}" id="dropDown1"
> items="#{Page1.list1}" label="Proximity To Elevator"
> labelOnTop="true"
> onChange="dropDown1Changed(); return false;"
> style="position: absolute; left: 120px; top:
> 48px"
> valueChangeListenerExpression="#{Page1.dropDown1_processValueChange}"/>
> <webuijsf:dropDown binding="#{Page1.dropDown2}"
> id="dropDown2" items="#{Page1.list2}" label="Floor" labelOnTop="true"
> onChange="dropDown2Changed(); return
> false;"
> style="left: 120px; top: 96px; position:
> absolute"
> valueChangeListenerExpression="#{Page1.dropDown2_processValueChange}"/>
> <webuijsf:dropDown binding="#{Page1.dropDown3}"
> id="dropDown3" items="#{Page1.list3}" label="Bed Type" labelOnTop="true"
> style="left: 120px; top: 144px; position:
> absolute"
> valueChangeListenerExpression="#{Page1.dropDown3_processValueChange}"/>
>
> My value change listeners just look at the selected value and update the
> other dropdown list options.
>
>
> Thanks,
> Ryan
>
>
>
>
> ---------- Forwarded message ----------
> From: Ratnadeep Bhattacharjee <Ratnadeep.Bhattacharjee_at_Sun.COM>
> To: users_at_woodstock.dev.java.net
> Date: Tue, 03 Jun 2008 16:43:27 -0400
> Subject: Re: Unable to disable components with JavaScript
> Shouldn't the setProps({disabled: true}) come after the refresh() line.
> Otherwise, when refresh() gets invoked the state of the dropdown is changed
> to what it is on the server - where disable is possibly "false" by default.
> I just took a glance at the code - so I could be wrong...
>
> -Deep.
>
>
> Ryan de Laplante wrote:
>
>> Hi,
>>
>> I created a new NetBeans 6.0.1 web project with Visual Web and am trying
>> to create a sample application where there are three dropdown lists. As
>> the user selects an item in the first list, the second list enables and
>> shows data associated with the selection. As the user selects an item
>> in the second dropdown list, the third one enables and displays data
>> associated with the selection. If the user selects a different item
>> from the first dropdown list, the third dropdown list is cleared and
>> disabled. I'm using AJAX features to avoid form submits.
>>
>> I've got this working, except the enable/disable part. I can see the
>> components enable/disable when I want to, but then they always revert
>> back to enabled immediately after. I've spent a few hours trying
>> different things and can't figure it out.
>>
>> JSP:
>>
>> in the head section:
>>
>> <webuijsf:script>
>> function init() {
>> dropDown2.setProps({disabled: true});
>> dropDown3.setProps({disabled: true});
>> }
>>
>> function dropDown1Changed() {
>> var dropDown2 =
>> document.getElementById('form1:dropDown2');
>> dropDown2.setProps({disable: false});
>> dropDown2.refresh('form1:dropDown1');
>> dropDown2.focus();
>>
>> var dropDown3 =
>> document.getElementById('form1:dropDown3');
>> dropDown3.setProps({disabled: true});
>> dropDown3.refresh('');
>> }
>>
>> function dropDown2Changed() {
>> var dropDown3 =
>> document.getElementById('form1:dropDown3');
>> dropDown3.setProps({disabled: false});
>> dropDown3.refresh('form1:dropDown2');
>> dropDown3.focus();
>> }
>> </webuijsf:script>
>>
>> Inside the body:
>>
>> <webuijsf:dropDown binding="#{Page1.dropDown1}" id="dropDown1"
>> items="#{Page1.list1}" label="Proximity To Elevator"
>> labelOnTop="true"
>> onChange="dropDown1Changed(); return false;"
>> style="position: absolute; left: 120px; top:
>> 48px"
>> valueChangeListenerExpression="#{Page1.dropDown1_processValueChange}"/>
>> <webuijsf:dropDown binding="#{Page1.dropDown2}"
>> id="dropDown2" items="#{Page1.list2}" label="Floor" labelOnTop="true"
>> onChange="dropDown2Changed(); return
>> false;"
>> style="left: 120px; top: 96px; position:
>> absolute"
>> valueChangeListenerExpression="#{Page1.dropDown2_processValueChange}"/>
>> <webuijsf:dropDown binding="#{Page1.dropDown3}"
>> id="dropDown3" items="#{Page1.list3}" label="Bed Type" labelOnTop="true"
>> style="left: 120px; top: 144px; position:
>> absolute"
>> valueChangeListenerExpression="#{Page1.dropDown3_processValueChange}"/>
>>
>> My value change listeners just look at the selected value and update the
>> other dropdown list options.
>>
>>
>> Thanks,
>> Ryan
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>
>>
>
>
> ---------- Forwarded message ----------
> From: Dan Labrecque <Dan.Labrecque_at_Sun.COM>
> To: users_at_woodstock.dev.java.net
> Date: Tue, 03 Jun 2008 16:49:54 -0400
> Subject: Re: Unable to disable components with JavaScript
> Take a look at how the refresh feature works in the TLD for dropDown below.
>
> http://webdev2.sun.com/woodstock-tlddocs
>
> Example #6 states:
>
> "Note that the refresh function can optionally take a list of elements to
> execute. Thus, a comma-separated list of ids can be provided to update
> components server-side: refresh("form1:id1,form2:id2,..."). When no
> parameter is given, the refresh function acts as a reset. That is, the
> component will be redrawn using values set server-side, but not updated."
>
> If you want to maintain the current selection, you must provide the ID of
> the dropDown being refreshed. However, this works more like a form submit.
> That is, the disabled state is not an HTML input value like a user
> selection. Calling refresh like this will override the client-side disabled
> state.
>
> That said, consider calling refresh first, then set the dropDown disabled.
> Alternatively, you can use a hidden field to maintain the disabled state.
>
> Dan
>
> Ryan de Laplante wrote:
>
>> Hi,
>>
>> I created a new NetBeans 6.0.1 web project with Visual Web and am trying
>> to create a sample application where there are three dropdown lists. As
>> the user selects an item in the first list, the second list enables and
>> shows data associated with the selection. As the user selects an item
>> in the second dropdown list, the third one enables and displays data
>> associated with the selection. If the user selects a different item
>> from the first dropdown list, the third dropdown list is cleared and
>> disabled. I'm using AJAX features to avoid form submits.
>>
>> I've got this working, except the enable/disable part. I can see the
>> components enable/disable when I want to, but then they always revert
>> back to enabled immediately after. I've spent a few hours trying
>> different things and can't figure it out.
>>
>> JSP:
>>
>> in the head section:
>>
>> <webuijsf:script>
>> function init() {
>> dropDown2.setProps({disabled: true});
>> dropDown3.setProps({disabled: true});
>> }
>>
>> function dropDown1Changed() {
>> var dropDown2 =
>> document.getElementById('form1:dropDown2');
>> dropDown2.setProps({disable: false});
>> dropDown2.refresh('form1:dropDown1');
>> dropDown2.focus();
>>
>> var dropDown3 =
>> document.getElementById('form1:dropDown3');
>> dropDown3.setProps({disabled: true});
>> dropDown3.refresh('');
>> }
>>
>> function dropDown2Changed() {
>> var dropDown3 =
>> document.getElementById('form1:dropDown3');
>> dropDown3.setProps({disabled: false});
>> dropDown3.refresh('form1:dropDown2');
>> dropDown3.focus();
>> }
>> </webuijsf:script>
>>
>> Inside the body:
>>
>> <webuijsf:dropDown binding="#{Page1.dropDown1}" id="dropDown1"
>> items="#{Page1.list1}" label="Proximity To Elevator"
>> labelOnTop="true"
>> onChange="dropDown1Changed(); return false;"
>> style="position: absolute; left: 120px; top:
>> 48px"
>> valueChangeListenerExpression="#{Page1.dropDown1_processValueChange}"/>
>> <webuijsf:dropDown binding="#{Page1.dropDown2}"
>> id="dropDown2" items="#{Page1.list2}" label="Floor" labelOnTop="true"
>> onChange="dropDown2Changed(); return
>> false;"
>> style="left: 120px; top: 96px; position:
>> absolute"
>> valueChangeListenerExpression="#{Page1.dropDown2_processValueChange}"/>
>> <webuijsf:dropDown binding="#{Page1.dropDown3}"
>> id="dropDown3" items="#{Page1.list3}" label="Bed Type" labelOnTop="true"
>> style="left: 120px; top: 144px; position:
>> absolute"
>> valueChangeListenerExpression="#{Page1.dropDown3_processValueChange}"/>
>>
>> My value change listeners just look at the selected value and update the
>> other dropdown list options.
>>
>>
>> Thanks,
>> Ryan
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>
>>
>
>
> ---------- Forwarded message ----------
> From: Ryan de Laplante <ryan_at_ijws.com>
> To: users_at_woodstock.dev.java.net
> Date: Tue, 03 Jun 2008 20:02:58 -0400
> Subject: Re: Unable to disable components with JavaScript
> Thanks Ratnadeep and Dan for responding so quickly. I did have the
> setProps after the refresh and had these issues, but I also tried a bunch of
> other things too not knowing how refresh really works. With this new
> knowledge I will take another crack at it.
>
> Thanks!
> Ryan
>
>
> Dan Labrecque wrote:
>
>> Take a look at how the refresh feature works in the TLD for dropDown
>> below.
>>
>> http://webdev2.sun.com/woodstock-tlddocs
>>
>> Example #6 states:
>>
>> "Note that the refresh function can optionally take a list of elements to
>> execute. Thus, a comma-separated list of ids can be provided to update
>> components server-side: refresh("form1:id1,form2:id2,..."). When no
>> parameter is given, the refresh function acts as a reset. That is, the
>> component will be redrawn using values set server-side, but not updated."
>>
>> If you want to maintain the current selection, you must provide the ID of
>> the dropDown being refreshed. However, this works more like a form submit.
>> That is, the disabled state is not an HTML input value like a user
>> selection. Calling refresh like this will override the client-side disabled
>> state.
>>
>> That said, consider calling refresh first, then set the dropDown disabled.
>> Alternatively, you can use a hidden field to maintain the disabled state.
>>
>> Dan
>>
>> Ryan de Laplante wrote:
>>
>>> Hi,
>>>
>>> I created a new NetBeans 6.0.1 web project with Visual Web and am trying
>>> to create a sample application where there are three dropdown lists. As
>>> the user selects an item in the first list, the second list enables and
>>> shows data associated with the selection. As the user selects an item
>>> in the second dropdown list, the third one enables and displays data
>>> associated with the selection. If the user selects a different item
>>> from the first dropdown list, the third dropdown list is cleared and
>>> disabled. I'm using AJAX features to avoid form submits.
>>>
>>> I've got this working, except the enable/disable part. I can see the
>>> components enable/disable when I want to, but then they always revert
>>> back to enabled immediately after. I've spent a few hours trying
>>> different things and can't figure it out.
>>>
>>> JSP:
>>>
>>> in the head section:
>>>
>>> <webuijsf:script>
>>> function init() {
>>> dropDown2.setProps({disabled: true});
>>> dropDown3.setProps({disabled: true});
>>> }
>>>
>>> function dropDown1Changed() {
>>> var dropDown2 =
>>> document.getElementById('form1:dropDown2');
>>> dropDown2.setProps({disable: false});
>>> dropDown2.refresh('form1:dropDown1');
>>> dropDown2.focus();
>>>
>>> var dropDown3 =
>>> document.getElementById('form1:dropDown3');
>>> dropDown3.setProps({disabled: true});
>>> dropDown3.refresh('');
>>> }
>>>
>>> function dropDown2Changed() {
>>> var dropDown3 =
>>> document.getElementById('form1:dropDown3');
>>> dropDown3.setProps({disabled: false});
>>> dropDown3.refresh('form1:dropDown2');
>>> dropDown3.focus();
>>> }
>>> </webuijsf:script>
>>>
>>> Inside the body:
>>>
>>> <webuijsf:dropDown binding="#{Page1.dropDown1}" id="dropDown1"
>>> items="#{Page1.list1}" label="Proximity To Elevator"
>>> labelOnTop="true"
>>> onChange="dropDown1Changed(); return false;"
>>> style="position: absolute; left: 120px; top:
>>> 48px"
>>> valueChangeListenerExpression="#{Page1.dropDown1_processValueChange}"/>
>>> <webuijsf:dropDown binding="#{Page1.dropDown2}"
>>> id="dropDown2" items="#{Page1.list2}" label="Floor" labelOnTop="true"
>>> onChange="dropDown2Changed(); return
>>> false;"
>>> style="left: 120px; top: 96px; position:
>>> absolute"
>>> valueChangeListenerExpression="#{Page1.dropDown2_processValueChange}"/>
>>> <webuijsf:dropDown binding="#{Page1.dropDown3}"
>>> id="dropDown3" items="#{Page1.list3}" label="Bed Type" labelOnTop="true"
>>> style="left: 120px; top: 144px; position:
>>> absolute"
>>> valueChangeListenerExpression="#{Page1.dropDown3_processValueChange}"/>
>>>
>>> My value change listeners just look at the selected value and update the
>>> other dropdown list options.
>>>
>>>
>>> Thanks,
>>> Ryan
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>
>>
>>
>
>
> ---------- Forwarded message ----------
> From: Ryan de Laplante <ryan_at_ijws.com>
> To: users_at_woodstock.dev.java.net
> Date: Wed, 04 Jun 2008 10:19:58 -0400
> Subject: Re: Unable to disable components with JavaScript
> Moving the setProps to after the refresh didn't help. I ended up removing
> the setProps and doing it server-side in the value change listeners. I also
> had to add the correct IDs to the refresh(). It now works the way I want,
> except the focus().
> function dropDown1Changed() {
> var dropDown2 =
> document.getElementById('form1:dropDown2');
>
> dropDown2.refresh('form1:dropDown1,form1:dropDown2,form1:dropDown3');
> var dropDown3 =
> document.getElementById('form1:dropDown3');
>
> dropDown3.refresh('form1:dropDown1,form1:dropDown2,form1:dropDown3');
> dropDown2.focus();
> }
> function dropDown2Changed() {
> var dropDown3 =
> document.getElementById('form1:dropDown3');
>
> dropDown3.refresh('form1:dropDown1,form1:dropDown2,form1:dropDown3');
> dropDown3.focus();
> }
>
> After I make a selection in dropDown1, I expect dropDown2 to have focus but
> it does not. After I make a selection in dropDown2 I expect dropDown3 to
> have focus but it does not. I don't see a server side property or method
> to set focus, so it probably has to be client side.
> Thanks for the link to the TLD documentation. I was going nuts trying to
> figure out how to use these components using only tutorials and examples.
> I thought the TLD javadoc was for programmers coding the components.
>
>
> Thanks,
> Ryan
>
>
> Dan Labrecque wrote:
>
>> Take a look at how the refresh feature works in the TLD for dropDown
>> below.
>>
>> http://webdev2.sun.com/woodstock-tlddocs
>>
>> Example #6 states:
>>
>> "Note that the refresh function can optionally take a list of elements to
>> execute. Thus, a comma-separated list of ids can be provided to update
>> components server-side: refresh("form1:id1,form2:id2,..."). When no
>> parameter is given, the refresh function acts as a reset. That is, the
>> component will be redrawn using values set server-side, but not updated."
>>
>> If you want to maintain the current selection, you must provide the ID of
>> the dropDown being refreshed. However, this works more like a form submit.
>> That is, the disabled state is not an HTML input value like a user
>> selection. Calling refresh like this will override the client-side disabled
>> state.
>>
>> That said, consider calling refresh first, then set the dropDown disabled.
>> Alternatively, you can use a hidden field to maintain the disabled state.
>>
>> Dan
>>
>
>
>
> ---------- Forwarded message ----------
> From: Dan Labrecque <Dan.Labrecque_at_Sun.COM>
> To: users_at_woodstock.dev.java.net
> Date: Wed, 04 Jun 2008 15:00:26 -0400
> Subject: Re: Unable to disable components with JavaScript
> The refresh request is performed asynchronously, so you're setProps call
> may have been executed before the response was returned. You could have
> subscribed to the refresh end event in order to invoke the setProps call
> after the refresh.
>
> Regarding focus, "dropDown2.focus()" is not a valid call. (This focus
> function is on the DOM node associated with the underlying HTML select
> element.) However, you can call dropDown2.getSelectElement().focus().
>
> Dan
>
> Ryan de Laplante wrote:
>
>> Moving the setProps to after the refresh didn't help. I ended up removing
>> the setProps and doing it server-side in the value change listeners. I also
>> had to add the correct IDs to the refresh(). It now works the way I want,
>> except the focus(). function dropDown1Changed() {
>> var dropDown2 =
>> document.getElementById('form1:dropDown2');
>>
>> dropDown2.refresh('form1:dropDown1,form1:dropDown2,form1:dropDown3');
>> var dropDown3 =
>> document.getElementById('form1:dropDown3');
>>
>> dropDown3.refresh('form1:dropDown1,form1:dropDown2,form1:dropDown3');
>> dropDown2.focus();
>> }
>> function dropDown2Changed() {
>> var dropDown3 =
>> document.getElementById('form1:dropDown3');
>>
>> dropDown3.refresh('form1:dropDown1,form1:dropDown2,form1:dropDown3');
>> dropDown3.focus();
>> }
>>
>> After I make a selection in dropDown1, I expect dropDown2 to have focus
>> but it does not. After I make a selection in dropDown2 I expect dropDown3
>> to have focus but it does not. I don't see a server side property or
>> method to set focus, so it probably has to be client side.
>> Thanks for the link to the TLD documentation. I was going nuts trying to
>> figure out how to use these components using only tutorials and examples.
>> I thought the TLD javadoc was for programmers coding the components.
>>
>>
>> Thanks,
>> Ryan
>>
>>
>> Dan Labrecque wrote:
>>
>>> Take a look at how the refresh feature works in the TLD for dropDown
>>> below.
>>>
>>> http://webdev2.sun.com/woodstock-tlddocs
>>>
>>> Example #6 states:
>>>
>>> "Note that the refresh function can optionally take a list of elements to
>>> execute. Thus, a comma-separated list of ids can be provided to update
>>> components server-side: refresh("form1:id1,form2:id2,..."). When no
>>> parameter is given, the refresh function acts as a reset. That is, the
>>> component will be redrawn using values set server-side, but not updated."
>>>
>>> If you want to maintain the current selection, you must provide the ID of
>>> the dropDown being refreshed. However, this works more like a form submit.
>>> That is, the disabled state is not an HTML input value like a user
>>> selection. Calling refresh like this will override the client-side disabled
>>> state.
>>>
>>> That said, consider calling refresh first, then set the dropDown
>>> disabled. Alternatively, you can use a hidden field to maintain the disabled
>>> state.
>>>
>>> Dan
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>
>>
>
>
> ---------- Forwarded message ----------
> From: "Felipe Jaekel" <fkjaekel_at_gmail.com>
> To: users_at_woodstock.dev.java.net
> Date: Wed, 4 Jun 2008 09:59:53 -0300
> Subject: Re: Asynchronously submit and refresh. How to?
> To refresh multiple components use Dynamic Faces
>
> 2008/5/20 Stefan Bley <stefan.bley_at_saxsys.de>:
>
>>
>> Hi Arnaud,
>>
>> thanks for your reply.
>>
>> I tried as you suggested. The event is triggered, but the values from cal1
>> and txt1 are not stored in the Bean's properties. I verify this through a
>> logging call in the event handler. :confused:
>>
>> Furthermore, how could I make refresh 2 components, say dd2 and dd3?
>>
>> Cheers, Stevy
>>
>>
>> Arnaud Brand wrote:
>> >
>> > Instead using
>> >
>> > dd1.submit("form1:cal1,form1:txt1");
>> > dd2.refresh("form1:dd1");
>> > I would rather try
>> > dd2.refresh("form1:dd1,form1:cal1,form1:txt1");
>> > This should submit dd1, cal1 and txt1, trigger your event listener and
>> > refresh dd2.
>> >
>> > 2 reasons for that :
>> > - if your bean "Bean" is scoped at the request level your second call
>> > (dd2.refresh) will have "lost" the values from your first call
>> > (dd1.submit).
>> > - it might be that dd2.refresh is called before dd1.submit actually
>> > returns (because submit is asynchronous), so may be your dd2 values are
>> > set in the bean after having already been read by dd2.refresh.
>> >
>> > I hope that helps. Have a nice evening,
>> > Arnaud
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Asynchronously-submit-and-refresh.-How-to--tp17316746p17334078.html
>> Sent from the Project Woodstock - Users mailing list archive at
>> Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>
>>
>
>
> ---------- Forwarded message ----------
> From: "Outar, Rob-P63430" <Robin.Outar_at_gdc4s.com>
> To: <users_at_woodstock.dev.java.net>
> Date: Wed, 4 Jun 2008 12:40:20 -0400
> Subject: Rendering issue with Netbeans and Firefox
>
> Very new at using JSF, in fact I am using it from Netbeans 6.1. Once I
> create the pages using the visual designer, in IE, for the most part they
> look as they were designed, however when I view them in Firefox, listbox
> seems to be the original size and spacing between components, a button in
> particular, is larger than IE. Not sure how to fix this, any help
> appreciated.
>
>
>
> After reading the Netbeans site I saw this:
>
>
>
> # Issue #95022: Resizing of textfield and other components does not work.
>
> Description: Due to a change in Woodstock components, resize handles have
> been removed from the following Woodstock components: TextField,
> TextArea,PasswordField, DropDown and ListBox. This issue impacts especially
> projects imported from Java Studio Creator and NetBeans Visual Web Pack 5.5/
> 5.5.1. Resized components may look different from how they looked in
> previous releases.
>
> Workaround: For TextField and TextArea components, use the columns and rows
> attributes, respectively. DropDown and ListBox components are automatically
> resized to the size of the longest item by the browser.
>
>
>
> Does the above explain why the listbox does not show up as the size I set
> in the designer?
>
>
>
> Thanks,
>
>
>
> Rob
>
>
>
>
> ---------- Forwarded message ----------
> From: Ryan de Laplante <ryan_at_ijws.com>
> To: users_at_woodstock.dev.java.net
> Date: Wed, 04 Jun 2008 14:34:43 -0400
> Subject: JSF 2.0 question
> Will JSF 2.0 provide a standard way for component sets to include only the
> CSS and JavaScript imports required by components being used on the page
> instead of forcing the component's entire theme to be downloaded? If I
> only use dropdown lists, text boxes, buttons, etc. then I shouldn't have to
> download 500 KB of CSS and JavaScript on the first page.
> Thanks,
> Ryan
>
>
>
> ---------- Forwarded message ----------
> From: Dan Labrecque <Dan.Labrecque_at_Sun.COM>
> To: users_at_woodstock.dev.java.net
> Date: Wed, 04 Jun 2008 15:41:01 -0400
> Subject: Re: JSF 2.0 question
> I don't believe this has anything to do with JSF 2.0 features. Woodstock
> combines CSS, JavaScript, and images to avoid generating multiple requests.
> At one time, requests were generated for separate component resources, but
> performance suffered greatly. Although the requests were small, the number
> of requests have far more impact on performance than the size of the
> request. (This is particularly true for images) Although, this is relative
> to how many components are used in the page. If the browser's cache is
> enabled, these resources should only be loaded once.
>
> If you are interested in the performance improvements made to Woodstock
> 4.2, please see the thread below. This includes combined files, lazy
> loading, gzip compression, etc.
>
>
> https://woodstock.dev.java.net/servlets/ProjectForumMessageView?messageID=23417&forumID=2879
>
> Also take a look at the Woodstock head tag for performance related
> attributes. For example, webuiAll and webuiJsfx can be used to tweak the
> overall download size, depending on what features you need.
>
> http://webdev2.sun.com/woodstock-tlddocs
>
> Dan
>
> Ryan de Laplante wrote:
>
>> Will JSF 2.0 provide a standard way for component sets to include only the
>> CSS and JavaScript imports required by components being used on the page
>> instead of forcing the component's entire theme to be downloaded? If I
>> only use dropdown lists, text boxes, buttons, etc. then I shouldn't have to
>> download 500 KB of CSS and JavaScript on the first page.
>> Thanks,
>> Ryan
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>
>>
>
>
> ---------- Forwarded message ----------
> From: Rebecca Searls <Rebecca.Searls_at_Sun.COM>
> To: dev_at_woodstock.dev.java.net, users_at_woodstock.dev.java.net
> Date: Wed, 04 Jun 2008 13:46:26 -0400
> Subject: converting jsf tab to woodstock tab
> I need to convert existing jsf tabs in an app to woodstock tabs.
> Please advise how to do this? There the typical code I have.
>
> <td valign="bottom"><!-- backends Tab -->
> <table class="passiveTabRight_primary" cellpadding="0" cellspacing="0">
> <tr>
> <td>
> <h:commandLink action="backends">
> <h:outputText
> value="#{adminResource['global.backendsTab']}"/>
> </h:commandLink>
> </td>
> </tr>
> </table>
> </td>
>
>
> ---------- Forwarded message ----------
> From: Venkatesh Babu <Venkatesh.M_at_Sun.COM>
> To: users_at_woodstock.dev.java.net
> Date: Thu, 05 Jun 2008 00:21:18 +0530
> Subject: Re: converting jsf tab to woodstock tab
> You can take a look at the tabset example at:
> http://webdev2.sun.com/example/faces/index.jsp
> It has the example source too.. You can assign the action of the
> commandLink to the actionExpression attribute and the
> value of the outputText to the text attribute of the webuijsf:tabSet
> component.
>
> -Venky
> Rebecca Searls wrote:
>
>> I need to convert existing jsf tabs in an app to woodstock tabs.
>> Please advise how to do this? There the typical code I have.
>>
>> <td valign="bottom"><!-- backends Tab -->
>> <table class="passiveTabRight_primary" cellpadding="0" cellspacing="0">
>> <tr>
>> <td>
>> <h:commandLink action="backends">
>> <h:outputText
>> value="#{adminResource['global.backendsTab']}"/>
>> </h:commandLink>
>> </td>
>> </tr>
>> </table>
>> </td>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>
>>
>
>
--
Tim Davenport
tim.g.davenport_at_gmail.com