Are you using a ālinkā component there, or ālink relationā?
It must be a link component (from the button section in the components list) - so I think I have misunderstood the feature that is going to be discontinued.
Sorry (but thanks for your help)!
Paul
Ya, thereās no such component as ālink relationā but rather ārelationā:
In Glide Apps, you can now just use a collection, even if itās a single relation.
For now, I was not able to find the map component in the new apps.
Will this component become available or will it not be continued?
Hey Jeff,
Thanks for your reply.
In my current (classic app) I can use āmapā as a style.
What you are referring is a component. It unfortunately, does not satisfy what I am doing with the classic app.
You can have a look here. Maybe makes it easier to understand the use case:
Hi Lennart,
What features do you think should be added to the maps component on the new Glide Apps?
What does it not do for you? Glide Apps (Pages) donāt have a concept of a list style view anymore. Every screen in Apps (Pages) are detail screens that allow you to add any component to any screen without being restricted to only a list/collection. If you only want to show a collection thatās fine. You can choose from any of the collection viewsā¦including the Map component, which is essentially a type of collection.
In Classic Apps, the Map style view is a type of list, and the Map component is a static map capable of only showing one pin.
In Apps (Pages), the Map component serves both roles. You can use it as a collection with multiple pins, or you can feed it a relation or filter it to only show one pin. Itās actually a lot more flexible now, in my opinion, because you can use it any way you want.
Being able to show the map full screen would be nice.
Furthermore, it would be great if the user would be zoomed to their current location (After giving consent to use location services).
Understood. I would agree that those two things are missing.
While you canāt get it to fill the entire screen, you can still adjust the aspect ratio to it fills a larger portion of the screen.
One technique that may work for youā¦if you are only concerned about pin locations within a certain distance to the userās current location, you can add a distance column to the table to calculate the distance from each location to the userās current location. Using that distance number, you can apply a filter to the map component to only show locations with a distance less than a number you have determined. The new map component is very good about readjusting and zooming the map extent to only show the filtered pins.
Yes, the piece I miss is the ability to specify what zoom level the map is presented at - I find the default is zoomed out too far.
As I understand it, the zoom adjusts to encompass all of the pins (the map extent). If you only have 1 or 2 pins close to each other, then it will zoom automatically to fit all pins on the map. To prevent the map from zooming in too much with a single pin, will will zoom out to a larger area. If you have more than one pin, is seem like it will zoom in tighter.
I agree, that being able to adjust the default zoom level could be useful.
New Glide ( Pages ) Apps will see CSS support in Rich Text Editor ?
How long will the migrator take to come into effect?
Iāve just upgraded from a grandfathered Pro plan but nothing has changed except for the amount leaving my accountā¦
Iāve transferred my app over to the new upgraded team but cannot see any of the fancy new integrations
This has not been my experience. This is the default zoom level in my test app:
This is what I would prefer - 3 clicks on the + sign
In this example there is only one data point
This is what I was referring to when I said this, so I think we are saying the same thing:
If you have 2 pins 10 feet apart, it will zoom in pretty close to encompass those pins and not much else. Pretty much close enough to see only your living room and bathroom. If Glide followed this same logic and you only had one pin, then it would zoom in far enough that you could see the color of your toothbrush. To prevent that, glide zooms out to a much wider area.
Iām not saying itās right or wrongā¦just my observation of how it works at this moment. Yes, I also agree that I would love more control of that default zoom when itās a single pin, or even multiple pins for that matter.
Have you seen the banner to join the beta? The new integrations arenāt fully released yet, but you can join the beta.
Rich text wonāt read CSS. CSS is supported but with a different method in the settings, only on Business & Enterprise.
So ,now , Classic App , are losing Css capabilities ,or not? Why Glide is doing this mess⦠, a lot of people here are not companies and have choose Glide as their NoCode solution and now this base is forgottenā¦, not really happy about it
Two Questions if possible!
1 - does this mean that updates for classic apps wonāt be happening since itās phasing out because I was going to put in a request for some small feature requests?
2 - Wondering if the switch to the new glide apps will allow us to keep our same URL, google tracking, subscriptions, QR Code, etc. I realize the full launch wonāt be available for awhile, but for future conversion, Iām more concerned with everything that my classic Glide app is connected to being seamless.