No subject

Sun Dec 12 18:29:16 UTC 2010

OpenSpendingJS can be visualisation experts who do not want to install<br>
Python, OpenSpending, Postgres, RabbitMQ and Solr on their dev<br>
machines. Instead, they can check out that repo, put in in their LAMP<br>
install and go into their settings on to set a<br>
user-custom script root, which will make get all of the scripts<br>
off their local version, e.g. <a href=3D"http://localhost/openspendingjs" t=
arget=3D"_blank">http://localhost/openspendingjs</a>. Gregor<br>
has been using it, and I think we should promote it more.<br></blockquote><=
div><br></div><div><div>They could clone openspending, but not run it. Simp=
ly go into=A0openspending/ui/public/static/openspendingjs and do the change=
s there.</div>

</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">
As for merging parts of the JS back into OS: we could do that, but<br>
then we potentially end up with two vendor lib archives - which I<br>
think is more trouble than we gain.<br></blockquote><div><br></div><div>Agr=
eed. I think everything related to openspending should be in openspending&#=
39;s repo.</div><div><br></div><div>Cheers,</div><div>V=EDtor.</div></div>



More information about the openspending-dev mailing list