From jolevesq at nrcan.gc.ca  Wed May  1 09:11:22 2013
From: jolevesq at nrcan.gc.ca (jolevesq)
Date: Wed, 1 May 2013 09:11:22 -0700 (PDT)
Subject: [OpenLayers-Dev] Lost panzoombar customization
Message-ID: <1367424682423-5050673.post@n6.nabble.com>

Hi,

In my application I customized the panzoombar control to add title, alt and
class attribute. Everything is working fine. When I set a new basemap with
map.setBaseLayer(map.getLayersByName(layerName)[0]); I loose all my
customization.

Is there a parameter I need to set to prevent this to happen?

Thanks

Johann Levesque



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Lost-panzoombar-customization-tp5050673.html
Sent from the OpenLayers Dev mailing list archive at Nabble.com.

From th.heuer at gmail.com  Thu May  2 16:51:04 2013
From: th.heuer at gmail.com (Tim-Hinnerk Heuer)
Date: Fri, 3 May 2013 11:51:04 +1200
Subject: [OpenLayers-Dev] ol3 - projection issues
Message-ID: <CAApG7taaLLzbXLFcAuNP579VDfwSyy8eY=asntx+yT6FhD9Tyw@mail.gmail.com>

Hi,

I'm wanting to include our WMS-V project into (at least) my development
version of ol3.  However, I have a couple of issues.  The main one is that
I cannot get our WMS to display.  Apparently, it is using the wrong EPSG
code (as verified by looking at the requests), even though I defined it
similarly to the custom projection example.

We are using EPSG:2193 which is the projection of our data and is not
trivial to change.

The relevant portion in the HTML is:

<script src="http://ourenvironment.scinfo.org.nz/js/OpenLayers/proj4js.js"
type="text/javascript"></script>
    <script src="
http://ourenvironment.scinfo.org.nz/js/OpenLayers/defs/EPSG2193.js"
type="text/javascript"></script>
    <script src="loader.js?id=wms-v" type="text/javascript"></script>

I have the following code in my example:

goog.require('ol.Attribution');
goog.require('ol.Map');
goog.require('ol.RendererHints');
goog.require('ol.View2D');
goog.require('ol.layer.ImageLayer');
goog.require('ol.projection');
goog.require('ol.source.SingleImageWMS');
goog.require('ol.source.TiledWMS');

var layers = [
  new ol.layer.TileLayer({
    source: new ol.source.TiledWMS({
      url: 'http://maps.scinfo.org.nz/basemaps/wms?',
      params: {
          'LAYERS': 'landscape_eco_painted_relief',
          'TILED': true,
          'VERSION': '1.1.1'
      },
      extent: [1000000, 4700000.0000001, 2200000, 6300000]
    })
  })
];
var projection = ol.projection.configureProj4jsProjection({
  code: 'EPSG:2193',
  extent: [1000000, 4700000.0000001, 2200000, 6300000],
  units: 'm'
});
var map = new ol.Map({
  //renderer: ol.RendererHint.CANVAS,
  renderer: ol.RendererHint.DOM,
  projection: projection,
  layers: layers,
  target: 'map',
  view: new ol.View2D({
    center: [1600000, 5500000],
    zoom: 4
  })
});

However, it doesn't work as expected.  The requests are going to for
example:
http://maps.scinfo.org.nz/basemaps/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&WIDTH=256&HEIGHT=256&LAYERS=landscape_eco_painted_relief&TILED=true&STYLES=&SRS=EPSG%3A3857&BBOX=2504688.542848654%2C5009377.085697312%2C5009377.08569731%2C7514065.628545968
which is obviously the wrong projection.

Note: When I zoom out a lot, I can see a faint hint of New Zealand, so it
seems like it could work.

Any help would be much appreciated.

Regards,
Tim

Tim-Hinnerk Heuer

Twitter: @geekdenz
Blog: http://www.thheuer.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130503/c688df25/attachment.html>

From ahocevar at opengeo.org  Mon May  6 07:52:42 2013
From: ahocevar at opengeo.org (Andreas Hocevar)
Date: Mon, 6 May 2013 16:52:42 +0200
Subject: [OpenLayers-Dev] ol3 - projection issues
In-Reply-To: <CAApG7taaLLzbXLFcAuNP579VDfwSyy8eY=asntx+yT6FhD9Tyw@mail.gmail.com>
References: <CAApG7taaLLzbXLFcAuNP579VDfwSyy8eY=asntx+yT6FhD9Tyw@mail.gmail.com>
Message-ID: <CAOiJ94is4UtRZjwozzF+4eBYH1TmDctJvdvhtP-42j8hu39dOg@mail.gmail.com>

You forgot to specify the projection in the View2D settings. See
http://ol3js.org/en/master/examples/wms-custom-proj.html for a working
example.

Also note that OL3 questions should be asked at
https://groups.google.com/d/forum/ol3-dev.

Andreas.

On Fri, May 3, 2013 at 1:51 AM, Tim-Hinnerk Heuer <th.heuer at gmail.com> wrote:
> Hi,
>
> I'm wanting to include our WMS-V project into (at least) my development
> version of ol3.  However, I have a couple of issues.  The main one is that I
> cannot get our WMS to display.  Apparently, it is using the wrong EPSG code
> (as verified by looking at the requests), even though I defined it similarly
> to the custom projection example.
>
> We are using EPSG:2193 which is the projection of our data and is not
> trivial to change.
>
> The relevant portion in the HTML is:
>
> <script src="http://ourenvironment.scinfo.org.nz/js/OpenLayers/proj4js.js"
> type="text/javascript"></script>
>     <script
> src="http://ourenvironment.scinfo.org.nz/js/OpenLayers/defs/EPSG2193.js"
> type="text/javascript"></script>
>     <script src="loader.js?id=wms-v" type="text/javascript"></script>
>
> I have the following code in my example:
>
> goog.require('ol.Attribution');
> goog.require('ol.Map');
> goog.require('ol.RendererHints');
> goog.require('ol.View2D');
> goog.require('ol.layer.ImageLayer');
> goog.require('ol.projection');
> goog.require('ol.source.SingleImageWMS');
> goog.require('ol.source.TiledWMS');
>
> var layers = [
>   new ol.layer.TileLayer({
>     source: new ol.source.TiledWMS({
>       url: 'http://maps.scinfo.org.nz/basemaps/wms?',
>       params: {
>           'LAYERS': 'landscape_eco_painted_relief',
>           'TILED': true,
>           'VERSION': '1.1.1'
>       },
>       extent: [1000000, 4700000.0000001, 2200000, 6300000]
>     })
>   })
> ];
> var projection = ol.projection.configureProj4jsProjection({
>   code: 'EPSG:2193',
>   extent: [1000000, 4700000.0000001, 2200000, 6300000],
>   units: 'm'
> });
> var map = new ol.Map({
>   //renderer: ol.RendererHint.CANVAS,
>   renderer: ol.RendererHint.DOM,
>   projection: projection,
>   layers: layers,
>   target: 'map',
>   view: new ol.View2D({
>     center: [1600000, 5500000],
>     zoom: 4
>   })
> });
>
> However, it doesn't work as expected.  The requests are going to for
> example:
> http://maps.scinfo.org.nz/basemaps/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&WIDTH=256&HEIGHT=256&LAYERS=landscape_eco_painted_relief&TILED=true&STYLES=&SRS=EPSG%3A3857&BBOX=2504688.542848654%2C5009377.085697312%2C5009377.08569731%2C7514065.628545968
> which is obviously the wrong projection.
>
> Note: When I zoom out a lot, I can see a faint hint of New Zealand, so it
> seems like it could work.
>
> Any help would be much appreciated.
>
> Regards,
> Tim
>
> Tim-Hinnerk Heuer
>
> Twitter: @geekdenz
> Blog: http://www.thheuer.com
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>



-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.

From bartvde at opengeo.org  Mon May  6 08:33:15 2013
From: bartvde at opengeo.org (Bart van den Eijnden)
Date: Mon, 6 May 2013 17:33:15 +0200
Subject: [OpenLayers-Dev] ANNOUNCEMENT: OpenLayers 2.13 RC1!
Message-ID: <021133FA-2772-4122-8F75-C1B144656623@opengeo.org>

The OpenLayers development team is proud to announce the first Release Candidate of OpenLayers 2.13.

OpenLayers 2.13 offers major improvements in various areas, with great HTML5- and CSS3-based new features.

We invite you to help us test the 2.13 release candidate! To test 2.13 in your applications, include the following tag in your OpenLayers-powered page:

<script src="http://openlayers.org/api/2.13-rc1/OpenLayers.js"></script>

As always, the source is available at http://openlayers.org/download/. Bug reports can be filed in GitHub at  https://github.com/openlayers/openlayers/issues. Please use the 2.13 label if you think you have found a regression.

The OpenLayers 2.13 release offers new features and improvements in various areas. Some of the highlights include:

Partial redesign of the Google v3 Layer
Partial redesign of Control.ModifyFeature to not use a built-in SelectFeature control, to better support mobile devices
Optional tile queueing with the introduction of OpenLayers.TileManager
Map: Animated zooming and GPU support
(Preliminary) support for IE10 touch
WPS client

It is also important to note that the 2.13 release deprecates a number of classes and functions. Applications that rely on deprecated objects now need to load the deprecated.js script.

For more information about the new features, deprecated code etc. see the release notes at [1].

Many thanks to all who have participated - and still participate - to the 2.13 release!

[1] < https://github.com/openlayers/openlayers/blob/release-2.13-rc1/notes/2.13.md>

-- 
Bart van den Eijnden
OpenGeo - http://opengeo.org
Expert service straight from the developers.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130506/2008bd91/attachment.html>

From r.mcauliffe at bom.gov.au  Mon May  6 21:09:58 2013
From: r.mcauliffe at bom.gov.au (Robert Mcauliffe)
Date: Tue, 7 May 2013 14:09:58 +1000
Subject: [OpenLayers-Dev] Submitting bug 968 [SEC=UNCLASSIFIED]
Message-ID: <122EC82C51E4074B995E23C4CC96001701018C3A81E2@BOM-VMBX-HO.bom.gov.au>

Hi Devs,

I've tried submitting a bug to OpenLayers in the past and was unsure it was 'successful', since it had no response. So I'm wondering if I need to announce them here too?

I've read http://trac.osgeo.org/openlayers/wiki/FilingTickets and followed it and submitted the following bug:

https://github.com/openlayers/openlayers/issues/968

Is there anything else I need to do?

Cheers,
Rob McAuliffe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130507/0aa511fd/attachment.html>

From ahocevar at opengeo.org  Mon May  6 22:20:57 2013
From: ahocevar at opengeo.org (Andreas Hocevar)
Date: Tue, 7 May 2013 07:20:57 +0200
Subject: [OpenLayers-Dev] Submitting bug 968 [SEC=UNCLASSIFIED]
In-Reply-To: <122EC82C51E4074B995E23C4CC96001701018C3A81E2@BOM-VMBX-HO.bom.gov.au>
References: <122EC82C51E4074B995E23C4CC96001701018C3A81E2@BOM-VMBX-HO.bom.gov.au>
Message-ID: <CAOiJ94ghi-nLiY+DO+UtFFnSxMjdxexkSBKz5FO23Zo0LJ+DyA@mail.gmail.com>

Thanks for the ticket and the notification. Sorry we missed your previous
bug report. The best way to get attention is a pull request accompanied by
a mailing list thread.

Andreas.
On May 7, 2013 6:20 AM, "Robert Mcauliffe" <r.mcauliffe at bom.gov.au> wrote:

> **
> Hi Devs,
>
> I've tried submitting a bug to OpenLayers in the past and was unsure it
> was 'successful', since it had no response. So I'm wondering if I need to
> announce them here too?
>
> I've read http://trac.osgeo.org/openlayers/wiki/FilingTickets and
> followed it and submitted the following bug:
>
> https://github.com/openlayers/openlayers/issues/968
>
> Is there anything else I need to do?
>
> Cheers,
> Rob McAuliffe
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130507/bdf67011/attachment.html>

From r.mcauliffe at bom.gov.au  Mon May  6 23:17:45 2013
From: r.mcauliffe at bom.gov.au (Robert Mcauliffe)
Date: Tue, 7 May 2013 16:17:45 +1000
Subject: [OpenLayers-Dev] Submitting bug 968 [SEC=UNCLASSIFIED]
In-Reply-To: <CAOiJ94ghi-nLiY+DO+UtFFnSxMjdxexkSBKz5FO23Zo0LJ+DyA@mail.gmail.com>
Message-ID: <122EC82C51E4074B995E23C4CC96001701018C3A81E8@BOM-VMBX-HO.bom.gov.au>

Andreas,

No worries, happy to follow whatever process works best for devs. If you're happy for me to, I'll update that FilingTickets page with that information.

Cheers,
Rob

________________________________
From: andreas.hocevar at gmail.com [mailto:andreas.hocevar at gmail.com] On Behalf Of Andreas Hocevar
Sent: Tuesday, 7 May 2013 3:21 PM
To: Robert Mcauliffe
Cc: openlayers-dev at lists.osgeo.org
Subject: Re: [OpenLayers-Dev] Submitting bug 968 [SEC=UNCLASSIFIED]


Thanks for the ticket and the notification. Sorry we missed your previous bug report. The best way to get attention is a pull request accompanied by a mailing list thread.

Andreas.

On May 7, 2013 6:20 AM, "Robert Mcauliffe" <r.mcauliffe at bom.gov.au<mailto:r.mcauliffe at bom.gov.au>> wrote:
Hi Devs,

I've tried submitting a bug to OpenLayers in the past and was unsure it was 'successful', since it had no response. So I'm wondering if I need to announce them here too?

I've read http://trac.osgeo.org/openlayers/wiki/FilingTickets and followed it and submitted the following bug:

https://github.com/openlayers/openlayers/issues/968

Is there anything else I need to do?

Cheers,
Rob McAuliffe

_______________________________________________
Dev mailing list
Dev at lists.osgeo.org<mailto:Dev at lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/openlayers-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130507/d0eaa13a/attachment.html>

