jquery-archive / plugins.jquery.com Goto Github PK

Allow plugins to specify a custom download URL to override the auto-generated GitHub URL.

Maintainers function should be in a list format so it matches the other areas in the sidebar.

Originally we said that users should not include "jquery" in the name of their plugins. However, @jrburke has raised concerns about integration with non-jQuery plugins, especially in the case of an app that's using AMD where jQuery itself is not the sole focus.

We should hash out the details of what's required to make sure that we jQuery plugins will play nicely in all environments.

@jrburke requested that the plugin names match the file names, e.g., "jquery.ui.dialog".

Is it problematic if the plugins use dashes instead of dots, e.g., "jquery-ui-dialog"?

Should we require that names be prefixed with "jquery"? While discussing this with @rdworth, we looked at the scenario of Wijmo, where a name such as "wijmo-wijdialog" should be unique in any system. Should we require "jquery-wijmo-wijdialog" anyway?

What are the actual concerns for something like an AMD loader?

We should show avatars for authors and maintainers.

Hello folks,
after a long chat with some guys of the jQuery-dev irc channel I decided to post on here my doubts about the new jQuery plugins website.
I know all the efforts that you have put redesigning all the new jQuery websites (jQuery UI, jQuery Mobile etc...) but I think that jQuery could do it better.

First let's check some design caveats:

• Homepage: http://gianlucaguarini.com/experiments/jquery-plugins/homepage.jpg
• Short pages: http://gianlucaguarini.com/experiments/jquery-plugins/footer.jpg

Such as design exercise I've made a prototype of the new jQuery plugins website http://www.gianlucaguarini.com/blog/jquery-plugins-website-redesign-proposal/ thinking that it should be clean an easy to use without many cerimonies.
Then one of the jQuery developers suggested to create new lint section on the new site, something like plugins.jquery.com/lint , having just the plugin ajax search on it.

I am not sure if this could be a good push for you to update your website but I am sure that I would expect something more from the jQuery dev team:

• what about an entire ajax navigation?
• you could create a JSON (JSONP) API allowing the other pluigins websites to fetch from your official data (the same API could be used to make your website entirely an ajax app)
• jQuery is going to drop the support for the old browsers right?! so where are the CSS3 transitions?

IMHO Code matters "write less do more" but also design is important and so jQuery payoff could be translated "show less get more"

that's it for now!

Plugin suites will have reserved prefixes. When a standalone plugin is being registered, we must validate that it does not start with an existing suite's prefix. Similarly, when a suite is registered, we must validate that all of its plugins are using the correct prefix.

We need to log all errors for retry and have a cron job that processes the failures. There should probably be a limit to the number of times a failure is retried and escalate to informing the team on continued failure.

We can figure out release dates by looking at the latest commit in a tag. We should set this as the created and modified times in the WordPress database and display it as the release date.

