You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add user extensions plugin for contexts. This plugin allows to enable / disable plugins defined as userPlugins when creating a context.
Acceptance criteria
The user extensions plugin can be added from context creator.
When a context contains this plugin, an entry in burger-menu is added, called "User Extensions"
When the user clicks on "user extensions" a list of plugins is shown
plugins marked as "user plugins" are listed (flat list), checked accordingly with the "default enabled" checkbox configured in the original context by the administrator
Title description and symbology of these entries should be the same of the context creator
if the user click on one of these entries, the related plugin is added to the map
Development of user-extensions in two phases:
1st phase:
exclude MapFooter at this stage and make it compatible with georchestra too it's hard. It's strictly related with all the issues with Layout renew, therefore solving this issue means do the layout renew.
For this reason I suggest to make the footer mandatory plugin, at this stage (it's also needed to show attribution. @tdipisa please tell me if you agree with me.
I'll proceed to check issues with not instanly rendered plugins.
Description
Add user extensions plugin for contexts. This plugin allows to enable / disable plugins defined as userPlugins when creating a context.
Acceptance criteria
Development of user-extensions in two phases:
1st phase:
Other Minor fixes required:
TOC should contain plugins to add functionalities like AddLayer, FilterLayer... (Pluggable TOC to enable toolbar buttons #4719 ):
Drawer Menu add/remove together with
TOC
(Drawer Menu should not render if TOC is not present #4698)Map footer fixes:
MapFooter
enable|disable do not update immediately (MapFooter enable|disable do not update immediately #4732)The text was updated successfully, but these errors were encountered: