No, the try/catch just became habit after the past couple of projects that had scopes changed ever two days and in turn, was causing issues, so I put the try catch in there and using I put $.iLogger.log instead of alert()
Good call on the chainability, will make that so. On 7/30/07, Klaus Hartl <[EMAIL PROTECTED]> wrote: > > > Benjamin Sterling wrote: > > I wanted to announce my first plug-in called jqShuffle. It is in alpha > > right now, because I know there a better ways of doing some of the stuff > > I want to do. > > > > The url for script and some very basic demos: > > http://www.benjaminsterling.com/experiments/jqShuffle/ > > > > Currently tested in IE6, IE7, FF2 (mac and pc). > > > > Any and all feedback welcomed. > > > > Tips on making the code better will be greatly appreciated. > > > Benjamin, wow, that looks impressive. I haven't seen such an effect yet. > > I noticed one little thing while quickly scanning the code: the plugin > function doesn't return anything. I think it is reasonable to maintain > chainability. > > You could add "return this;" after the end of the try/catch block (is > that really required by the way?). > > Great work! > > > --Klaus > -- Benjamin Sterling http://www.KenzoMedia.com http://www.KenzoHosting.com
