Bring client-side together with server side.

[EricBoix]

An implementation of client side (GUI/JS) usage of this component is located in the UD-Viz component:

• Contribute
• DocumentComments
• DocumentValidation
• Authentication
• ...what concerns GuidedTour...

What about moving that code within this Spatial-multimedia_db repository, and make it a JS package, and import that package to UD-Viz ?

The advantages would be:

• one can GUI explore (explore with a GUI) the component usage
• keep the client side-close to the server-side because they co-evolve
• avoid polluting UD-Viz with this component (as opposed to e.g. some other implementation)

An alternative (proposed by @valentinMachado ) to the creation of a JS package would be for this server to expose its client side code to the client. UD-Viz would then dynamically (e.g. at Ud-Viz run time) download the client UI code from this server and dynamically integrate it in the UI.

Historical note

This issue use to live in UD-Serv repository

[valentinMachado]

@EricBoix actually my idea was pretty bad.. a better approach here as discussed in tech meeting would be to create inside this repository a javascript package. This package would have @ud-viz/browser as peerDependency, and would be builded in the same way as @ud-viz/browser (no css in sources, in a framework style to be reused in other project). We could also imagine to build an application base on this package in this repository to edit the database.

Here are the list of all the issues smdb related in ud-viz repo:

• Widget documents : UX Improvements  UD-Viz#507
• Linking building and documents  UD-Viz#174
• Cannot create new guided tour through the interface UD-Viz#80
• Contribute CameraPositioner widget to SMDB UD-Viz#371