The Milyn Project has released Smooks v0.4. Smooks is described as "an extendable Component Framework for performing content manipulations (transformations) in a browser-aware manner."

Smooks can be used to inject discrete pieces of content that are specially formatted. Smooks is built on top of Tinak, a Java component that performs browser recognition on the server. Tinak is a tag libraries that recognize different browsers thus allowing developers to include or exclude content on that basis.
 
Using Smooks means that one can build server-side solutions to:
- Inter-browser incompatibilities.
- Mobilize web content making it accessible on mobile browsers.

Does the need for this type of framework indicate that we need more standardization work on the side of the browser or would standardization stifle innovation?

The Milyn Project has released Smooks v0.4. Smooks is described as "an extendable Component Framework for performing content manipulations (transformations) in a browser-aware manner."

Erm... what does this mean? It sounds like the marketroids were having a bit too much fun with the BS generator. Can someone please explain or update this write up?

Cheers,

E

The Milyn Project has released Smooks v0.4. Smooks is described as "an extendable Component Framework for performing content manipulations (transformations) in a browser-aware manner."

Erm... what does this mean? It sounds like the marketroids were having a bit too much fun with the BS generator. Can someone please explain or update this write up?Cheers,E

Point taken! I'd love if someone could help word this better.

I'd hope from the samples on codehaus more clearly illustrate what it's about.

Basically, the framework allows you to write discrete pieces of transformation logic and target them at specific markup elements on specific browser(s), or profile(s) of browser. What can might this be useful for? Fixing some of the browser incompatibility bugs...

Again, see codehaus.