| 6 | | || '''Status''' || draft, being discussed, in progress, complete, rejected, deferred || |
| 7 | | || '''Assigned to release''' || Release number, to be determined || |
| 8 | | || '''Resources''' || Indicate if the required resources are available to complete the proposal || |
| | 6 | || '''Status''' || draft || |
| | 7 | || '''Assigned to release''' || to be determined || |
| | 8 | || '''Resources''' || ? || |
| 34 | | An in depth proposal can be found here : link |
| 35 | | ... |
| | 38 | |
| | 39 | If removing Intermap, we have to consider which features will be missing in OL, and how we can replace them. |
| | 40 | Intermap at the moment is made of different components: |
| | 41 | Map viewer (client):: |
| | 42 | The map viewer is replaced with OL. We have automatically the following features: |
| | 43 | * Zoom in/out/ |
| | 44 | * Zoom slider |
| | 45 | * Panning. |
| | 46 | We're missing some features (at least in the out-of-the-box OL version): |
| | 47 | * Zoom to full extent |
| | 48 | * Markers (Francois showed some nice alternatives indeed) |
| | 49 | Layer manager (client):: |
| | 50 | OL has a built-in layer manager, but that's more integrated in OL than in the host environment, and may not be the better choice when embedding OL somewhere. |
| | 51 | Francois showed us a layer manager implemented with [http://trac.mapfish.org/trac/mapfish MapFish], which offers some widgets aimed at map controls. This library uses Ext-JS so we may explore its use, also considering the fact that other proposals aim to the implementation in ext-js of the whole GN user interface.[[BR]] |
| | 52 | We may keep the current implementations for adding layers (server selection + layer selection). |
| | 53 | PDF builder (server):: |
| | 54 | !MapFish offers an advanced PDF builder, implemented server side via a servlet. This one could easily replace the current Intermap implementation.[[BR]] |
| | 55 | We have to consider that these server-side process will force us to use another application on the application server; that means we still have to have another application for map related processing beside Geonetwork. |
| | 56 | WMC builder (server):: |
| | 57 | In Intermap a WMC context document is built server side whenever needed. OL can create such a document client side, so we can send it to the server when needed. |
| | 58 | Mail context + thumbnail + URL w/ WMC:: |
| | 59 | In IM we can now send email containing a thumbnail of the currently visualized map, and a URL that allow to reopen the GN/IM site with the very same map content. A WMC document is also sent as attachment, should the URL be too long and the browser unable to handle it.[[BR]] |
| | 60 | We have to reimplement completely this feature; on the content side, we may send the PDF instead of the thumbnail, and the WMC document can be generated client-side by OL. [[BR]] |
| | 61 | Please note that the URL you can use to open GN/IM at a certain context is a feature we have to consider when studying other proposals aimed at making REST-like URL possibile in GN. |
| | 62 | |
| | 63 | Since OL may perform XHR toward remote servers we also need a proxy servlet to forward such requests, since browser security policies usually block them. |
