Updated Meetings (markdown)
+49
@@ -1,3 +1,52 @@
|
|||||||
|
## 2014-11-28 Meeting Summary
|
||||||
|
|
||||||
|
### MapQuest source bug
|
||||||
|
|
||||||
|
Andreas found a bug in the MapQuest source. He expected a major bug in the tile renderer, but it turns out to just be a configuration error for the MapQuest OSM layer. Andreas created a PR: <https://github.com/openlayers/ol3/pull/2978>.
|
||||||
|
|
||||||
|
### WebGL vector rendering
|
||||||
|
|
||||||
|
Éric mentioned that reviews are still very welcome. Guillaume from Camptocamp is looking at improving the performance. But this shouldn't block the merge of the PR.
|
||||||
|
|
||||||
|
### Custom interactions and controls
|
||||||
|
|
||||||
|
We don't currently provide a clear API for creating custom controls and interactions. We discussed what the API could be.
|
||||||
|
|
||||||
|
Currently, methods that can be implemented/overridden by developers of custom controls/interactions are declared in the `oli.js` externs file. See [`setMap`](https://github.com/openlayers/ol3/blob/9e591d21d0fb70c60f837b47ec24b8d36ef828f7/externs/oli.js#L126-L130) and [`handleMapBrowserEvent`](https://github.com/openlayers/ol3/blob/9e591d21d0fb70c60f837b47ec24b8d36ef828f7/externs/oli.js#L146-L153) in that externs file.
|
||||||
|
|
||||||
|
Another option is to rely on constructor options. For example, a custom interaction could look like this:
|
||||||
|
|
||||||
|
```js
|
||||||
|
app.CustomInteraction = function() {
|
||||||
|
ol.interaction.Interaction.call(this, {
|
||||||
|
handleEventFunction: app.CustomInteraction.prototype.handleEvent.bind(this)
|
||||||
|
});
|
||||||
|
};
|
||||||
|
ol.inherits(app.CustomInteraction, ol.interaction.Interaction);
|
||||||
|
|
||||||
|
app.CustomInteraction.prototype.handleEvent = function(e) {
|
||||||
|
// …
|
||||||
|
};
|
||||||
|
|
||||||
|
var customInteraction = new app.CustomInteraction();
|
||||||
|
```
|
||||||
|
|
||||||
|
or even this (for simple cases):
|
||||||
|
|
||||||
|
```js
|
||||||
|
var customInteraction = new ol.interaction.Interaction({
|
||||||
|
handleEventFunction: function(e) {
|
||||||
|
// …
|
||||||
|
}
|
||||||
|
});
|
||||||
|
```
|
||||||
|
|
||||||
|
We think this is better than relying on externs (in `oli.js`) as done currently. In particular we don't need to extend the docs tools, as constructor options are used for customization. This is also consistent with the `tileUrlFunction` and `tileLoadingFunction` options we have for tile sources.
|
||||||
|
|
||||||
|
### Use different CRS/SRS parameter in ImageWMS
|
||||||
|
|
||||||
|
Andreas discussed https://github.com/openlayers/ol3/issues/2966. There are cases where the view is configured with a projection whose code is not supported by the WMS server. In that case you want to be able to configure the `ImageWMS` source with the projection code supported by the WMS server, and expect that everything will work correctly. We hope that @relet will look into that.
|
||||||
|
|
||||||
## 2014-11-20 Meeting Summary
|
## 2014-11-20 Meeting Summary
|
||||||
|
|
||||||
### WebGL vector rendering
|
### WebGL vector rendering
|
||||||
|
|||||||
Reference in New Issue
Block a user