[MapQuery] Directory layout + external libs in Git repo

Christian Wygoda arsgeografica at googlemail.com
Thu Nov 11 08:43:15 EST 2010

I'll probably write a shell script to download and extract everything, such
a script could easily live inside the repo.

Also, in follow up to
http://lists.osgeo.org/pipermail/mapquery/2010-July/000091.html I'd like to
suggest following file name scheme for our code

* jquery.geomap.map.js (now geoMap.js)
* jquery.geomap.layer.js (now geoMap.js)

For the widgets:
* jquery.geomap.toc.js

Aggregated "release" (someday...):
* jquery.geomap.js

On Thu, Nov 11, 2010 at 2:24 PM, Volker Mische <volker.mische at gmail.com>wrote:

> Hi,
> On 11/11/2010 02:19 PM, Christian Wygoda wrote:
> > Hi all,
> >
> > I am pretty busy doing massive raster calculations using GRASS for an
> > freelance project for the last week and will be busy with it for a while
> > to come. While watching GRASS eating my CPU cycles, I looked trough the
> > code repo and asked myself two things:
> >
> > 1) The file and directory layout is not very cleaned up right now. Code
> > and OpenLayers mixed in one directory, for example. I'd suggest having
> > demo, lib(external dependencies like OL, jQuery), src and test
> directories.
> +1
> > 2) We're keep OpenLayers, jQuery and jQuery UI code in our own repo. I'd
> > suggest not to do that, instead have a strict layout (see above) and
> > make developers responsible for having the right code available. A
> > README file in the lib dir should name explicit dependencies and how to
> > arrange files to make demos, tests, etc. work. (is there something like
> > pip for python for javascript?)
> Sounds like a good idea. Perhaps we can also have a seperate download
> that only needs to be extracted into the lib dir and you are set.
> Cheers,
>   Volker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapquery/attachments/20101111/56fcb6ee/attachment.html

More information about the MapQuery mailing list