I wonder how practical it would be to replicate this functionality in OL3? Maybe something that could plug into a tile layer to generate a vector overlay where each request is represented as a feature. More work than just using OL2 but it might be worth suggesting to the OL developers.
On 2017-10-05 06:36 AM, Ian Turton wrote: > Yes, please - I was struggling with this the other day. > > Ian > > On 5 October 2017 at 14:31, Andrea Aime <andrea.a...@geo-solutions.it > <mailto:andrea.a...@geo-solutions.it>> wrote: > > Hi, > I would like to propose we bring back the OL2 preview as an > alternative output format "application/openlayers2". > > The reason is quite simple, I'm tired of pulling hairs with the > current canvas based preview. > I just spend some days debugging issues that were happening mostly > when doing requests in tiled mode, > and hunting down the right request in the network logs has been > quite a drag of time. > > Yes, there is a system variable to bring back the OL2 preview, but > it's not the default, cannot be easily > activated on a production system. > > Also, at least from a didactic perspective, it's nice to pull up > OL2 and tell the students to just right click on the > map/the tiles and see that it's really just a WMS call, rather > than pulling up the dev tools and also explain > them the network view in the process. > > Of course I'm not proposing to simply go back to OL2, but in some > ways the OL3 preview is not > a full replacement for the old OL2, so imho best to have them both > available at the same time > by just changing a request parameter, keeping OL2 as a possible > option while OL3+ remains > the default for previews. > > Objections? :-) > > Cheers > Andrea > > PS: another very annoying thing is that the OL3 preview just shows > nothing when > a request fails, instead of a "broken image" like in OL2, but I > guess for this there are solutions, > like using "error in image" for exceptions or something like that, > sounds more like a bug in need > of fixing instead of an architectural problem. > == > > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information.==Ing. Andrea Aime > @geowolfTechnical LeadGeoSolutions S.A.S.Via di Montramito > 3/A55054 Massarosa (LU)phone: +39 0584 962313 > <tel:+39%200584%20962313>fax: +39 0584 1660272 > <tel:+39%200584%20166%200272>mob: +39 339 8844549 > > <tel:+39%20339%20884%204549>http://www.geo-solutions.ithttp://twitter.com/geosolutions_it > <http://twitter.com/geosolutions_it> > > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 > > Le informazioni contenute in questo messaggio di posta elettronica > e/o nel/i file/s allegato/i sono da considerarsi strettamente > riservate. Il loro utilizzo è consentito esclusivamente al > destinatario del messaggio, per le finalità indicate nel messaggio > stesso. Qualora riceviate questo messaggio senza esserne il > destinatario, Vi preghiamo cortesemente di darcene notizia via > e-mail e di procedere alla distruzione del messaggio stesso, > cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, > copiarlo, od utilizzarlo per finalità diverse, costituisce > comportamento contrario ai principi dettati dal D.Lgs. 196/2003. > > The information in this message and/or attachments, is intended > solely for the attention and use of the named addressee(s) and may > be confidential or proprietary in nature or covered by the > provisions of privacy act (Legislative Decree June, 30 2003, > no.196 - Italy's New Data Protection Code).Any use not in accord > with its purpose, any disclosure, reproduction, copying, > distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please > contact immediately the sender by telephone, fax or e-mail and > delete the information in this message that has been received in > error. The sender does not give any warranty or accept liability > as the content, accuracy or completeness of sent messages and > accepts no responsibility for changes made after they were sent > or for other risks which arise as a result of e-mail transmission, > viruses, etc. > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > <mailto:Geoserver-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > <https://lists.sourceforge.net/lists/listinfo/geoserver-devel> > > > > > -- > Ian Turton > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- Kevin Michael Smith <smit...@draconic.ca>
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
