From: Edwin C. <com...@gm...> - 2010-02-10 09:00:15
|
Hi Andrew, I already had an idea the XYZ doc's mixed XYZ and OSM. The correlation between OL en GWT-OL is important, but XYZ extends Grid, so it seems a particular kind of Grid. Renaming it to XYZGrid would be acceptable to my mind, but there's also a lot to say for a one-on-one correspondence. I do think GWT-OL can divert from OL if it makes things clearer. Examples are Vector and VectorFeature that are both called Vector in OL, because in JS you cannot import packages, so you always have the full name or eventually I would like to move the stuff in Style to a class called Symbology (which has already been suggested in OL). Regarding documentation I think we do good to refer to the original doc in javascript, but I think referring to the actual URL of specific version of OL is a bit to brittle. Also, it can't do any harm to give additional clarifications, as not all things in OpenLayers are described that clearly to the API user and sometimes there is redundancy in OL or there are legacy functions which you want to make users of the API aware of. I totally agree on you that it would be nice if GWT-OL would be pure GWT! In fact, in time I think we should start a pure GWT implementation just as the OpenScales folks did for Flex (http://openscales.org/). However, at present I do not structurally have time to pull that of the ground. There is a Belgian company who is implementing a map component in GWT (http://majas.dfc.be/), but they are basing it on SmartGWT, which is itself a javascript wrapper. If you have a smart idea for a translator infrastructure, then please post it to the developers mailing list to discuss it. Greetings, Edwin On 10 February 2010 01:23, Andrew Hughes <ahh...@gm...> wrote: > Hi Again, > The doc's are wrong for the XYZ constructor, it is XYZ and not OSM :) > I think correlation between openlayers and gwt-openlayers is important so > I'd personally prefer to stick to XYZ. It made it into the 2.8 release so > it's pretty safe to assume this was named for a sensible reason (even if we > don't know what that is) :) The Z probably refer's to scale/resolution or > the 'height' of the grid/matrix axis. > Similarly, since gwt-openlayers is implemented in JS then we should probably > use the native documentation: > http://dev.openlayers.org/releases/OpenLayers-2.8/doc/apidocs/files/OpenLayers/Map-js.html#OpenLayers.Map.updateSize > I'll open a ticket, and hopefully commit some code in the next day or so :) > Mercurial, sourceforge & gwt-openlayers are new to me. GWT and OpenLayers > are not :) > > Andrew > p.s. I wish this was pure GWT. So much can be done with data/widget's over > RPC it's a pitty we have to push/translate all the objects to "openlayers" > object's over RPC. Is there some form of Generic architecture we could add > to the classes so that a translator can be assigned to a wrapped class? This > is a tough one. > > On Tue, Feb 9, 2010 at 7:38 PM, Edwin Commandeur > <com...@gm...> wrote: >> >> Hi Andrew, >> >> It is indeed unproblematic to wrap updateSize, but then I think we >> should describe it's use clearer than it is currently described in the >> OpenLayers API. I will add the method to Map and document that it's >> for specific kinds of divs. Any suggestions for JavaDoc are welcome. >> >> Great if you would like to research the XYZ layer a bit and add a Trac >> ticket about it. The name XYZ layer is a horrible choice of name IMHO. >> It should at least have been called XYZGrid and maybe we can give it >> that name in GWT-OL. I do not fully understand the Z -bit, but that is >> probably my lack of knowledge about this type of layer. >> >> Greetings, >> Edwin >> >> On 8 February 2010 23:49, Andrew Hughes <ahh...@gm...> wrote: >> > Hi There, >> > update() >> > ------------ >> > The problem is specifically related to Google BaseLayer's in OpenLayers >> > v2.8. >> > When the div size is changed at runtime you need to call it to sync the >> > google div's (afaik). Looks like OpenLayers v3.0 has fixed this. >> > However, if >> > the method is there I don't see any harm in wrapping it. >> > Layer.XYZ >> > ---------------- >> > My use case is that we have a client who is 110% esri. So, esri Cached >> > Maps, >> > REST services e.t.c. I've got to get some of these wrapped if we are >> > going >> > to use OpenLayers. I wasn't aware of the inheritence/relationship of >> > XYZ, >> > OSM, TMS e.t.c. Regardless of this I will submit this to trac, do some >> > RnD >> > of the openlayers src and introduce this to openlayers-gwt. I will also >> > have >> > a look at OpenLayers 3.0 to see if there are any considerations to make >> > now. >> > >> > Cheers :) >> > >> > On Tue, Feb 9, 2010 at 6:44 AM, Edwin Commandeur >> > <com...@gm...> wrote: >> >> >> >> Hi Andrew, >> >> >> >> I wonder when the updateSize method should be called. As far as I know >> >> it should work to let the OpenLayers div be 100% by 100% of the parent >> >> div, since the size of the div is requested from the div when it is >> >> needed. It seems that the updateSize method is a work-around for when >> >> you set a fixed width and height, while in reality the map is not >> >> fixed, but the parent div can be expanded and the div containing the >> >> map should resize to its parent. However, maybe I am missing out on >> >> something there. >> >> >> >> If you have a good use case for the XYZ class then please add it to >> >> Trac. You can create tickets without having to log in. It seems the >> >> XYZ class is a low-level thing intended for use in specific OpenLayers >> >> classes, such as the OSM layer. I see that it wrongly states above the >> >> XYZ constructor that it is the OSM layer constructor. We should >> >> possible wrap both the XYZ and the OSM layer, with the OSM layer >> >> extending XYZ. >> >> >> >> For OpenStreetMap things are a bit unclear to me, because there is >> >> also the TMS layer, which is wrapped by GWT-OL by someone who used >> >> OpenStreetMap. I am not sure which layer is more up to date XYZ/OSM or >> >> TMS. It seems that one of them is obsolete. The 'osm-layer.html' >> >> example in OpenLayers 2.8 includes OSM data by means of a WMS. The >> >> 'tms.html' does have a TMS layer, but is not what I expected to see. >> >> Andrew, if you know more about this, please let me know. >> >> >> >> Greetings, >> >> Edwin >> >> >> >> On 8 February 2010 05:54, Andrew Hughes <ahh...@gm...> wrote: >> >> > Hi Guys, >> >> > I have a few things I would like to add/wrap. >> >> > Map.updateSize() >> >> > >> >> > >> >> > http://dev.openlayers.org/releases/OpenLayers-2.8/doc/apidocs/files/OpenLayers/Map-js.html#OpenLayers.Map.updateSize >> >> > Layer.XYZ >> >> > >> >> > >> >> > http://dev.openlayers.org/releases/OpenLayers-2.8/doc/apidocs/files/OpenLayers/Layer/XYZ-js.html >> >> > >> >> > How would you like me to proceed? Do we raise issues or what first >> >> > e.t.c??? >> >> > Cheers. >> >> > >> >> > >> >> > >> >> > ------------------------------------------------------------------------------ >> >> > The Planet: dedicated and managed hosting, cloud storage, colocation >> >> > Stay online with enterprise data centers and the best network in the >> >> > business >> >> > Choose flexible plans and management services without long-term >> >> > contracts >> >> > Personal 24x7 support from experience hosting pros just a phone call >> >> > away. >> >> > http://p.sf.net/sfu/theplanet-com >> >> > _______________________________________________ >> >> > Gwt-openlayers-users mailing list >> >> > Gwt...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users >> >> > >> >> > >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > The Planet: dedicated and managed hosting, cloud storage, colocation >> > Stay online with enterprise data centers and the best network in the >> > business >> > Choose flexible plans and management services without long-term >> > contracts >> > Personal 24x7 support from experience hosting pros just a phone call >> > away. >> > http://p.sf.net/sfu/theplanet-com >> > _______________________________________________ >> > Gwt-openlayers-users mailing list >> > Gwt...@li... >> > https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users >> > >> > > > |