I've already stated my appreciation for what the plugin will do(and does so far) in the original announcement thread. I also offered money for it once usable. I have a client project which would have been made more pleasant by this. As it stands, though, I'm having to look at the Prototype alternative. Besides knowing near-nothing about Prototype, I just prefer the way jQuery works.
The bright red text at the top of the page itself points out the major issue: Severe lack of browser testing. That, coupled with suggesting that people start using it in favor of a stable, tested alternative while misrepresenting that alternative's use(Thickbox is /not/ just for images) is yes, a joke. The issue here isn't me saying this is crap. I'm not, and it's not; I'm rather amazed. But the plugin is not ready for public use, eg: replacing Thickbox. Do you actually think the original message's suggestion is a valid consideration? I'm perfectly willing to offer what I can in the way of testing and markup, once some goals are stated. The scripting itself is probably already well beyond my abilities. If I've been late in providing notes, well, sorry, I have clients and can probably devote even less time to this than Gilles himself, but here we go: The plugin's first and third examples fail to launch(with errors) in my copies of both IE6 and IE7. The second does launch, but the text is unselectable. I doubt many people will find that acceptable. IE5.5(why not, since browser goals aren't stated), produces identical behavior, though the button rollovers are a little off. The examples fail altogether in Safari 2.0.4. Unacceptable. While the comments about table use are arguably valid, they're largely unimportant compared to the simple fact that the plugin just plain doesn't work in too many cases. It does seem a bit slow. I suppose it remains to be seen whether this is just something that has to be dealt with, or if the code is unoptimized given it's so early in development. Why can the links not fall back to something if JS is turned off? Is that actually a requirement(which would be unfortunate), or just something that hasn't been accounted for(yet)? On 11/25/06, Rey Bango <[EMAIL PROTECTED]> wrote:
Su, if you're going to make a comment like that, at least have the courtesy to: 1) Cite the reasons that you feel his work isn't ready 2) Offer up solutions or examples that could help him out in improving his work Gilles is trying to provide functionality which really isn't available to the jQuery community and it would be better if everyone provided some sensible guidance instead of simply stating criticisms. Lets be helpful here guys. Rey... Su wrote: > On 11/25/06, *Webunity | Gilles van den Hoven* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > And use my window plugin :) > > > I realize there's a smiley on the end, but this really /is/ a joke, > right? Your plugin frankly isn't anywhere near ready for public use, as > much as I wish it were. > > > ------------------------------------------------------------------------ > > _______________________________________________ > jQuery mailing list > [email protected] > http://jquery.com/discuss/ _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
_______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
