I think this should go into core. I appreciate contrib modules shaking off the issues here before presenting this as a project for D7, but I feel it's going to be rather annoying to have all those cool modules depend on that pesky library module everyone will need to install. Why not just have a includes/libraries.inc and get it over with?

There's already some work towards that in the core, from what I understand, but they don't want to have a central location for libraries, see:

* #315100: Allow to add JS/CSS libraries (sets of files, settings, and dependent libraries)
* http://drupal.org/update/modules/6/7#drupal_add_library

We could build a list of requirements before #496240: sites/<site>/libraries: Standard place for thirdparty module requirements gets un-postponed here than start advocating inclusion over there.

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented
Status: Active » Closed (won't fix)

It's 50 lines of code, because I didn't have the time to focus on development yet.

Properly supporting *external* libraries is a major challenge. There are multiple ways to achieve it, and Libraries API wants to provide an API to support all ways. If you read #315100: Allow to add JS/CSS libraries (sets of files, settings, and dependent libraries) more closely, then you can learn that support for external libraries was purposively left out from that patch.

Neither Libraries API nor Drupal core are ready for this yet.

And with "ready" I mean concepts, architecture, technology, and paradigm.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Status: Closed (won't fix) » Postponed

Well, "not ready" doesn't mean "never". Can't we just keep that in mind?

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented
Status: Postponed » Closed (won't fix)

You can be sure it's kept in mind. There is no point in having an issue languishing around for months or even a year.