Skip to content

Commit 9d9c674

Browse files
committed
Add Appveyor badge
Also remove old roadmap section of README
1 parent c16a19a commit 9d9c674

File tree

1 file changed

+3
-23
lines changed

1 file changed

+3
-23
lines changed

README.md

Lines changed: 3 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# DNN JavaScript Libraries
22

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+
35
Version 7.2 of the [DNN Platform](http://www.dnnsoftware.com) introduced the
46
JavaScript Library extension type. This allows common JavaScript libraries to
57
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.
3133
# Packages
3234

3335
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).
3637

3738
# Goal
3839

@@ -118,27 +119,6 @@ included on the page once (rather than both components including their own
118119
version of the script). Likewise, if both components request different versions
119120
of the script, just the higher version will be included.
120121

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-
142122
# License
143123

144124
This code is released under the [MIT license](LICENSE.md).

0 commit comments

Comments
 (0)