Here is the code I am using and the resulting markup. I am using JSF 1.2 impl
in glassfish and this might be the problem, but I think it is the render
class for the datalist. I have placed elipses(...) for irrelevent stuff.
<h:panelGroup layout="block" id="unranked">
<f:verbatim><ul class="sortablelist" id="unranked"
style="..."></f:verbatim>
<t:dataList var="player"
value="#{profile.leaguePlayers}"
layout="simple">
<h:outputText value="<li class='green'
id='playerId_#{player.id}'>#{player.summaryName}</li>" escape="false"/>
</t:dataList>
<f:verbatim></ul></f:verbatim>
</h:panelGroup>
The markup is this:
<div id="midview:content:unranked">
<ul class="sortablelist" id="unranked" style="...">
<span id="midview:content:test1">
<li class='green' id='playerId_57'>Tooth Fairy</li>
<li class='green' id='playerId_57'>Boogie Man</li>
<li class='green' id='playerId_57'>Big Foot</li>
...
...
...
</span></ul></div>
By the way, I want to apologize for making an tasteless remark about having
to spend extra effort on fixing the implementation. I understand that some,
if not most, of the work is done by volunteers and I shouldn't exclude
myself from this pool of people. I appreciate all open source that I can
leverage to get my work done and it probably is about time I contribute a
little.
I have a question about html rendering kits and W3C specifications. The html
rendering kits I have looked at don't mention the specification of the W3C
they are rendering to and this may be problematic in the future. I imagine
the implementations we see today render 4.01, but what keeps the components
synchronized with the spec when the spec hypothethically evolves. This seems
like it will create lots of maintenance work, but it would be helpful in the
JSF rendering kits to keep track of what level of spec the kit is rendering
for. For instance, if I am doing in house development, I may archive a
browser at the 4.01 spec and then I can keep using an older html rendering
kit as I can control the environment. But when the 5.0 spec comes out, there
will probably be fundamental changes and browsers will accommodate this.
Browsers may not remain interpretting 4.01 and instead only render 5.0. I
can see this as problematic, especially if a developer is using a 4.01
rendering kit with browsers that support 5.0 specification. Of course, this
argument is completely hypothetical as I have no knowledge of a W3C 5.0 HTML
specification.
Related to the above paragraph, if I was to make modifications to the
rendering portion of the datalist, I imagine it should be to 4.01
specifications. Is this a correct presumption on my part? This will be my
first time working on a component, so hopefully this doesn't turn into a
case of biting off more than I can chew.
Thank you for all your help and attentiveness,
Danimal
Mike Kienenberger wrote:
>
> On 8/21/06, Danimal <[EMAIL PROTECTED]> wrote:
>> Well, I tried the simple datalist and the problem is that it renders a
>> span
>> tag around the output.
>
> Does it? What's your page code look like? Most "non-rendering"
> components won't render anything unless they're forced to by you
> putting in a style class or an explicit id value.
>
>
>> This is unnecessary and it breaks what I am trying to
>> do. Is there a way to do away with the span tag? I am thinking about just
>> downloading the source and making the slight modification to make the
>> datalist more robust. However, I am leary of taking this route as it is
>> going to require extra effort on my part.
>
> If you fix a bug or improve something, contribute a patch of the
> change and we'll add it to MyFaces.
>
>
>> PS: I apologize to the list for responding to this thread earlier with
>> just
>> a thank you. I just read the etiquette tips above in red.
>
> Not sure what tips those are, but I'd disagree with them -- it's
> certainly helpful to response to a thread stating that a solution
> worked so the next person reading the thread knows there's a solution.
>
>
--
View this message in context:
http://www.nabble.com/Tomahawk-DataList-tf2138090.html#a5910568
Sent from the MyFaces - Users forum at Nabble.com.