From th.heuer at gmail.com  Wed May  8 03:58:56 2013
From: th.heuer at gmail.com (Tim-Hinnerk Heuer)
Date: Wed, 8 May 2013 22:58:56 +1200
Subject: [OpenLayers-Dev] ol3 - projection issues
In-Reply-To: <CAOiJ94is4UtRZjwozzF+4eBYH1TmDctJvdvhtP-42j8hu39dOg@mail.gmail.com>
References: <CAApG7taaLLzbXLFcAuNP579VDfwSyy8eY=asntx+yT6FhD9Tyw@mail.gmail.com>
	<CAOiJ94is4UtRZjwozzF+4eBYH1TmDctJvdvhtP-42j8hu39dOg@mail.gmail.com>
Message-ID: <CAApG7tYf=nQzfSMecjgUR_KpEvrObd7BFhQsdZ=2BAqxxf9cUQ@mail.gmail.com>

Yes, I noticed after I've sent it, but Eric had already answered my
question.  Thanks anyway though!

Tim-Hinnerk Heuer

Twitter: @geekdenz
Blog: http://www.thheuer.com


On 7 May 2013 02:52, Andreas Hocevar <ahocevar at opengeo.org> wrote:

> You forgot to specify the projection in the View2D settings. See
> http://ol3js.org/en/master/examples/wms-custom-proj.html for a working
> example.
>
> Also note that OL3 questions should be asked at
> https://groups.google.com/d/forum/ol3-dev.
>
> Andreas.
>
> On Fri, May 3, 2013 at 1:51 AM, Tim-Hinnerk Heuer <th.heuer at gmail.com>
> wrote:
> > Hi,
> >
> > I'm wanting to include our WMS-V project into (at least) my development
> > version of ol3.  However, I have a couple of issues.  The main one is
> that I
> > cannot get our WMS to display.  Apparently, it is using the wrong EPSG
> code
> > (as verified by looking at the requests), even though I defined it
> similarly
> > to the custom projection example.
> >
> > We are using EPSG:2193 which is the projection of our data and is not
> > trivial to change.
> >
> > The relevant portion in the HTML is:
> >
> > <script src="
> http://ourenvironment.scinfo.org.nz/js/OpenLayers/proj4js.js"
> > type="text/javascript"></script>
> >     <script
> > src="http://ourenvironment.scinfo.org.nz/js/OpenLayers/defs/EPSG2193.js"
> > type="text/javascript"></script>
> >     <script src="loader.js?id=wms-v" type="text/javascript"></script>
> >
> > I have the following code in my example:
> >
> > goog.require('ol.Attribution');
> > goog.require('ol.Map');
> > goog.require('ol.RendererHints');
> > goog.require('ol.View2D');
> > goog.require('ol.layer.ImageLayer');
> > goog.require('ol.projection');
> > goog.require('ol.source.SingleImageWMS');
> > goog.require('ol.source.TiledWMS');
> >
> > var layers = [
> >   new ol.layer.TileLayer({
> >     source: new ol.source.TiledWMS({
> >       url: 'http://maps.scinfo.org.nz/basemaps/wms?',
> >       params: {
> >           'LAYERS': 'landscape_eco_painted_relief',
> >           'TILED': true,
> >           'VERSION': '1.1.1'
> >       },
> >       extent: [1000000, 4700000.0000001, 2200000, 6300000]
> >     })
> >   })
> > ];
> > var projection = ol.projection.configureProj4jsProjection({
> >   code: 'EPSG:2193',
> >   extent: [1000000, 4700000.0000001, 2200000, 6300000],
> >   units: 'm'
> > });
> > var map = new ol.Map({
> >   //renderer: ol.RendererHint.CANVAS,
> >   renderer: ol.RendererHint.DOM,
> >   projection: projection,
> >   layers: layers,
> >   target: 'map',
> >   view: new ol.View2D({
> >     center: [1600000, 5500000],
> >     zoom: 4
> >   })
> > });
> >
> > However, it doesn't work as expected.  The requests are going to for
> > example:
> >
> http://maps.scinfo.org.nz/basemaps/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&WIDTH=256&HEIGHT=256&LAYERS=landscape_eco_painted_relief&TILED=true&STYLES=&SRS=EPSG%3A3857&BBOX=2504688.542848654%2C5009377.085697312%2C5009377.08569731%2C7514065.628545968
> > which is obviously the wrong projection.
> >
> > Note: When I zoom out a lot, I can see a faint hint of New Zealand, so it
> > seems like it could work.
> >
> > Any help would be much appreciated.
> >
> > Regards,
> > Tim
> >
> > Tim-Hinnerk Heuer
> >
> > Twitter: @geekdenz
> > Blog: http://www.thheuer.com
> >
> > _______________________________________________
> > Dev mailing list
> > Dev at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> >
>
>
>
> --
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130508/d4ceb73c/attachment.html>

From bartvde at opengeo.org  Mon May 13 04:32:03 2013
From: bartvde at opengeo.org (Bart van den Eijnden)
Date: Mon, 13 May 2013 13:32:03 +0200
Subject: [OpenLayers-Dev] ANNOUNCEMENT: OpenLayers 2.13 RC2
Message-ID: <A70408B1-135B-4B11-BECA-C30175D5790F@opengeo.org>

The OpenLayers dev team is proud to announce the 2nd release candidate of OpenLayers 2.13! RC2 comes about one week after RC1, and fixes a number of things:

 * missing @requires tag in the ModifyFeature control. #969
 * make sure OpenLayers.Util.isEquivalentUrl does not fail on comma separated arguments such as bbox for url comparisons in the TileManager. #974
 * make Feature handler propogate touch events. #955

See  https://github.com/openlayers/openlayers/issues?milestone=9&state=closed for details.

We invite you to help us test the 2.13 release candidate! To test 2.13 in your applications, include the following tag in your OpenLayers-powered page:

<script src="http://openlayers.org/api/2.13-rc2/OpenLayers.js"></script>

As always, the source is available at http://openlayers.org/download/. Bug reports can be filed in GitHub at  https://github.com/openlayers/openlayers/issues. Make sure to use the 2.13 label (and for developers, the 2.13-rc2 milestone).

Thanks!

-- 
Bart van den Eijnden
OpenGeo - http://opengeo.org
Expert service straight from the developers.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130513/1a23eb30/attachment.html>

From waelinsat at gmail.com  Tue May 14 13:57:29 2013
From: waelinsat at gmail.com (waelinsat)
Date: Tue, 14 May 2013 13:57:29 -0700 (PDT)
Subject: [OpenLayers-Dev] OpenLayers.getPixelFromLonLat don't return the
	correct values
Message-ID: <1368565049982-5053241.post@n6.nabble.com>

Hi All; 

I just need some help. It seems like the OpenLayers.getPixelFromLonLat don't
return a correct values, there's always a little difference. 

For example : 

map.getLonLatFromPixel( map.getPixelFromLonLat( new
OpenLayers.LonLat(9.55,35.23) ) ) in a normal case returns the same long/lat
which is (9.55,35.23) but this is not the result, i always had values like
9.59874, 35.60154 ... i know that it's not too far but i should resolve it. 

There 's any solution for this ? 

regards, 



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-getPixelFromLonLat-don-t-return-the-correct-values-tp5053241.html
Sent from the OpenLayers Dev mailing list archive at Nabble.com.

From th.heuer at gmail.com  Tue May 14 18:07:01 2013
From: th.heuer at gmail.com (Tim-Hinnerk Heuer)
Date: Wed, 15 May 2013 13:07:01 +1200
Subject: [OpenLayers-Dev] 2.12-dev - Delay in tile hiding
Message-ID: <CAApG7tbV=3=O1i25+wh5K54fi3rg1yJrpKLJMnfA7+XhDSUkvQ@mail.gmail.com>

Hi,

We have a problem with the latest development version of OL. While it fixed
the problem in IE10 where the map was tearing, it now has another problem:

When zooming, our top level layers' tiles are hidden with a significant
amount of delay. This results in it feeling very slow even though our WMS
delivery is very fast. In fact you can see the zoomed in tiles while the
fuzzy tiles that are at a smaller scale are still displayed. After about
3-5 seconds they get hidden correctly, but I think they should be hidden
already at the time the larger scale is displayed.

I hope this makes sense as I find it hard to put this into words.

Any help much appreciated. I don't mind fixing it myself, but I don't know
where to even look for this.

Thanks,
Tim
Tim-Hinnerk Heuer

Twitter: @geekdenz
Blog: http://www.thheuer.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130515/bd49cabf/attachment.html>

From th.heuer at gmail.com  Tue May 14 18:09:35 2013
From: th.heuer at gmail.com (Tim-Hinnerk Heuer)
Date: Wed, 15 May 2013 13:09:35 +1200
Subject: [OpenLayers-Dev] 2.12-dev - Delay in tile hiding
In-Reply-To: <CAApG7tbV=3=O1i25+wh5K54fi3rg1yJrpKLJMnfA7+XhDSUkvQ@mail.gmail.com>
References: <CAApG7tbV=3=O1i25+wh5K54fi3rg1yJrpKLJMnfA7+XhDSUkvQ@mail.gmail.com>
Message-ID: <CAApG7ta_OhEM76Xt2Bxy3k9SdTz_aHE-1-aWUDkr1P1U-DQavQ@mail.gmail.com>

To clarify:
I tried looking into the tweening of the zoom and turning it off and
playing with the settings. I even turned off tweening for panning. But both
things didn't change this behavior while the tweening was visibly off.

Any hints?

Cheers,
T

Tim-Hinnerk Heuer

Twitter: @geekdenz
Blog: http://www.thheuer.com


On 15 May 2013 13:07, Tim-Hinnerk Heuer <th.heuer at gmail.com> wrote:

> Hi,
>
> We have a problem with the latest development version of OL. While it
> fixed the problem in IE10 where the map was tearing, it now has another
> problem:
>
> When zooming, our top level layers' tiles are hidden with a significant
> amount of delay. This results in it feeling very slow even though our WMS
> delivery is very fast. In fact you can see the zoomed in tiles while the
> fuzzy tiles that are at a smaller scale are still displayed. After about
> 3-5 seconds they get hidden correctly, but I think they should be hidden
> already at the time the larger scale is displayed.
>
> I hope this makes sense as I find it hard to put this into words.
>
> Any help much appreciated. I don't mind fixing it myself, but I don't know
> where to even look for this.
>
> Thanks,
> Tim
> Tim-Hinnerk Heuer
>
> Twitter: @geekdenz
> Blog: http://www.thheuer.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130515/7f56fb81/attachment.html>

From th.heuer at gmail.com  Tue May 14 19:43:55 2013
From: th.heuer at gmail.com (Tim-Hinnerk Heuer)
Date: Wed, 15 May 2013 14:43:55 +1200
Subject: [OpenLayers-Dev] 2.12-dev - Delay in tile hiding
In-Reply-To: <CAApG7ta_OhEM76Xt2Bxy3k9SdTz_aHE-1-aWUDkr1P1U-DQavQ@mail.gmail.com>
References: <CAApG7tbV=3=O1i25+wh5K54fi3rg1yJrpKLJMnfA7+XhDSUkvQ@mail.gmail.com>
	<CAApG7ta_OhEM76Xt2Bxy3k9SdTz_aHE-1-aWUDkr1P1U-DQavQ@mail.gmail.com>
Message-ID: <CAApG7tbuSSHXCNpmeEwQcfz9rbC4t-LzaL1V6JNAyrajZNsWJA@mail.gmail.com>

To answer my own question:

I found that this can be worked around by changing the
removeBackBufferDelay
in the WMS Options:

var options = {/*...*/}
// ...
options.removeBackBufferDelay = 0;
OpenLayers.Layer.WMS(description, url, params, options);

The delay is supposed to fix a flicker, which I didn't notice. So, if you
have flicker problems, the default is 2500, but I would make it less than
that.

Comments welcome.

Cheers,
Tim

Tim-Hinnerk Heuer

Twitter: @geekdenz
Blog: http://www.thheuer.com


On 15 May 2013 13:09, Tim-Hinnerk Heuer <th.heuer at gmail.com> wrote:

> To clarify:
> I tried looking into the tweening of the zoom and turning it off and
> playing with the settings. I even turned off tweening for panning. But both
> things didn't change this behavior while the tweening was visibly off.
>
> Any hints?
>
> Cheers,
> T
>
> Tim-Hinnerk Heuer
>
> Twitter: @geekdenz
> Blog: http://www.thheuer.com
>
>
> On 15 May 2013 13:07, Tim-Hinnerk Heuer <th.heuer at gmail.com> wrote:
>
>> Hi,
>>
>> We have a problem with the latest development version of OL. While it
>> fixed the problem in IE10 where the map was tearing, it now has another
>> problem:
>>
>> When zooming, our top level layers' tiles are hidden with a significant
>> amount of delay. This results in it feeling very slow even though our WMS
>> delivery is very fast. In fact you can see the zoomed in tiles while the
>> fuzzy tiles that are at a smaller scale are still displayed. After about
>> 3-5 seconds they get hidden correctly, but I think they should be hidden
>> already at the time the larger scale is displayed.
>>
>> I hope this makes sense as I find it hard to put this into words.
>>
>> Any help much appreciated. I don't mind fixing it myself, but I don't
>> know where to even look for this.
>>
>> Thanks,
>> Tim
>> Tim-Hinnerk Heuer
>>
>> Twitter: @geekdenz
>> Blog: http://www.thheuer.com
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130515/7bfdd66f/attachment.html>

From ahocevar at opengeo.org  Wed May 15 01:31:31 2013
From: ahocevar at opengeo.org (Andreas Hocevar)
Date: Wed, 15 May 2013 10:31:31 +0200
Subject: [OpenLayers-Dev] 2.12-dev - Delay in tile hiding
In-Reply-To: <CAApG7tbuSSHXCNpmeEwQcfz9rbC4t-LzaL1V6JNAyrajZNsWJA@mail.gmail.com>
References: <CAApG7tbV=3=O1i25+wh5K54fi3rg1yJrpKLJMnfA7+XhDSUkvQ@mail.gmail.com>
	<CAApG7ta_OhEM76Xt2Bxy3k9SdTz_aHE-1-aWUDkr1P1U-DQavQ@mail.gmail.com>
	<CAApG7tbuSSHXCNpmeEwQcfz9rbC4t-LzaL1V6JNAyrajZNsWJA@mail.gmail.com>
Message-ID: <CAOiJ94i-wuMWkDYTswVB0-iAfjgjbaZ5jeZ7ND+yjh-TswX=Fw@mail.gmail.com>

For opaque layers, it should not matter what delay you use. But for
transparent layers, to get a good visual experience, you have two
options:

1) Set the removeBackBufferDelay to 0. Can cause flicker, and will
only solve the problems if all tiles are delivered very fast so they
appear in the same rendering pass.

