Re: Clay challange
On 2/14/07, Gary VanMatre [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED]
Hi
Thanks, Ryan. This is what you get when you copy/paste and then go blind :) (I
need to sit down and repeat to my self: DO NOT DO THIS! a thousand times)
You are not alone there. Hey Ryan, what's the status of that Eclipse 3.2 plug
in that you are trying to get IBM to donate?
The donation is coming along. I need to submit a couple of documents
to ibm and then a review will be held on it. Sorry for the wait, it
has been mostly due to my busyness and somewhat the tedious process
ibm has in place.
For those of you that don't know I was planning to donate an eclipse
plugin with a gui and drag n drop for building clay config files. It
dynamically finds all the clay config defs in your project and builds
a component palette. When you create new component defs they get
added to the palette. So it's all about reusablilty.
Hermod
Gary
-Original Message-
From: Ryan Wynn [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 13, 2007 11:23 PM
To: user@shale.apache.org; [EMAIL PROTECTED]
Subject: Re: Clay challange
On 2/13/07, Hermod Opstvedt wrote:
Hi
I'm struggling with a component that I have defined:
value=#{messages['navnpanel.text']}
value=#{messages['navnpanel.text']}
It is supposed to render a fieldset with a legend, and a label inside it.
However the label never appears and there are no errors what so ever.
I think you might need to look at your renderIds. The renderId
attribute is a way of ordering component children. RenderIds are only
relevant for sibling elements. If you have 2 sibling elements with
the same renderId value then one of the elements will be
lost/replaced.
In your case the t:htmlTag and outputLabel both have the same parent
(t:htmlTag) but they also use the same renderId (2). They should
instead be 1 and 2.
My renderIds usually start at 1 for each element set and increment
from there. I think only the relative values matter, so you could
have renderIds 6 and 3 and you would still get 2 children with the 3
renderId as the first child.
With inheritance you are able to override a component's children
selectively by specifying another component with the same renderId.
...
...
..
both c1 and c2 produce a clay component with 2 children. c2 uses
inheritance and the renderId attribute to override the second
outputText in c1 with an inputText. But, c2 still inherits the first
outputText child from c1.
Hope this helps.
Hermod
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that DnB NOR cannot
accept any payment orders or other legally binding correspondence with
customers as a part of an email.
This email message has been virus checked by the anti virus programs used
in the DnB NOR Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
RE: Clay challange
From: [EMAIL PROTECTED]
Hi
Thanks, Ryan. This is what you get when you copy/paste and then go blind :)
(I
need to sit down and repeat to my self: DO NOT DO THIS! a thousand times)
You are not alone there. Hey Ryan, what's the status of that Eclipse 3.2 plug
in that you are trying to get IBM to donate?
Hermod
Gary
-Original Message-
From: Ryan Wynn [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 13, 2007 11:23 PM
To: user@shale.apache.org; [EMAIL PROTECTED]
Subject: Re: Clay challange
On 2/13/07, Hermod Opstvedt wrote:
Hi
I'm struggling with a component that I have defined:
value=#{messages['navnpanel.text']}
value=#{messages['navnpanel.text']}
It is supposed to render a fieldset with a legend, and a label inside it.
However the label never appears and there are no errors what so ever.
I think you might need to look at your renderIds. The renderId
attribute is a way of ordering component children. RenderIds are only
relevant for sibling elements. If you have 2 sibling elements with
the same renderId value then one of the elements will be
lost/replaced.
In your case the t:htmlTag and outputLabel both have the same parent
(t:htmlTag) but they also use the same renderId (2). They should
instead be 1 and 2.
My renderIds usually start at 1 for each element set and increment
from there. I think only the relative values matter, so you could
have renderIds 6 and 3 and you would still get 2 children with the 3
renderId as the first child.
With inheritance you are able to override a component's children
selectively by specifying another component with the same renderId.
...
...
..
both c1 and c2 produce a clay component with 2 children. c2 uses
inheritance and the renderId attribute to override the second
outputText in c1 with an inputText. But, c2 still inherits the first
outputText child from c1.
Hope this helps.
Hermod
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that DnB NOR cannot
accept any payment orders or other legally binding correspondence with
customers as a part of an email.
This email message has been virus checked by the anti virus programs used
in the DnB NOR Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Re: Clay challange
On 2/13/07, Hermod Opstvedt [EMAIL PROTECTED] wrote:
Hi
I'm struggling with a component that I have defined:
component jsfid=navnpanel extends=clay id=navnpanel
element jsfid=t:htmlTag renderId=1
attributes
set name=value value=fieldset /
/attributes
element jsfid=t:htmlTag renderId=2
attributes
set name=value value=legend /
/attributes
element jsfid=outputText renderId=2
attributes
set name=value
value=#{messages['navnpanel.text']}
/set
/attributes
/element
/element
element jsfid=outputLabel renderId=2
attributes
set name=value
value=#{messages['navnpanel.text']}/set
/attributes
/element
/element
/component
It is supposed to render a fieldset with a legend, and a label inside it.
However the label never appears and there are no errors what so ever.
I think you might need to look at your renderIds. The renderId
attribute is a way of ordering component children. RenderIds are only
relevant for sibling elements. If you have 2 sibling elements with
the same renderId value then one of the elements will be
lost/replaced.
In your case the t:htmlTag and outputLabel both have the same parent
(t:htmlTag) but they also use the same renderId (2). They should
instead be 1 and 2.
My renderIds usually start at 1 for each element set and increment
from there. I think only the relative values matter, so you could
have renderIds 6 and 3 and you would still get 2 children with the 3
renderId as the first child.
With inheritance you are able to override a component's children
selectively by specifying another component with the same renderId.
component jsfid=c1 extends=clay
element jsfid=outputText renderId=1.../element
element jsfid=outputText renderId=2.../element
/component
component jsfid=c2 extends=c1
element jsfid=inputText renderId=2../element
/component
both c1 and c2 produce a clay component with 2 children. c2 uses
inheritance and the renderId attribute to override the second
outputText in c1 with an inputText. But, c2 still inherits the first
outputText child from c1.
Hope this helps.
Hermod
RE: Clay challange
Hi
Thanks, Ryan. This is what you get when you copy/paste and then go blind :) (I
need to sit down and repeat to my self: DO NOT DO THIS! a thousand times)
Hermod
-Original Message-
From: Ryan Wynn [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 13, 2007 11:23 PM
To: user@shale.apache.org; [EMAIL PROTECTED]
Subject: Re: Clay challange
On 2/13/07, Hermod Opstvedt [EMAIL PROTECTED] wrote:
Hi
I'm struggling with a component that I have defined:
component jsfid=navnpanel extends=clay id=navnpanel
element jsfid=t:htmlTag renderId=1
attributes
set name=value value=fieldset /
/attributes
element jsfid=t:htmlTag renderId=2
attributes
set name=value value=legend /
/attributes
element jsfid=outputText renderId=2
attributes
set name=value
value=#{messages['navnpanel.text']}
/set
/attributes
/element
/element
element jsfid=outputLabel renderId=2
attributes
set name=value
value=#{messages['navnpanel.text']}/set
/attributes
/element
/element
/component
It is supposed to render a fieldset with a legend, and a label inside it.
However the label never appears and there are no errors what so ever.
I think you might need to look at your renderIds. The renderId
attribute is a way of ordering component children. RenderIds are only
relevant for sibling elements. If you have 2 sibling elements with
the same renderId value then one of the elements will be
lost/replaced.
In your case the t:htmlTag and outputLabel both have the same parent
(t:htmlTag) but they also use the same renderId (2). They should
instead be 1 and 2.
My renderIds usually start at 1 for each element set and increment
from there. I think only the relative values matter, so you could
have renderIds 6 and 3 and you would still get 2 children with the 3
renderId as the first child.
With inheritance you are able to override a component's children
selectively by specifying another component with the same renderId.
component jsfid=c1 extends=clay
element jsfid=outputText renderId=1.../element
element jsfid=outputText renderId=2.../element
/component
component jsfid=c2 extends=c1
element jsfid=inputText renderId=2../element
/component
both c1 and c2 produce a clay component with 2 children. c2 uses
inheritance and the renderId attribute to override the second
outputText in c1 with an inputText. But, c2 still inherits the first
outputText child from c1.
Hope this helps.
Hermod
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that DnB NOR cannot
accept any payment orders or other legally binding correspondence with
customers as a part of an email.
This email message has been virus checked by the anti virus programs used
in the DnB NOR Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Tutorial....Re: Clay challange
Hi,
Where can i best tutorial from Shale
You may even send me tons of links . More interested in architecture.
Wondering if Shale can use used as Half-object pattern. Part of shale run
on client machine, Part of shale runs on server- Reason is integration with
Web 2.0 technologies
Thanks in advance.
Chand
- Original Message -
From: [EMAIL PROTECTED]
To: user@shale.apache.org
Sent: Tuesday, February 13, 2007 10:44 PM
Subject: RE: Clay challange
Hi
Thanks, Ryan. This is what you get when you copy/paste and then go blind
:) (I need to sit down and repeat to my self: DO NOT DO THIS! a thousand
times)
Hermod
-Original Message-
From: Ryan Wynn [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 13, 2007 11:23 PM
To: user@shale.apache.org; [EMAIL PROTECTED]
Subject: Re: Clay challange
On 2/13/07, Hermod Opstvedt [EMAIL PROTECTED] wrote:
Hi
I'm struggling with a component that I have defined:
component jsfid=navnpanel extends=clay id=navnpanel
element jsfid=t:htmlTag renderId=1
attributes
set name=value value=fieldset /
/attributes
element jsfid=t:htmlTag renderId=2
attributes
set name=value value=legend
/
/attributes
element jsfid=outputText renderId=2
attributes
set name=value
value=#{messages['navnpanel.text']}
/set
/attributes
/element
/element
element jsfid=outputLabel renderId=2
attributes
set name=value
value=#{messages['navnpanel.text']}/set
/attributes
/element
/element
/component
It is supposed to render a fieldset with a legend, and a label inside it.
However the label never appears and there are no errors what so ever.
I think you might need to look at your renderIds. The renderId
attribute is a way of ordering component children. RenderIds are only
relevant for sibling elements. If you have 2 sibling elements with
the same renderId value then one of the elements will be
lost/replaced.
In your case the t:htmlTag and outputLabel both have the same parent
(t:htmlTag) but they also use the same renderId (2). They should
instead be 1 and 2.
My renderIds usually start at 1 for each element set and increment
from there. I think only the relative values matter, so you could
have renderIds 6 and 3 and you would still get 2 children with the 3
renderId as the first child.
With inheritance you are able to override a component's children
selectively by specifying another component with the same renderId.
component jsfid=c1 extends=clay
element jsfid=outputText renderId=1.../element
element jsfid=outputText renderId=2.../element
/component
component jsfid=c2 extends=c1
element jsfid=inputText renderId=2../element
/component
both c1 and c2 produce a clay component with 2 children. c2 uses
inheritance and the renderId attribute to override the second
outputText in c1 with an inputText. But, c2 still inherits the first
outputText child from c1.
Hope this helps.
Hermod
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that DnB NOR cannot
accept any payment orders or other legally binding correspondence with
customers as a part of an email.
This email message has been virus checked by the anti virus programs used
in the DnB NOR Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
