Closed (fixed)
Project:
Drupal.org site moderators
Component:
Site organization
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 May 2007 at 16:30 UTC
Updated:
29 Jul 2009 at 20:20 UTC
With JJeff adding several JQuery related modules and the possibility of this category growing, should we add a JQuery tag for projects?
Comments for or against. I am in the 'for' side at this point.
Comments
Comment #1
boris mann commentedIt should probably be called either "AJAX" or "Javascript" -- there are several other JavaScript libraries / effects that have projects.
Comment #2
sime"for", "Javascript"
Comment #3
dwwit's not (yet) clear what kind of guidelines we'd establish for if a project belongs in this category or not. for example, both project_issue.js and signup.js exist, and add some useful UI functionality if JS is enabled. i can imagine a ton of modules that at least provide *some* JS UI goodness, especially in 5.x. however, it seems silly to put all of them into a "Javascript" category. clearly, y'all have something else in mind. not just providing some JS goodness, but a module that more fundamentally depends on JS?
before i'd +1 this, i'd like to hear a concise statement of what belongs here and what doesn't, something that's unambiguous and easy for project maintainers (and end users) to understand...
maybe i'm over-thinking this.
cheers,
-derek
Comment #4
boris mann commentedLightbox module, Scriptaculous module, Magic Javascript thumbnail action of doom module. Make sense? :P
Comment #5
sepeck commentedAs Boris said. The initial thought occurred when looking at jjeff's modules and thinking, I wonder what other jquery goodness (now modified to javascript goodness) was out there to help me make my site more pretty.
Comment #6
dwwok, to be clear: since signup.module does *a little* bit of JS goodness to make the UI more pretty, does that qualify? just trying to understand the criteria. i suspect this will be hard to quantify. i'm not saying the category is a bad idea, but i'm anticipating project maintainer confusion over this, so if someone could spell out some relatively simple and concrete criteria for what modules belong there, i think that'd be helpful. "here are some names of modules you've never heard of, make sense?" isn't what i'm asking for. ;) an algorithm to decide, not a set of training data, is what i'm hoping for... that said, i'll shut up now.
Comment #7
gregglesHow about this:
If the main purpose of your module is to provide additional functionality via Javascript then you should use the Javascript tag. If your module's main purpose is to provide some set of features and Javascript helps make those features richer, do not use the Javascript tag.
Comment #8
simeThe shortest suggestion I have is:
"Javascript Plugins & Libraries"
Comment #9
simeSorry greggles, changing your title back.
(Note, my short description above is intended for the project edit page. This is where people are when they choose the categories and it doesn't offer long descriptions.
Comment #10
beginner commentedDon't include 'jQuery' in the title: that's already too specific.
+1 for anything with 'javascript'.
I suggest "Javascript utilities", or simply "javascript".
Comment #11
sepeck commentedAdded Javascript Utilities with greggles description.
Someone needs to update the documentation/announce/be willing to take a rough pass through the modules to tag them.
Comment #12
dwwthanks for taking care of this, sepeck, i was just about to do the same, myself. ;)
FYI: "active (needs more info)" means "the submitter wasn't clear and we can't make progress fixing this until they tell us what they're talking about". as such, it's not listed in the default views of the issue queues. even though there's not really a patch, we use CNW for these sorts of "still needs to be documented", etc tasks at the end of an issue that's mostly been "fixed".
Comment #13
dave reidHasn't had any follow up in over 2 years. If modules haven't organized themselves with the new category by now, too bad. Marking as fixed.