-
-
Notifications
You must be signed in to change notification settings - Fork 380
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
Toolbar placement alteration #252
Comments
I like the idea of a UI redesign. I've also been thinking along the same lines with regards to making the interface more flexible and modular. I think it will be necessary to incorporate functionality like the new expressions syntax. A few thoughts:
I'm currently working on comping up some UI/UX ideas as well. Look forward to contributing more to this discussion. Thanks for getting the ball rolling, @orangemug. |
As a frequent user of Maputnik, a feature I'd really like is two additional zoom buttons. Right now, the zoom buttons go up or down exactly one zoom level (e.g. from 15.43 to 16.43). I'd like the new buttons to go up or down to the next even zoom (e.g. from 15.43 to 16). Settings are usually made for the even zoom numbers, so I often want to get back to those after freely zooming with my scroll wheel. Not sure if this is the place for a smaller feature request, so let me know if I should move it. |
I've moved #252 (comment) to it's own ticket #256 |
Here's a quick UX comp I've been working on. I took some of the ideas from @orangemug and expanded on them. My goal is to make the layer editor more modular and incorporate the expressions syntax into layer properties. Expressions UI ideas:
It's still a work in progress, but I'd like to get some feedback from the community on the direction of this UX. |
Hey @justenPalmer lets break down your ideas a little, so we can discuss them. Plan of action, move the expression syntax discussion to issue #223. It was probably my fault this is an overly broad issue title. Here lets just discuss one topic that is getting room for more panels. Changes are better discussed piece by piece so we can implement them and track separately. It looks like the the basic approach is the same moving the toolbar vertically and to the left of the UI. |
@orangemug will do. With that in mind, I think this comp does demonstrate a slight alteration to the toolbar you made which is to place the title of the style currently being edited in the top bar. This gives the user greater context and also gives them a way to potentially go up a level and select another style to edit or create a new one. |
Thanks @justenPalmer
I'd assume that most people don't name there styles something useful until it's time to publish them. So the name probably doesn't give much context at the moment. When we finish GitHub integration we could put the repo name up top. With GitHub you're kind of forced into naming the repository at start of the journey. |
@orangemug, yeah it would be interesting to see how many users would find the name useful. When a new stylesheet gets created, we could use a default name of "Style 1" and give the user the ability to change the name. If a stylesheet gets uploaded, we could use the filename prefix as the style name. I think it's important to have a name associated with the style to help the user track that style, especially if the user has multiple styles they are concurrently modifying. |
I've created a prototype here Looking for feedback. Here are some details
|
The new UI is a very nice improvment. I like the preview/inspect button from @justenPalmer and close to the 'zoom level' makes sense. |
I'd like to suggest moving the toolbar from the top, to the left of the editor, and changing from modals to using 'panels' in the main UI.
Here are some mockups of my proposed changes (ignore the contents of the 'Layers' & 'Layer' panels).
Rather than opening modals for each action, we would instead swap out the 'panels'. So for example if I want to add a source I would
Reasons for this change are as follows
Issues
Any thoughts/feedback would be much appreciated.
The text was updated successfully, but these errors were encountered: