Opened 4 years ago
Last modified 4 years ago
#20097 new enhancement
Enhance the preference dialog
| Reported by: | Klumbumbus | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | preferences | Cc: | taylor.smock |
Description
This is a follow up from #7548.
- Consider if the plugins mapillary and streetside either move their subtabs from "Display" tab to "Plugins" tab (like the plugins wikipedia and pdfimport do) or use own tabs. Subtabs of "Display" tab doesn't fit so well anymore imho.
- Switch to Jtree, JList or ... to improve the Aqua LaF workaround (ticket:7548#comment:81, ticket:7548#comment:101, ticket:7548#comment:108)
- Add a searchbox to filter the preferences to find things quicker (ticket:7548#comment:81)
Attachments (1)
Change History (9)
comment:1 by , 4 years ago
| Cc: | added |
|---|
follow-up: 3 comment:2 by , 4 years ago
I do agree that the current location (Display) no longer makes as much sense. I don't mind moving them to the Plugins tab, but I had been hoping to move the StreetSide plugin into the Mapillary plugin (I'm hoping I can just copy the URLs over for a minimally viable release -- I would need to do some more work so that StreetSide uses its own images, have its own rendering for icons, etc.). I just haven't had time for that yet. So I would prefer to create a new tab specifically for street-level imagery, but for the short term, moving both StreetSide and Mapillary to the Plugins tab are OK with me.
comment:3 by , 4 years ago
Replying to taylor.smock:
So I would prefer to create a new tab specifically for street-level imagery, but for the short term, moving both StreetSide and Mapillary to the Plugins tab are OK with me.
Sounds fine.
comment:5 by , 4 years ago
| Keywords: | preferences added |
|---|---|
| Type: | defect → enhancement |
comment:6 by , 4 years ago
Preference location for Mapillary was moved from Display to Plugins in 149dc95a88db24e12a7cb74c9ec24c347016bc3c.
The attachment:20097.streetside.patch is functionally the same as the one for the Mapillary plugin.
follow-up: 8 comment:7 by , 4 years ago
While you're at it, I don't know if you're affected by #20076 in one of the plugins you maintain.
comment:8 by , 4 years ago
Replying to Don-vip:
While you're at it, I don't know if you're affected by #20076 in one of the plugins you maintain.
As it happens, yes. I just moved MapWithAI functions into a new top-level menu, and I think my OpenQA plugin also uses a top level menu, but I haven't touched that plugin in quite some time (except for some not-quite-done changes when Osmose changed their API on me). But OpenQA might be in Data. I'll have to check that.
Potential issues for moving MapWithAI to built-in menu items:
- I am now dynamically adding/removing entries based off of location (similar to the Imagery menu), and I don't know how easy it will be for me to do that in one of the pre-built entries. Should be doable though. I hope. If not, you may see some patches. :)
- I added a preference link (again, similar to the Imagery menu) to disable/enable entries by default. This was just a convenience entry, so if I lose it, not a big deal.
Anyway, I'll think on it, and see if I can realistically move all the functions into appropriate menus.
Taylor, what do you think about the first point?