I believe the manner in which that the warning will be shown, and the way it looks should be part of the theme. But the onblur actions, and the verify function should be part of the aspect, as they don't do anything visual whatsoever.
Right now the only way I have found to add a js action to a component is to write a .js file that looks for a component with the proper id when a page loads and adds the action in js. And subsequently adding that file as a parameter to every "IncludePageMeta"-transformer in every theme's sitemap.
I guess another way could be to write a XSL file and use XPath to look for the right component and add the action and then add that XSL-Transformer in every theme's sitemap somewhere after dri2xhtml.xsl.
The problem with both these solutions is that they have to be done at the theme level, and therefore the functionality of the aspect doesn't fit in one neat package, which was the beauty of manakin in the first place.
Would it be possible to have an addAction("onblur/onclick/onfocus/...", "someJsFunction();") method in java for DRI components, or maybe even an addAttribute("anyAttribute", "anyValue") method, or are there fundamental objections to this concept?
(I apologize if this message got on the mailing list twice, I sent it using an email adress that was not subscribed to this list the first time)
Check out the new SourceForge.net Marketplace.
just about anything Open Source.