Closed anderserla closed 9 years ago
Will now fetch dependencies needed to build OpenEMap. Instructions added to README.md. Development examples can use dependencies fetched by the new setup but that will require additional work.
Would it be possible to build one big javascript file including all dependencies, like GeoExt, OpenLayers, ExtJS? Would that be smart? Would it be against the license rules? @sweco-sebhar
Yes, no and yes. :)
Finished support for development. This now works for me:
git clone https://github.com/Sundsvallskommun/OpenEMap-WebUserInterface.git oemap
cd oemap
git checkout develop
npm install
grunt devserver
After the above I can open http://localhost:8000/dev/debug.html
in a browser. A nice feature of devserver mode is that the debug page will automatically reload when sources are changed.
I've also reworked build/dist a bit so grunt dist
will create a complete release dir in release/OpenEMap-x.x.x
with the version set in package.json.
PS. This is only tested on Linux. Will probably work on Mac but Windows probably needs some tweaking. PS2. Now tested in Windows 8.1 it just works no tweaks needed :)
Eventual TODOs:
Also I think it's a mistake to include the dir release
in the repository (also applies to ext-theme-oep repo and is the reason I do not use it). Versions should simply be tagged. A built release can be attached to the tag/release in github.
Jsdocs build handled in issue #143, marking this issue as done.
Not yet finished. No feature branch since this stuff does not affect current project setup.