From: Alex B. <en...@tu...> - 2001-09-10 18:56:40
|
>> I think you'd probably just want to have a flag in the form Definition that >> says "Do JS validation on this one with some stock function" >> >> I'm sure that would be pretty easy to do. > > > I noticed the event flags in the entityDefs (onChange, onBlur, etc). It uh... where? There aren't any Onchange/onblur/ etc flags in entity defs. There may be in UI control definitions. I wanted to associate default UI Controls with each entity field for convenience, but that's the only place On(x) would ever go. > looks like the facility to add client-side validation (minimal) is > pretty much in place. Perhaps this is something that can be messed with > in the future. Yes, pretty much. We can probably do UI Controls for the JS validation pieces or something, such that formBuilder just assembles the outpt from UIControlBuilder. > On another note, I think it's a great idea to expand the TODO/TASKS > list. I'm _very_ eager to help with this project, but so much is going > on all over the place, I haven't found myself comfortable enough > anywhere to begin. An isolated task list with any/all pertinent > information would be most helpful. I'm sure I'm not the only developer > reading this list that feels this way. Yeah, I had that feeling. I've done a portion of the task defs, and will continue to work through them. I'll let everyone know when I'm done. At this point, the tasks can be divided up into two camps: make and EntityManager. I'm much more concerned with EntityManager at the moment, because we can always return to Make and construct new and cool things: but the system isn't complete until that stuff is up and working. After the Make and EM tasks are done, we can get into builders, and the system will be pretty near done. Most of the Builder code already exists, also. :) > SO EVERYONE WAKE UP AND START ASKING QUESTIONS. =] heh _a |