HTML parser was[Re: HTML5: data-* atrributes]

[Bob Schellink <sa...@gmail.com>]

I've changed the subject as I don't think this is related to data attributes.

It sounds as what you are after is an HTML parser that is smart enough to add the model data based
on the server-side component ID.

So is the use case to separate the designer from the developer? I think a developer is very
fortunate if there is a dedicated designer for every page of the project. In my experience designers
tend to be involved right in the beginning to design the site after which the developers take over.
So forcing one to develop the markup for every page would mean a lot of duplication of effort,
especially if the develop is alone in maintaining the application. Contrast that with:

$table

which renders all the markup.

You also mention dynamic updating, but that sounded like Ajax?

Btw, if I recall this is the way Wicket[1] works so there might already be an Apache project that
provides what you are after.

Kind regards

Bob

[1]: http://wicket.apache.org/

On 1/10/2010 02:45, florin.g wrote:
> 
> Bob,
> 
> Keep an open mind for a second. 
> 
> How about if we don't use velocity?
> 
> Here's what I'd do, but I don't have the time (sometime I believe the
> brains) to implement such a thing:
> 
> Use the html element ID to identify the mapped java object on the server.
> Process as needed - if text bound to server data (such as a first name of a
> person), the client side would be a  tag; if the element is a structural
> element (table row, selection option) then the server side would do the
> looping. 
> 
> Example 1:
> 
> <p>Dear , we announce a great party this weekend ().</p> 
> 
> The example above will eliminate the use of velocity on the client side:
> #firstName.
> 
> Example 2:
> 
> <table id="invitationsList">
>    <tr id="listItem">
>         <td class="some-class" id="firstName></td>
>         <td id="lastName" class="another-class"></td>
>         <td>Name tag color: </td>
> </tr></table>
> 
> Now, the serverside will know that this a collection and will deal
> accordingly. 
> 
> Why not? To me it is like a dream come true. Whenever I see php or jsp in an
> html page, ah. Would this not eliminate velocity completely? Not only so,
> but you will eliminate the building of any html on the serverside too. Page
> designers will have full control over the page. The use of page fragments
> will facilitate reusable components.
> 
> Do I make any sense?
> 
>