[MetaCRS] Fwd: [ol3-dev] proj4js

Calvin Metcalf calvin.metcalf at gmail.com
Wed Jun 19 07:11:48 PDT 2013


I'm going to start opening issues on github for the various things that
Andreas and I mentioned so we can discus them there.  Also if people are
unfamiliar with the build tools I set up, grunt (http://gruntjs.com/) is
the task runner and Uglify2 (https://github.com/mishoo/UglifyJS2) via this
grunt plugin (https://github.com/gruntjs/grunt-contrib-uglify) is being
used to minify.


On Wed, Jun 19, 2013 at 10:03 AM, Andreas Hocevar <ahocevar at opengeo.org>wrote:

> Ok, I went ahead and moved my fork to http://github.com/proj4js/proj4js.
> If MetaCRS folks are unhappy with this move, we can easily move the
> repository to the metacrs organization. @Mike, I also made you an owner of
> the proj4js organization.
>
> @Calvin, I merged your pull request, because I think it is a good starting
> point.
>
> Regarding Closure vs. Uglifyjs, I like the uglifyjs approach because we
> can get along without python in the build chain, and it looks like it will
> be easier to create a fancy online build tool this way. I have to admit I
> have more experience with Closure, but I'm happy to try something new.
>
> Andreas.
>
>
>
> On Tue, Jun 18, 2013 at 5:06 PM, Andreas Hocevar <ahocevar at opengeo.org>wrote:
>
>> Thanks Calvin. I haven't looked at the code yet, but please do create a
>> pull request against my repo - it's easier to review if it's a pull request.
>>
>> Andreas.
>>
>>
>> On Tue, Jun 18, 2013 at 4:46 PM, Calvin Metcalf <calvin.metcalf at gmail.com
>> > wrote:
>>
>>> I through something together quickly on github it's a clone of Andreas'
>>> repo containing some of the changes Michael put in but using grunt and
>>> uglify https://github.com/calvinmetcalf/proj4js that can be a pull
>>> request to Andreas repo.
>>>
>>>
>>> On Tue, Jun 18, 2013 at 9:44 AM, Michael Adair <madair at dmsolutions.ca>wrote:
>>>
>>>>  Hi Andreas,
>>>>
>>>> I started a version that would compile with the Closure compiler in
>>>> advanced mode, as well as removing all the asynchronous loading stuff, and
>>>> this is at http://svn.osgeo.org/metacrs/proj4js/branches/closure.  I
>>>> did see Eric's reply to my query about it a while ago but haven't gotten
>>>> much farther than I was a that point.
>>>>
>>>> I would be happy to have some help improving the library and I would
>>>> still like to be involved and contribute, but for a move to github I would
>>>> also ask for someone to take over leadership of the project, since an old
>>>> fart like me is still having issues figuring out github (at least until I
>>>> can use it actively in a project).
>>>>
>>>> Thanks for taking this on,
>>>>
>>>> Mike
>>>>
>>>>
>>>> On 18/06/2013 4:17 AM, Andreas Hocevar wrote:
>>>>
>>>> I would be willing to lead that effort, because I have plans for
>>>> proj4js too, to make it play nicely with OpenLayers 3. These plans
>>>> include:
>>>>
>>>> * Move the repository to github (either a proj4js organization or a
>>>> metacrs organizations if other metacrs projects want to join).
>>>>
>>>> * Create a hosted build tool to create builds that only contain
>>>> projections that the user needs, with the ability to fetch projection
>>>> defs (including axis order!) from http://spatialreference.org/.
>>>>
>>>> * Use Closure Compiler in Advanced Mode to ensure builds are as small
>>>> as possible.
>>>>
>>>> * Make it extensible so developers can add custom transforms, and add
>>>> custom transforms e.g. for Swiss projections, where proj4js only uses
>>>> a 3 param transform because it does not do grid transforms.
>>>>
>>>> * Make the validity extent a property of the projection, and let the
>>>> custom build tool fetch validity extents from
>>>> http://epsg-registry.org/ (or http://spatialreference.org/ if we can
>>>> agree on a way to extend either proj4 defs or OGC WKT defs to include
>>>> the validity extent).
>>>>
>>>> I went ahead and created both proj4js and metacrs
>>>> organizations on github, as a precaution. Please let me know if you're
>>>> ok cloning the proj4js repo to github, and if I should do it in the proj4js
>>>> or the metacrs organization. Also get in touch with me to become an owner
>>>> of these organizations on github.
>>>>
>>>> Andreas.
>>>>
>>>> On Tue, Jun 18, 2013 at 8:57 AM, OL3 Dev on behalf of Bart van den
>>>> Eijnden <ol3-dev at googlegroups.com> wrote:
>>>> > Seems that some people are interested in "revamping" proj4js:
>>>> >
>>>> > https://twitter.com/CWMma/status/346683497496334336
>>>> >
>>>> > Best regards,
>>>> > Bart
>>>> >
>>>> > --
>>>> > Bart van den Eijnden
>>>> > OpenGeo - http://opengeo.org
>>>> > Expert service straight from the developers.
>>>>
>>>>  --
>>>> Andreas Hocevar
>>>> OpenGeo - http://opengeo.org/
>>>> Expert service straight from the developers.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> MetaCRS mailing listMetaCRS at lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/metacrs
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> MetaCRS mailing list
>>>> MetaCRS at lists.osgeo.org
>>>> http://lists.osgeo.org/mailman/listinfo/metacrs
>>>>
>>>>
>>>
>>>
>>> --
>>> -Calvin W. Metcalf
>>>
>>> _______________________________________________
>>> MetaCRS mailing list
>>> MetaCRS at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/metacrs
>>>
>>>
>>
>>
>> --
>> Andreas Hocevar
>> OpenGeo - http://opengeo.org/
>> Expert service straight from the developers.
>>
>
>
>
> --
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.
>



-- 
-Calvin W. Metcalf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/metacrs/attachments/20130619/0f151de1/attachment-0001.html>


More information about the MetaCRS mailing list