vladholubiev / gmmenhancer Goto Github PK

Current changelog is in pure .txt, furthermore most of it is written in Ukrainian. The goal is to leverage the power of modern-looking Markdown and translate as much as possible.

Current options page looks quite awkward. Fortunately, some new changes recently appeared in Chrome API.

[#25317 Fixed - Help extensions authors make options pages with a consistent look](Help extensions authors make options pages with a consistent look)
A new way of writing options page (only supported from Chrome 40 onwards).

As Bag Dasan and Igor Vusyk reported, there is a strange bug which happens in unknown situations. Left sidebar is empty:

Can't click on Add New button after saving any kind of objects that need an approvement. Possibly caused by styling message box.

Adding buttons directly to pages html is obsolete technique and it causes several difficulties:

• Changing page DOM has bad influence on a performance
• Ancillary buttons clutter the interface and cause troubles on small displays
• They bring a disorder to the extensions structure

The best solution is to move buttons (Templates, Short Links) to extensions popup, where the other buttons are.

• Move Short links button
• Move Templates button

It would be great if the extension could insert additional fields with translation of object name.

• Find a way to simulate a click on Add more names
• Discover if any click simulations can be replaced with html insertions
• Set up Yandex.Translate API
• Gather everything in nameTranslation.js

Igor Vusyk suggested to add some predefined default icons for templates. Now it's only possible to point a direct link to the icon.

At the earliest stage of extension development, there was a feature that allowed to review an edit in one click. Unfortunately, due to some changes in MapMakers code the feature was broken and the present goal is to recover it to the life.

Overview:
In some cases height values are added to building's Name instead of appropriate field in building parameters list item.
Also when it happens the autocompleting of duplicates is not working and user needs to hit Save manually.
I have an assumption that this issue appears when page is not loaded yet and user clicks the height button.

Example:
I got the wrong value few times in a row when pressed the 1 floor button immediately after loading the edit.

As mentioned on the official issue tracker there is a great need in this kind of feature. Editing round objects is exhausting and often ends with clumsy rough edges. So the goal is to find a way how to programmatically click on map in certain points.

As Victor Sopilnyak submitted, there is a strange bug which causes an impossibility to save an edit! Of course, he described the steps to reproduce the problem. They are pretty simple:

• Edit any object
• Save an edit. It must be published instantly
• Edit any other object
• Press Save button
• See how it isn't saving. Pressing the button yields no result.

Unfortunately, I've failed to reproduce the problem.

Nowadays it is necessary to set two intersected working hours ranges to mark a POI as working around the clock. It was considered as a routine work, thus can be done with an extension. Presumable solutions are to insert a button or a checkbox into working hours block.

Chrome has chrome.runtime.onInstalled event. It will be useful to open a page with an update summary or extensions description after it is installed. Fancy gif animations are encouraged.

• Add an event listener to a eventPage.js
• Compose and style the help and update pages
• Upload them on the server