2) Configure your layer with transitionEffect set to 'map-resize'. If
the transparent layer is an overlay, the new base layer tiles will
cover the whole map and you will not see old resolution tiles from the
overlay layer during loading.

Does this address your concerns?

Andreas.

On Wed, May 15, 2013 at 4:43 AM, Tim-Hinnerk Heuer <th.heuer at gmail.com> wrote:
> To answer my own question:
>
> I found that this can be worked around by changing the
> removeBackBufferDelay
> in the WMS Options:
>
> var options = {/*...*/}
> // ...
> options.removeBackBufferDelay = 0;
> OpenLayers.Layer.WMS(description, url, params, options);
>
> The delay is supposed to fix a flicker, which I didn't notice. So, if you
> have flicker problems, the default is 2500, but I would make it less than
> that.
>
> Comments welcome.
>
> Cheers,
> Tim
>
> Tim-Hinnerk Heuer
>
> Twitter: @geekdenz
> Blog: http://www.thheuer.com
>
>
> On 15 May 2013 13:09, Tim-Hinnerk Heuer <th.heuer at gmail.com> wrote:
>>
>> To clarify:
>> I tried looking into the tweening of the zoom and turning it off and
>> playing with the settings. I even turned off tweening for panning. But both
>> things didn't change this behavior while the tweening was visibly off.
>>
>> Any hints?
>>
>> Cheers,
>> T
>>
>> Tim-Hinnerk Heuer
>>
>> Twitter: @geekdenz
>> Blog: http://www.thheuer.com
>>
>>
>> On 15 May 2013 13:07, Tim-Hinnerk Heuer <th.heuer at gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> We have a problem with the latest development version of OL. While it
>>> fixed the problem in IE10 where the map was tearing, it now has another
>>> problem:
>>>
>>> When zooming, our top level layers' tiles are hidden with a significant
>>> amount of delay. This results in it feeling very slow even though our WMS
>>> delivery is very fast. In fact you can see the zoomed in tiles while the
>>> fuzzy tiles that are at a smaller scale are still displayed. After about 3-5
>>> seconds they get hidden correctly, but I think they should be hidden already
>>> at the time the larger scale is displayed.
>>>
>>> I hope this makes sense as I find it hard to put this into words.
>>>
>>> Any help much appreciated. I don't mind fixing it myself, but I don't
>>> know where to even look for this.
>>>
>>> Thanks,
>>> Tim
>>> Tim-Hinnerk Heuer
>>>
>>> Twitter: @geekdenz
>>> Blog: http://www.thheuer.com
>>
>>
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>



-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.

From jezaustin at gmail.com  Wed May 15 04:23:27 2013
From: jezaustin at gmail.com (jezaustin)
Date: Wed, 15 May 2013 04:23:27 -0700 (PDT)
Subject: [OpenLayers-Dev] OpenLayers.getPixelFromLonLat don't return the
	correct values
In-Reply-To: <1368565049982-5053241.post@n6.nabble.com>
References: <1368565049982-5053241.post@n6.nabble.com>
Message-ID: <1368617007869-5053372.post@n6.nabble.com>

Have you tried using map.getLayerPxFromViewPortPx? I found I needed this in
my click handlers.

map.getLonLatFromPixel(
 map.getLayerPxFromViewPortPx(
  map.getPixelFromLonLat(
   new OpenLayers.LonLat(9.55,35.23) 
  )
 )
);



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-getPixelFromLonLat-don-t-return-the-correct-values-tp5053241p5053372.html
Sent from the OpenLayers Dev mailing list archive at Nabble.com.

From ahocevar at opengeo.org  Wed May 15 04:56:20 2013
From: ahocevar at opengeo.org (Andreas Hocevar)
Date: Wed, 15 May 2013 13:56:20 +0200
Subject: [OpenLayers-Dev] OpenLayers.getPixelFromLonLat don't return the
 correct values
In-Reply-To: <1368565049982-5053241.post@n6.nabble.com>
References: <1368565049982-5053241.post@n6.nabble.com>
Message-ID: <CAOiJ94hRJvmKbxbckH=CVaNHKnYOO=wmEvCXdV5s-kgVAy6mkw@mail.gmail.com>

This is a matter of resolution. Think of a pixel and a geographic location
(o) inside the pixel:

 -------
|    o  |
|       |
|       |
 -------

This location is not in the center of the pixel. When you call
getPixelFromLonLat, you get the pixel in the above image. And when you then
call getLonLatFromPixel with the resulting pixel, you get the center of the
pixel as location:

 -------
|       |
|   o   |
|       |
 -------

This is the difference you're seeing, and there is no way to resolve it
other than doing this conversion at a resolution that is higher than your
desired accuracy of geographic coordinates.

Andreas.


On Tue, May 14, 2013 at 10:57 PM, waelinsat <waelinsat at gmail.com> wrote:

> Hi All;
>
> I just need some help. It seems like the OpenLayers.getPixelFromLonLat
> don't
> return a correct values, there's always a little difference.
>
> For example :
>
> map.getLonLatFromPixel( map.getPixelFromLonLat( new
> OpenLayers.LonLat(9.55,35.23) ) ) in a normal case returns the same
> long/lat
> which is (9.55,35.23) but this is not the result, i always had values like
> 9.59874, 35.60154 ... i know that it's not too far but i should resolve it.
>
> There 's any solution for this ?
>
> regards,
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.x6.nabble.com/OpenLayers-getPixelFromLonLat-don-t-return-the-correct-values-tp5053241.html
> Sent from the OpenLayers Dev mailing list archive at Nabble.com.
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>



-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130515/04cf4c31/attachment-0001.html>

From waelinsat at gmail.com  Fri May 17 01:38:17 2013
From: waelinsat at gmail.com (Wael Tarhouni)
Date: Fri, 17 May 2013 09:38:17 +0100
Subject: [OpenLayers-Dev] Adding Mapbox Layer with OpenLayers
Message-ID: <CAPBhV0dfM4ERNMg83J3q6ct6bEeav=K4m2V6QT63WLxLA6=6BA@mail.gmail.com>

Hi all;

I'm trying to add a based layer based on this tiles :
http://a.tiles.mapbox.com/v3/mapbox.afghanistan-grey/page.html and i found
an example in the openLayers examples which uses a Mapbox OSM Layer with
OpenLayers.Layer.XYZ. The problem is that the server which provides this
tiles don't provide all countries ...

My question is : there's any server which provides all this tiles?

-- 
Wael Tarhouni
Ing?nieur en R?seaux informatiques et T?l?communications de l'INSAT

(+216) 22 239 551
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130517/fceaaead/attachment.html>

From bartvde at opengeo.org  Fri May 17 04:27:54 2013
From: bartvde at opengeo.org (Bart van den Eijnden)
Date: Fri, 17 May 2013 13:27:54 +0200
Subject: [OpenLayers-Dev] ANNOUNCEMENT: OpenLayers 2.13 RC3
Message-ID: <E094ECFC-A82F-4B3D-BF4A-81C027E0EFB4@opengeo.org>

The OpenLayers dev team is proud to announce the 3rd release candidate of OpenLayers 2.13! RC3 comes about one week after RC2, and fixes a number of things:

 * mergeNewParams does not work with POST requests #975
 * OL 2.13rc2 layer.setVisibility() with TileManager does not always work with GeoExt 1.x #977

See https://github.com/openlayers/openlayers/issues?milestone=10&state=closed for details.

We invite you to help us test the 2.13 release candidate! To test 2.13 in your applications, include the following tag in your OpenLayers-powered page:

<script src="http://openlayers.org/api/2.13-rc3/OpenLayers.js"></script>

As always, the source is available at http://openlayers.org/download/. Bug reports can be filed in GitHub at  https://github.com/openlayers/openlayers/issues. Make sure to use the 2.13 label (and for developers, the 2.13-rc4 milestone).

Thanks!

-- 
Bart van den Eijnden
OpenGeo - http://opengeo.org
Expert service straight from the developers.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130517/dcda4965/attachment.html>

From mr at mry4n.net  Fri May 17 14:24:15 2013
From: mr at mry4n.net (Michael Ryan)
Date: Fri, 17 May 2013 17:24:15 -0400
Subject: [OpenLayers-Dev] Testing
Message-ID: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>

Hi,
I'd like to help get the following patch committed by doing testing on it. Can someone direct me to documentation on how to do this testing? I've found old info from trac.osgeo and info for OL3 on github. But I'm not sure what I'm supposed to do for OL 2.1x.
Thanks,
Mike

https://github.com/openlayers/openlayers/pull/174#ref-issue-6562621
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130517/4b20fc02/attachment.html>

From list at rdewit.net  Sat May 18 02:18:09 2013
From: list at rdewit.net (Roald de Wit)
Date: Sat, 18 May 2013 19:18:09 +1000
Subject: [OpenLayers-Dev] ANNOUNCEMENT: OpenLayers 2.13 RC3
In-Reply-To: <E094ECFC-A82F-4B3D-BF4A-81C027E0EFB4@opengeo.org>
References: <E094ECFC-A82F-4B3D-BF4A-81C027E0EFB4@opengeo.org>
Message-ID: <51974751.3070302@rdewit.net>

Hi all,

OL 2.13 is shaping up to be a great release! Thanks go to the devs for 
the hard work on it and @bartvde for being the release manager.

The new TileManager [1] is promising, especially for mobile app 
development. It is new code though and may still contain some bugs.

I would like to ask everyone, who hasn't done so yet, to test out with 
their apps with 2.13 with the TileManager enabled (*before* the final 
version has been released), especially people that use OL with GeoExt 
(GE): one bug manifested itself through GE [2] (although the cause had 
nothing to do with GE). Has anyone tested all GeoExt 1.1 examples with 
OL 2.13 yet?

Thanks,

Roald

[1] 
https://github.com/openlayers/openlayers/blob/master/notes/2.13.md#layergrid-tile-queue-and-tileloadingdelay-changes
[2] https://github.com/openlayers/openlayers/pull/974




On 17/05/13 21:27, Bart van den Eijnden wrote:
> The OpenLayers dev team is proud to announce the 3rd release candidate 
> of OpenLayers 2.13! RC3 comes about one week after RC2, and fixes a 
> number of things:
>
>  * mergeNewParams does not work with POST requests #975
>  * OL 2.13rc2 layer.setVisibility() with TileManager does not always 
> work with GeoExt 1.x #977
>
> See 
> https://github.com/openlayers/openlayers/issues?milestone=10&state=closed 
> for details.
>
> We invite you to help us test the 2.13 release candidate! To test 2.13 
> in your applications, include the following tag in your 
> OpenLayers-powered page:
>
> <script src="http://openlayers.org/api/2.13-rc3/OpenLayers.js"></script>
>
> As always, the source is available at http://openlayers.org/download/. 
> Bug reports can be filed in GitHub at 
> https://github.com/openlayers/openlayers/issues. Make sure to use the 
> 2.13 label (and for developers, the 2.13-rc4 milestone).
>
> Thanks!
>
> -- 
> Bart van den Eijnden
> OpenGeo - http://opengeo.org <http://opengeo.org/>
> Expert service straight from the developers.
>
>
>
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev


From ahocevar at opengeo.org  Sun May 19 04:20:44 2013
From: ahocevar at opengeo.org (Andreas Hocevar)
Date: Sun, 19 May 2013 13:20:44 +0200
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
Message-ID: <CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>

Hi,

thanks for willing to help out! That pull request needs unit tests. To get
started, look at the contents of the tests/ folder in the repository. The
html files in there contain test cases. It should be rather
self-explanatory how to write tests with TestAnotherWay (the test framework
used), if you are familiar with the concept of unit tests.

Andreas.


On Fri, May 17, 2013 at 11:24 PM, Michael Ryan <mr at mry4n.net> wrote:

> Hi,
> I'd like to help get the following patch committed by doing testing on it.
> Can someone direct me to documentation on how to do this testing? I've
> found old info from trac.osgeo and info for OL3 on github. But I'm not sure
> what I'm supposed to do for OL 2.1x.
> Thanks,
> Mike
>
> https://github.com/openlayers/openlayers/pull/174#ref-issue-6562621
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>
>


-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130519/153b251a/attachment.html>

From mr at mry4n.net  Mon May 20 13:12:39 2013
From: mr at mry4n.net (Michael Ryan)
Date: Mon, 20 May 2013 16:12:39 -0400
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
Message-ID: <806F2C10-4093-4639-8DA2-7F8B77A182B5@mry4n.net>

OK, I'm understanding TestAnotherWay and I'm coming up with tests. 

I was going to use a version of the feature-click example with four overlapping circles and then click all the possibilities (none, all four, just two, etc.). 

So, how do I simulate a button click in a specific location? I was looking at the test for buttonclick.html, but that  doesn't seem to be what I want. And I assume it isn't practical to use TestAnotherWay's record feature?

I'm continuing to work on this. If anyone can help me out, it would be appreciated. 

-m


On May 19, 2013, at 7:20 AM, Andreas Hocevar <ahocevar at opengeo.org> wrote:

> Hi,
> 
> thanks for willing to help out! That pull request needs unit tests. To get started, look at the contents of the tests/ folder in the repository. The html files in there contain test cases. It should be rather self-explanatory how to write tests with TestAnotherWay (the test framework used), if you are familiar with the concept of unit tests.
> 
> Andreas.
> 
> 
> On Fri, May 17, 2013 at 11:24 PM, Michael Ryan <mr at mry4n.net> wrote:
> Hi,
> I'd like to help get the following patch committed by doing testing on it. Can someone direct me to documentation on how to do this testing? I've found old info from trac.osgeo and info for OL3 on github. But I'm not sure what I'm supposed to do for OL 2.1x.
> Thanks,
> Mike
> 
> https://github.com/openlayers/openlayers/pull/174#ref-issue-6562621
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> 
> 
> 
> 
> -- 
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130520/1ff63a96/attachment.html>

From mr at mry4n.net  Mon May 20 14:04:19 2013
From: mr at mry4n.net (Michael Ryan)
Date: Mon, 20 May 2013 17:04:19 -0400
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
Message-ID: <40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>

I'll answer my question about triggering a buttonclick by saying, it looks like you use trigger() which takes coordinates as an argument as in this test:  https://github.com/drewwells/openlayers/blob/master/tests/Control/Measure.html

From mr at mry4n.net  Tue May 21 14:21:01 2013
From: mr at mry4n.net (Michael Ryan)
Date: Tue, 21 May 2013 17:21:01 -0400
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
	<40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>
