Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leaflet 1.0-beta1 compatibility #90

Closed
IvanSanchez opened this issue Aug 11, 2015 · 21 comments
Closed

Leaflet 1.0-beta1 compatibility #90

IvanSanchez opened this issue Aug 11, 2015 · 21 comments

Comments

@IvanSanchez
Copy link

Some users of Leaflet 1.0-beta1 are complaining that Proj4leaflet only works with 0.7.3. See Leaflet/Leaflet#3731

@perliedman
Copy link
Contributor

There is a branch for 1.0 here: https://github.com/kartena/proj4leaflet/tree/leaflet-proj-refactor. We should probably verify it against beta1, since it was developed quite a while ago, and also make sure to include this in the docs.

@chronixlo
Copy link

The 1.0 branch doesn't have the TMS function but it can be copypasted from master. Seems to work 👍

@perliedman
Copy link
Contributor

I think that is deliberate, since TMS should work without Proj4Leaflet's hack in Leaflet 1.0. That is, you shouldn't have to use L.Proj.CRS.TMS any longer, you can just use CRS and set tms: true on the TileLayer.

@semone
Copy link
Contributor

semone commented Sep 2, 2015

The branch is now verified against beta and updated!

@jgravois
Copy link

The branch is now verified against beta and updated!

awesome! do ya'll plan on tagging a version? we'd love to reference something official in one of our own published samples.

@semone
Copy link
Contributor

semone commented Sep 18, 2015

The verified branch is the leaflet-proj-refactor which should work with Leaflet 1.0-beta. Since the changes form Leaflet 0.7 -> 1.0 affects Proj4Leaflet alot there won't be one branch supporting both. When Leaflet 1.0 is stable and not in beta anymore there will be a new version out of Proj4Leaflet.

If you are using Leaflet 0.7.x there is a tagged version which should work for you:
https://github.com/kartena/Proj4Leaflet/releases

Maybe i missunderstood your question?!

@jgravois
Copy link

thanks for your response. since Leaflet 1.0.0beta1 is locked now, i was suggesting that it would be helpful if you could tag an actual compatible version (as opposed to pointing people at a live branch) even if your own release is a beta too.

http://github.com/Esri/esri-leaflet/releases

@semone
Copy link
Contributor

semone commented Sep 18, 2015

Now I follow! Good suggestion, I have now fixed that, actually I didn't know about the pre-release feature, you learn new stuff everyday 😃

@chronixlo
Copy link

I don't have a demo for this but going from 1.0 beta to latest master broke pinch zooming. WGS84 proj works fine so I'm assuming it's a proj issue. Can anyone confirm?

@semone
Copy link
Contributor

semone commented Sep 30, 2015

I think this is related to issue #97?

@chronixlo
Copy link

Oh jeez sorry :D Somehow missed it

@sivesind
Copy link

sivesind commented Aug 19, 2016

@semone @pthorin Thx for the great work on Proj4Leaflet! Any chance of you publishing the 1.0.0-beta.2 version to npm?

@sivesind
Copy link

sivesind commented Aug 22, 2016

@semone @pthorin Also, the version of proj4leaflet (set in package.json) in branch leaflet-proj-refactor is set to 0.7.0. I guess it should be 1.0.0-beta.2 or something along that line?

@semone
Copy link
Contributor

semone commented Aug 22, 2016

hi @sivesind #120 has the latest rc-3 which I hope someone will be able to look at and merge in. It has the correct version in package.json and that one is the one I hope we publish to npm. Will that be okey for you or do you specifically need the beta for some reason? 😄

@sivesind
Copy link

sivesind commented Aug 22, 2016

Hi @semone! RC3 where everything is fixed sounds great! I just need a proj4leaflet version compatible with leaflet@1.0.0-rc-3, since we use esri-leaflet@2.0.2 depending on it. If proj4leaflet@1.0.0-rc3 gets to npm it would be perfect :-)

Is it @pthorin the one who can merge? Do you have a guess on when this might be merged and published to npm? Keep up the great work!

@semone
Copy link
Contributor

semone commented Aug 22, 2016

@perliedman is the one who should have the credit for the great work!

@pthorin can merge, I can merge as well but would like a pair of eyes on what I have done :)

@sivesind
Copy link

sivesind commented Aug 22, 2016

@semone Well, happy merging, really looking forward to see it in npm :-) I've pulled your branch, have tested it with a utm projection and that worked fine. For what it is worth :-)

@perliedman Thank you for your great work!

@pthorin
Copy link

pthorin commented Sep 5, 2016

@sivesind I have merged #120, and am looking into publishing a new npm version, but I want to fix #109 first.

Sorry for taking so long.

@sivesind
Copy link

sivesind commented Sep 5, 2016

@pthorin no apologies needed! I'm just happy proj4leaflet exists, because of you excellent people:-) Keep up the good work! If I find any bugs I'll try to contribute, we have an in-house GIS expert that may assist me.

@bhaskarvk
Copy link

Hi guys any updates on this ? Leaflet 1.x has been stable now for quite some time. And also thanks for all the work on this guys.

@pthorin
Copy link

pthorin commented Jan 25, 2017

Closed in 1.0.0 (#126).

@pthorin pthorin closed this as completed Jan 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants