Jorn, Great stuff so far!
I wonder, though, if it would be possible to have settings.rules and settings.messages be organized by element name instead of element ID. If I'm trying export server-side validation rules to your plugin (as JSON and then converted into your settings format by a small wrapper), the server-side validation processor may not know what each element's ID attribute is. I suppose, in my wrapper, I could take all of the element names and find the appropriate IDs, but it seems like it would be easier if settings.rules and settings.messages were organized by element name. On 3/20/07, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
Dan G. Switzer, II schrieb: > For example, for radio & checkbox elements you use the NAME attribute, but > for everything else you use the ID attribute. I just find it confusing to > try to explain the difference (on when you use what.) > Currently I'm internally passing around element IDs. I want to remove that as far as possible, maybe I can reduce the need for IDs, too. There is one good argument for using IDs: You can click the error labels to focus the associated input, without any additional JS, just using the for attribute. -- Jörn Zaefferer http://bassistance.de _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
-- Aaron Heimlich Web Developer [EMAIL PROTECTED] http://aheimlich.freepgs.com
_______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