Message-ID: <F7929F27-9659-4BF5-AAD9-F5A90B729D2D@mry4n.net>

While I've understood I need to use trigger() somehow, I have been unsuccessful in implementing it. 

I was using test for buttonclick as a reference: https://github.com/openlayers/openlayers/blob/master/tests/Events/buttonclick.html

I would have assumed that within the context of the featurclick example
https://github.com/openlayers/openlayers/pull/174/files

I could have used something like 

events = OpenLayers.Events(map, document.getElementById("map"));
events.triggerEvent({type: 'mousedown', xy: new OpenLayers.Pixel(0,0)}, map);
events.triggerEvent({type: 'mouseup', xy: new OpenLayers.Pixel(0,0)}, map);

But, apparently, that's wrong. 

Am I trying to do something that isn't possible? I'm assuming I'm just implementing it wrong. Any thoughts?

-Mike

On May 20, 2013, at 5:04 PM, Michael Ryan <mr at mry4n.net> wrote:

> I'll answer my question about triggering a buttonclick by saying, it looks like you use trigger() which takes coordinates as an argument as in this test:  https://github.com/drewwells/openlayers/blob/master/tests/Control/Measure.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130521/b6997fea/attachment.html>

From mr at mry4n.net  Wed May 22 07:34:24 2013
From: mr at mry4n.net (Michael Ryan)
Date: Wed, 22 May 2013 10:34:24 -0400
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <F7929F27-9659-4BF5-AAD9-F5A90B729D2D@mry4n.net>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
	<40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>
	<F7929F27-9659-4BF5-AAD9-F5A90B729D2D@mry4n.net>
Message-ID: <7BF80FB9-7BDF-415B-9E0B-CEA275A70750@mry4n.net>

Thank you Andreas for clearing up that I should assign events like so:

events = map.events

The other part of this is that you have specify that the event you are triggering is a left-click.

By tracing the code you see that you need to set the "which" attribute to 1 in the object passed to triggerEvent(), otherwise onClick in featureclick.js ignores the event. 

So, this is what my code should have looked like:

events = map.events;
events.triggerEvent( 'mousedown', {xy: new OpenLayers.Pixel(0,0), which: 1}, map);
events.triggerEvent('mouseup', {xy: new OpenLayers.Pixel(0,0), which: 1}, map);

I'm assuming I can get tests written today. Although, I'm not exactly clear how to submit them. If anyone wants to clue me in to that procedure I'd appreciate it.

-Mike

On May 21, 2013, at 5:21 PM, Michael Ryan <mr at mry4n.net> wrote:

> While I've understood I need to use trigger() somehow, I have been unsuccessful in implementing it. 
> 
> I was using test for buttonclick as a reference: https://github.com/openlayers/openlayers/blob/master/tests/Events/buttonclick.html
> 
> I would have assumed that within the context of the featurclick example
> https://github.com/openlayers/openlayers/pull/174/files
> 
> I could have used something like 
> 
> events = OpenLayers.Events(map, document.getElementById("map"));
> events.triggerEvent({type: 'mousedown', xy: new OpenLayers.Pixel(0,0)}, map);
> events.triggerEvent({type: 'mouseup', xy: new OpenLayers.Pixel(0,0)}, map);
> 
> But, apparently, that's wrong. 
> 
> Am I trying to do something that isn't possible? I'm assuming I'm just implementing it wrong. Any thoughts?
> 
> -Mike
> 
> On May 20, 2013, at 5:04 PM, Michael Ryan <mr at mry4n.net> wrote:
> 
>> I'll answer my question about triggering a buttonclick by saying, it looks like you use trigger() which takes coordinates as an argument as in this test:  https://github.com/drewwells/openlayers/blob/master/tests/Control/Measure.html
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130522/5dcad731/attachment.html>

From ahocevar at opengeo.org  Wed May 22 19:02:34 2013
From: ahocevar at opengeo.org (Andreas Hocevar)
Date: Wed, 22 May 2013 21:02:34 -0500
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <7BF80FB9-7BDF-415B-9E0B-CEA275A70750@mry4n.net>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
	<40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>
	<F7929F27-9659-4BF5-AAD9-F5A90B729D2D@mry4n.net>
	<7BF80FB9-7BDF-415B-9E0B-CEA275A70750@mry4n.net>
Message-ID: <CAOiJ94g9utR1OapD0DJ3JhVyy__SfN_2LoY5VYuPj2LkJiYcFQ@mail.gmail.com>

Hey Michael,

you should find all information on how to submit code here:
http://trac.osgeo.org/openlayers/wiki/HowToContribute. You will want to
create a pull request, as explained here:
http://trac.osgeo.org/openlayers/wiki/CreatingPatches.

I hope this helps.

Andreas.


On Wed, May 22, 2013 at 9:34 AM, Michael Ryan <mr at mry4n.net> wrote:

> Thank you Andreas for clearing up that I should assign events like so:
>
> events = map.events
>
> The other part of this is that you have specify that the event you are
> triggering is a left-click.
>
> By tracing the code you see that you need to set the "which" attribute to
> 1 in the object passed to triggerEvent(), otherwise onClick in
> featureclick.js ignores the event.
>
> So, this is what my code should have looked like:
>
> events = map.events;
> events.triggerEvent( 'mousedown', {xy: new OpenLayers.Pixel(0,0), which:
> 1}, map);
> events.triggerEvent('mouseup', {xy: new OpenLayers.Pixel(0,0), which: 1},
> map);
>
> I'm assuming I can get tests written today. Although, I'm not exactly
> clear how to submit them. If anyone wants to clue me in to that procedure
> I'd appreciate it.
>
> -Mike
>
> On May 21, 2013, at 5:21 PM, Michael Ryan <mr at mry4n.net> wrote:
>
> While I've understood I need to use trigger() somehow, I have been
> unsuccessful in implementing it.
>
> I was using test for buttonclick as a reference:
> https://github.com/openlayers/openlayers/blob/master/tests/Events/buttonclick.html
>
> I would have assumed that within the context of the featurclick example
> https://github.com/openlayers/openlayers/pull/174/files
>
> I could have used something like
>
> events = OpenLayers.Events(map, document.getElementById("map"));
> events.triggerEvent({type: 'mousedown', xy: new OpenLayers.Pixel(0,0)},
> map); events.triggerEvent({type: 'mouseup', xy: new OpenLayers.Pixel(0,0)},
> map);
>
> But, apparently, that's wrong.
>
> Am I trying to do something that isn't possible? I'm assuming I'm just
> implementing it wrong. Any thoughts?
>
> -Mike
>
> On May 20, 2013, at 5:04 PM, Michael Ryan <mr at mry4n.net> wrote:
>
> I'll answer my question about triggering a buttonclick by saying, it looks
> like you use trigger() which takes coordinates as an argument as in this
> test:
> https://github.com/drewwells/openlayers/blob/master/tests/Control/Measure.html
>
>
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>
>


-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130522/528cf184/attachment.html>

From bartvde at opengeo.org  Thu May 23 00:59:11 2013
From: bartvde at opengeo.org (Bart van den Eijnden)
Date: Thu, 23 May 2013 09:59:11 +0200
Subject: [OpenLayers-Dev] MOTION Release OpenLayers 2.13RC3 as final
Message-ID: <1C97DBC2-B442-4543-B399-C8D15844A89C@opengeo.org>

Since 2.13RC3 was released last Friday and no new issues have been reported since then, I'd like the PSC to vote on a motion to release 2.13RC3 as final.

Thanks to Andreas for all his hard work on solving the RC bugs, whilst I only had to manage the release process itself (the easy part).

Best regards,
Bart

-- 
Bart van den Eijnden
OpenGeo - http://opengeo.org
Expert service straight from the developers.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130523/e407f3da/attachment.html>

From list at rdewit.net  Thu May 23 01:25:38 2013
From: list at rdewit.net (Roald de Wit)
Date: Thu, 23 May 2013 18:25:38 +1000
Subject: [OpenLayers-Dev] MOTION Release OpenLayers 2.13RC3 as final
In-Reply-To: <1C97DBC2-B442-4543-B399-C8D15844A89C@opengeo.org>
References: <1C97DBC2-B442-4543-B399-C8D15844A89C@opengeo.org>
Message-ID: <519DD282.7000909@rdewit.net>

Hi Bart,

I'm sorry to disappoint you but one issue has been reported 5 days ago 
and has a pull request waiting (thanks to Andreas for fixing this quickly):

https://github.com/openlayers/openlayers/pull/980

Regards, Roald


On 23/05/13 17:59, Bart van den Eijnden wrote:
> Since 2.13RC3 was released last Friday and no new issues have been 
> reported since then, I'd like the PSC to vote on a motion to release 
> 2.13RC3 as final.
>
> Thanks to Andreas for all his hard work on solving the RC bugs, whilst 
> I only had to manage the release process itself (the easy part).
>
> Best regards,
> Bart
>
> -- 
> Bart van den Eijnden
> OpenGeo - http://opengeo.org <http://opengeo.org/>
> Expert service straight from the developers.
>
>
>
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130523/02aa638e/attachment.html>

From bartvde at opengeo.org  Thu May 23 01:31:52 2013
From: bartvde at opengeo.org (Bart van den Eijnden)
Date: Thu, 23 May 2013 10:31:52 +0200
Subject: [OpenLayers-Dev] MOTION Release OpenLayers 2.13RC3 as final
In-Reply-To: <519DD282.7000909@rdewit.net>
References: <1C97DBC2-B442-4543-B399-C8D15844A89C@opengeo.org>
	<519DD282.7000909@rdewit.net>
Message-ID: <C60FF6A4-49E7-4657-826A-AB5457814E74@opengeo.org>

Ah, then I take my motion back ;-)

Sorry I missed that, my github issues tab was on closed, doh.

Will work in a new RC then. Thanks for the bump.

Best regards,
Bart

-- 
Bart van den Eijnden
OpenGeo - http://opengeo.org
Expert service straight from the developers.



On May 23, 2013, at 10:25 AM, Roald de Wit <list at rdewit.net> wrote:

> Hi Bart,
> 
> I'm sorry to disappoint you but one issue has been reported 5 days ago and has a pull request waiting (thanks to Andreas for fixing this quickly):
> 
> https://github.com/openlayers/openlayers/pull/980
> 
> Regards, Roald
> 
> 
> On 23/05/13 17:59, Bart van den Eijnden wrote:
>> Since 2.13RC3 was released last Friday and no new issues have been reported since then, I'd like the PSC to vote on a motion to release 2.13RC3 as final.
>> 
>> Thanks to Andreas for all his hard work on solving the RC bugs, whilst I only had to manage the release process itself (the easy part).
>> 
>> Best regards,
>> Bart
>> 
>> -- 
>> Bart van den Eijnden
>> OpenGeo - http://opengeo.org
>> Expert service straight from the developers.
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Dev mailing list
>> Dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130523/70059670/attachment-0001.html>

From jachym.cepicky at gmail.com  Thu May 23 06:34:34 2013
From: jachym.cepicky at gmail.com (Jachym Cepicky)
Date: Thu, 23 May 2013 15:34:34 +0200
Subject: [OpenLayers-Dev] no 'addcontrol' event?
Message-ID: <519E1AEA.9000004@gmail.com>

Hi,

looking at the documentation and into Map.js, it seems, there is
'addcontrol' event fired, when new OL.Control arrives to map.


I know, it's little bit late for the next release, but it might be nice
feature to have, relatively fast to implement - any idea?

Jachym

-- 
Jachym Cepicky
Help Service - Remote Sensing s.r.o.
jachym.cepicky at gmail.com
HS-RS: jachym at hsrs.cz http://bnhelp.cz
http://les-ejk.cz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130523/fa4d0406/attachment.pgp>

From adube at mapgears.com  Thu May 23 07:32:23 2013
From: adube at mapgears.com (=?UTF-8?B?QWxleGFuZHJlIER1YsOp?=)
Date: Thu, 23 May 2013 10:32:23 -0400
Subject: [OpenLayers-Dev] no 'addcontrol' event?
In-Reply-To: <519E1AEA.9000004@gmail.com>
References: <519E1AEA.9000004@gmail.com>
Message-ID: <519E2877.7020301@mapgears.com>

Hi Jachym,

   If you extend the Map object, you could create your own event or do 
whatever you want in the addControl method directly:

MyMap = OpenLayers.Class(OpenLayers.Map, {
     addControl: function(control, px) {
         OpenLayers.Map.prototype.addControl.apply(this, arguments);

         // do whatever you want here
         // you could trigger a custom event, for example
     }
});

and use :

var map = new MyMap(/* your config*/);

HTH,

Alexandre


On 13-05-23 09:34 AM, Jachym Cepicky wrote:
> Hi,
>
> looking at the documentation and into Map.js, it seems, there is
> 'addcontrol' event fired, when new OL.Control arrives to map.
>
>
> I know, it's little bit late for the next release, but it might be nice
> feature to have, relatively fast to implement - any idea?
>
> Jachym
>
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev


-- 
Alexandre Dub?
Mapgears
www.mapgears.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130523/6828fc3f/attachment.html>

From mr at mry4n.net  Thu May 23 10:33:00 2013
From: mr at mry4n.net (Michael Ryan)
Date: Thu, 23 May 2013 13:33:00 -0400
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <CAOiJ94g9utR1OapD0DJ3JhVyy__SfN_2LoY5VYuPj2LkJiYcFQ@mail.gmail.com>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
	<40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>
	<F7929F27-9659-4BF5-AAD9-F5A90B729D2D@mry4n.net>
	<7BF80FB9-7BDF-415B-9E0B-CEA275A70750@mry4n.net>
	<CAOiJ94g9utR1OapD0DJ3JhVyy__SfN_2LoY5VYuPj2LkJiYcFQ@mail.gmail.com>
Message-ID: <3702064C-0422-4126-A9A8-A47252632FF6@mry4n.net>

Thanks for all the help, Andreas.

I'm pretty sure I can figure the contrib stuff out. 

At the moment, I'm hitting a wall with why a very simple test works if I just run the featureclick.html page, but not when I run the test function:

https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html

When I run the html page the logevt array has length 2. In the test, it's length 0. Yet I'm running the exact same code.

I know this is taking a while and I may be missing the 2.13 deadline, but I'll keep plugging away at this til I get it right. 

-Mike

On May 22, 2013, at 10:02 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:

