[OpenLayers-Dev] Format.WFST: misleading name
Hi list, maybe it's a bit too late to startup this discussion, but anyway, I think the name Format.WFST is a bit misleading, and I would prefer Format.WFS. It's misleading since it implies only transactional stuff, but Format.WFST also writes out stuff for non-transactional requests, such as GetFeature. If you look at the OGC spec, you'll see that the term WFS-T (or WFST) is not even an official name. The WFS spec has basic (read-only) and transactional parts and that is exactly what this format implements, so Format.WFS is more logical to me. What do others think? Best regards, Bart ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
[OpenLayers-Dev] Bug in ie7 (maybe ie6 also) in /OpenlLayers/lib/OpenLayers/Proptocol/HTTP.js on line 324:
When I run openlayers in ie7 I have an error in
/OpenlLayers/lib/OpenLayers/Proptocol/HTTP.js on line 324:
'status' is Null or is not an object
This does not happen in firefox.
Now if I look closer to the code, it is a bug in a method
'handleResponse' of the object OpenLayers.Protocol.HTTP
the method begins like this:
handleResponse: function(resp, options) {
var request = resp.priv;
if(options.callback) {
if(request.status = 200 request.status 300) { ...
Now in my case I don't exactly know why resp.priv is null. So I just
changed the code like this and all seams to work fine (in ie and firefox):
handleResponse: function(resp, options) {
var request = resp.priv;
if(options.callback) {
if(request request.status = 200 request.status 300)
{ ...
This would just check if request is not null before trying to see if
there is a status with it. Anyway if request is null the status can
not be = 200 and 300. So the corrected code is not wrong.
___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev
Re: [OpenLayers-Dev] Bug in ie7 (maybe ie6 also) in /OpenlLayers/lib/OpenLayers/Proptocol/HTTP.js on line 324:
Hi,
i think you hit http://trac.openlayers.org/ticket/1896
Its fixed in trunk,
cheers
Ivan
On Mon, Mar 16, 2009 at 11:20 AM, adu...@hbs-research.com
adu...@hbs-research.com wrote:
When I run openlayers in ie7 I have an error in
/OpenlLayers/lib/OpenLayers/Proptocol/HTTP.js on line 324:
'status' is Null or is not an object
This does not happen in firefox.
Now if I look closer to the code, it is a bug in a method
'handleResponse' of the object OpenLayers.Protocol.HTTP
the method begins like this:
handleResponse: function(resp, options) {
var request = resp.priv;
if(options.callback) {
if(request.status = 200 request.status 300) { ...
Now in my case I don't exactly know why resp.priv is null. So I just
changed the code like this and all seams to work fine (in ie and firefox):
handleResponse: function(resp, options) {
var request = resp.priv;
if(options.callback) {
if(request request.status = 200 request.status 300)
{ ...
This would just check if request is not null before trying to see if
there is a status with it. Anyway if request is null the status can
not be = 200 and 300. So the corrected code is not wrong.
___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev
___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev
Re: [OpenLayers-Dev] SelectFeature control
Thanks Eric, I'll have to try that in the following days. I'll let you know if I have comments. Regards, Alexandre Eric Lemoine wrote: On Fri, Mar 13, 2009 at 4:28 PM, Eric Lemoine eric@gmail.com wrote: I like it. See the attached eric-to-alexandre patch ;-) Alexandre, I attached a more complete patch to http://trac.openlayers.org/ticket/1596. Cheers, -- Eric -- Alexandre Dubé Mapgears www.mapgears.com ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
Re: [OpenLayers-Dev] Format.WFST: misleading name
On Mon, Mar 16, 2009 at 11:08:51AM +0100, bart...@osgis.nl wrote: Hi list, maybe it's a bit too late to startup this discussion, but anyway, I think the name Format.WFST is a bit misleading, and I would prefer Format.WFS. It's misleading since it implies only transactional stuff, but Format.WFST also writes out stuff for non-transactional requests, such as GetFeature. If you look at the OGC spec, you'll see that the term WFS-T (or WFST) is not even an official name. The WFS spec has basic (read-only) and transactional parts and that is exactly what this format implements, so Format.WFS is more logical to me. What do others think? We already have an existing Format.WFS that we need to maintain for backwards compatibility. Best regards, Bart ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev -- Christopher Schmidt MetaCarta ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
Re: [OpenLayers-Dev] Format.WFST: misleading name
Ah right, I missed that one. So this is something which can be changed at OL 3.0? Best regards, Bart On Mon, Mar 16, 2009 at 11:08:51AM +0100, bart...@osgis.nl wrote: Hi list, maybe it's a bit too late to startup this discussion, but anyway, I think the name Format.WFST is a bit misleading, and I would prefer Format.WFS. It's misleading since it implies only transactional stuff, but Format.WFST also writes out stuff for non-transactional requests, such as GetFeature. If you look at the OGC spec, you'll see that the term WFS-T (or WFST) is not even an official name. The WFS spec has basic (read-only) and transactional parts and that is exactly what this format implements, so Format.WFS is more logical to me. What do others think? We already have an existing Format.WFS that we need to maintain for backwards compatibility. Best regards, Bart ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev -- Christopher Schmidt MetaCarta ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
Re: [OpenLayers-Dev] Format.WFST: misleading name
On Mon, Mar 16, 2009 at 03:19:27PM +0100, bart...@osgis.nl wrote: Ah right, I missed that one. So this is something which can be changed at OL 3.0? Yes; I dont' know enough to say whether it should be or not, but it would be a candidate for that. One reason that I feel the WFS-T name is more accurate, looking at the Format.WFS code, is that the Format.WFS calls out to FOrmat.GML for everything *except* creating transactions: reading is all done by GML. I don't know enough to say whether this is correct or not, but that's hy the *existing* format.wfs would probably be better as format.wfs-t. Best regards, Bart On Mon, Mar 16, 2009 at 11:08:51AM +0100, bart...@osgis.nl wrote: Hi list, maybe it's a bit too late to startup this discussion, but anyway, I think the name Format.WFST is a bit misleading, and I would prefer Format.WFS. It's misleading since it implies only transactional stuff, but Format.WFST also writes out stuff for non-transactional requests, such as GetFeature. If you look at the OGC spec, you'll see that the term WFS-T (or WFST) is not even an official name. The WFS spec has basic (read-only) and transactional parts and that is exactly what this format implements, so Format.WFS is more logical to me. What do others think? We already have an existing Format.WFS that we need to maintain for backwards compatibility. Best regards, Bart ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev -- Christopher Schmidt MetaCarta -- Christopher Schmidt MetaCarta ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
[OpenLayers-Dev] analytics
Hey- Are the results from Google Analytics for http://openlayers.org available anywhere publicly? I'm particularly interested in visits for Sept 1, 08 - Feb 28, 09 (inclusive). I'd also be curious to hear download stats for the same time period. Thanks for any info. Tim -- Tim Schaub OpenGeo - http://opengeo.org Expert service straight from the developers. ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
Re: [OpenLayers-Dev] analytics
On Mon, Mar 16, 2009 at 03:54:56PM -0600, Tim Schaub wrote: Hey- Are the results from Google Analytics for http://openlayers.org available anywhere publicly? I'm particularly interested in visits for Sept 1, 08 - Feb 28, 09 (inclusive). I'd also be curious to hear download stats for the same time period. Thanks for any info. Not that I'm aware of, but I'm happy to make them available to anyone who is interested; if you give me a Google account, I'll gladly add you as an administrator on the site, and you can mess around or add people to your heart's content. Note that until the end of December, very little of OpenLayers traffic was measured by analytics: only the homepage visits. Starting At that time (I can look in SVN for exact commits) trac, api docs, documentation, etc. were all added. If there's a way to make stats publicly available through Google anaytics (or if anyone has a preferred tool other than Google analytics which does), I'm happy to switch things over or change settings. Regards, -- Christopher Schmidt MetaCarta ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
Re: [OpenLayers-Dev] SelectFeature control
Hi Eric, This is sweet. It accomplish everything we need to have two or more SelectFeatures controls at the same time, on the same layer. And the new highlight events make it possible to have temporary things happening at the same time, like displaying a popup on hover. Great work Eric. You're going to make a lot of people happy with this fix. Alexandre Eric Lemoine wrote: Alexandre, I attached a more complete patch to http://trac.openlayers.org/ticket/1596. Cheers, -- Eric -- Alexandre Dubé Mapgears www.mapgears.com ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
Re: [OpenLayers-Dev] analytics
Hey- Christopher Schmidt wrote: On Mon, Mar 16, 2009 at 03:54:56PM -0600, Tim Schaub wrote: Hey- Are the results from Google Analytics for http://openlayers.org available anywhere publicly? I'm particularly interested in visits for Sept 1, 08 - Feb 28, 09 (inclusive). I'd also be curious to hear download stats for the same time period. Thanks for any info. Not that I'm aware of, but I'm happy to make them available to anyone who is interested; if you give me a Google account, I'll gladly add you as an administrator on the site, and you can mess around or add people to your heart's content. Thanks. It looks like we should at least be able to track downloads from the homepage with something like the patch for http://trac.openlayers.org/ticket/1989. Not sure about adding a class name to wiki links, but we could also modify the patch to look for all anchors with href matching /^(http:\/\/openlayers.org)?\/download\//. Thoughts? Tim Note that until the end of December, very little of OpenLayers traffic was measured by analytics: only the homepage visits. Starting At that time (I can look in SVN for exact commits) trac, api docs, documentation, etc. were all added. If there's a way to make stats publicly available through Google anaytics (or if anyone has a preferred tool other than Google analytics which does), I'm happy to switch things over or change settings. Regards, -- Tim Schaub OpenGeo - http://opengeo.org Expert service straight from the developers. ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
Re: [OpenLayers-Dev] analytics
On Mon, Mar 16, 2009 at 05:29:37PM -0600, Tim Schaub wrote: Hey- Christopher Schmidt wrote: On Mon, Mar 16, 2009 at 03:54:56PM -0600, Tim Schaub wrote: Hey- Are the results from Google Analytics for http://openlayers.org available anywhere publicly? I'm particularly interested in visits for Sept 1, 08 - Feb 28, 09 (inclusive). I'd also be curious to hear download stats for the same time period. Thanks for any info. Not that I'm aware of, but I'm happy to make them available to anyone who is interested; if you give me a Google account, I'll gladly add you as an administrator on the site, and you can mess around or add people to your heart's content. Thanks. It looks like we should at least be able to track downloads from the homepage with something like the patch for http://trac.openlayers.org/ticket/1989. Tracking downloads is reasonably easy from logs, in my opinion; I just haven't written the log parser to do it. That said, I have no problems with making it easier for multiple people to see it by putting it in analytics; if you're happy with it, check it in :) Website is still manual 'svn up', so kick me after it's checked in and I'll update it. Not sure about adding a class name to wiki links, but we could also modify the patch to look for all anchors with href matching /^(http:\/\/openlayers.org)?\/download\//. I'm totally cool with anything you want to suggest; trac modifications are a bit hacky at the moment, so I'll try and dig those out and get them published next week so that other people can get involved. Note that any modifications we make to trac will have to be made again after we migrate to OSGeo. Thoughts? Tim Note that until the end of December, very little of OpenLayers traffic was measured by analytics: only the homepage visits. Starting At that time (I can look in SVN for exact commits) trac, api docs, documentation, etc. were all added. If there's a way to make stats publicly available through Google anaytics (or if anyone has a preferred tool other than Google analytics which does), I'm happy to switch things over or change settings. Regards, -- Tim Schaub OpenGeo - http://opengeo.org Expert service straight from the developers. ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev -- Christopher Schmidt MetaCarta ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
Re: [OpenLayers-Dev] analytics
Hey- Christopher Schmidt wrote: On Mon, Mar 16, 2009 at 05:29:37PM -0600, Tim Schaub wrote: Hey- Christopher Schmidt wrote: On Mon, Mar 16, 2009 at 03:54:56PM -0600, Tim Schaub wrote: Hey- Are the results from Google Analytics for http://openlayers.org available anywhere publicly? I'm particularly interested in visits for Sept 1, 08 - Feb 28, 09 (inclusive). I'd also be curious to hear download stats for the same time period. Thanks for any info. Not that I'm aware of, but I'm happy to make them available to anyone who is interested; if you give me a Google account, I'll gladly add you as an administrator on the site, and you can mess around or add people to your heart's content. Thanks. It looks like we should at least be able to track downloads from the homepage with something like the patch for http://trac.openlayers.org/ticket/1989. Tracking downloads is reasonably easy from logs, in my opinion; I just haven't written the log parser to do it. That said, I have no problems with making it easier for multiple people to see it by putting it in analytics; if you're happy with it, check it in :) Website is still manual 'svn up', so kick me after it's checked in and I'll update it. Not sure about adding a class name to wiki links, but we could also modify the patch to look for all anchors with href matching /^(http:\/\/openlayers.org)?\/download\//. I'm totally cool with anything you want to suggest; trac modifications are a bit hacky at the moment, so I'll try and dig those out and get them published next week so that other people can get involved. Note that any modifications we make to trac will have to be made again after we migrate to OSGeo. Ok. Done (kick). We'll see how that does. Only modified foot.html so no special class names or real track hacking involved. Thanks (for feedback svn up'ping), Tim Thoughts? Tim Note that until the end of December, very little of OpenLayers traffic was measured by analytics: only the homepage visits. Starting At that time (I can look in SVN for exact commits) trac, api docs, documentation, etc. were all added. If there's a way to make stats publicly available through Google anaytics (or if anyone has a preferred tool other than Google analytics which does), I'm happy to switch things over or change settings. Regards, -- Tim Schaub OpenGeo - http://opengeo.org Expert service straight from the developers. ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev -- Tim Schaub OpenGeo - http://opengeo.org Expert service straight from the developers. ___ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
