In order to accommodate 3rd party rendering libraries (Ajax, Dojo, etc) in the
screen widgets, we need to discuss how that support will appear in the screen
widget XML files.
I'll start things off with a suggestion I made in another thread. Everyone is
welcome to join in and offer their ideas. When we reach an agreement, we can
submit the results to Jira and begin building it out.
I was thinking we could simply extend the existing widgets with additional
attributes. The new attributes would pass 3rd party specific data to the
rendering classes. The new attributes are ignored by rendering classes that
don't need them. All rendering classes render all widgets in some form - some
rendering classes might have additional bells and whistles based upon the
additional attributes, while others downgrade gracefully and still provide a
usable screen rendering.
So, the widget XML would look something like this:
<container id="some-id" style="some-style" dojo="some Dojo data" ajax="some
Ajax data" foo="some foo data">
...
</container>
The additional attributes could be applied to any screen widget element, not
just the container element.
The advantage I see to this approach is it is fully backwards compatible. We
can add attributes to any screen widget element without breaking existing
rendering code.
That's it. Like I said, please add your ideas.
-Adrian
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.