> Hey Michael,
> 
> you should find all information on how to submit code here: http://trac.osgeo.org/openlayers/wiki/HowToContribute. You will want to create a pull request, as explained here: http://trac.osgeo.org/openlayers/wiki/CreatingPatches.
> 
> I hope this helps.
> 
> Andreas.
> 
> 
> On Wed, May 22, 2013 at 9:34 AM, Michael Ryan <mr at mry4n.net> wrote:
> Thank you Andreas for clearing up that I should assign events like so:
> 
> events = map.events
> 
> The other part of this is that you have specify that the event you are triggering is a left-click.
> 
> By tracing the code you see that you need to set the "which" attribute to 1 in the object passed to triggerEvent(), otherwise onClick in featureclick.js ignores the event. 
> 
> So, this is what my code should have looked like:
> 
> events = map.events;
> events.triggerEvent( 'mousedown', {xy: new OpenLayers.Pixel(0,0), which: 1}, map);
> events.triggerEvent('mouseup', {xy: new OpenLayers.Pixel(0,0), which: 1}, map);
> 
> I'm assuming I can get tests written today. Although, I'm not exactly clear how to submit them. If anyone wants to clue me in to that procedure I'd appreciate it.
> 
> -Mike
> 
> On May 21, 2013, at 5:21 PM, Michael Ryan <mr at mry4n.net> wrote:
> 
>> While I've understood I need to use trigger() somehow, I have been unsuccessful in implementing it. 
>> 
>> I was using test for buttonclick as a reference: https://github.com/openlayers/openlayers/blob/master/tests/Events/buttonclick.html
>> 
>> I would have assumed that within the context of the featurclick example
>> https://github.com/openlayers/openlayers/pull/174/files
>> 
>> I could have used something like 
>> 
>> events = OpenLayers.Events(map, document.getElementById("map"));
>> events.triggerEvent({type: 'mousedown', xy: new OpenLayers.Pixel(0,0)}, map);
>> events.triggerEvent({type: 'mouseup', xy: new OpenLayers.Pixel(0,0)}, map);
>> 
>> But, apparently, that's wrong. 
>> 
>> Am I trying to do something that isn't possible? I'm assuming I'm just implementing it wrong. Any thoughts?
>> 
>> -Mike
>> 
>> On May 20, 2013, at 5:04 PM, Michael Ryan <mr at mry4n.net> wrote:
>> 
>>> I'll answer my question about triggering a buttonclick by saying, it looks like you use trigger() which takes coordinates as an argument as in this test:  https://github.com/drewwells/openlayers/blob/master/tests/Control/Measure.html
>> 
> 
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> 
> 
> 
> 
> -- 
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130523/0a427d24/attachment.html>

From ahocevar at opengeo.org  Thu May 23 12:26:12 2013
From: ahocevar at opengeo.org (Andreas Hocevar)
Date: Thu, 23 May 2013 14:26:12 -0500
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <3702064C-0422-4126-A9A8-A47252632FF6@mry4n.net>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
	<40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>
	<F7929F27-9659-4BF5-AAD9-F5A90B729D2D@mry4n.net>
	<7BF80FB9-7BDF-415B-9E0B-CEA275A70750@mry4n.net>
	<CAOiJ94g9utR1OapD0DJ3JhVyy__SfN_2LoY5VYuPj2LkJiYcFQ@mail.gmail.com>
	<3702064C-0422-4126-A9A8-A47252632FF6@mry4n.net>
Message-ID: <CAOiJ94jA4s0+GWZZVgx4xVeRwckvuNjfWXNrg_o5FXNyw6m9ow@mail.gmail.com>

I think the problem is that your init() function won't be called when the
page is loaded by the test runner. So you'll have to call init() from the
test function (test_onClick12 in the current code).

Andreas.


On Thu, May 23, 2013 at 12:33 PM, Michael Ryan <mr at mry4n.net> wrote:

> Thanks for all the help, Andreas.
>
> I'm pretty sure I can figure the contrib stuff out.
>
> At the moment, I'm hitting a wall with why a very simple test works if I
> just run the featureclick.html page, but not when I run the test function:
>
>
> https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html
>
> When I run the html page the logevt array has length 2. In the test, it's
> length 0. Yet I'm running the exact same code.
>
> I know this is taking a while and I may be missing the 2.13 deadline, but
> I'll keep plugging away at this til I get it right.
>
> -Mike
>
> On May 22, 2013, at 10:02 PM, Andreas Hocevar <ahocevar at opengeo.org>
> wrote:
>
> Hey Michael,
>
> you should find all information on how to submit code here:
> http://trac.osgeo.org/openlayers/wiki/HowToContribute. You will want to
> create a pull request, as explained here:
> http://trac.osgeo.org/openlayers/wiki/CreatingPatches.
>
> I hope this helps.
>
> Andreas.
>
>
> On Wed, May 22, 2013 at 9:34 AM, Michael Ryan <mr at mry4n.net> wrote:
>
>> Thank you Andreas for clearing up that I should assign events like so:
>>
>> events = map.events
>>
>> The other part of this is that you have specify that the event you are
>> triggering is a left-click.
>>
>> By tracing the code you see that you need to set the "which" attribute to
>> 1 in the object passed to triggerEvent(), otherwise onClick in
>> featureclick.js ignores the event.
>>
>> So, this is what my code should have looked like:
>>
>> events = map.events;
>> events.triggerEvent( 'mousedown', {xy: new OpenLayers.Pixel(0,0), which:
>> 1}, map);
>> events.triggerEvent('mouseup', {xy: new OpenLayers.Pixel(0,0), which: 1},
>> map);
>>
>> I'm assuming I can get tests written today. Although, I'm not exactly
>> clear how to submit them. If anyone wants to clue me in to that procedure
>> I'd appreciate it.
>>
>> -Mike
>>
>> On May 21, 2013, at 5:21 PM, Michael Ryan <mr at mry4n.net> wrote:
>>
>> While I've understood I need to use trigger() somehow, I have been
>> unsuccessful in implementing it.
>>
>> I was using test for buttonclick as a reference:
>> https://github.com/openlayers/openlayers/blob/master/tests/Events/buttonclick.html
>>
>> I would have assumed that within the context of the featurclick example
>> https://github.com/openlayers/openlayers/pull/174/files
>>
>> I could have used something like
>>
>> events = OpenLayers.Events(map, document.getElementById("map"));
>> events.triggerEvent({type: 'mousedown', xy: new OpenLayers.Pixel(0,0)},
>> map); events.triggerEvent({type: 'mouseup', xy: new OpenLayers.Pixel(0,0)},
>> map);
>>
>> But, apparently, that's wrong.
>>
>> Am I trying to do something that isn't possible? I'm assuming I'm just
>> implementing it wrong. Any thoughts?
>>
>> -Mike
>>
>> On May 20, 2013, at 5:04 PM, Michael Ryan <mr at mry4n.net> wrote:
>>
>> I'll answer my question about triggering a buttonclick by saying, it
>> looks like you use trigger() which takes coordinates as an argument as in
>> this test:
>> https://github.com/drewwells/openlayers/blob/master/tests/Control/Measure.html
>>
>>
>>
>>
>> _______________________________________________
>> Dev mailing list
>> Dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>>
>>
>
>
> --
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.
>
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>
>


-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130523/8d701ed4/attachment.html>

From mr at mry4n.net  Thu May 23 14:30:21 2013
From: mr at mry4n.net (Michael Ryan)
Date: Thu, 23 May 2013 17:30:21 -0400
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <CAOiJ94jA4s0+GWZZVgx4xVeRwckvuNjfWXNrg_o5FXNyw6m9ow@mail.gmail.com>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
	<40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>
	<F7929F27-9659-4BF5-AAD9-F5A90B729D2D@mry4n.net>
	<7BF80FB9-7BDF-415B-9E0B-CEA275A70750@mry4n.net>
	<CAOiJ94g9utR1OapD0DJ3JhVyy__SfN_2LoY5VYuPj2LkJiYcFQ@mail.gmail.com>
	<3702064C-0422-4126-A9A8-A47252632FF6@mry4n.net>
	<CAOiJ94jA4s0+GWZZVgx4xVeRwckvuNjfWXNrg_o5FXNyw6m9ow@mail.gmail.com>
Message-ID: <BF778A30-951D-4333-9309-8B732F9F3E67@mry4n.net>

I checked that out, but that didn't seem to be it. I noticed in buttonclick.html that it just uses onload=init() in the body tag and doesn't call init() in any of the test functions.

However, it seems ilke I have to add the featureclick event and assign it a function with parantheses, whereas running it in the html requires no parentheses. 

So the test function now looks like this:

function test_onClick23(t) {
	t.plan(1);
	logevt = [];
	map.events.on({featureclick: logEvent()});
	events = map.events;
	lonlat = new OpenLayers.LonLat(0,0);
	pixel = map.getPixelFromLonLat(lonlat);
	trigger('mousedown', pixel);
	trigger('mouseup', pixel);
	t.eq(logevt.length, 2, "testing log length");
	t.wait_result( 3 );
}

and the logEvent function is:

function logEvent(e) {

	//alert("Does this happen?");
	logevt.push(e);
}

https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html

The problem is that no matter how many features I add, the logevt array is length 1.

I tried using the t.wait_result() function, taking a wild stab that since a featureclick event gets fired for each feature that maybe there's some timing issue that gets taken care of when you view featureclick.html but needs to be accounted for in testing. Unfortunately, t.wait_result() didn't change anything.

-Mike

On May 23, 2013, at 3:26 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:

> I think the problem is that your init() function won't be called when the page is loaded by the test runner. So you'll have to call init() from the test function (test_onClick12 in the current code).
> 
> Andreas.
> 
> 
> On Thu, May 23, 2013 at 12:33 PM, Michael Ryan <mr at mry4n.net> wrote:
> Thanks for all the help, Andreas.
> 
> I'm pretty sure I can figure the contrib stuff out. 
> 
> At the moment, I'm hitting a wall with why a very simple test works if I just run the featureclick.html page, but not when I run the test function:
> 
> https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html
> 
> When I run the html page the logevt array has length 2. In the test, it's length 0. Yet I'm running the exact same code.
> 
> I know this is taking a while and I may be missing the 2.13 deadline, but I'll keep plugging away at this til I get it right. 
> 
> -Mike
> 
> On May 22, 2013, at 10:02 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:
> 
>> Hey Michael,
>> 
>> you should find all information on how to submit code here: http://trac.osgeo.org/openlayers/wiki/HowToContribute. You will want to create a pull request, as explained here: http://trac.osgeo.org/openlayers/wiki/CreatingPatches.
>> 
>> I hope this helps.
>> 
>> Andreas.
>> 
>> 
>> On Wed, May 22, 2013 at 9:34 AM, Michael Ryan <mr at mry4n.net> wrote:
>> Thank you Andreas for clearing up that I should assign events like so:
>> 
>> events = map.events
>> 
>> The other part of this is that you have specify that the event you are triggering is a left-click.
>> 
>> By tracing the code you see that you need to set the "which" attribute to 1 in the object passed to triggerEvent(), otherwise onClick in featureclick.js ignores the event. 
>> 
>> So, this is what my code should have looked like:
>> 
>> events = map.events;
>> events.triggerEvent( 'mousedown', {xy: new OpenLayers.Pixel(0,0), which: 1}, map);
>> events.triggerEvent('mouseup', {xy: new OpenLayers.Pixel(0,0), which: 1}, map);
>> 
>> I'm assuming I can get tests written today. Although, I'm not exactly clear how to submit them. If anyone wants to clue me in to that procedure I'd appreciate it.
>> 
>> -Mike
>> 
>> On May 21, 2013, at 5:21 PM, Michael Ryan <mr at mry4n.net> wrote:
>> 
>>> While I've understood I need to use trigger() somehow, I have been unsuccessful in implementing it. 
>>> 
>>> I was using test for buttonclick as a reference: https://github.com/openlayers/openlayers/blob/master/tests/Events/buttonclick.html
>>> 
>>> I would have assumed that within the context of the featurclick example
>>> https://github.com/openlayers/openlayers/pull/174/files
>>> 
>>> I could have used something like 
>>> 
>>> events = OpenLayers.Events(map, document.getElementById("map"));
>>> events.triggerEvent({type: 'mousedown', xy: new OpenLayers.Pixel(0,0)}, map);
>>> events.triggerEvent({type: 'mouseup', xy: new OpenLayers.Pixel(0,0)}, map);
>>> 
>>> But, apparently, that's wrong. 
>>> 
>>> Am I trying to do something that isn't possible? I'm assuming I'm just implementing it wrong. Any thoughts?
>>> 
>>> -Mike
>>> 
>>> On May 20, 2013, at 5:04 PM, Michael Ryan <mr at mry4n.net> wrote:
>>> 
>>>> I'll answer my question about triggering a buttonclick by saying, it looks like you use trigger() which takes coordinates as an argument as in this test:  https://github.com/drewwells/openlayers/blob/master/tests/Control/Measure.html
>>> 
>> 
>> 
>> _______________________________________________
>> Dev mailing list
>> Dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>> 
>> 
>> 
>> 
>> -- 
>> Andreas Hocevar
>> OpenGeo - http://opengeo.org/
>> Expert service straight from the developers.
> 
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> 
> 
> 
> 
> -- 
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130523/c39df22b/attachment-0001.html>

From ahocevar at opengeo.org  Thu May 23 15:20:13 2013
From: ahocevar at opengeo.org (Andreas Hocevar)
Date: Thu, 23 May 2013 17:20:13 -0500
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <BF778A30-951D-4333-9309-8B732F9F3E67@mry4n.net>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
	<40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>
	<F7929F27-9659-4BF5-AAD9-F5A90B729D2D@mry4n.net>
	<7BF80FB9-7BDF-415B-9E0B-CEA275A70750@mry4n.net>
	<CAOiJ94g9utR1OapD0DJ3JhVyy__SfN_2LoY5VYuPj2LkJiYcFQ@mail.gmail.com>
	<3702064C-0422-4126-A9A8-A47252632FF6@mry4n.net>
	<CAOiJ94jA4s0+GWZZVgx4xVeRwckvuNjfWXNrg_o5FXNyw6m9ow@mail.gmail.com>
	<BF778A30-951D-4333-9309-8B732F9F3E67@mry4n.net>
Message-ID: <CANrS==M3gKEAU1PF-FFri0LW4Wj8e+K7pC4ckN4M45jyGpO01Q@mail.gmail.com>

