| Comments |
| 9/19/2011 5:43:21 PM |
Bob Denny |
Enough testing, I declare it finshed. |
| 9/16/2011 4:09:53 PM |
Bob Denny |
This was solved in the Scheduler forms for astro-imaging and photometry, no need to modify the validation code. |
| 9/16/2011 3:19:41 PM |
Bob Denny |
Dang, I put collapsible sections into the Scheduler submission forms (SCHEDULER-691) and it appears to inhibit forms validation in that section.
Furthermore, If an invalid field exists in a collapsed section, the right thing to do is to expand the section and pop up the balloon error message. More crosstalk between plugins :-(( |
| 9/13/2011 12:25:48 PM |
Bob Denny |
I have also snuck into this an upgrade to the popup lightbox-type alerts to be self-sizing with limits. So far, I have tghe DC3.Lightbox.showAlert() calls from inside the browser framework working fine (see the LightBoxTest item for a demo).
Now I just found out that the alerts and popups that are from remoted ACP.Util.Console object are also in need to self-sizing, Furthermore, the Yes/No alert is really lame!! It now uses radiobuttons and an "answer" button. This should be with separate Yes and No buttons. Adding more to the time estimate of this task. |
| 9/11/2011 7:03:57 PM |
Bob Denny |
|
| 9/11/2011 4:21:11 PM |
Bob Denny |
|
| 9/11/2011 4:16:43 PM |
Bob Denny |
|
| 9/11/2011 4:13:45 PM |
Bob Denny |
More validation, for date/time. Needed a custom validator which restricts the possible formats to avoid the regional issues with month names and day/month ordering. It will only accept yyyy/mm/dd numeric for the date part. |
| 9/8/2011 8:15:36 AM |
Bob Denny |
|
| 9/2/2011 8:33:42 AM |
Bob Denny |
|
| 9/1/2011 6:05:59 PM |
Bob Denny |
|
| 9/1/2011 11:02:12 AM |
Bob Denny |
|
| 8/31/2011 5:37:57 PM |
Bob Denny |
Well, it's done. The net result was a streamlining of the support for the expando-row forms. See DC3.Lib plugin in the framework and the various forms. |
| 8/31/2011 5:34:45 PM |
Bob Denny |
|
| 8/31/2011 5:32:26 PM |
Bob Denny |
|
| 8/30/2011 9:14:55 PM |
Bob Denny |
|
| 8/30/2011 11:51:04 AM |
Bob Denny |
Lots more coming! This will now include validation logic in the existing ACP web forms all over the place. Increased time estimate. |
| 8/30/2011 9:07:17 AM |
Bob Denny |
|
| 8/30/2011 8:41:33 AM |
Bob Denny |
|
| 8/30/2011 7:32:47 AM |
Bob Denny |
I think I have it completed. Mark this 'testing' while I do the validation on SCHEDULER-691 and the existing ACP forms (will open a separate ACP ticket for that). |
| 8/29/2011 5:42:23 PM |
Bob Denny |
|
| 8/29/2011 5:07:29 PM |
Bob Denny |
|
| 8/29/2011 5:05:28 PM |
Bob Denny |
|
| 8/29/2011 9:01:15 AM |
Bob Denny |
The form hookup with the validator should be in a TW plugin. Doing that now. |
| 8/29/2011 8:59:50 AM |
Bob Denny |
Decided to use the jQuery bValidator plugin. During initial checkout of the 0.54 version, I discovered that he was iterating over arrays with for(x in y), and it was returning the names of the prototype additions to Array (in TiddlyWiki) as i values! I found this article on StackOverflow that explains it all. Bottom line, use counted for loops on arrays. |
