1 Jun 2010 10:17 PM #11
I added a listener in the new version for when a user presses enter while the field is focused (in-case the user manually mods the date). Not sure about the validation end of it, I don't have much experience with that.
1 Jun 2010 10:24 PM #12
Kryo, last question when you planned release new version?
1 Jun 2010 10:25 PM #13
Doing a quick package as we "speak"
1 Jun 2010 11:14 PM #14
0.2a should be completely compatible with 0.1a, but I am thinking about putting together a completely new element for date range selection which would include a few techniques i've picked up since I first wrote this.
1 Jun 2010 11:30 PM #15
Kryo, thank you for your support! all my problems with the choice of dates is now solved
3 Jun 2010 7:58 AM #16
Looks great. I am trying to shoehorn this into an existing app but having problems with the date formatting. Does this ux support the config parameter 'format'?
Right now the value being presented by your ux is 'Thu May 27 00:00:00 EDT 2010' however I would like it to present in MM/DD/YYYY format.
Thanks for a nice user-friendly addition to the ux library. Kudos!
3 Jun 2010 11:14 AM #17
Description: Sets the format that the dates should be formatted.
7 Jun 2010 8:17 AM #18
Just so you know, it doesn't work with 3.0.0. I know you haven't tested it with that, but it might save someone the time it took me to figure it out.
Great extension though
7 Jun 2010 8:19 AM #19
Hi Emily, question, when you say it doesn't work, what was the problem you were having? If it's something simple, I could patch it so it would be compatible for ExtJs 3.*.
9 Jun 2010 8:58 AM #20
OK I have no idea what happened to my first response about this but it got lost somehow!
The error I got was 'this.cells is undefined' from in one of the standard extjs libraries in the update method of the DatePicker class (can't remember line number or which file!). I believe this error came up in a previous post when someone tried it with one of the 2.x versions. I didn't spend a lot of time debugging it (just tried up to date version of extjs instead), but the bit of DateRange that it didn't like was the switch case on line 241. What happened on a UI level was that the first time you clicked on the trigger the error above would get thrown and no menu would get rendered. If you clicked the trigger again (without reloading) the menu would appear and all work except that the dateRange / Custom Date Range preset option wouldn't appear.
If you want me to have another poke around let me know. I like the extension, and I don't mind contributing if I can spare the time.