Right now you are calling logEvent() once, and you're doing so when
you define the listener:

    map.events.on({featureclick: logEvent()});

Instead, this should read

    map.events.on({featureclick: logEvent});

Andreas.

On Thu, May 23, 2013 at 4:30 PM, Michael Ryan <mr at mry4n.net> wrote:
> I checked that out, but that didn't seem to be it. I noticed in
> buttonclick.html that it just uses onload=init() in the body tag and doesn't
> call init() in any of the test functions.
>
> However, it seems ilke I have to add the featureclick event and assign it a
> function with parantheses, whereas running it in the html requires no
> parentheses.
>
> So the test function now looks like this:
>
> function test_onClick23(t) {
> t.plan(1);
> logevt = [];
> map.events.on({featureclick: logEvent()});
> events = map.events;
> lonlat = new OpenLayers.LonLat(0,0);
> pixel = map.getPixelFromLonLat(lonlat);
> trigger('mousedown', pixel);
> trigger('mouseup', pixel);
> t.eq(logevt.length, 2, "testing log length");
> t.wait_result( 3 );
> }
>
> and the logEvent function is:
>
> function logEvent(e) {
>
> //alert("Does this happen?");
> logevt.push(e);
> }
>
> https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html
>
> The problem is that no matter how many features I add, the logevt array is
> length 1.
>
> I tried using the t.wait_result() function, taking a wild stab that since a
> featureclick event gets fired for each feature that maybe there's some
> timing issue that gets taken care of when you view featureclick.html but
> needs to be accounted for in testing. Unfortunately, t.wait_result() didn't
> change anything.
>
> -Mike
>
> On May 23, 2013, at 3:26 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:
>
> I think the problem is that your init() function won't be called when the
> page is loaded by the test runner. So you'll have to call init() from the
> test function (test_onClick12 in the current code).
>
> Andreas.
>
>
> On Thu, May 23, 2013 at 12:33 PM, Michael Ryan <mr at mry4n.net> wrote:
>>
>> Thanks for all the help, Andreas.
>>
>> I'm pretty sure I can figure the contrib stuff out.
>>
>> At the moment, I'm hitting a wall with why a very simple test works if I
>> just run the featureclick.html page, but not when I run the test function:
>>
>>
>> https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html
>>
>> When I run the html page the logevt array has length 2. In the test, it's
>> length 0. Yet I'm running the exact same code.
>>
>> I know this is taking a while and I may be missing the 2.13 deadline, but
>> I'll keep plugging away at this til I get it right.
>>
>> -Mike
>>
>> On May 22, 2013, at 10:02 PM, Andreas Hocevar <ahocevar at opengeo.org>
>> wrote:
>>
>> Hey Michael,
>>
>> you should find all information on how to submit code here:
>> http://trac.osgeo.org/openlayers/wiki/HowToContribute. You will want to
>> create a pull request, as explained here:
>> http://trac.osgeo.org/openlayers/wiki/CreatingPatches.
>>
>> I hope this helps.
>>
>> Andreas.
>>
>>
>> On Wed, May 22, 2013 at 9:34 AM, Michael Ryan <mr at mry4n.net> wrote:
>>>
>>> Thank you Andreas for clearing up that I should assign events like so:
>>>
>>> events = map.events
>>>
>>> The other part of this is that you have specify that the event you are
>>> triggering is a left-click.
>>>
>>> By tracing the code you see that you need to set the "which" attribute to
>>> 1 in the object passed to triggerEvent(), otherwise onClick in
>>> featureclick.js ignores the event.
>>>
>>> So, this is what my code should have looked like:
>>>
>>> events = map.events;
>>> events.triggerEvent( 'mousedown', {xy: new OpenLayers.Pixel(0,0), which:
>>> 1}, map);
>>> events.triggerEvent('mouseup', {xy: new OpenLayers.Pixel(0,0), which: 1},
>>> map);
>>>
>>> I'm assuming I can get tests written today. Although, I'm not exactly
>>> clear how to submit them. If anyone wants to clue me in to that procedure
>>> I'd appreciate it.
>>>
>>> -Mike
>>>
>>> On May 21, 2013, at 5:21 PM, Michael Ryan <mr at mry4n.net> wrote:
>>>
>>> While I've understood I need to use trigger() somehow, I have been
>>> unsuccessful in implementing it.
>>>
>>> I was using test for buttonclick as a reference:
>>> https://github.com/openlayers/openlayers/blob/master/tests/Events/buttonclick.html
>>>
>>> I would have assumed that within the context of the featurclick example
>>> https://github.com/openlayers/openlayers/pull/174/files
>>>
>>> I could have used something like
>>>
>>> events = OpenLayers.Events(map, document.getElementById("map"));
>>> events.triggerEvent({type: 'mousedown', xy: new OpenLayers.Pixel(0,0)},
>>> map); events.triggerEvent({type: 'mouseup', xy: new OpenLayers.Pixel(0,0)},
>>> map);
>>>
>>> But, apparently, that's wrong.
>>>
>>> Am I trying to do something that isn't possible? I'm assuming I'm just
>>> implementing it wrong. Any thoughts?
>>>
>>> -Mike
>>>
>>> On May 20, 2013, at 5:04 PM, Michael Ryan <mr at mry4n.net> wrote:
>>>
>>> I'll answer my question about triggering a buttonclick by saying, it
>>> looks like you use trigger() which takes coordinates as an argument as in
>>> this test:
>>> https://github.com/drewwells/openlayers/blob/master/tests/Control/Measure.html
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> Dev at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>>>
>>
>>
>>
>> --
>> Andreas Hocevar
>> OpenGeo - http://opengeo.org/
>> Expert service straight from the developers.
>>
>>
>>
>> _______________________________________________
>> Dev mailing list
>> Dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>>
>
>
>
> --
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.
>
>



-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.

From ahocevar at opengeo.org  Thu May 23 15:31:26 2013
From: ahocevar at opengeo.org (Andreas Hocevar)
Date: Thu, 23 May 2013 17:31:26 -0500
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <CANrS==M3gKEAU1PF-FFri0LW4Wj8e+K7pC4ckN4M45jyGpO01Q@mail.gmail.com>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
	<40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>
	<F7929F27-9659-4BF5-AAD9-F5A90B729D2D@mry4n.net>
	<7BF80FB9-7BDF-415B-9E0B-CEA275A70750@mry4n.net>
	<CAOiJ94g9utR1OapD0DJ3JhVyy__SfN_2LoY5VYuPj2LkJiYcFQ@mail.gmail.com>
	<3702064C-0422-4126-A9A8-A47252632FF6@mry4n.net>
	<CAOiJ94jA4s0+GWZZVgx4xVeRwckvuNjfWXNrg_o5FXNyw6m9ow@mail.gmail.com>
	<BF778A30-951D-4333-9309-8B732F9F3E67@mry4n.net>
	<CANrS==M3gKEAU1PF-FFri0LW4Wj8e+K7pC4ckN4M45jyGpO01Q@mail.gmail.com>
Message-ID: <CAOiJ94ghdHkPJ3JVf6ap2-jYEbD2ha5skXODuUNMutWOt-tVqQ@mail.gmail.com>

But the real problem is that the clientX and clientY in your mock events is
relative to the map viewport, but should be relative to the browser
viewport. You'll need to use OpenLayers.Util.pagePosition to get the
position of the map's viewportDiv and add that to the  pixel coordinate you
are currently using.

Andreas.


On Thu, May 23, 2013 at 5:20 PM, Andreas Hocevar <ahocevar at opengeo.org>wrote:

> Right now you are calling logEvent() once, and you're doing so when
> you define the listener:
>
>     map.events.on({featureclick: logEvent()});
>
> Instead, this should read
>
>     map.events.on({featureclick: logEvent});
>
> Andreas.
>
> On Thu, May 23, 2013 at 4:30 PM, Michael Ryan <mr at mry4n.net> wrote:
> > I checked that out, but that didn't seem to be it. I noticed in
> > buttonclick.html that it just uses onload=init() in the body tag and
> doesn't
> > call init() in any of the test functions.
> >
> > However, it seems ilke I have to add the featureclick event and assign
> it a
> > function with parantheses, whereas running it in the html requires no
> > parentheses.
> >
> > So the test function now looks like this:
> >
> > function test_onClick23(t) {
> > t.plan(1);
> > logevt = [];
> > map.events.on({featureclick: logEvent()});
> > events = map.events;
> > lonlat = new OpenLayers.LonLat(0,0);
> > pixel = map.getPixelFromLonLat(lonlat);
> > trigger('mousedown', pixel);
> > trigger('mouseup', pixel);
> > t.eq(logevt.length, 2, "testing log length");
> > t.wait_result( 3 );
> > }
> >
> > and the logEvent function is:
> >
> > function logEvent(e) {
> >
> > //alert("Does this happen?");
> > logevt.push(e);
> > }
> >
> >
> https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html
> >
> > The problem is that no matter how many features I add, the logevt array
> is
> > length 1.
> >
> > I tried using the t.wait_result() function, taking a wild stab that
> since a
> > featureclick event gets fired for each feature that maybe there's some
> > timing issue that gets taken care of when you view featureclick.html but
> > needs to be accounted for in testing. Unfortunately, t.wait_result()
> didn't
> > change anything.
> >
> > -Mike
> >
> > On May 23, 2013, at 3:26 PM, Andreas Hocevar <ahocevar at opengeo.org>
> wrote:
> >
> > I think the problem is that your init() function won't be called when the
> > page is loaded by the test runner. So you'll have to call init() from the
> > test function (test_onClick12 in the current code).
> >
> > Andreas.
> >
> >
> > On Thu, May 23, 2013 at 12:33 PM, Michael Ryan <mr at mry4n.net> wrote:
> >>
> >> Thanks for all the help, Andreas.
> >>
> >> I'm pretty sure I can figure the contrib stuff out.
> >>
> >> At the moment, I'm hitting a wall with why a very simple test works if I
> >> just run the featureclick.html page, but not when I run the test
> function:
> >>
> >>
> >>
> https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html
> >>
> >> When I run the html page the logevt array has length 2. In the test,
> it's
> >> length 0. Yet I'm running the exact same code.
> >>
> >> I know this is taking a while and I may be missing the 2.13 deadline,
> but
> >> I'll keep plugging away at this til I get it right.
> >>
> >> -Mike
> >>
> >> On May 22, 2013, at 10:02 PM, Andreas Hocevar <ahocevar at opengeo.org>
> >> wrote:
> >>
> >> Hey Michael,
> >>
> >> you should find all information on how to submit code here:
> >> http://trac.osgeo.org/openlayers/wiki/HowToContribute. You will want to
> >> create a pull request, as explained here:
> >> http://trac.osgeo.org/openlayers/wiki/CreatingPatches.
> >>
> >> I hope this helps.
> >>
> >> Andreas.
> >>
> >>
> >> On Wed, May 22, 2013 at 9:34 AM, Michael Ryan <mr at mry4n.net> wrote:
> >>>
> >>> Thank you Andreas for clearing up that I should assign events like so:
> >>>
> >>> events = map.events
> >>>
> >>> The other part of this is that you have specify that the event you are
> >>> triggering is a left-click.
> >>>
> >>> By tracing the code you see that you need to set the "which" attribute
> to
> >>> 1 in the object passed to triggerEvent(), otherwise onClick in
> >>> featureclick.js ignores the event.
> >>>
> >>> So, this is what my code should have looked like:
> >>>
> >>> events = map.events;
> >>> events.triggerEvent( 'mousedown', {xy: new OpenLayers.Pixel(0,0),
> which:
> >>> 1}, map);
> >>> events.triggerEvent('mouseup', {xy: new OpenLayers.Pixel(0,0), which:
> 1},
> >>> map);
> >>>
> >>> I'm assuming I can get tests written today. Although, I'm not exactly
> >>> clear how to submit them. If anyone wants to clue me in to that
> procedure
> >>> I'd appreciate it.
> >>>
> >>> -Mike
> >>>
> >>> On May 21, 2013, at 5:21 PM, Michael Ryan <mr at mry4n.net> wrote:
> >>>
> >>> While I've understood I need to use trigger() somehow, I have been
> >>> unsuccessful in implementing it.
> >>>
> >>> I was using test for buttonclick as a reference:
> >>>
> https://github.com/openlayers/openlayers/blob/master/tests/Events/buttonclick.html
> >>>
> >>> I would have assumed that within the context of the featurclick example
> >>> https://github.com/openlayers/openlayers/pull/174/files
> >>>
> >>> I could have used something like
> >>>
> >>> events = OpenLayers.Events(map, document.getElementById("map"));
> >>> events.triggerEvent({type: 'mousedown', xy: new OpenLayers.Pixel(0,0)},
> >>> map); events.triggerEvent({type: 'mouseup', xy: new
> OpenLayers.Pixel(0,0)},
> >>> map);
> >>>
> >>> But, apparently, that's wrong.
> >>>
> >>> Am I trying to do something that isn't possible? I'm assuming I'm just
> >>> implementing it wrong. Any thoughts?
> >>>
> >>> -Mike
> >>>
> >>> On May 20, 2013, at 5:04 PM, Michael Ryan <mr at mry4n.net> wrote:
> >>>
> >>> I'll answer my question about triggering a buttonclick by saying, it
> >>> looks like you use trigger() which takes coordinates as an argument as
> in
> >>> this test:
> >>>
> https://github.com/drewwells/openlayers/blob/master/tests/Control/Measure.html
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Dev mailing list
> >>> Dev at lists.osgeo.org
> >>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Andreas Hocevar
> >> OpenGeo - http://opengeo.org/
> >> Expert service straight from the developers.
> >>
> >>
> >>
> >> _______________________________________________
> >> Dev mailing list
> >> Dev at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> >>
> >
> >
> >
> > --
> > Andreas Hocevar
> > OpenGeo - http://opengeo.org/
> > Expert service straight from the developers.
> >
> >
>
>
>
> --
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>



-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130523/e45edcf7/attachment.html>

