Posts:
8,332
Registered:
31-Jan-2006
|
|
|
|
Re: Map types
Posted:
4 Apr 25, 15:18
in response to: Laza
|
|
|
As far as I can tell, the marker deprecation, announced over a year ago, applies only to apps that want to do some customization. The basic marker positioning and labeling doesn't appear to be changing. This page was updated just yesterday:
https://developers.google.com/maps/documentation/javascript/reference/advanced-markers
And the markers on my maps are still behaving perfectly normally. |
|
|
Posts:
1,510
Registered:
6-Sep-2005
|
|
|
|
Re: Map types
Posted:
4 Apr 25, 17:24
in response to: JeffTucker
|
|
|
|
They write a warning on the console every time a user uses the Marker library. They say, they will remove it in the future but will notify users 12 months before that.
|
|
|
Posts:
8,332
Registered:
31-Jan-2006
|
|
|
Posts:
1,510
Registered:
6-Sep-2005
|
|
|
|
Re: Map types
Posted:
4 Apr 25, 18:05
in response to: JeffTucker
|
|
|
|
|
|
You are using the old direct library call, not the new "async". Perhaps this is why you don't get this warning.
|
|
|
Posts:
8,332
Registered:
31-Jan-2006
|
|
|
|
Re: Map types
Posted:
4 Apr 25, 18:28
in response to: Laza
|
|
|
|
Whatever the reason, it's all still working, and I am, in fact, using AdvancedMarkerElement(), which is what the warning tells the coder to do. And there are no indications that it's going to stop working, so there's no need to jump ship!
|
|
|
Posts:
190
Registered:
18-Jun-2010
|
|
|
|
Re: Map types
Posted:
4 Apr 25, 18:33
in response to: JeffTucker
|
|
|
So which one should I choose?
See the problem? For the typical user, this is a bewildering forest of mostly dead ends. It's a bit like steering someone to Linux because they don't want to be ensnared by "the man!" Down the rabbit hole they go. 
Not a user has to choose those overlays, a developer of a web site chooses an overlay which makes sense.
+1
So, to incorporate "better OSM" into a skin, I'd need to quiz the jAlbum user on where most of his site visitors are coming from, and what they're most interested in. I'd probably have to incorporate an AI module to help choose the right leaflet, and do the Javascript coding.
Most jAlbum users are not web site developers. Most of them probably wouldn't even qualify as "techies." They're photographers, people with families, school teachers, travelers, and so on.
You're right  I'll still point out two things:
- OSM has layers with global coverage, so there's no need to know where visitors are coming from. But when it comes to satellite imagery, I admit Google is better than OSM.
- A jAlbum user doesn't necessarily need to write JavaScript; that's more the developer's responsibility. But for a developer, it's easy to write code that reads an OSM layer definition from a file rather than hard-coding it in JavaScript. From there, defining the desired layers is much easier for a gallery author.
|
|
|
Posts:
1,510
Registered:
6-Sep-2005
|
|
|
|
Re: Map types
Posted:
5 Apr 25, 07:32
in response to: JeffTucker
|
|
|
|
Yes, I don't worry much at the moment, either. But it's bad to think that all websites are constantly depreciating and need to be updated every year or two. The cloud-dependency in web photo albums is rather a disadvantage. Especially now, when the world is collapsing.
|
|
|
Posts:
8,332
Registered:
31-Jan-2006
|
|
|
|
Re: Map types
Posted:
5 Apr 25, 14:35
in response to: Laza
|
|
|
|
That's the problem with any mapping service, no matter which one you choose. You can't host all of the maps on your own server.
At least the browsers themselves haven't clobbered us. For example, the old Highslide JS script that was behind my Matrix skin was abandoned by its developer in 2011 (no money in it), but it all still works in current browsers. That's almost a miracle.
|
|
|
|
Legend
|
|
Forum admins
|
|
Helpful Answer
|
|
Correct Answer
|
|
