Announcing the jQuery Plugin Registry • Hacker News Board

Re: Announcing the jQuery Plugin Registry

#21

Post by k3n » Thu, Jan 17, 2013, 4:18 PM UTC

stagas wrote: post #13

Another registry for Javascript files and another json package description. This is getting ridiculous, you guys (npm, component, bower, volo, ender, jam and now plugins.jquery) should get together and fix this mess.

Would any of the CommonJS[1] "packages" specs be a good fit for them, or are they all too disparate? Is that even a concern of CommonJS?

It seems like JS could use some sort of working group to address these types of issues, such as PHP with the FIG[2] (Framework Interoperability Group); not sure if CommonJS is it, or could be...

1. http://www.commonjs.org/

2. http://www.php-fig.org/

Re: Announcing the jQuery Plugin Registry

#22

Post by edwinnathaniel » Thu, Jan 17, 2013, 4:21 PM UTC

stagas wrote: post #13

Another registry for Javascript files and another json package description. This is getting ridiculous, you guys (npm, component, bower, volo, ender, jam and now plugins.jquery) should get together and fix this mess.

Sometimes it takes a while to herd wild cats.

I hope there will be less arguments of "...but standards are bad..." this time around.

JS community is maturing to the point where they do need to stop reinventing the wheel.

Occasionally there are developers who just love to write more code and churn stuffs out cuz you know.. that's what rockstars do :) (and make a name for themselves).

Re: Announcing the jQuery Plugin Registry

#23

Post by fourstar » Thu, Jan 17, 2013, 4:27 PM UTC

mk3 wrote: post #10

What I hate, that most of the jQuery plugins have a huge lack of documentation. You select plugin and then spend next day trying to figure out how it's working. It's almost the same as dowloading random js file form random website and trying to use it. Looked through currently available repos, and half of them lack even simple plugin usage cases in repositories :)

If you keep using plugins, you're probably going to want to understand how they work since you can't always rely on the person developing them. That said, I'm STOKED that this is finally back!

Re: Announcing the jQuery Plugin Registry

#24

Post by bti » Thu, Jan 17, 2013, 4:50 PM UTC

fourstar wrote: post #23

mk3 wrote: post #10

What I hate, that most of the jQuery plugins have a huge lack of documentation. You select plugin and then spend next day trying to figure out how it's working. It's almost the same as dowloading random js file form random website and trying to use it. Looked through currently available repos, and half of them lack even simple plugin usage cases in repositories :)

If you keep using plugins, you're probably going to want to understand how they work since you can't always rely on the person developing them. That said, I'm STOKED that this is finally back!

It's the selection process that is annoying. I want to see the plugin working on a simple demo page, especially if it is doing something visual.

Re: Announcing the jQuery Plugin Registry

#25

Post by hunvreus » Thu, Jan 17, 2013, 5:01 PM UTC

mk3 wrote: post #10

What I hate, that most of the jQuery plugins have a huge lack of documentation. You select plugin and then spend next day trying to figure out how it's working. It's almost the same as dowloading random js file form random website and trying to use it. Looked through currently available repos, and half of them lack even simple plugin usage cases in repositories :)

That's why I like the component (http://github.com/component/component) approach; keeping things to such a minimum feature wise that you can understand very easily what each component does.

I love jQuery, but modules tend to be overdoing it on the configuration/options side. Keep things lean and orchestrate.

Re: Announcing the jQuery Plugin Registry

#26

Post by jbrooksuk » Thu, Jan 17, 2013, 5:11 PM UTC

I'm having issues getting my plugins to display, even after adding the service hook, creating the package file and tagging it, it's been hours and yet nothing.

Re: Announcing the jQuery Plugin Registry

#27

Post by jeresig » Thu, Jan 17, 2013, 5:15 PM UTC

jbrooksuk wrote: post #26

I'm having issues getting my plugins to display, even after adding the service hook, creating the package file and tagging it, it's been hours and yet nothing.

I had a similar issue so I posted a question in the #jquery-content IRC channel. They're looking in to it and recommended that I press the "Test Hook" button from the Webhook panel to get it to go through - and that worked. It sounds like the tags aren't being detected for some reason.

Re: Announcing the jQuery Plugin Registry

#28

Post by kevinSuttle » Thu, Jan 17, 2013, 5:17 PM UTC

Hold on. jQuery has been around for 7 years, and this is just now being put up? Did I miss something?

Re: Announcing the jQuery Plugin Registry

#29

Post by kevinSuttle » Thu, Jan 17, 2013, 5:18 PM UTC

stagas wrote: post #13

Another registry for Javascript files and another json package description. This is getting ridiculous, you guys (npm, component, bower, volo, ender, jam and now plugins.jquery) should get together and fix this mess.

I like what the Ruby community did with RVM and RBenv. https://gist.github.com/1912050

Re: Announcing the jQuery Plugin Registry

#30

Post by xymostech » Thu, Jan 17, 2013, 5:45 PM UTC

kevinSuttle wrote: post #28

Hold on. jQuery has been around for 7 years, and this is just now being put up? Did I miss something?

I'm pretty sure it used to exist, and then got taken down because it had too much crap on it. Looks like they've redesigned it, and are hoping that they'll get less crap this time around.