From mr at mry4n.net  Thu May 23 17:50:21 2013
From: mr at mry4n.net (Michael Ryan)
Date: Thu, 23 May 2013 20:50:21 -0400
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <CAOiJ94ghdHkPJ3JVf6ap2-jYEbD2ha5skXODuUNMutWOt-tVqQ@mail.gmail.com>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
	<40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>
	<F7929F27-9659-4BF5-AAD9-F5A90B729D2D@mry4n.net>
	<7BF80FB9-7BDF-415B-9E0B-CEA275A70750@mry4n.net>
	<CAOiJ94g9utR1OapD0DJ3JhVyy__SfN_2LoY5VYuPj2LkJiYcFQ@mail.gmail.com>
	<3702064C-0422-4126-A9A8-A47252632FF6@mry4n.net>
	<CAOiJ94jA4s0+GWZZVgx4xVeRwckvuNjfWXNrg_o5FXNyw6m9ow@mail.gmail.com>
	<BF778A30-951D-4333-9309-8B732F9F3E67@mry4n.net>
	<CANrS==M3gKEAU1PF-FFri0LW4Wj8e+K7pC4ckN4M45jyGpO01Q@mail.gmail.com>
	<CAOiJ94ghdHkPJ3JVf6ap2-jYEbD2ha5skXODuUNMutWOt-tVqQ@mail.gmail.com>
Message-ID: <E3A336C0-D3D2-4572-80E1-37641A3AE624@mry4n.net>

Added pagePosition and set featureclick to logEvent in the test and get the same result where it works in the html page but not in the testing function:

https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html

-Mike

On May 23, 2013, at 6:31 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:

> But the real problem is that the clientX and clientY in your mock events is relative to the map viewport, but should be relative to the browser viewport. You'll need to use OpenLayers.Util.pagePosition to get the position of the map's viewportDiv and add that to the  pixel coordinate you are currently using.
> 
> Andreas.
> 
> 
> On Thu, May 23, 2013 at 5:20 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:
> Right now you are calling logEvent() once, and you're doing so when
> you define the listener:
> 
>     map.events.on({featureclick: logEvent()});
> 
> Instead, this should read
> 
>     map.events.on({featureclick: logEvent});
> 
> Andreas.
> 
> On Thu, May 23, 2013 at 4:30 PM, Michael Ryan <mr at mry4n.net> wrote:
> > I checked that out, but that didn't seem to be it. I noticed in
> > buttonclick.html that it just uses onload=init() in the body tag and doesn't
> > call init() in any of the test functions.
> >
> > However, it seems ilke I have to add the featureclick event and assign it a
> > function with parantheses, whereas running it in the html requires no
> > parentheses.
> >
> > So the test function now looks like this:
> >
> > function test_onClick23(t) {
> > t.plan(1);
> > logevt = [];
> > map.events.on({featureclick: logEvent()});
> > events = map.events;
> > lonlat = new OpenLayers.LonLat(0,0);
> > pixel = map.getPixelFromLonLat(lonlat);
> > trigger('mousedown', pixel);
> > trigger('mouseup', pixel);
> > t.eq(logevt.length, 2, "testing log length");
> > t.wait_result( 3 );
> > }
> >
> > and the logEvent function is:
> >
> > function logEvent(e) {
> >
> > //alert("Does this happen?");
> > logevt.push(e);
> > }
> >
> > https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html
> >
> > The problem is that no matter how many features I add, the logevt array is
> > length 1.
> >
> > I tried using the t.wait_result() function, taking a wild stab that since a
> > featureclick event gets fired for each feature that maybe there's some
> > timing issue that gets taken care of when you view featureclick.html but
> > needs to be accounted for in testing. Unfortunately, t.wait_result() didn't
> > change anything.
> >
> > -Mike
> >
> > On May 23, 2013, at 3:26 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:
> >
> > I think the problem is that your init() function won't be called when the
> > page is loaded by the test runner. So you'll have to call init() from the
> > test function (test_onClick12 in the current code).
> >
> > Andreas.
> >
> >
> > On Thu, May 23, 2013 at 12:33 PM, Michael Ryan <mr at mry4n.net> wrote:
> >>
> >> Thanks for all the help, Andreas.
> >>
> >> I'm pretty sure I can figure the contrib stuff out.
> >>
> >> At the moment, I'm hitting a wall with why a very simple test works if I
> >> just run the featureclick.html page, but not when I run the test function:
> >>
> >>
> >> https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html
> >>
> >> When I run the html page the logevt array has length 2. In the test, it's
> >> length 0. Yet I'm running the exact same code.
> >>
> >> I know this is taking a while and I may be missing the 2.13 deadline, but
> >> I'll keep plugging away at this til I get it right.
> >>
> >> -Mike
> >>
> >> On May 22, 2013, at 10:02 PM, Andreas Hocevar <ahocevar at opengeo.org>
> >> wrote:
> >>
> >> Hey Michael,
> >>
> >> you should find all information on how to submit code here:
> >> http://trac.osgeo.org/openlayers/wiki/HowToContribute. You will want to
> >> create a pull request, as explained here:
> >> http://trac.osgeo.org/openlayers/wiki/CreatingPatches.
> >>
> >> I hope this helps.
> >>
> >> Andreas.
> >>
> >>
> >> On Wed, May 22, 2013 at 9:34 AM, Michael Ryan <mr at mry4n.net> wrote:
> >>>
> >>> Thank you Andreas for clearing up that I should assign events like so:
> >>>
> >>> events = map.events
> >>>
> >>> The other part of this is that you have specify that the event you are
> >>> triggering is a left-click.
> >>>
> >>> By tracing the code you see that you need to set the "which" attribute to
> >>> 1 in the object passed to triggerEvent(), otherwise onClick in
> >>> featureclick.js ignores the event.
> >>>
> >>> So, this is what my code should have looked like:
> >>>
> >>> events = map.events;
> >>> events.triggerEvent( 'mousedown', {xy: new OpenLayers.Pixel(0,0), which:
> >>> 1}, map);
> >>> events.triggerEvent('mouseup', {xy: new OpenLayers.Pixel(0,0), which: 1},
> >>> map);
> >>>
> >>> I'm assuming I can get tests written today. Although, I'm not exactly
> >>> clear how to submit them. If anyone wants to clue me in to that procedure
> >>> I'd appreciate it.
> >>>
> >>> -Mike
> >>>
> >>> On May 21, 2013, at 5:21 PM, Michael Ryan <mr at mry4n.net> wrote:
> >>>
> >>> While I've understood I need to use trigger() somehow, I have been
> >>> unsuccessful in implementing it.
> >>>
> >>> I was using test for buttonclick as a reference:
> >>> https://github.com/openlayers/openlayers/blob/master/tests/Events/buttonclick.html
> >>>
> >>> I would have assumed that within the context of the featurclick example
> >>> https://github.com/openlayers/openlayers/pull/174/files
> >>>
> >>> I could have used something like
> >>>
> >>> events = OpenLayers.Events(map, document.getElementById("map"));
> >>> events.triggerEvent({type: 'mousedown', xy: new OpenLayers.Pixel(0,0)},
> >>> map); events.triggerEvent({type: 'mouseup', xy: new OpenLayers.Pixel(0,0)},
> >>> map);
> >>>
> >>> But, apparently, that's wrong.
> >>>
> >>> Am I trying to do something that isn't possible? I'm assuming I'm just
> >>> implementing it wrong. Any thoughts?
> >>>
> >>> -Mike
> >>>
> >>> On May 20, 2013, at 5:04 PM, Michael Ryan <mr at mry4n.net> wrote:
> >>>
> >>> I'll answer my question about triggering a buttonclick by saying, it
> >>> looks like you use trigger() which takes coordinates as an argument as in
> >>> this test:
> >>> https://github.com/drewwells/openlayers/blob/master/tests/Control/Measure.html
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Dev mailing list
> >>> Dev at lists.osgeo.org
> >>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Andreas Hocevar
> >> OpenGeo - http://opengeo.org/
> >> Expert service straight from the developers.
> >>
> >>
> >>
> >> _______________________________________________
> >> Dev mailing list
> >> Dev at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> >>
> >
> >
> >
> > --
> > Andreas Hocevar
> > OpenGeo - http://opengeo.org/
> > Expert service straight from the developers.
> >
> >
> 
> 
> 
> --
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> 
> 
> 
> -- 
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130523/5a8894a8/attachment-0001.html>

From bartvde at opengeo.org  Fri May 24 03:18:07 2013
From: bartvde at opengeo.org (Bart van den Eijnden)
Date: Fri, 24 May 2013 12:18:07 +0200
Subject: [OpenLayers-Dev] ANNOUNCEMENT: OpenLayers 2.13 RC4
Message-ID: <12D18576-9A3C-4066-83A6-AF766C77022E@opengeo.org>

The OpenLayers dev team is proud to announce the 4th release candidate of OpenLayers 2.13! RC4 comes about one week after RC3, and fixes a number of things:

 * Re-adding layer to map fails with TileManager enabled #980
 * Small Encoded Polyline bugfix #981
 * ModifyFeature control: Two consecutive events "before/afterfeaturemodified" #984

See  https://github.com/openlayers/openlayers/issues?milestone=11&state=closed for details.

We invite you to help us test the 2.13 release candidate! To test 2.13 in your applications, include the following tag in your OpenLayers-powered page:

<script src="http://openlayers.org/api/2.13-rc4/OpenLayers.js"></script>

As always, the source is available at http://openlayers.org/download/. Bug reports can be filed in GitHub at  https://github.com/openlayers/openlayers/issues. Make sure to use 2.13-RC4 in the title of the issue (and for developers, please assign those tickets to the 2.13-rc5 milestone).

Thanks!

-- 
Bart van den Eijnden
OpenGeo - http://opengeo.org
Expert service straight from the developers.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130524/1b6e375f/attachment.html>

From mr at mry4n.net  Fri May 24 11:23:17 2013
From: mr at mry4n.net (Michael Ryan)
Date: Fri, 24 May 2013 14:23:17 -0400
Subject: [OpenLayers-Dev] Testing
In-Reply-To: <CAOiJ94ghdHkPJ3JVf6ap2-jYEbD2ha5skXODuUNMutWOt-tVqQ@mail.gmail.com>
References: <5909A60D-192D-4562-8153-A579D6543C12@mry4n.net>
	<CAOiJ94i2XH2xrwxje3+aPNeivfQXov13JHL0O=ZPHxc_w4kJtg@mail.gmail.com>
	<40F7C13B-C1D8-443E-816D-A411A644751C@mry4n.net>
	<F7929F27-9659-4BF5-AAD9-F5A90B729D2D@mry4n.net>
	<7BF80FB9-7BDF-415B-9E0B-CEA275A70750@mry4n.net>
	<CAOiJ94g9utR1OapD0DJ3JhVyy__SfN_2LoY5VYuPj2LkJiYcFQ@mail.gmail.com>
	<3702064C-0422-4126-A9A8-A47252632FF6@mry4n.net>
	<CAOiJ94jA4s0+GWZZVgx4xVeRwckvuNjfWXNrg_o5FXNyw6m9ow@mail.gmail.com>
	<BF778A30-951D-4333-9309-8B732F9F3E67@mry4n.net>
	<CANrS==M3gKEAU1PF-FFri0LW4Wj8e+K7pC4ckN4M45jyGpO01Q@mail.gmail.com>
	<CAOiJ94ghdHkPJ3JVf6ap2-jYEbD2ha5skXODuUNMutWOt-tVqQ@mail.gmail.com>
Message-ID: <7CE313E3-40BC-4702-A31E-934838BB2AFE@mry4n.net>

The best I've come up with is to verify that a nofeatureclick event occurs in the test event, which would indicate something is off with the pixel I'm sending. 

However, I've used pagePosition to compensate for clicking in the correct location on the map. But it's only a difference of 8 pixels in either direction. And the circles have a radius of 30 pixels, so I don't think that would matter anyway. 

Again, everything works if I just run featureclick.html, but not when I run the test. 

https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html

-Mike

On May 23, 2013, at 6:31 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:

