If possible, add Nuget Package support without ruining the current build tools.

[maitredede]

Your lib is fantastic ! But I think you may add a nuget package. Here is a sample of a .NuSpec file :

<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
    <metadata>
        <id>VisJs</id>
        <version>3.0.0</version>
        <title>Vis.Js</title>
        <authors>Almende B.V</authors>
        <projectUrl>http://visjs.org/</projectUrl>
        <requireLicenseAcceptance>false</requireLicenseAcceptance>
        <description>Vis.js is a dynamic, browser based visualization library. The library is designed to be easy to use, to handle large amounts of dynamic data, and to enable manipulation of and interaction with the data. The library consists of the components DataSet, Timeline, Network, Graph2d, and Graph3d.</description>
        <summary />
    </metadata>
    <files>
        <file src="dist\img\network\acceptDeleteIcon.png" target="content\Content\visjs\img\network\acceptDeleteIcon.png" />
        <file src="dist\img\network\addNodeIcon.png" target="content\Content\visjs\img\network\addNodeIcon.png" />
        <file src="dist\img\network\backIcon.png" target="content\Content\visjs\img\network\backIcon.png" />
        <file src="dist\img\network\connectIcon.png" target="content\Content\visjs\img\network\connectIcon.png" />
        <file src="dist\img\network\cross.png" target="content\Content\visjs\img\network\cross.png" />
        <file src="dist\img\network\cross2.png" target="content\Content\visjs\img\network\cross2.png" />
        <file src="dist\img\network\deleteIcon.png" target="content\Content\visjs\img\network\deleteIcon.png" />
        <file src="dist\img\network\downArrow.png" target="content\Content\visjs\img\network\downArrow.png" />
        <file src="dist\img\network\editIcon.png" target="content\Content\visjs\img\network\editIcon.png" />
        <file src="dist\img\network\leftArrow.png" target="content\Content\visjs\img\network\leftArrow.png" />
        <file src="dist\img\network\minus.png" target="content\Content\visjs\img\network\minus.png" />
        <file src="dist\img\network\plus.png" target="content\Content\visjs\img\network\plus.png" />
        <file src="dist\img\network\rightArrow.png" target="content\Content\visjs\img\network\rightArrow.png" />
        <file src="dist\img\network\upArrow.png" target="content\Content\visjs\img\network\upArrow.png" />
        <file src="dist\img\network\zoomExtends.png" target="content\Content\visjs\img\network\zoomExtends.png" />
        <file src="dist\img\timeline\delete.png" target="content\Content\visjs\img\timeline\delete.png" />
        <file src="dist\vis.css" target="content\Content\visjs\vis.css" />
        <file src="dist\vis.min.css" target="content\Content\visjs\vis.min.css" />
        <file src="dist\vis.js" target="content\Scripts\vis.js" />
        <file src="dist\vis.min.js" target="content\Scripts\vis.min.js" />
    </files>
</package>

[josdejong]

Yes that could be nice. I'm not familiar with NuGet and how to publish there. I think though that your example package can be simplified to something like:

<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
    <metadata>
        <id>vis</id>
        <version>3.0.0</version>
        <title>vis.js</title>
        <authors>Almende B.V.</authors>
        <projectUrl>http://visjs.org/</projectUrl>
        <requireLicenseAcceptance>false</requireLicenseAcceptance>
        <description>Vis.js is a dynamic, browser based visualization library. The library is designed to be easy to use, to handle large amounts of dynamic data, and to enable manipulation of and interaction with the data. The library consists of the components DataSet, Timeline, Network, Graph2d, and Graph3d.</description>
        <summary />
    </metadata>
    <files>
        <file src="dist\**\*" target="lib" />
    </files>
</package>

[maitredede]

I used Nuget Package Explorer (http://npe.codeplex.com/) to create it, based on the release zip. I don't know if the files/file supports wildcards, but the target I put are the common targets for Asp.net projects : ~/Scripts for javascript, ~/Content for the rest. With Nuget Package Explorer, you can open existing packages to see how there are done (like jquery, bootstrap, etc...)

[josdejong]

ehhh yeah... running linux here...

[maitredede]

And it won't run on Mono since it is WPF... Someday I will try to see where is the status of the Wine project with compatibility of the microsoft framework... The nuspec documentation is here : http://docs.nuget.org/docs/reference/nuspec-reference But on Mono, I am pretty sure you can run the commandline nuget.exe tool that will package the files and publish it... I will try to make a test...

[josdejong]

I suppose you could get it working via mono, but I don't think it's a good idea to make the build/release cycle dependent on platform specific tools or prerequisites like mono and nuget.exe.

It would be great if there is a solution to automatically update nuget packages from github, like bower does.

[maitredede]

It seams that you can use MyGet to achieve this : http://weblogs.asp.net/bsimser/automatically-publishing-nuget-packages-from-github According to the blog post, MyGet can handle all the stuff (git pull, create package, publish to myge, upstream to nuget...).

[AlexDM0]

Hi,

Over the last year a lot of feature requests have been made. We have just introduced our new website which has a list of the requested features. We have placed this request on that list.

The list can be found here: http://visjs.org/featureRequests.html

An explaination of the new system can be found here: http://visjs.org/blog.html#New\ website\ for\ vis.js!

I would like to stress that this does not mean we abandon this request. Discussion here will continue if needed on this feature but we will close it to keep our Github issue page more of a bug-todo list.

Future feature requests will still be made here and then added to the website by us.

Regards,

Alex

[mojoaxel]

Reopening as Feature-Request issue (see #2114). Everybody: Please feel free to implement this!

[johandanforth]

+1 for nuget package, also for a typedef-package. I may find the time soon to add such packages myself if no one objects to it?