No subject

OpenSpendingJS can be visualisation experts who do not want to install
Python, OpenSpending, Postgres, RabbitMQ and Solr on their dev
machines. Instead, they can check out that repo, put in in their LAMP
install and go into their settings on OpenSpending.org to set a
user-custom script root, which will make OS.org get all of the scripts
off their local version, e.g. http://localhost/openspendingjs. Gregor
has been using it, and I think we should promote it more.

As for merging parts of the JS back into OS: we could do that, but
then we potentially end up with two vendor lib archives - which I
think is more trouble than we gain.

Cheers,

 - Friedrich

On Tue, Jul 31, 2012 at 10:07 AM, Rufus Pollock <rufus.pollock at okfn.org> wr=
ote:
> The issue is / was that openspendingjs contains a bunch of apps and
> code that should get deployed separately. It was also an idea at one
> point that people would use / reuse the js code in openspendingjs
> elsewhere. I think it might make sense to merge the js code that
> openspending needs into the openspending repo thereby removing the
> dependency on openspendingjs.
>
> Rufus
>
> On 30 July 2012 23:12, Vitor Baptista <vitor at vitorbaptista.com> wrote:
>> Hi,
>>
>> Why are openspending and openspendingjs separate? They always were
>> separated, or we had a problem that was solved by splitting them?
>>
>> Cheers,
>> V=C3=ADtor.
>>
>> _______________________________________________
>> openspending-dev mailing list
>> openspending-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/openspending-dev
>>
>
>
>
> --
> Co-Founder, Open Knowledge Foundation
> Promoting Open Knowledge in a Digital Age
> http://www.okfn.org/ - http://blog.okfn.org/
>
> _______________________________________________
> openspending-dev mailing list
> openspending-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/openspending-dev