> But the real problem is that the clientX and clientY in your mock events is relative to the map viewport, but should be relative to the browser viewport. You'll need to use OpenLayers.Util.pagePosition to get the position of the map's viewportDiv and add that to the  pixel coordinate you are currently using.
> 
> Andreas.
> 
> 
> On Thu, May 23, 2013 at 5:20 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:
> Right now you are calling logEvent() once, and you're doing so when
> you define the listener:
> 
>     map.events.on({featureclick: logEvent()});
> 
> Instead, this should read
> 
>     map.events.on({featureclick: logEvent});
> 
> Andreas.
> 
> On Thu, May 23, 2013 at 4:30 PM, Michael Ryan <mr at mry4n.net> wrote:
> > I checked that out, but that didn't seem to be it. I noticed in
> > buttonclick.html that it just uses onload=init() in the body tag and doesn't
> > call init() in any of the test functions.
> >
> > However, it seems ilke I have to add the featureclick event and assign it a
> > function with parantheses, whereas running it in the html requires no
> > parentheses.
> >
> > So the test function now looks like this:
> >
> > function test_onClick23(t) {
> > t.plan(1);
> > logevt = [];
> > map.events.on({featureclick: logEvent()});
> > events = map.events;
> > lonlat = new OpenLayers.LonLat(0,0);
> > pixel = map.getPixelFromLonLat(lonlat);
> > trigger('mousedown', pixel);
> > trigger('mouseup', pixel);
> > t.eq(logevt.length, 2, "testing log length");
> > t.wait_result( 3 );
> > }
> >
> > and the logEvent function is:
> >
> > function logEvent(e) {
> >
> > //alert("Does this happen?");
> > logevt.push(e);
> > }
> >
> > https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html
> >
> > The problem is that no matter how many features I add, the logevt array is
> > length 1.
> >
> > I tried using the t.wait_result() function, taking a wild stab that since a
> > featureclick event gets fired for each feature that maybe there's some
> > timing issue that gets taken care of when you view featureclick.html but
> > needs to be accounted for in testing. Unfortunately, t.wait_result() didn't
> > change anything.
> >
> > -Mike
> >
> > On May 23, 2013, at 3:26 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:
> >
> > I think the problem is that your init() function won't be called when the
> > page is loaded by the test runner. So you'll have to call init() from the
> > test function (test_onClick12 in the current code).
> >
> > Andreas.
> >
> >
> > On Thu, May 23, 2013 at 12:33 PM, Michael Ryan <mr at mry4n.net> wrote:
> >>
> >> Thanks for all the help, Andreas.
> >>
> >> I'm pretty sure I can figure the contrib stuff out.
> >>
> >> At the moment, I'm hitting a wall with why a very simple test works if I
> >> just run the featureclick.html page, but not when I run the test function:
> >>
> >>
> >> https://github.com/m1k3ry4n/openlayers/blob/master/tests/Events/featureclick.html
> >>
> >> When I run the html page the logevt array has length 2. In the test, it's
> >> length 0. Yet I'm running the exact same code.
> >>
> >> I know this is taking a while and I may be missing the 2.13 deadline, but
> >> I'll keep plugging away at this til I get it right.
> >>
> >> -Mike
> >>
> >> On May 22, 2013, at 10:02 PM, Andreas Hocevar <ahocevar at opengeo.org>
> >> wrote:
> >>
> >> Hey Michael,
> >>
> >> you should find all information on how to submit code here:
> >> http://trac.osgeo.org/openlayers/wiki/HowToContribute. You will want to
> >> create a pull request, as explained here:
> >> http://trac.osgeo.org/openlayers/wiki/CreatingPatches.
> >>
> >> I hope this helps.
> >>
> >> Andreas.
> >>
> >>
> >> On Wed, May 22, 2013 at 9:34 AM, Michael Ryan <mr at mry4n.net> wrote:
> >>>
> >>> Thank you Andreas for clearing up that I should assign events like so:
> >>>
> >>> events = map.events
> >>>
> >>> The other part of this is that you have specify that the event you are
> >>> triggering is a left-click.
> >>>
> >>> By tracing the code you see that you need to set the "which" attribute to
> >>> 1 in the object passed to triggerEvent(), otherwise onClick in
> >>> featureclick.js ignores the event.
> >>>
> >>> So, this is what my code should have looked like:
> >>>
> >>> events = map.events;
> >>> events.triggerEvent( 'mousedown', {xy: new OpenLayers.Pixel(0,0), which:
> >>> 1}, map);
> >>> events.triggerEvent('mouseup', {xy: new OpenLayers.Pixel(0,0), which: 1},
> >>> map);
> >>>
> >>> I'm assuming I can get tests written today. Although, I'm not exactly
> >>> clear how to submit them. If anyone wants to clue me in to that procedure
> >>> I'd appreciate it.
> >>>
> >>> -Mike
> >>>
> >>> On May 21, 2013, at 5:21 PM, Michael Ryan <mr at mry4n.net> wrote:
> >>>
> >>> While I've understood I need to use trigger() somehow, I have been
> >>> unsuccessful in implementing it.
> >>>
> >>> I was using test for buttonclick as a reference:
> >>> https://github.com/openlayers/openlayers/blob/master/tests/Events/buttonclick.html
> >>>
> >>> I would have assumed that within the context of the featurclick example
> >>> https://github.com/openlayers/openlayers/pull/174/files
> >>>
> >>> I could have used something like
> >>>
> >>> events = OpenLayers.Events(map, document.getElementById("map"));
> >>> events.triggerEvent({type: 'mousedown', xy: new OpenLayers.Pixel(0,0)},
> >>> map); events.triggerEvent({type: 'mouseup', xy: new OpenLayers.Pixel(0,0)},
> >>> map);
> >>>
> >>> But, apparently, that's wrong.
> >>>
> >>> Am I trying to do something that isn't possible? I'm assuming I'm just
> >>> implementing it wrong. Any thoughts?
> >>>
> >>> -Mike
> >>>
> >>> On May 20, 2013, at 5:04 PM, Michael Ryan <mr at mry4n.net> wrote:
> >>>
> >>> I'll answer my question about triggering a buttonclick by saying, it
> >>> looks like you use trigger() which takes coordinates as an argument as in
> >>> this test:
> >>> https://github.com/drewwells/openlayers/blob/master/tests/Control/Measure.html
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Dev mailing list
> >>> Dev at lists.osgeo.org
> >>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Andreas Hocevar
> >> OpenGeo - http://opengeo.org/
> >> Expert service straight from the developers.
> >>
> >>
> >>
> >> _______________________________________________
> >> Dev mailing list
> >> Dev at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> >>
> >
> >
> >
> > --
> > Andreas Hocevar
> > OpenGeo - http://opengeo.org/
> > Expert service straight from the developers.
> >
> >
> 
> 
> 
> --
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> 
> 
> 
> -- 
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130524/e1a92e0c/attachment.html>

From list at rdewit.net  Mon May 27 17:54:26 2013
From: list at rdewit.net (Roald de Wit)
Date: Tue, 28 May 2013 10:54:26 +1000
Subject: [OpenLayers-Dev] ANNOUNCEMENT: OpenLayers 2.13 RC4
In-Reply-To: <12D18576-9A3C-4066-83A6-AF766C77022E@opengeo.org>
References: <12D18576-9A3C-4066-83A6-AF766C77022E@opengeo.org>
Message-ID: <51A40042.4060502@rdewit.net>

Hi,

It is with great pleasure that I noticed that tschaub's FeatureAgent has 
just been merged into master [1] and will be added to OL 2.13 
(presumably)! Even though adding new features to a release candidate is 
not recommended, this is very nice functionality, so I won't complain! :-)

Since the attention now is on features and events, can the devs please 
have a look at pull request #67 [2] and consider to merge this very 
useful feature (click xy coordinates in featureselected events) too? It 
somehow didn't make it into 2.12 and it would be a shame if it didn't 
make it into 2.13 either.

Thanks

Roald

[1] https://github.com/openlayers/openlayers/pull/174
[2] https://github.com/openlayers/openlayers/pull/67


On 24/05/13 20:18, Bart van den Eijnden wrote:
> The OpenLayers dev team is proud to announce the 4th release candidate 
> of OpenLayers 2.13! RC4 comes about one week after RC3, and fixes a 
> number of things:
>
>  * Re-adding layer to map fails with TileManager enabled #980
>  * Small Encoded Polyline bugfix #981
>  * ModifyFeature control: Two consecutive events 
> "before/afterfeaturemodified" #984
>
> See 
> https://github.com/openlayers/openlayers/issues?milestone=11&state=closed 
> for details.
>
> We invite you to help us test the 2.13 release candidate! To test 2.13 
> in your applications, include the following tag in your 
> OpenLayers-powered page:
>
> <script src="http://openlayers.org/api/2.13-rc4/OpenLayers.js"></script>
>
> As always, the source is available at http://openlayers.org/download/. 
> Bug reports can be filed in GitHub at 
> https://github.com/openlayers/openlayers/issues. Make sure to use 
> 2.13-RC4 in the title of the issue (and for developers, please assign 
> those tickets to the 2.13-rc5 milestone).
>
> Thanks!
>
> -- 
> Bart van den Eijnden
> OpenGeo - http://opengeo.org <http://opengeo.org/>
> Expert service straight from the developers.
>
>
>
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130528/5af55289/attachment.html>

From bartvde at opengeo.org  Mon May 27 22:22:23 2013
From: bartvde at opengeo.org (Bart van den Eijnden)
Date: Tue, 28 May 2013 07:22:23 +0200
Subject: [OpenLayers-Dev] ANNOUNCEMENT: OpenLayers 2.13 RC4
In-Reply-To: <51A40042.4060502@rdewit.net>
References: <12D18576-9A3C-4066-83A6-AF766C77022E@opengeo.org>
	<51A40042.4060502@rdewit.net>
Message-ID: <CC36D165-7F62-41BB-A43B-5F76A23924D9@opengeo.org>

The reason the feature agent was added so late in the process is because it doesn't touch any core functionality, it is completely separate. Hence no chance of breakage.

Reading the ticket you reference, I don't feel comfortable merging given @elemoine's comment. But I'll let Eric and Andreas shed their light on this since they were involved.

Bart

Sent from my iPhone

On May 28, 2013, at 2:54 AM, Roald de Wit <list at rdewit.net> wrote:

> Hi,
> 
> It is with great pleasure that I noticed that tschaub's FeatureAgent has just been merged into master [1] and will be added to OL 2.13 (presumably)! Even though adding new features to a release candidate is not recommended, this is very nice functionality, so I won't complain! :-)
> 
> Since the attention now is on features and events, can the devs please have a look at pull request #67 [2] and consider to merge this very useful feature (click xy coordinates in featureselected events) too? It somehow didn't make it into 2.12 and it would be a shame if it didn't make it into 2.13 either.
> 
> Thanks
> 
> Roald
> 
> [1] https://github.com/openlayers/openlayers/pull/174
> [2] https://github.com/openlayers/openlayers/pull/67
> 
> 
> On 24/05/13 20:18, Bart van den Eijnden wrote:
>> The OpenLayers dev team is proud to announce the 4th release candidate of OpenLayers 2.13! RC4 comes about one week after RC3, and fixes a number of things:
>> 
>>  * Re-adding layer to map fails with TileManager enabled #980
>>  * Small Encoded Polyline bugfix #981
>>  * ModifyFeature control: Two consecutive events "before/afterfeaturemodified" #984
>> 
>> See  https://github.com/openlayers/openlayers/issues?milestone=11&state=closed for details.
>> 
>> We invite you to help us test the 2.13 release candidate! To test 2.13 in your applications, include the following tag in your OpenLayers-powered page:
>> 
>> <script src="http://openlayers.org/api/2.13-rc4/OpenLayers.js"></script>
>> 
>> As always, the source is available at http://openlayers.org/download/. Bug reports can be filed in GitHub at  https://github.com/openlayers/openlayers/issues. Make sure to use 2.13-RC4 in the title of the issue (and for developers, please assign those tickets to the 2.13-rc5 milestone).
>> 
>> Thanks!
>> 
>> -- 
>> Bart van den Eijnden
>> OpenGeo - http://opengeo.org
>> Expert service straight from the developers.
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Dev mailing list
>> Dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130528/1b66b12e/attachment.html>

From ahocevar at opengeo.org  Tue May 28 08:44:20 2013
From: ahocevar at opengeo.org (Andreas Hocevar)
Date: Tue, 28 May 2013 09:44:20 -0600
Subject: [OpenLayers-Dev] ANNOUNCEMENT: OpenLayers 2.13 RC4
In-Reply-To: <CC36D165-7F62-41BB-A43B-5F76A23924D9@opengeo.org>
References: <12D18576-9A3C-4066-83A6-AF766C77022E@opengeo.org>
	<51A40042.4060502@rdewit.net>
	<CC36D165-7F62-41BB-A43B-5F76A23924D9@opengeo.org>
Message-ID: <CAOiJ94h6USJhGp2FrdiArvCgisWmYHCGJnctHo9V6fgv_mO9YA@mail.gmail.com>

I agree with Bart here.

Andreas.


On Mon, May 27, 2013 at 11:22 PM, Bart van den Eijnden
<bartvde at opengeo.org>wrote:

> The reason the feature agent was added so late in the process is because
> it doesn't touch any core functionality, it is completely separate. Hence
> no chance of breakage.
>
> Reading the ticket you reference, I don't feel comfortable merging given
> @elemoine's comment. But I'll let Eric and Andreas shed their light on this
> since they were involved.
>
> Bart
>
> Sent from my iPhone
>
> On May 28, 2013, at 2:54 AM, Roald de Wit <list at rdewit.net> wrote:
>
> Hi,
>
> It is with great pleasure that I noticed that tschaub's FeatureAgent has
> just been merged into master [1] and will be added to OL 2.13 (presumably)!
> Even though adding new features to a release candidate is not recommended,
> this is very nice functionality, so I won't complain! :-)
>
> Since the attention now is on features and events, can the devs please
> have a look at pull request #67 [2] and consider to merge this very useful
> feature (click xy coordinates in featureselected events) too? It somehow
> didn't make it into 2.12 and it would be a shame if it didn't make it into
> 2.13 either.
>
> Thanks
>
> Roald
>
> [1] https://github.com/openlayers/openlayers/pull/174
> [2] https://github.com/openlayers/openlayers/pull/67
>
>
> On 24/05/13 20:18, Bart van den Eijnden wrote:
>
> The OpenLayers dev team is proud to announce the 4th release candidate of
> OpenLayers 2.13! RC4 comes about one week after RC3, and fixes a number of
> things:
>
>   * Re-adding layer to map fails with TileManager enabled #980
>  * Small Encoded Polyline bugfix #981
>  * ModifyFeature control: Two consecutive events
> "before/afterfeaturemodified" #984
>
>  See
> https://github.com/openlayers/openlayers/issues?milestone=11&state=closedfor details.
>
>  We invite you to help us test the 2.13 release candidate! To test 2.13
> in your applications, include the following tag in your OpenLayers-powered
> page:
>
>  <script src="http://openlayers.org/api/2.13-rc4/OpenLayers.js"></script>
>
>  As always, the source is available at http://openlayers.org/download/.
> Bug reports can be filed in GitHub at
> https://github.com/openlayers/openlayers/issues. Make sure to use
> 2.13-RC4 in the title of the issue (and for developers, please assign those
> tickets to the 2.13-rc5 milestone).
>
>  Thanks!
>
>   --
> Bart van den Eijnden
> OpenGeo - http://opengeo.org
> Expert service straight from the developers.
>
>
>
>
>
> _______________________________________________
> Dev mailing listDev at lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/openlayers-dev
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>
>


-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130528/53ea9066/attachment-0001.html>

From bartvde at opengeo.org  Thu May 30 06:54:34 2013
From: bartvde at opengeo.org (Bart van den Eijnden)
Date: Thu, 30 May 2013 15:54:34 +0200
Subject: [OpenLayers-Dev] ANNOUNCEMENT: OpenLayers 2.13 RC5
Message-ID: <E7830DE3-27E0-4F43-A316-4A5AC86EB2CB@opengeo.org>

The OpenLayers dev team is proud to announce the 5th release candidate of OpenLayers 2.13! RC5 comes about one week after RC4, and fixes one issue:

 * Vector layer duplicates when changing to Google base layer https://github.com/openlayers/openlayers/pull/987

It also adds one new function, the featureclick events extension which supports detecting events on overlapping features. Check out https://github.com/openlayers/openlayers/pull/174 for more info.

See https://github.com/openlayers/openlayers/issues?milestone=12&state=closed for details.

We invite you to help us test the 2.13 release candidate! To test 2.13 in your applications, include the following tag in your OpenLayers-powered page:

<script src="http://openlayers.org/api/2.13-rc5/OpenLayers.js"></script>

As always, the source is available at http://openlayers.org/download/. Bug reports can be filed in GitHub at  https://github.com/openlayers/openlayers/issues. Make sure to use 2.13-RC5 in the title of the issue (and for developers, please assign those tickets to the 2.13-rc6 milestone).

Thanks!

-- 
Bart van den Eijnden
OpenGeo - http://opengeo.org
Expert service straight from the developers.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20130530/7eb4e02c/attachment.html>