-
Notifications
You must be signed in to change notification settings - Fork 405
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
How to replace/insert the DefaultViewer using the plugin architecture? #1410
Comments
Hi,
You are done. |
I'm still having an issue with the viewer prop is not set. I've added "viewer": "{context.CustomViewer}" but when evaluated in PluginUtils.js parseExpression() is undefined. My CustomViewerPlugin.js is being loaded (also added it to localConfig.json). Here is the localConfig.json ( I copied the "Identify" section from another example ):
Thanks! |
Also, how do you change the info_format or format for the buildRequests from 'text/plain' to another value? There is an action changeMapInfoFormat(), but I'm going to guess that this can be configured. I think I'm almost there with my little custom viewer. Just need to get the 'viewer' prop working and change the map info format. thanks again! |
Did you add add your component in the require section of plugins.js: CustomViewer: require('/CustomViewer')? |
The simplest way to change the default info format is changing appConfig.js, there is an example for mobile mode, you can do the same for the defaultState: mapInfo: {infoFormat: 'text/html'} |
Hi mbarto,
thanks for you help! |
Hi @alturium you can send an email to the developers mailing list Regards, |
Hi Matteo, in regards to ? i'm not sure which issue or what you have in mind. -Michael |
Hi Michael, I thought you could send an email to the mailing list describing your problem and then we (the Geosolutions team) would open a issue if needed or giving you an answer on the ML. So everyone interested can access it and get the answer. |
Hi,
What is the best to use a different and custom Feature Info panel for the Identify plugin, which defaults to the DefaultViewer? There is a property for 'viewer' for Identify but I can't figure out how to best insert my viewer into the state with the current plugin architecture.
One obvious solution is to insert via a custom action/reducer to change the viewer. But when would be the best time to call this action in the setup sequences? Another solution is to create my own Identify plugin, but with the 'viewer' prop it looks like it has designed for to be extended. Plus, I don't want to maintain my own Identify, since there are 35 props being sent to it.
Part of my confusion is the plugin architecture and figuring out how it works.
Thanks ahead of time!
The text was updated successfully, but these errors were encountered: