Turkiyenin en sevilen filmlerinin yer aldigi porno internet sitemiz olan ve sex tarzi bir site olan sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir.
Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.
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.
I updated the main thread with the 0.2a version. It was quickly packaged and its kind of late, so if there is any issues, please let me know. I kept both versions in case some one finds a use for the older version.
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.
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.
Yes, configuration supports 'format' parameter, as indicated in the demo.html page. In the demo I am using a fixed format, so you'll need to change the default value format as well:
========== Entry: format Description: Sets the format that the dates should be formatted. Default: Y-m-d
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.