Skip to content

OpenLayers 3 Austria Code Sprint Spring 2015

Jump to bottom
Björn Harrtell edited this page Apr 2, 2015 · 42 revisions

When

March 29 - April 5, 2015

Where

JUFA Schladming. Schladming is one of the bigger ski resorts in Austria. So in addition to focused work in the beautiful seminar room of the hotel, there should be plenty opportunities to have fun (skiing, apres ski, brew pub, ...).

The closest airport is Salzburg. From Salzburg, there are direct ÖBB trains to Schladming. In Salzburg, buses (route #2) from the airport to the railway station run every 10-20 minutes. The hotel in Schladming is in walking distance from the railway station.

Who

The final number of participants must be provided by Feb. 20th, 2015.

Confirmed participants (max 10):

  • Guillaume Beraudo
  • Bart van den Eijnden
  • Andreas Hocevar
  • Marc Jansen
  • Eric Lemoine
  • Victor Malaret
  • Petr Pridal
  • Tobias Sauerwein
  • Tim Schaub
  • Björn Harrtell

Rooms

We have reservations for 2 single rooms and 4 double rooms from March 29 to April 5. The final arrival and departure dates must be provided by February 20th, 2015.

Room 603 (single)

  • Tim Schaub, arrival 3/29, departure 4/5

Room 604 (single)

  • Éric Lemoine, arrival 3/29, departure 4/5

Room 605 (double)

  • Bart van den Eijnden, arrival 3/29, departure 4/4
  • Andreas Hocevar, arrival 3/29, departure 4/4

Room 609 (double)

  • Guillaume Beraudo, arrival 3/29, departure 4/5
  • Tobias Sauerwein, arrival 3/29, departure 4/5

Room 608 (double)

  • Marc Jansen arrival 3/29, departure 4/3
  • Petr Pridal, arrival 3/29 late, departure 4/2

Room 610 (double)

  • Victor Malaret, arrival 3/29, departure 4/5
  • Björn Harrtell, arrival 4/1, departure 4/5

What

The main theme of the sprint is: "Making ol3 more user friendly". Topics to focus on include documentation, build process and API.

Ideas from Andreas:

  • Official bower distribution
  • Continue working on online build tool and server, based on https://github.com/openlayers/openlayers.github.io/pull/42.
  • Get single-file source of examples (including HTML, CSS and JS) for copy/paste
  • Improve "Getting started" docs
  • Triage, review and merge pull requests from new/occasional contributors

Ideas from Bart:

Ideas from Éric:

  • Attempt to improve the performance of tile layers by drawing tiles directly to the output canvas instead of using an intermediary canvas/framebuffer.
  • Start working on WebGL support for lines, polygons and texts.
  • For better performance use the "Immediate" API rather than the "Replay" for drawing features.
  • Continue the "tilted view" work that I started a while back.
  • Automated tests for the renderers output (https://github.com/openlayers/ol3/issues/2923).
  • User API for layer pixel/color manipulation (see Tile Image recoloring thread on the mailing list). User-provided shaders is something I'm interested in.
  • See if we can improve the performance of WebGL point by doing more stuff on the GPU.
  • Simplify/clarify our build setup, possibly by moving code from serve.js and build.js to closure-util. This will also allow for more sharing across closure-util based projects.
  • Vector tiles. Draw vector tiles without artifacts at tile boundaries with stroked polygons.
  • Binary formats for efficiently transporting large amount of vector data.
  • Improvements to the cluster source. In part. there currently is no animation, and I think this is lacking.
  • Make the API doc nicer and more convenient (use and contribute to https://github.com/documentationjs/documentation)
  • Update the examples on github.io on each push to master.
  • Add tolerance to hit detection mechanism.

Ideas from Marc

  • Start a 'Migrating-from-OpenLayers v2.13.1' document
  • Make a side by side comparison of the capabilities of OpenLayers v2 vs. v3, with the examples of v2 being providing basic structure. The goal here is to document what currently is in v3, what in the future may be in v3 and what is very unlikely to be included. That last part should possibly include hints to third party libraries or custom code to accomplish the desired.
  • Evaluate whether API-doc search can be configured to also search for keys in configuration objects

Ideas from Tim:

  • Publish a build service and a client at openlayers.org so people can create builds of the library from the web
  • Flesh out the API docs
  • Build examples from a common template, add more structured data to examples (YAML front-matter), create a better UI for searching and discovering examples
  • Discuss vector tiles and develop consensus on how vector loading should be handled
  • Write a Geobuf format
  • Render to a single map Canvas without intermediate Canvases per raster layer
  • Discuss raster reprojection

Ideas from Björn:

  • Revisit selection logic regarding multi option (#3453)
  • Improve select event to include associated information like layer (#3454)
  • High level Modify interaction events (#3461)
  • Implement SelectBox interaction (inherit from DragBox, based on box-select example) (#3465)
  • Finish GWC source implementation (useful for self-contained deploys including cached map data)
  • Write tutorial/template for browser applications that use ol3 as a dependency
  • Discuss if oli and olx could be partly/fully replaced with automated process
  • Discuss if/when ES5 getters/setters could be used and if it's possible to use them in a backward compatible way
Clone this wiki locally