Hi, i have a website that uses hebrew windows-1255 encoding (for various reasons i can't change it to utf-8)
the picasa album names are shown in gibberish because of this.
can this be fixed or controlled in any way ?
thanks

I've added a pagination style to the search results page, just need to get it hooked up to pagination that's actually working. If the HTML it spits out is different just let me know and I'll get the styles fixed.

The "licenses" field described in package.md requires the use of license abbreviations when provided. Linking to or including the full list of valid abbreviations would help package.json maintainers. I assume the abbreviations are the ones used on the OSI licenses list. Since the list would also have to be scraped and mirrored for use in the pre-commit package.json validator, perhaps a link to the list that the validator itself uses would be more appropriate, in case it becomes out of sync with the OSI version.

There was discussion on IRC on #jquery about this.

I re-used the code for the search bar from the navigation area, but the javascript is conflicting because they both have the same ID's I believe. The javascript should be updated so they both work independently, but still use the same classes, states, etc...

We need custom pages for the front page, search results, listing of plugins by keyword, etc.

We should have an HTTP server running in node that processes the post-receive hooks. The CLI script is nice for testing, but really shouldn't be used in production.

We need a script that will replay all previous history (from the SQLite database) and rebuild the WordPress site.

We're collecting watchers and forks on every push, but we're only updating the data in WordPress when there's a new release. There should be a script that loops through all plugins and updates their data daily via a cron job.

Hi

jquery plugin cookie can not download why?

Need someone to plugin new HTML styles for the "New Plugins" section on the homepage into a new function for new plugins. The design called for an article format instead of a list format. We should keep the original list format for use in sidebars elsewhere throughout the site.

Is there a mailing list or something to coordinate efforts? I'd very much like to help with this project and hopefully finish it up. It seems to have stalled, with the last commit over a month agao.

Figure out where and how a screenshot can be used on the site and add support for it.

Will we host these on the CDN, inside WordPress, or just somewhere on the web server?

What dimensions?
What will we do with incorrectly sized user images?
What will the placeholder be for plugins that don't have a screenshot?

We should have a weighted search that searches across all content, including terms.

This looks like a straightforward way of getting the top 10 most-used tags:

  $tags_args = array('orderby' => 'count', 'order' => 'DESC', 'number' => 10);
  $tags = get_tags( $tags_args );

I ran across a problem with this, however. If a plugin has 3 updates, then a tag for that plugin will be counted 4 times. We need a better way of adding up the tags that counts each tag only once for a particular plugin.

If there are user errors during processing, we should try to notify the user. We can get the user's email address from the post-receive hook. We should only notify on real problems that the user would care about; we definitely don't want to be spamming users.

Right now we blindly link to dependencies, assuming that they exist. In reality, the dependency may not exist on the plugins site; some dependencies may not even be jQuery plugins. We should check if the plugin exists and link to it conditionally.

I just set up MAMP, WordPress and the plugins.jquery.com wp-content stuff. Everything worked flawlessly in the step-to-step process. However, there seems to be problems with .local virtual hosts on Lion, you can read more about it here: http://forum.mamp.info/viewtopic.php?f=6&t=14081

TL;DR
.local seems to be triggering a lookup in the bonjour service on Lion, and makes every DNS lookup painfully slow. I switched to .dev and it worked directly, no issues what-so-ever.

We need to explain how the process of reserving plugin namespaces will take place, and how we can avoid "land-grab" scenarios. Is there an open source implementation of The Honor System?

A few developers interested in the idea of a package manager (like npm) aimed at client-side JavaScript have recently started a discussion and plans around how to build such a tool.

Part of the design that we haven't yet worked out is the module meta data and the repo. I was happily surprised to see that you seem to have answered (possibly) that question for us!

Would you be interested in some discussion around how to ingrate a package manager tool into your repo?

see: https://github.com/micmath/ssm
and: http://groups.google.com/group/amdpackages-discuss

There should be an easier way to install a working plugins site. This is complicated by the fact that most devs will work with a fresh single site WordPress install from scratch, while production will run with an existing multi-site WordPress install and an existing copy of web-base-template.

Ideally something like curl some-script | sh which will do whatever makes sense (at a minimum the majority of what is listed under plugins.jquery.com setup in the readme).

All of our package.json fields that aren't exactly the same as npm's package.json should be moved under a jquery field to ensure compatibility.

This has already cropped up as an issue with the dependencies field since a plugin's final dependencies are unrelated to its npm dependencies, so npm install will do the incorrect thing.

package.md says: "You may not supply a comparator with a version containing an x." It should be made clear whether or not this means, for example, that you can't supply a comparator with a bare number. (The logic would be that "1" maps to "1.x.x", so presumably ">=1" is disallowed because that maps to ">=1.x.x" which comes under the quoted prohibition.)

As well as clarifying the mapping in the specification, please make the pre-commit validator for package.json files validate against dependency versions. This was suggested by scottgonzalez on IRC in #jquery.

I was just looking at the documentation of how to include demo URLs into the package.json.

It states: demo: The url to the plugin demo or demos.

Since I would like to include mutliple URLs I assumed that I have to put them into an Array (just like keywords for example). But when I was looking at the code in service.js (line 150) it appears to me as if a String is expected for package.demo.

So my questions / issues would be: a. will this String (when containing multiple URLs) be split on whitespaces or something else (or is this designed to be a single URL)? and b. wouldn't using an Array of strings for everything that can have multiple values be easier, more convenient and more consistent (see keywords vs. demo). In any case I think mentioning this in the docs would be awesome.
Or did I overlook something else here?

src/main.js is using node dependencies, but no where are they actually listed. A package.json should fix that.

The versions shortcode should have links to the other versions. The current version should just be text.

(I am sorry if this is posted to the wrong place, but the Jquery forums seem to be closed to this and send me here...) I am just wondering if ANYONE has managed to get the wonderful Beautytips plugin to play nicely with a jQuery version greater than 1.4.2. I am happily running them on 1.4.2, but want to run 1.7 for obvious performance reasons. It seems that there were changes in 1.4.3 that rendered the current versions of btips useless, and I can't even seem to find another site running btips running on recent versions of jquery.

1.dropdown list unshow
var iSelectHeight = ($('li',$ul).length)*($('li:first',$ul).height());//+1 else bug ff
iSelectHeight = (iSelectHeight == 0 ? ($('li',$ul).length * 24) : iSelectHeight);// add this code

2.select changed,but ui unchange.
//add this code
$('select.jqTransformHidden').live('change',function(){
var thiz = $(this);
var text = thiz.find('option:selected').text();
var ul = thiz.parents('div.jqTransformSelectWrapper:first ul');
ul.find('a').removeClass('selected');
ul.find('a:contains("' + text + '")').addClass('selected');
ul.prev().find('span').text(text);
});

Currently plugin suites reserve all names with their given prefix. Plugins that extend a plugin from a suite should be allowed to use the suite's prefix. The can be accomplished by allowing non-suites to use a suite's prefix if they contain at least one extra dot. For example, jquery.ui.autocomplete would be reserved for the jQuery UI suite, but jquery.ui.autocomplete.html would be available to anyone.

I've just added the styles for the notification bar that shows if a user is looking at an older version of a plugin. Can someone hook that up in WordPress so it only shows when it's supposed to, links to the latest version, and can be hidden by clicking close (or should that not even be an option? I'm not 100% sure)

In order to have a listing of all plugins by the same owner (identified by the service's owner username), WordPress needs the owner field. It doesn't get it currently, as it's not part of the package.json, though it is in the sqlite plugins table.

If you have comments or concerns about the way we've configured the package.json for jQuery plugins, this here's the place to raise them.

GitHub is awesome, but some people prefer other sites, like BitBucket, for their repository hosting. It would be ideal if we can only require "open source development," not "open source development on GitHub only."

Now that plugins don't need to have a prefix, we'll need to move pages to /docs/ so that there's no chance of a name collision. We'll also need to prevent the creation of a plugin named docs.