-
Notifications
You must be signed in to change notification settings - Fork 13
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
Make buffer/query/theme/featureinfo/redline/quickplot work with existing fusion backend. #224
Closed
8 tasks done
Comments
jumpinjackie
added a commit
that referenced
this issue
May 8, 2017
…e/etc - Rename ajax-viewer-shim to viewer-shim as this is now a shim for both AJAX and Fusion viewer APIs - Shim enough Fusion APIs to allow theme to work - Shim enough Fusion APIs to allow buffer to work
jumpinjackie
added a commit
that referenced
this issue
May 8, 2017
… in Fusion query widget. Also change IMapViewer.queryMapFeature to allow for Partial<> query options
jumpinjackie
added a commit
that referenced
this issue
May 8, 2017
jumpinjackie
added a commit
that referenced
this issue
May 8, 2017
jumpinjackie
added a commit
that referenced
this issue
May 9, 2017
jumpinjackie
added a commit
that referenced
this issue
May 9, 2017
- Fusion.ajaxRequest - [MapWidget].digitizeLine
jumpinjackie
added a commit
that referenced
this issue
May 9, 2017
jumpinjackie
added a commit
that referenced
this issue
May 9, 2017
This allows zooming to selected features from the Fusion search widget to work.
jumpinjackie
added a commit
that referenced
this issue
May 9, 2017
…ot working against the existing Fusion backend, nuke our verbatim copy under viewer/server (except for the Task Pane placeholder page)
jumpinjackie
added a commit
that referenced
this issue
May 23, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The PHP code under
viewer/server
is a verbatim copy of the fusion backend code.Rather than duplicate a whole bunch of backend code, I think it is safe to assume Fusion is already present and that our viewer is deployed in a sibling folder to
fusion
and just redirect our buffer/query/theme/featureinfo/redline/quickplot commands to there instead.This will simplify the npm module story as we can hold onto the above assumption and not have to bundle a whole bunch of redundant PHP code (in a JS package registry!) and burden the package consumer with a whole bunch of webpack trickery to copy our version of the PHP backend to the right spot for these aformentioned tools to work.
The following tools should leverage the existing Fusion backend where possible.
As an unintentional (but useful) side-effect, this will also force us to have to shim/polyfill various parts of the current Fusion API, which will go some way towards addressing #145
The text was updated successfully, but these errors were encountered: