Child pages
  • Meeting 150901 (Tuesday)
Skip to end of metadata
Go to start of metadata

 

Practical

The meeting is to be held on Tuesday, September 1st @ geohub

Invitees: Oskari

Participants

Open topics last meeting(s) JIRA

http://jira.geomajas.org/secure/Dashboard.jspa?selectPageId=10150

Open topics last meeting(s) (not in JIRA)

  1. OSGEO, more collaboration with the OSGEO Java world
    1. Open question of Dirk about collaboration between java osgeo projects
  2. Scope/roadmap discussion for Oliver/Pieter/JanDM/Dirk
    1. GWT2 client, e.g. https://github.com/geomajas/geomajas-project-client-gwt2/pull/104 we really need to clear out the scope of gwt2 client, and the role of geomajas (server) in this. We should document this, and put it in the contributor guide for future references
    2. Add WFS plug-in to gwt2 client
    3. WMS
    4. Selection in featureselected deprecated, think about the interfaces
  3. Lazy loading of feature attributes: Currently, all information of feature is copied from e.g. hibernate to Feature object. Sometimes, you want only a core of info to be loaded, rest e.g. image should be lazy loaded.
    1. Primitive attribute: add boolean: lazy. Default false.
    2. Add boolean 'loadLazy' as extra attribute to functions as featureClicked
    3. Suggestion (Pieter): use different model for rendering and other functions
    4. TODO: discussion needed, with JanDM
  4. Geomajas mobile
    1. Would it be possible to go somewhat in-depth in the technical side of how mobile should be implemented?
    2. => T-days
      • Work: 
        • pinching: keep same zoom level while pinching, only get other zoom level tiles when pinching finished => one week
        • tile queue (previous work done by JanDM) => optional
    3. Can the map be used as a widget (eg. https://gitlab.geosparc.com/geosparc/sleevemonkey/blob/SMK2/example-gwt2/src/main/java/org/sleevemonkey/example/gwt2/geodesk/client/ApplicationLayout.ui.xml -> <map:MapPresenter.View ui:field='mapWidget' />)
      Expected behaviour should be that we can place this in a HtmlPanel and that it takes the full width and height + automatic resizing without outside manipulation. This way we can avoid complex gwt elements like DockedLayout, etc in our design.
      We should also avoid the use of as many complex gwt elements as possible (DockedLayouts, ResizeLayout, HorizontalPanels, VerticalePanel, etc) evenry element that add styling, tables, etc to the design.
    4. => T-day: 
      • MapWidget is absolute. 
      • MapLayout panel for resizing? 
      • Let widget extend from ResizeLayout panel?
      • TO INVESTIGATE: make ResizeLayout parent default?
      • if mapWidget in div: need to interpret sink event (Gwt does this in case of using Gwt Layouts)
      • FlowLayout creates just div (<=> DockLayout)
      • TODO: Create sample where gwt map is created in <div id="putMapWithin">
  5. Client WFS plugin Client-side WFS plugin
    • proposal by JanDM: https://github.com/geomajas/geomajas-project-client-gwt2/pull/129
    • Discussion on rendering:
      • the current implementation does not include a general feature based layer (except for the sample). Feature based layers should render vector data in some way or another. SVG is a possibility but has limitations in terms of interleaving with other, raster-based, layers. An alternative is to render everything on canvas, but than we would have to implement mouse events on features by keeping an index.

Reccuring topics

New topics

  • Dirk: Oskari
  • OSGeo Live DVD: The Geomajas application has a loader of 30 seconds. On slow PC's the Geomajas application is not started up after 30 seconds, takes longer time (Java startup). Proposal of OSGeo Live DVD Community is to extend to 40 seconds.
  • Starting technology roadmap
  • No labels

1 Comment

  1. T-days discussion:

    Dirk: Oskari // Starting technology roadmap

    Meeting Geomajas-Oskari: how to collaborate?

    Oskari Technology: Leaflet front-end; shp to table; backend: Java and Geotools.

    Front-end collaboration: clash between Oskari's js and Geomajas' Java/Gwt.

    Is a common roadmap possible (also other projects: CartoDB (ruby server side), ...)?

    Why was Geomajas not used as starting point for Oskari? Because of complexity + GWT technology not wide-spread.

    How make Geomajas a valid starting point for current start-up projects:

    • make simpler
    • document further
    • support other client technology (not GWT)
    • make simpler to add Geomajas to existing project (make dependency list smaller); 
    • Geomajas server does not have a strong API (what functions?)

    Difficult to integrate with other projects.

    What is Geomajas' core roadmap? What makes Geomajas Geomajas?

    • Enterprise customers.
    • Geodata wiki?
    • Manage enterprise geodata (domain + geo serving)

    Interoperability: more server side focus.

    INSPIRE: not develop from scratch, see other simple technologies and extend to make INSPIRE compliant. Current users of INSPIRE: academic, university.

     

    Open source collaboration in geo sector:

    • 1000+ enthousiasts in many different projects
    • Organise in complementary communities
    • server: most used: Geoserver
    • client: most used: Open Layers

     

    Organise roadmap/liveablity discussion: continue on our own or merge/collaborate with other communities.

    OSGeo Live DVD: The Geomajas application has a loader of 30 seconds. On slow PC's the Geomajas application is not started up after 30 seconds, takes longer time (Java startup). Proposal of OSGeo Live DVD Community is to extend to 40 seconds.

    ok