Posted by kewlguy on November 9, 2009 at 4:22am
Jump to:
| Project: | AES encryption |
| Version: | 7.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Issue Summary
Hi I was just wondering if there were any plans for module maintainers to implement the Libraries API style such as in the WYSIWYG project?
This post explains what was done there for files or libraries that are needed or required to run a module. It might save some work to implement a like or similar solution for the libraries that are required for the installation of this module.
Comments
#1
Hi and thanks for the suggestion. Libraries API seems like a good intiative, I'll think about implementing it.
#2
This crossed my mind when I first installed the module so this is certainly something that will happen in the coming versions of AES.
However, I don't know if I want to require the dependency for the libraries api so I would want it to function with and without the Libraries module. I'm sure this can be done but I'm not deeply familiar with the libraries api yet.
When AES is looking for the phpseclib library it would first check for the libraries api. If it exists, then it would use the library api's functions to attempt to load the library. If the libraries api exists and fails to load the phpseclib library then AES may try to load it manually or may just fail to load it as well.
If the libraries api does not exist, it would look for phpseclib in the same location as the libraries api would. It would also check for what would become the legacy path to phpseclib which is inside the aes module folder.
Postponing for now. I am trying to decide how I am going to support the D7 branch before I start creating version 2.x branches for this module.