|
1 | 1 | # DNN JavaScript Libraries |
2 | 2 |
|
| 3 | +[https://ci.appveyor.com/api/projects/status/github/EngageSoftware/Dnn-JavaScript-Libraries?svg=true](https://ci.appveyor.com/project/bdukes/dnn-javascript-libraries) |
| 4 | + |
3 | 5 | Version 7.2 of the [DNN Platform](http://www.dnnsoftware.com) introduced the |
4 | 6 | JavaScript Library extension type. This allows common JavaScript libraries to |
5 | 7 | exist in a single place within a DNN site, instead of every module, skin, and |
@@ -31,8 +33,7 @@ commit your changes and submit a pull request on GitHub. |
31 | 33 | # Packages |
32 | 34 |
|
33 | 35 | The installable packages are included within this GitHub repository as |
34 | | -[releases](/EngageSoftware/DNN-JavaScript-Libraries/releases). They are also |
35 | | -published on the [DNN Forge](http://www.dnnsoftware.com/forge). |
| 36 | +[releases](/EngageSoftware/DNN-JavaScript-Libraries/releases). |
36 | 37 |
|
37 | 38 | # Goal |
38 | 39 |
|
@@ -118,27 +119,6 @@ included on the page once (rather than both components including their own |
118 | 119 | version of the script). Likewise, if both components request different versions |
119 | 120 | of the script, just the higher version will be included. |
120 | 121 |
|
121 | | -# Roadmap |
122 | | - |
123 | | -The obvious next step for this project is to add more libraries. There's a |
124 | | -short list in [the Issues list for this repo](/EngageSoftware/DNN-JavaScript-Libraries/issues), |
125 | | -but we've started work on a [PowerShell script](New-PackageFromBower.psm1) that integrates with a |
126 | | -script package manager, [Bower](http://bower.io/), so that with very |
127 | | -little effort, we can get the latest version of a script, package it, and |
128 | | -publish it. |
129 | | - |
130 | | -In addition, there are some enhancements to DNN itself that would help this be |
131 | | -an even more useful tool. The main enhancement is to provide a similar mechanism |
132 | | -for shared CSS components. For example, many jQuery plugins are going to include |
133 | | -basic styles to make them work. It would be nice if there was a way to get CSS |
134 | | -that matched the requested JavaScript Library. Also, JavaScript libraries with |
135 | | -multiple JavaScript files could be handled together more cleanly, rather than as |
136 | | -a bunch of separate libraries. Finally, one of the big ways that would make |
137 | | -this more of a no-brainer is if the extension installation process automatically |
138 | | -found dependent packages on the [DNN Forge](http://www.dnnsoftware.com/forge) |
139 | | -rather than asking clients to install the JavaScript Library package(s) before |
140 | | -installing your component. |
141 | | - |
142 | 122 | # License |
143 | 123 |
|
144 | 124 | This code is released under the [MIT license](LICENSE.md). |
|
0 commit comments