David G. Friedman wrote:
Should MyFaces start a new taglib section for visual effects with use a
taglib prefix of "e:" (or "d" for "dhtml effects")? That way, the base tags
stay simple, the extensions extend tag functionality while remaining simple
yet functional, the visual effects become optional whiz-bang web browser
features, and any ajax-communicating components fill in a 4th library for
those interested in components of that nature.
Any opinions on this proposal?
Regards,
David
Just forgot, you cannot make a clear distinction between ajax and effects.
The main problem is following. If you want for instance to have
an effect, which is turned off by a user action for a session, you now
suddenly have an effect which needs ajax.
I want to give an example.
You have a squish or puffed field with a message, you give the user the
option to puff it away for login time.
What happens is, that you puff the component away, which is a clear
effect, but you also trigger an ajax server side event, which stores
the this component is cleard for the session state somewhere in the
users session, now once the user hits the page again, the renderer of
the puff checks if it is puffed away for session from the user, and
omits the rendering of itself and its subcomponents, if this is the case.
So where do you want to categorize it, is it now just the special
effects group, or the ajax group of things?
The other thing is, that I have not seen one single effect or ajax
component, which really needs javascript enabled.
The autocomplete for instance could theoretically be turned into
a simple text field without any server side stuff.
Puff, Whatever ... is basically rendered into a harmless div, once you
dont want javascript (the hooks are not in there yet, though)
The only component I could think of which would enforce pure javascript
could be some kind of progress bar...
The lines are rather blurry on how you categorize things.
