Although that looks pretty, in real world i cant see it being very functional. for a time picker it takes up a lot of space and the way the sub time intervals extend beyond the hour intervals makes it difficult to contain it to a specific space.
_____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of nutron Sent: Friday, 14 November 2008 5:12 AM To: [email protected] Subject: Re: Sweet time picker plugin http://ajaxian.com/archives/time-picker-ui On Mon, Oct 13, 2008 at 7:30 PM, Iván N Paz <[EMAIL PROTECTED] <http://n2.nabble.com/user/SendEmail.jtp?type=node&node=1494914&i=0> > wrote: I had such issue with a personal project.... problem which I "solved" by setting a variable "gEscBindsTo" [self-explaining-name ;-)] but that was just my case.. and it was very specific... Would this work for you??? >> http://blog.kassens.net/outerclick-event [hope you don't mind Jan ;-)] About the ESC key, I don't know who gets the event 1st... thats not clear to me, as it seems to be different across browsers, which would pose a problem... If there weren't any inconsistencies, you could attach to the "keydown::ESC", stop event propagation, and then detach after hiding the widget... just some ideas here... not quite sure though (it all dependes on the flow of the event) Another idea I would like to throw... What about surrounding the whole widget on a DIV and attach the mouseleave that would close it? I've seen it working like that on some multi-level drop-downs built using pure CSS, the concept is the same... not sure if that's suitable in this situation.... Cheers, Iván On 10/13/08, SilverTab <[EMAIL PROTECTED] <http://n2.nabble.com/user/SendEmail.jtp?type=node&node=1331491&i=0> > wrote: > > Ivan: true, it definitely could conflict in such a case... but Esc key > event could definitely be optional... right now I'm concentrating my > efforts on the "click outside of the panel", that will cancel and hide > the picker, and revert the text input to its original value... I've > added the Esc key event but it's only a matter of 1 or 2 lines of code > so...as I said, could definitely be an option... you make a valid > point though! worth thinking about! I might just remove it altogether, > still not sure :) > > > > > On Oct 13, 9:50 pm, "Iván N Paz" <[EMAIL PROTECTED] > <http://n2.nabble.com/user/SendEmail.jtp?type=node&node=1331491&i=1> > wrote: > > Hi SilverTab, I've been following your development.... > > > > Just one thing... Do you consider the ESC key would be a viable > solution??? > > > > Take this scenario, for instance... > > > > You have a sort of window that pops-up (a div with content created > > either by means of new Element(...) or XHR-loaded) that would > > create/load a form, and that form uses your date picker... > > > > What if the "pseudo-window" already has ESC key bound to close it??? > > Who would get the event first??? Doesnt this conlict with it??? > > > > Just a doubt.... ;-) > -- ◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦ www.ivanicus.com The MooTools Tutorial: www.mootorial.com CNET Clientside: clientside.cnet.com _____ View this message in context: Re: <http://n2.nabble.com/Sweet-time-picker-plugin-tp1306377p1494914.html> Sweet time picker plugin Sent from the MooTools Users mailing <http://n2.nabble.com/MooTools-Users-f660466.html> list archive at Nabble.com.
