[jQuery] Missing semi-colons in form plugin.
FYI: Semi-colons are missing on lines 87 & 605 of the form plugin, thus making it hard to compress/obfuscate.
[jQuery] jQuery + Gears Data Dilemma
Greetings, An application I've been working on is in the process of trying to integrate Gears support into itself. The application is heavily driven by jQuery, UI and an assortment of plugins. The support for gears involves a number of get and set type calls, where data is retrieved and populated in a form or taken from a form and stored some where. We'd like to keep the implementation open enough that down the road we can work HTML5 support and potentially even Adobe AIR support into the app. Right now these particular requests are attached to click() or submit() handlers in jQuery and fire off various AJAX requests. I'm wondering if anyone has come with a good/decent solution to modularizing these types of requests within jQuery-style javascript code and what the pattern they use are. What I am trying to avoid is a click() handler with conditions for each of the various sources, and I also need to be able to turn a source off, plugin a different source and then optionally return back to that first source. Looking forward to feedback from anyone who's faced this predicament already. Pax, - Stan
[jQuery] Re: [treeview] Trigger event...
In my current setup the click() event does get bound first and does return false, the treeview click handler still kicks in. It looks like line 67 handles the action, I wonder if that could be placed under some conditional in a future version? Thinking out loud here... Pax, SL On Aug 21, 4:28 pm, "Jörn Zaefferer" <[EMAIL PROTECTED]> wrote: > Try binding your click-event first, returning false from the function > you add. Apply the treeview afterwards - in theory, the tree shouldn't > do anything after your click function got called. > > Jörn > > On Thu, Aug 21, 2008 at 9:56 PM, Stan Lemon <[EMAIL PROTECTED]> wrote: > > > Jorn, > > Greetings! Love your treeview plugin and I've used it on a number of > > projects. I have a particular project right now where in my > > particular node I have a that has a click function > > attached to it, and when that click function is called I'd like for > > the treeview action not to be called. Ideally, how this would is > > click on the hitarea item would fire off the toggler and anything else > > would produce in no action from the treeview plugin. I'm not seeing > > an easy way of doing this, am I missing something or do you have any > > ideas? > > > Thanks, > > Stan
[jQuery] [treeview] Trigger event...
Jorn, Greetings! Love your treeview plugin and I've used it on a number of projects. I have a particular project right now where in my particular node I have a that has a click function attached to it, and when that click function is called I'd like for the treeview action not to be called. Ideally, how this would is click on the hitarea item would fire off the toggler and anything else would produce in no action from the treeview plugin. I'm not seeing an easy way of doing this, am I missing something or do you have any ideas? Thanks, Stan
[jQuery] Re: New jQuery Plug-in: Multicolumn Dropdown
Dan, Key navigation doesn't work at all - I'm not able to key down or anything. I wonder if the hotkeys plugin for jQuery might be helpful in this front since it normalizes key entry behavior? Just a thought. Thanks again for the stellar plugin. Pax, - Stan On Jun 19, 4:05 pm, "Dan G. Switzer, II" <[EMAIL PROTECTED]> wrote: > Stan, > > > > >Very nice plugin! > > >I second Jorn's thought on the usage of both modes. I found myself > >slightly confused at first when I went into keyboard mode and couldn't > >click on anything. Seems to be an issue too when you click on the > >arrow, the menu is expanded and then you proceed to click on the white > >area that would normally trigger the keyboard mode. > > >I know Safari wasn't in your list of supported browsers, but I did > >notice that the keyboard mode didn't seem to work correctly in Safari > >3.1 on OS X. Safari has a fairly decent user base, especially amongst > >the jQuery crowd and I could see this as advantageous to you to get > >the plugin more circulated. > > >All in all, excellent plugin - I will likely use it on a project of my > >own. > > What about the keyboard functionality isn't working? Is it not working at > all, or just not working correctly? > > Unfortunately capturing keyboard entry is really a PITA. It varies > drastically from browser-to-browser even on the same OS. It certainly does > not surprise me it's not working correctly on Mac Safari. > > Obviously, if you find a fix, please let me know. > > -Dan
[jQuery] Re: New jQuery Plug-in: Multicolumn Dropdown
Very nice plugin! I second Jorn's thought on the usage of both modes. I found myself slightly confused at first when I went into keyboard mode and couldn't click on anything. Seems to be an issue too when you click on the arrow, the menu is expanded and then you proceed to click on the white area that would normally trigger the keyboard mode. I know Safari wasn't in your list of supported browsers, but I did notice that the keyboard mode didn't seem to work correctly in Safari 3.1 on OS X. Safari has a fairly decent user base, especially amongst the jQuery crowd and I could see this as advantageous to you to get the plugin more circulated. All in all, excellent plugin - I will likely use it on a project of my own. Pax, - Stan On Jun 19, 1:59 pm, "Jörn Zaefferer" <[EMAIL PROTECTED]> wrote: > Hey Dan, > > great plugin, the interface is both innovative and familiar, and works > well - as long as I use either mouse or keyboard, but not both. The > inconsistent behaviour was already mentioned by so many others in this > thread, I hope it gives you an idea how to merge both controls into > one. > > If that inconsistency could be removed, the widget would be even greater. > > Regards > Jörn > > On Thu, Jun 19, 2008 at 7:48 PM, Dan G. Switzer, II > > <[EMAIL PROTECTED]> wrote: > > > Graeme, > > >>This plugin looks really cool! > > >>I found a small issue: > > >>If you load the page for the first time (in ff3) and just click on the > >>blank > >>area in the dropdown (instead of the down arrow) there is no animation when > >>it expands down and the hierarchy arrows don't work when you use the mouse. > >>If you then click the down arrow and go down a level or two in the > >>hierarchy > >>and don't select something and go back to clicking on the blank area of the > >>dropdown, the formatting gets messed up (large vertical spacing of the > >>"Entertainment" entry in the demo). > > > 1) If you click inside the text box, you go into "keyboard" entry mode--so > > you're actually seeing the "autocomplete" box, not the dropdown menu. You > > can change the styles in the CSS to make this look however you want (so that > > you can make it look visual different.) Currently, when you're in keyboard > > entry mode you can not use the mouse to select entries. You can disable > > keyboard support by using a element instead of an element > > and then clicking "inside" would always cause the same menu as dropdown > > arrow. > > > 2) The second issue (with the large vertical spacing) seems to be related to > > the Chili plug-in (which is used for syntax highlighting.) The problem seems > > to be random and only occurs when Firebug reports Chili errors (at least > > that's the only time I've seen the behavior.) I've never seen the behavior > > on a page that doesn't have the Chili plug-in. > > > -Dan
[jQuery] Re: Superfish Menu Fade-out
Just to follow up, I've documented my hack here: http://stanlemon.net/index/articles/hiding-a-superfish-menu.html Right now I've not seen any break down in other browsers, even with sub menus. Only issue I've seen is a closing animation to height the hide flickers a bit in IE - adding opacity hiding it fixes the issue, fwiw. Pax, - Stan On Apr 16, 9:42 am, "Joel Birch" <[EMAIL PROTECTED]> wrote: > Hi Reuben, > > Superfish doesn't support closing animations. I tried it a while ago > but experienced too many glitches caused when mousing back over a > submenu that is in the process of closing. There has been some > interest in getting this working recently, so hopefully I'll get to it > some day. > > Stan Lemon recently sent me a patch which attempts to add closing > animations. I'll list it here incase you want to experiment with it, > but I have not tried it at all: > > hideSuperfishUl : function(){ > var o = $.superfish.op, > $ul = $('li.'+o.hoverClass,this).add(this) > .find('>ul').animate(o.animationClose, o.speed, > function() { > $(this).css('visibility','hidden'); > $ul.removeClass(o.hoverClass); > }); > return this; > > }, > > You would also need to add animationClose to the options object. > > Joel Birch.
[jQuery] Re: markItUp! 1.0 (former jTagEditor) is finally released!
Can you clarify what the differences are between this and jTagEditor? Also... have you ever considered making a single image sprint of the buttons? That might save some load-time. Thanks for your work on this plugin, I use it quite a bit and very appreciative for it! Pax, - Stan On Mar 23, 2:48 pm, Jay Salvat <[EMAIL PROTECTED]> wrote: > Hi all! > > I'm proud to announce you the official release of markItUp! (former > jTagEditor) and markItUp! website. > I hope everything will be ok and i forgot nothing important. > > Website:http://markitup.jaysalvat.com/ > > Examples:http://markitup.jaysalvat.com/examples/ > > Feedbacks are welcomed! > > Jay S.
[jQuery] Macro templates for jQuery & UI
Greetings, There has been some conversation on the UI list about templating solutions for jQuery. Ext has a light weight template library which handles basic variable assignment and supporting formatting methods. I finally decided to port the Ext solution to jQuery. I've tried to conform to the UI API in my port. It was suggested that I pass this port onto the general list for feedback and thoughts. My goal here is really to propose the idea. I think UI could benefit from a baaic template library, whether that be this port or a different implementation. Anyhow, take a look at: http://stanlemon.net/files/ui.template.js Thoughts and feedback are much appreciated. Pax, - Stan