Posted by ica on September 14, 2007 at 9:22pm
Jump to:
| Project: | Yahoo YUI |
| Version: | 5.x-2.2 |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | bakyildiz |
| Status: | closed (fixed) |
Issue Summary
Would not be better if YUI library (possibly any other 3rd party library) better to be uploaded/exist in a top level Drupal directory?
for instance a top level directory and referenced from there?
drupal
-libraries
--yui
--scriptalicious (another lib example)
-misc
-files
etc.YUI library is large also other modules by other modules such as
http://drupal.org/project/yui
and there would be some other modules based on YUI lib
imho - rather than each module depended on the same library and requesting the lib to be exist/uploaded in their module directory, a directory structure above will save, space, time, energy for all
ps: another matter/example is the Scriptalicious library would be example to be but its is related to other modules dependent on Scriptalicious
thanks
Comments
#1
Actually this is an critical issue. The yui package should be shared in a common way so that the modules could use the same package instead of describing and copying under each module.
#2
in the YUI case we have the option to use Yahoo's hosted file. I believe that this should be optional and up for the user to choose since both ways could be less/more useful depending on the user's environment.
Right now we're working on merging the currently existing YUI modules (menu, editor, calendar) into a main project for the YUI. In this case I think we should have a main module which will provide this functionality/choice for the user, and the other modules should depend on this module to define where and how to retrieve the YUI files.
#3
I have two things to contribute to this conversation:
1) I agree that we should have one main YUI module that "manages" all of the other installed YUI modules. The main YUI module would keep track of whether the YUI files are local or hosted (probably based on a user setting).
2) I also think we should merge all of the YUI projects that support core component functionality into one Drupal project/module. We could then keep each supported YUI component in a subdirectory of the main YUI module. This is what jstools has done and it seems to work well.
Other modules may want to take advantage of the YUI module API. For instance, I foresee a CCK field that supports the calendar and another CCK field that supports the rich text editor. There are plenty of use cases that we could come up with. Having the core functionality for each component in one module would probably make this easier.
Hopefully this makes sense.
#4
Yahoo YUI has a main YUI module where we can select the usage of the yui library.
Installation
------------
- Copy the yui module into Drupal modules directory.
- The is two option of how to consume the yui library. (The default is hosting appoch.)
1. Hosting approach
Use the required yui library directly form http://yui.yahooapis.com/2.3.0
2. Local approach
Download the yui library.
Create a directory named "lib" under yui module directory.
Extract library under lib diretory.
- Login as an administrator. Enable the module in the "Administer" -> "Site building" -> "modules"
- Edit the settings under "Administer" -> "Site configuration" -> "YUI Common Settings" for any change.
#5
#6
I have done all the settings as per your installation instructions and installed the yui calendar, yui editor, yui menu modules. I could able to activate only yui menu module. Can you help me how to implement other two modules? Also I want to use Container, animation, rich text editor, Drag & Drop etc... with YUI. Can I do it? Give me some examples.