gwt-openlayers-users — Users list. Moderately active.

Re: [Gwt-openlayers-users] GWT-OpenLayers

[Michael S. <M.s...@gm...>]

Hello,
thanks for your fast answer. My code is:
           
 MapWidget mapWidget;
            Map map;
            WMS wmsLayer;
            Markers markers;

            // Create OSM layer
            OSMOptions osmOptions = new OSMOptions();

            OSM mapnik = OSM.Mapnik("mapnik", osmOptions);
            mapnik.setIsBaseLayer(true);
            mapnik.setDisplayInLayerSwitcher(true);

            // Create map options
            MapOptions mapOptions = new MapOptions();
            mapOptions.setControls(new JObjectArray(new JSObject[]{}));
            mapOptions.setNumZoomLevels(16);
            mapOptions.setProjection("EPSG:4326");

            // Create map widget and map objects
            mapWidget = new MapWidget("800px", "600px", mapOptions);
            map = mapWidget.getMap();
            markers = new Markers("marker layer");

            // Create WMS map layer
            WMSParams wmsParams = new WMSParams();
            wmsParams.setFormat("image/png");
            wmsParams.setLayers("basic");
            wmsParams.setStyles("");

            WMSOptions wmsLayerParams = new WMSOptions();
            wmsLayerParams.setUntiled();
            wmsLayerParams.setTransitionEffect(TransitionEffect.RESIZE);


            wmsLayer = new WMS("WMS Layer", "http://labs.metacarta.com /wms/vmap0", wmsParams, wmsLayerParams);


            // Add layers and controls to map
            map.addLayers(new Layer[]{wmsLayer, mapnik, markers});

            map.addControl(new PanZoomBar());
            map.addControl(new MousePosition());
            map.addControl(new NavToolBar());
            map.addControl(new LayerSwitcher());


The GlassFush Webserver show a File not Found exception.

-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Re: [Gwt-openlayers-users] WFSParams Problem

[Edwin C. <com...@gm...>]

Hi Poul,

The WFS classes in 0.4 are stubs that did not really do anything and
looking into the old WFSParams code I see that it is missing the
constructor:

	public WFSParams(){
		this(JSObject.createJSObject());
	}

You could try subclass WFSParams, for example as:


public WFSParamsExt extends WFSParams {

	protected WFSParamsExt(JSObject jsObject) {
		super(jsObject);
	}

	public WFSParamsExt(){
		this(JSObject.createJSObject());
	}
}


Then you can pass a WFSParamsExt where WFSParams is expected, thanks
to polymorphism :)...

Another issue with doing WFS is that you will need a proxy (due to
cross-domain restrictions on XMLHttpRequest requests). In GWT-OL there
is no way to set OpenLayers.ProxyHost, so you will need to do that via
JSNI and either get the Python proxy in OL examples up, or grab some
proxy code from some place.

Right now, I am fragmentarily working on a BasicWFS example for the
showcase that uses WFSProtocol (which is minimally implemented in
GWT-OL trunk) and a proxy bundled with GWT-OL. It is not finished, but
maby it is good staring point if you check out the source from
Mercurial.

Greetings,
Edwin



Are you using GWT 2.0? Because

On 25 February 2010 10:00, paweluz <pa...@tl...> wrote:
> Hi!
>
> Sorry for writing to you directly but I really do not know what to do. I am using openlayers_gwt-0.4.jar and I have problem with WFSParams. It does not work for me at all... Here is my topic
>
> http://n2.nabble.com/WFS-GWT-WFSParams-problem-td4631183.html#a4631183
>
> I have also written to gwt...@li... but my message does not appears on the forum.
>
> I hope you can help me...
>
> Regards,
> Poul
>

[Gwt-openlayers-users] Full screen map only fills corner of window

[dan t. <dan...@go...>]

Hi,

I'm having some trouble putting together a basic GWT-OpenLayers app. It's
just a full-screen MapWidget connecting to a WMS.

The problem is that, when the page initially loads, the map only appears in
the top left-hand corner of the page.

If I drag the map, or zoom in/out, then the map resizes to cover the whole
window.

I guess that somehow the size of the Div/Widget isn't being set correctly;
perhaps somehow OpenLayers is getting its size/position too early, and then
drawing in the wrong place?

I've tried to find an event I can listen for to tell me when the page as
loaded, and so allow me to (attempt to) resize/redraw the map, but I can't
find one, and I've no idea if it would work anyway.

Does anyone have any ideas?

For the record, I'm in Standards mode using a RootLayoutPanel, although I
hope that's not the problem as I'd really rather to change to Quirks mode.

Thanks for your help.

dan

Re: [Gwt-openlayers-users] GWT-OpenLayers

[Edwin C. <com...@gm...>]

Hi Michael,

I myself have never used OSM. Maybe someone on the user list can help out.

What code are you trying and what errors do you get?

Greetings,
Edwin

On 24 February 2010 20:35, m-power <m-...@us...> wrote:
>
> Message body follows:
>
> Hello,
> this is a great Project from you. But I have some problems
> with integrate a Open Street Mapnik Map. I get always an
> exception. With the wms layer from the example my
> application work.
> Can you give me please an exaplme for useing this api with
> Open Street Map ?
> Greetings,
> Michael
>
>
> --
> This message has been sent to you, a registered SourceForge.net user,
> by another site user, through the SourceForge.net site.  This message
> has been delivered to your SourceForge.net mail alias.  You may reply
> to this message using the "Reply" feature of your email client, or
> using the messaging facility of SourceForge.net at:
> https://sourceforge.net/sendmessage.php?touser=2820351
>
>

Re: [Gwt-openlayers-users] Maven + Project Structure and Showcase

[Andrew H. <ahh...@gm...>]

FYI: Here's the post from the "GWT Eclipse Plugin Team" @ 14th Jan.

http://groups.google.com/group/google-web-toolkit/browse_thread/thread/b43de4bb51a0ea2d/b0b46575d4892d9c
<http://groups.google.com/group/google-web-toolkit/browse_thread/thread/b43de4bb51a0ea2d/b0b46575d4892d9c>

On Mon, Feb 22, 2010 at 5:11 PM, Andrew Hughes <ahh...@gm...> wrote:

> Thanks Guys,
>
> There's quite a lot of chatter on the GWT forums regarding support for
> Maven. GWT 1.7+ made things harder for the Maven guys - many of the
> complexities have now been resolved (mostly due to GWT's hardcoded paths)
> but it's not 100%. Google appear to have acknowledged that a significant
> proportion of GWT development occurs outside the confounds of Eclipse and do
> in fact exist inside maven. We all like EJB's and Hibernate and Spring and
> Seam and Struts and.... anyway you get it :)
>
> If not now for the showcase, then perhaps soon....
>
> Re tests: I think this is a tomcat vs jetty classpath issue. In particular
> this is related to the Mock dependencies. I don't have code to look at right
> now, but I this is a known problem and a change in the gwt-***** <scope> can
> resolve it. I'll have a dig and see what I can find.
>
>
>
> Take it easy :)
>
>
>
> On Mon, Feb 22, 2010 at 12:56 AM, Farrukh Najmi <
> fa...@we...> wrote:
>
>>
>> Guys,
>>
>> First my apologies taht I have not been very involved as UI and GWT has
>> been off my radar for a while.
>> However, I must say I second doing all project management, build,
>> distribution, testing etc. tasks via maven.
>> I also second using maven for all sample projects such as showcase.
>>
>> When I was doing active GWT dev all my projects were maven based and I
>> was able to debug client and server code with Netbeans IDE just fine.
>>
>> Make sure to use the following for gwt maven projects:
>>
>> http://mojo.codehaus.org/gwt-maven-plugin/
>>
>> and to not use the following deprectaed project:
>>
>> http://code.google.com/p/gwt-maven/
>>
>> Sorry I do not have more informatioon at my finger tips but wanted to
>> make sure I endorsed the idea of
>> using maven maximally. The benefits are huge.
>>
>> On 02/21/2010 08:06 AM, Edwin Commandeur wrote:
>> > Hi Andrew,
>> >
>> > On of the strongholds of GWT is the IDE support. The showcase has been
>> > setup as Google Eclipse project, since that is easy to get running
>> > within the Eclipse IDE as long as you have the official Google Eclipse
>> > plugin (which will most probably be up-to-date with GWT versions).
>> >
>> > The GWT-OL is just a jar-red GWT module, so that is easy to compile
>> > and package with Maven.
>> >
>> > The showcase is a webapp and the Google Eclipse default folder
>> > structure does not follow the Maven defaults. The showcase should be
>> > packaged as a war not a jar. However, I think you would always want to
>> > run the showcase in an IDE, in order to be able look at the code and
>> > to be able to debug it.
>> >
>> > I would agree that it would be nice to use Maven for both building the
>> > GWT-OL jar and the showcase, and to be independent of the IDE for
>> > running the showcase (most IDEs have good Maven support).
>> >
>> > It is a bit of a pain indeed that you now have to copy the the GWT-OL
>> > jar to the showcase. Though an Ant task could easily do that after a
>> > package and that Ant task could be called from Maven. Also, it is
>> > probably possible to use Maven only for the dependency management for
>> > the showcase. Then the default Maven goal for the GWT-OL module should
>> > be install.
>> >
>> > I haven't looked at the gwt-maven project for a while, but in the past
>> > it used to be a bit of a pain to get Maven and GWT play together if
>> > you want to launch the project and debug it in the IDE. At least, not
>> > as easy as using the Google Eclipse plugin. For example look at:
>> > http://www.screaming-penguin.com/node/7353. It is not difficult, but
>> > automatic copying of the GWT-OL jar or using Maven only for dependency
>> > management and subsequently running the project with Google Eclipse
>> > seems easier to me.
>> >
>> > What you can always do is make the poms, and copy the showcase stuff
>> > over to a new folder, for example 'samples' or 'explorer' that is
>> > setup with Maven in mind and if that works out fine, then we can drop
>> > the original showcase.
>> >
>> > One other thing that has not been fixed yet in the Maven poms is how
>> > to run the testcases. The GWT stuff is Ant oriented, so it was easy to
>> > setup an Ant test target, but it would be good to fix this in Maven as
>> > well.
>> >
>> > Greetings,
>> > Edwin
>> >
>> >
>> >
>> > On 19 February 2010 00:05, Andrew Hughes<ahh...@gm...>  wrote:
>> >
>> >> Hi Guys,
>> >> I wanted to add something to the showcase (based on some new
>> additions). But
>> >> this was a little bit odd because...
>> >> 1. The showcase is not a maven project.
>> >> 2. If it was, then the showcase/openlayers and not grouped maven
>> project
>> >> (modules) so I can't (easily) have the showcase depend on the latest
>> >> snapshot
>> >> and then you can get into the fact that the showcase really should be
>> on the
>> >> same compile/test/release lifecycle e.t.c.
>> >> To fix this would require the following:
>> >> gwt-openlayers/pom.xml   (artifactId=parent, packaging=pom)
>> >> gwt-openlayers/gwt-openlayers/pom.xml
>> >> (artifactId=gwt-openlayers, packaging=jar)
>> >> gwt-openlayers/showcase/pom.xml (artifactId=showcase, packaging=jar).
>> >> otherwise, I can't (easily) do a showcase example of recent changes, I
>> can't
>> >> release them with the gwt-openlayers release and I can't sync the two
>> >> dependencies in the release phase.
>> >> Thoughts? :)
>> >>
>>
>> --
>> Regards,
>> Farrukh
>>
>> Web: http://www.wellfleetsoftware.com
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Gwt-openlayers-users mailing list
>> Gwt...@li...
>> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
>>
>
>

Re: [Gwt-openlayers-users] Maven + Project Structure and Showcase

[Andrew H. <ahh...@gm...>]

Thanks Guys,

There's quite a lot of chatter on the GWT forums regarding support for
Maven. GWT 1.7+ made things harder for the Maven guys - many of the
complexities have now been resolved (mostly due to GWT's hardcoded paths)
but it's not 100%. Google appear to have acknowledged that a significant
proportion of GWT development occurs outside the confounds of Eclipse and do
in fact exist inside maven. We all like EJB's and Hibernate and Spring and
Seam and Struts and.... anyway you get it :)

If not now for the showcase, then perhaps soon....

Re tests: I think this is a tomcat vs jetty classpath issue. In particular
this is related to the Mock dependencies. I don't have code to look at right
now, but I this is a known problem and a change in the gwt-***** <scope> can
resolve it. I'll have a dig and see what I can find.



Take it easy :)



On Mon, Feb 22, 2010 at 12:56 AM, Farrukh Najmi <
fa...@we...> wrote:

>
> Guys,
>
> First my apologies taht I have not been very involved as UI and GWT has
> been off my radar for a while.
> However, I must say I second doing all project management, build,
> distribution, testing etc. tasks via maven.
> I also second using maven for all sample projects such as showcase.
>
> When I was doing active GWT dev all my projects were maven based and I
> was able to debug client and server code with Netbeans IDE just fine.
>
> Make sure to use the following for gwt maven projects:
>
> http://mojo.codehaus.org/gwt-maven-plugin/
>
> and to not use the following deprectaed project:
>
> http://code.google.com/p/gwt-maven/
>
> Sorry I do not have more informatioon at my finger tips but wanted to
> make sure I endorsed the idea of
> using maven maximally. The benefits are huge.
>
> On 02/21/2010 08:06 AM, Edwin Commandeur wrote:
> > Hi Andrew,
> >
> > On of the strongholds of GWT is the IDE support. The showcase has been
> > setup as Google Eclipse project, since that is easy to get running
> > within the Eclipse IDE as long as you have the official Google Eclipse
> > plugin (which will most probably be up-to-date with GWT versions).
> >
> > The GWT-OL is just a jar-red GWT module, so that is easy to compile
> > and package with Maven.
> >
> > The showcase is a webapp and the Google Eclipse default folder
> > structure does not follow the Maven defaults. The showcase should be
> > packaged as a war not a jar. However, I think you would always want to
> > run the showcase in an IDE, in order to be able look at the code and
> > to be able to debug it.
> >
> > I would agree that it would be nice to use Maven for both building the
> > GWT-OL jar and the showcase, and to be independent of the IDE for
> > running the showcase (most IDEs have good Maven support).
> >
> > It is a bit of a pain indeed that you now have to copy the the GWT-OL
> > jar to the showcase. Though an Ant task could easily do that after a
> > package and that Ant task could be called from Maven. Also, it is
> > probably possible to use Maven only for the dependency management for
> > the showcase. Then the default Maven goal for the GWT-OL module should
> > be install.
> >
> > I haven't looked at the gwt-maven project for a while, but in the past
> > it used to be a bit of a pain to get Maven and GWT play together if
> > you want to launch the project and debug it in the IDE. At least, not
> > as easy as using the Google Eclipse plugin. For example look at:
> > http://www.screaming-penguin.com/node/7353. It is not difficult, but
> > automatic copying of the GWT-OL jar or using Maven only for dependency
> > management and subsequently running the project with Google Eclipse
> > seems easier to me.
> >
> > What you can always do is make the poms, and copy the showcase stuff
> > over to a new folder, for example 'samples' or 'explorer' that is
> > setup with Maven in mind and if that works out fine, then we can drop
> > the original showcase.
> >
> > One other thing that has not been fixed yet in the Maven poms is how
> > to run the testcases. The GWT stuff is Ant oriented, so it was easy to
> > setup an Ant test target, but it would be good to fix this in Maven as
> > well.
> >
> > Greetings,
> > Edwin
> >
> >
> >
> > On 19 February 2010 00:05, Andrew Hughes<ahh...@gm...>  wrote:
> >
> >> Hi Guys,
> >> I wanted to add something to the showcase (based on some new additions).
> But
> >> this was a little bit odd because...
> >> 1. The showcase is not a maven project.
> >> 2. If it was, then the showcase/openlayers and not grouped maven project
> >> (modules) so I can't (easily) have the showcase depend on the latest
> >> snapshot
> >> and then you can get into the fact that the showcase really should be on
> the
> >> same compile/test/release lifecycle e.t.c.
> >> To fix this would require the following:
> >> gwt-openlayers/pom.xml   (artifactId=parent, packaging=pom)
> >> gwt-openlayers/gwt-openlayers/pom.xml
> >> (artifactId=gwt-openlayers, packaging=jar)
> >> gwt-openlayers/showcase/pom.xml (artifactId=showcase, packaging=jar).
> >> otherwise, I can't (easily) do a showcase example of recent changes, I
> can't
> >> release them with the gwt-openlayers release and I can't sync the two
> >> dependencies in the release phase.
> >> Thoughts? :)
> >>
>
> --
> Regards,
> Farrukh
>
> Web: http://www.wellfleetsoftware.com
>
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Gwt-openlayers-users mailing list
> Gwt...@li...
> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
>

Re: [Gwt-openlayers-users] Maven + Project Structure and Showcase

[Farrukh N. <fa...@we...>]

Guys,

First my apologies taht I have not been very involved as UI and GWT has 
been off my radar for a while.
However, I must say I second doing all project management, build, 
distribution, testing etc. tasks via maven.
I also second using maven for all sample projects such as showcase.

When I was doing active GWT dev all my projects were maven based and I 
was able to debug client and server code with Netbeans IDE just fine.

Make sure to use the following for gwt maven projects:

http://mojo.codehaus.org/gwt-maven-plugin/

and to not use the following deprectaed project:

http://code.google.com/p/gwt-maven/

Sorry I do not have more informatioon at my finger tips but wanted to 
make sure I endorsed the idea of
using maven maximally. The benefits are huge.

On 02/21/2010 08:06 AM, Edwin Commandeur wrote:
> Hi Andrew,
>
> On of the strongholds of GWT is the IDE support. The showcase has been
> setup as Google Eclipse project, since that is easy to get running
> within the Eclipse IDE as long as you have the official Google Eclipse
> plugin (which will most probably be up-to-date with GWT versions).
>
> The GWT-OL is just a jar-red GWT module, so that is easy to compile
> and package with Maven.
>
> The showcase is a webapp and the Google Eclipse default folder
> structure does not follow the Maven defaults. The showcase should be
> packaged as a war not a jar. However, I think you would always want to
> run the showcase in an IDE, in order to be able look at the code and
> to be able to debug it.
>
> I would agree that it would be nice to use Maven for both building the
> GWT-OL jar and the showcase, and to be independent of the IDE for
> running the showcase (most IDEs have good Maven support).
>
> It is a bit of a pain indeed that you now have to copy the the GWT-OL
> jar to the showcase. Though an Ant task could easily do that after a
> package and that Ant task could be called from Maven. Also, it is
> probably possible to use Maven only for the dependency management for
> the showcase. Then the default Maven goal for the GWT-OL module should
> be install.
>
> I haven't looked at the gwt-maven project for a while, but in the past
> it used to be a bit of a pain to get Maven and GWT play together if
> you want to launch the project and debug it in the IDE. At least, not
> as easy as using the Google Eclipse plugin. For example look at:
> http://www.screaming-penguin.com/node/7353. It is not difficult, but
> automatic copying of the GWT-OL jar or using Maven only for dependency
> management and subsequently running the project with Google Eclipse
> seems easier to me.
>
> What you can always do is make the poms, and copy the showcase stuff
> over to a new folder, for example 'samples' or 'explorer' that is
> setup with Maven in mind and if that works out fine, then we can drop
> the original showcase.
>
> One other thing that has not been fixed yet in the Maven poms is how
> to run the testcases. The GWT stuff is Ant oriented, so it was easy to
> setup an Ant test target, but it would be good to fix this in Maven as
> well.
>
> Greetings,
> Edwin
>
>
>
> On 19 February 2010 00:05, Andrew Hughes<ahh...@gm...>  wrote:
>    
>> Hi Guys,
>> I wanted to add something to the showcase (based on some new additions). But
>> this was a little bit odd because...
>> 1. The showcase is not a maven project.
>> 2. If it was, then the showcase/openlayers and not grouped maven project
>> (modules) so I can't (easily) have the showcase depend on the latest
>> snapshot
>> and then you can get into the fact that the showcase really should be on the
>> same compile/test/release lifecycle e.t.c.
>> To fix this would require the following:
>> gwt-openlayers/pom.xml   (artifactId=parent, packaging=pom)
>> gwt-openlayers/gwt-openlayers/pom.xml
>> (artifactId=gwt-openlayers, packaging=jar)
>> gwt-openlayers/showcase/pom.xml (artifactId=showcase, packaging=jar).
>> otherwise, I can't (easily) do a showcase example of recent changes, I can't
>> release them with the gwt-openlayers release and I can't sync the two
>> dependencies in the release phase.
>> Thoughts? :)
>>      

-- 
Regards,
Farrukh

Web: http://www.wellfleetsoftware.com

Re: [Gwt-openlayers-users] Maven + Project Structure and Showcase

[Edwin C. <com...@gm...>]

Hi Andrew,

On of the strongholds of GWT is the IDE support. The showcase has been
setup as Google Eclipse project, since that is easy to get running
within the Eclipse IDE as long as you have the official Google Eclipse
plugin (which will most probably be up-to-date with GWT versions).

The GWT-OL is just a jar-red GWT module, so that is easy to compile
and package with Maven.

The showcase is a webapp and the Google Eclipse default folder
structure does not follow the Maven defaults. The showcase should be
packaged as a war not a jar. However, I think you would always want to
run the showcase in an IDE, in order to be able look at the code and
to be able to debug it.

I would agree that it would be nice to use Maven for both building the
GWT-OL jar and the showcase, and to be independent of the IDE for
running the showcase (most IDEs have good Maven support).

It is a bit of a pain indeed that you now have to copy the the GWT-OL
jar to the showcase. Though an Ant task could easily do that after a
package and that Ant task could be called from Maven. Also, it is
probably possible to use Maven only for the dependency management for
the showcase. Then the default Maven goal for the GWT-OL module should
be install.

I haven't looked at the gwt-maven project for a while, but in the past
it used to be a bit of a pain to get Maven and GWT play together if
you want to launch the project and debug it in the IDE. At least, not
as easy as using the Google Eclipse plugin. For example look at:
http://www.screaming-penguin.com/node/7353. It is not difficult, but
automatic copying of the GWT-OL jar or using Maven only for dependency
management and subsequently running the project with Google Eclipse
seems easier to me.

What you can always do is make the poms, and copy the showcase stuff
over to a new folder, for example 'samples' or 'explorer' that is
setup with Maven in mind and if that works out fine, then we can drop
the original showcase.

One other thing that has not been fixed yet in the Maven poms is how
to run the testcases. The GWT stuff is Ant oriented, so it was easy to
setup an Ant test target, but it would be good to fix this in Maven as
well.

Greetings,
Edwin



On 19 February 2010 00:05, Andrew Hughes <ahh...@gm...> wrote:
> Hi Guys,
> I wanted to add something to the showcase (based on some new additions). But
> this was a little bit odd because...
> 1. The showcase is not a maven project.
> 2. If it was, then the showcase/openlayers and not grouped maven project
> (modules) so I can't (easily) have the showcase depend on the latest
> snapshot
> and then you can get into the fact that the showcase really should be on the
> same compile/test/release lifecycle e.t.c.
> To fix this would require the following:
> gwt-openlayers/pom.xml   (artifactId=parent, packaging=pom)
> gwt-openlayers/gwt-openlayers/pom.xml
> (artifactId=gwt-openlayers, packaging=jar)
> gwt-openlayers/showcase/pom.xml (artifactId=showcase, packaging=jar).
> otherwise, I can't (easily) do a showcase example of recent changes, I can't
> release them with the gwt-openlayers release and I can't sync the two
> dependencies in the release phase.
> Thoughts? :)
> --AH
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Gwt-openlayers-users mailing list
> Gwt...@li...
> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
>
>

[Gwt-openlayers-users] Maven + Project Structure and Showcase

[Andrew H. <ahh...@gm...>]

Hi Guys,

I wanted to add something to the showcase (based on some new additions). But
this was a little bit odd because...

1. The showcase is not a maven project.
2. If it was, then the showcase/openlayers and not grouped maven project
(modules) so I can't (easily) have the showcase depend on the latest
snapshot

and then you can get into the fact that the showcase really should be on the
same compile/test/release lifecycle e.t.c.

To fix this would require the following:

gwt-openlayers/pom.xml   (artifactId=parent, packaging=pom)
gwt-openlayers/gwt-openlayers/pom.xml
(artifactId=gwt-openlayers, packaging=jar)
gwt-openlayers/showcase/pom.xml (artifactId=showcase, packaging=jar).

otherwise, I can't (easily) do a showcase example of recent changes, I can't
release them with the gwt-openlayers release and I can't sync the two
dependencies in the release phase.

Thoughts? :)
--AH

[Gwt-openlayers-users] Popup CloseListener

[Christopher N. <cna...@gm...>]

Hi,

I have a question about the addCloseListener method for Popup.  My
CloseListener callback is executed if I create a Popup; however, if I
instead create a FramedCloud Popup which extends Popup, the callback
function never gets called and I am not sure why there is a disconnect.

The code below works just fine:

final Popup popup = new Popup( "myid", vectorFeature.getCenterLonLat(),
null, text, true );

popup.addCloseListener( new CloseListener() {

  public void onPopupClose( JSObject evt ) {
    Window.alert("callback executed");
  }
});

vectorFeature.setPopup( popup );

map.addPopup( vectorFeature.getPopup() );

With the above code, the alert message is displayed when the popup is
closed.

If I change the first line to:

final FramedCloud popup = new FramedCloud( "myid",
vectorFeature.getCenterLonLat(), null, text, null, true );

and leave the rest of the code the same, then the FramedCloud's
CloseListener callback is never called.  Any ideas why the callback doesn't
work with FramedCloud?  Am I doing something wrong?

Thanks,
Chris

Re: [Gwt-openlayers-users] Wrapping OpenLayers.Util.X ?

[Edwin C. <com...@gm...>]

Hi Andrew,

A pure GWT port of OpenLayers would be ideal, but that is also a lot
more work than wrapping OpenLayers.

Wrapping OL is still useful, because without a wrapping OpenLayers is
not accessible to the parts of your application that are in GWT. If
there were no wrapper library, then everbody would have to write all
wrapper code themselves.

A lot of hard work has gone into OpenLayers and it would take quite an
effort to do a implementation in GWT (like OpenScales for Flex).

It would be nice to provide a convenience method for
setOnImageLoadErrorDisplayNone(). However, I would favor that on the
Map object rather than on the MapWidget.

Greetings,
Edwin



On 18 February 2010 00:15, Andrew Hughes <ahh...@gm...> wrote:
> Thanks Edwin :)
> I've got quite a bit of catching up to do on gwt-openlayers but hopefully
> you can be patient with me :) apologies.
> Agree on class/namespace and static method's only.
> I don't like all this JSNI JavaScript (I'm guessing you don't either). It
> would be so much nicer if this were pure GWT :'( It seems unavoidable. Given
> that the  implementation is most likely going to be defined in JSNI, then
> why bother wrapping it at all? It's no different from doing the following:
> public class MyMapWidget extends Composite{
>     public MyMapWidget(){
>         ...//stuff
>         MyMapWidget. setOnImageLoadErrorDisplayNone();
>         ...//other stuff...
>     }
>     public static native void setOnImageLoadErrorDisplayNone()/*-{
>       $wnd.Openlayers.Util.onImageLoadError = function(){this.style.display
> ="none";}
>     }-*/;
> }
> What do you think?
> Cheers
> --AH
>
> On Wed, Feb 17, 2010 at 11:15 PM, Edwin Commandeur
> <com...@gm...> wrote:
>>
>> Hi Andrew,
>>
>> The Util class does indeed contain some handy functions that would be
>> nice to wrap. The Util class should never be instantiated and should
>> only have static methods in my opinion so both a Util and UtilImpl are
>> not strictly necessary, but having both may give more flexibility and
>> clarity than only a Util with static JSNI methods in it.
>>
>> If we mirror OL then Util is in the
>> org.gwtopenmaps.client.openlayers.* namespace and not in
>> org.gwtopenmaps.client.openlayers.util.*
>>
>> Example of usage:
>>
>> Util.extend(x:JSObjectWrapper, y:JSObjectWrapper)
>>
>> in Util:
>>
>> public static JSObjectWrapper extend(JSObjectWrapper destination,
>> JSObjectWrapper source){
>>  JSObject obj = UtilImpl.extend(destination.getJSObject(),
>> source.getJSObject());
>>  return destination.setJSObject(obj);
>> }
>>
>> In UtilImpl
>>
>> public static JSObject extend(JSObject destination, JSObject source)/*-{
>>  return $wnd.OpenLayers.Util.extend(destination, source);
>> }-*/;
>>
>> The example you give is immediately an example for which plain JSNI
>> seems the most appropriate, because you need to create a function that
>> can be pretty broad. You could off course do sth similar as in
>> setFormatOutput of MousePositionOptions, but plain JSNI is more
>> straightfoward:
>>
>> public static void onImageLoadErrorDisplayNone()/*-{
>>   $wnd.Openlayers.Util.onImageLoadError = function()
>> {this.style.display ="none";}
>> }-*/;
>>
>> Such a function could off course be added as a convenience to GWT-OL
>> on the Util object.
>>
>> Greetings,
>> Edwin
>>
>> On 17 February 2010 07:18, Andrew Hughes <ahh...@gm...> wrote:
>> > Hi Guys,
>> > There is a (handy) OpenLayer's class that doesn't appear to be wrapped
>> >
>> > 'OpenLayers/Util.js': http://trac.openlayers.org/browser/tags/openlayers/release-2.8/lib/OpenLayers/Util.js
>> > I'd like to wrapping this
>> > with: org.gwtopenmaps.openlayers.client.Util.java
>> > and org.gwtopenmaps.openlayers.client.UtilImp.java
>> > There's a slight naming overlap with
>> > the org.gwtopenmaps.openlayers.client.util package. But is a minor
>> > issue.
>> > Anyone like to chip in on this one? Trac ticket e.t.c. I need this so I
>> > can
>> > fix those annoying pink tiles for missing map images.
>> > Like this.. OpenLayers.Util.onImageLoadError = function() {
>> > this.style.display="none";}
>> > This appears to be a singleton (same for us) and I'm not sure if this
>> > should
>> > 'extends OpenLayersObjectWrapper'. Some advice would be great.
>> > Cheers :)
>> > --AH
>> >
>> > ------------------------------------------------------------------------------
>> > SOLARIS 10 is the OS for Data Centers - provides features such as
>> > DTrace,
>> > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>> > http://p.sf.net/sfu/solaris-dev2dev
>> > _______________________________________________
>> > Gwt-openlayers-users mailing list
>> > Gwt...@li...
>> > https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
>> >
>> >
>
>

Re: [Gwt-openlayers-users] Dynamic (% based) map Resizing

[Edwin C. <com...@gm...>]

Hi Andrew,

If you want to ensure that the map centers on the same center you may
want to listen to the beforeresize and afterresize event of the Panel
in which the map is embedded, if the panel throws these (GXT does).
Then you would have to get the center and store it before resize and
do setCenter after resize. Otherwise I think OpenLayers will apply
it's own logic to where it recenters.

Greetings,
Edwin

On 18 February 2010 11:56, Philipp Verhoeven
<phi...@go...> wrote:
> Greetings,
>
> I'm not sure if this is the right answer to your problem, but when I was
> working with resizing the map using relative sizes the map had to be in a
> DockPanel.
>
> Something like this:
>
> DockPanel dp = new DockPanel();
> dp.setHeight("100%");
> dp.setWidth("100%");
> dp.add(map.getMapWidget(), DockPanel.CENTER);
> addItem(dp);
>
> Maybe this helped!?
>
> Cheers!
>
>
> 2010/2/18 Andrew Hughes <ahh...@gm...>
>>
>> Hi AGAIN,
>> I've got a 100%x100% MapWidget inside a SplitPanel. Since the split panel
>> is resizeable (via a mouse drag), how can gwt-openlayers keep the map
>> focused on the centroid on resize. At the moment it just maintains the
>> minX/minY in the upper left top cnr.
>> Thanks AGAIN! :)
>>
>> ------------------------------------------------------------------------------
>> Download Intel&reg; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Gwt-openlayers-users mailing list
>> Gwt...@li...
>> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
>>
>
>
> ------------------------------------------------------------------------------
> Download Intel&reg; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Gwt-openlayers-users mailing list
> Gwt...@li...
> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
>
>

Re: [Gwt-openlayers-users] Dynamic (% based) map Resizing

[Philipp V. <phi...@go...>]

Greetings,

I'm not sure if this is the right answer to your problem, but when I was
working with resizing the map using relative sizes the map had to be in a
DockPanel.

Something like this:

DockPanel dp = new DockPanel();
dp.setHeight("100%");
dp.setWidth("100%");
dp.add(map.getMapWidget(), DockPanel.CENTER);
addItem(dp);

Maybe this helped!?

Cheers!


2010/2/18 Andrew Hughes <ahh...@gm...>

> Hi AGAIN,
>
> I've got a 100%x100% MapWidget inside a SplitPanel. Since the split panel
> is resizeable (via a mouse drag), how can gwt-openlayers keep the map
> focused on the centroid on resize. At the moment it just maintains the
> minX/minY in the upper left top cnr.
>
> Thanks *AGAIN*! :)
>
>
> ------------------------------------------------------------------------------
> Download Intel&reg; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Gwt-openlayers-users mailing list
> Gwt...@li...
> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
>
>

[Gwt-openlayers-users] Dynamic (% based) map Resizing

[Andrew H. <ahh...@gm...>]

Hi AGAIN,

I've got a 100%x100% MapWidget inside a SplitPanel. Since the split panel is
resizeable (via a mouse drag), how can gwt-openlayers keep the map focused
on the centroid on resize. At the moment it just maintains the minX/minY in
the upper left top cnr.

Thanks *AGAIN*! :)

Re: [Gwt-openlayers-users] Wrapping OpenLayers.Util.X ?

[Edwin C. <com...@gm...>]

Hi Andrew,

The Util class does indeed contain some handy functions that would be
nice to wrap. The Util class should never be instantiated and should
only have static methods in my opinion so both a Util and UtilImpl are
not strictly necessary, but having both may give more flexibility and
clarity than only a Util with static JSNI methods in it.

If we mirror OL then Util is in the
org.gwtopenmaps.client.openlayers.* namespace and not in
org.gwtopenmaps.client.openlayers.util.*

Example of usage:

Util.extend(x:JSObjectWrapper, y:JSObjectWrapper)

in Util:

public static JSObjectWrapper extend(JSObjectWrapper destination,
JSObjectWrapper source){
  JSObject obj = UtilImpl.extend(destination.getJSObject(),
source.getJSObject());
  return destination.setJSObject(obj);
}

In UtilImpl

public static JSObject extend(JSObject destination, JSObject source)/*-{
  return $wnd.OpenLayers.Util.extend(destination, source);
}-*/;

The example you give is immediately an example for which plain JSNI
seems the most appropriate, because you need to create a function that
can be pretty broad. You could off course do sth similar as in
setFormatOutput of MousePositionOptions, but plain JSNI is more
straightfoward:

public static void onImageLoadErrorDisplayNone()/*-{
   $wnd.Openlayers.Util.onImageLoadError = function()
{this.style.display ="none";}
}-*/;

Such a function could off course be added as a convenience to GWT-OL
on the Util object.

Greetings,
Edwin

On 17 February 2010 07:18, Andrew Hughes <ahh...@gm...> wrote:
> Hi Guys,
> There is a (handy) OpenLayer's class that doesn't appear to be wrapped
> 'OpenLayers/Util.js': http://trac.openlayers.org/browser/tags/openlayers/release-2.8/lib/OpenLayers/Util.js
> I'd like to wrapping this with: org.gwtopenmaps.openlayers.client.Util.java
> and org.gwtopenmaps.openlayers.client.UtilImp.java
> There's a slight naming overlap with
> the org.gwtopenmaps.openlayers.client.util package. But is a minor issue.
> Anyone like to chip in on this one? Trac ticket e.t.c. I need this so I can
> fix those annoying pink tiles for missing map images.
> Like this.. OpenLayers.Util.onImageLoadError = function() {
> this.style.display="none";}
> This appears to be a singleton (same for us) and I'm not sure if this should
> 'extends OpenLayersObjectWrapper'. Some advice would be great.
> Cheers :)
> --AH
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> Gwt-openlayers-users mailing list
> Gwt...@li...
> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
>
>

[Gwt-openlayers-users] Wrapping OpenLayers.Util.X ?

[Andrew H. <ahh...@gm...>]

Hi Guys,

There is a (handy) OpenLayer's class that doesn't appear to be wrapped
'OpenLayers/Util.js':
http://trac.openlayers.org/browser/tags/openlayers/release-2.8/lib/OpenLayers/Util.js

I'd like to wrapping this with: org.gwtopenmaps.openlayers.client.Util.java
and org.gwtopenmaps.openlayers.client.UtilImp.java

There's a slight naming overlap with
the org.gwtopenmaps.openlayers.client.util package. But is a minor issue.

Anyone like to chip in on this one? Trac ticket e.t.c. I need this so I can
fix those annoying pink tiles for missing map images.
Like this.. OpenLayers.Util.onImageLoadError = function() {
this.style.display="none";}

This appears to be a singleton (same for us) and I'm not sure if this should
'extends OpenLayersObjectWrapper'. Some advice would be great.

Cheers :)
--AH

Re: [Gwt-openlayers-users] Why are the default's different in OL and GWT-OL?

[Edwin C. <com...@gm...>]

Hi Andrew,

Are you referring to the PanZoom control and alike that are put by
default on the map by OpenLayers? The defaults in GWT-OL should be the
same as in OL, so please report it when you find differences. In the
GWT-OL examples the default controls are removed from the map with
mapOptions.removeDefaultControls(). If you do not call
removeDefaultControls on the mapOptions passed to the map then the
default controls should appear.

The reason to have the removeDefaultControls option ar because
a) In GWT-OL it is not as easy as in Javascript to remove these
default controls from the map.
b) Some default controls appear not to be used much in practice. For
instance, for PanZoom people often use the PanZoomBar in applications,
but it is not clear from the OL documentation that both will be added
if you add PanZoomBar. Also, controls that are not visible, but set by
default, such as the Attribution control, you probably want to put on
the map when you need them.

Greetings,
Edwin

On 16 February 2010 07:20, Andrew Hughes <ahh...@gm...> wrote:
> Hi Guys,
> If you look at OpenLayers maps with no defaults (like control's e.t.c) they
> give you some sensible ones. This is assumed or expected behavior. It's
> implied by the examples and online documentation. Behavior is consistent and
> I feel appropriate. GWT-OpenLayers doesn't seem to have the same defaults,
> which makes the assumptions, examples, documentation in OpenLayers no longer
> consistent.
> Is this something I am only experiencing?
> --AH
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> Gwt-openlayers-users mailing list
> Gwt...@li...
> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
>
>

[Gwt-openlayers-users] Why are the default's different in OL and GWT-OL?

[Andrew H. <ahh...@gm...>]

Hi Guys,

If you look at OpenLayers maps with no defaults (like control's e.t.c) they
give you some sensible ones. This is assumed or expected behavior. It's
implied by the examples and online documentation. Behavior is consistent and
I feel appropriate. GWT-OpenLayers doesn't seem to have the same defaults,
which makes the assumptions, examples, documentation in OpenLayers no longer
consistent.

Is this something I am only experiencing?

--AH

Re: [Gwt-openlayers-users] WFS Layer

[Edwin C. <com...@gm...>]

Hi Christopher,

Great to hear that setting the proxy host worked.

You are free to create Trac tickets for these strategies. As anonymous
user you may create new tickets (you only cannot assign them etc).
Contributions are always welcome. Filling Trac with valid tickets is
also valuable.

The long term goal is to wrap OL completely, so that includes the
strategies :)...

Greetings,
Edwin

On 12 February 2010 16:20, Christopher Navarro <cna...@gm...> wrote:
> Thanks for your quick reply Edwin.  I successfully set the proxy host using
> the JSNI code you provided and loaded my WFS layer.  I will look at what is
> in trunk because I would prefer to use the WFS protocol.
>
> I don't see any of the OpenLayers Strategies such as Cluster, BBOX, etc, is
> support planned in the near term for these options?  I didn't see it among
> the tickets in Trac.
>
> Regards,
> Chris
>
> On Thu, Feb 11, 2010 at 4:36 PM, Edwin Commandeur
> <com...@gm...> wrote:
>>
>> Hi Christopher,
>>
>> Without a proxy it is not possible for OpenLayers to do WFS requests,
>> because of cross-domain restrictions on Javascript.
>>
>> Before going into ProxyHost: The recommended way to create a WFS layer
>> is via WFSProtocol. We are intending to remove the WFS layer
>> alltogether, as it appears to be the legacy way to talk to a WFS. You
>> can look at the latest OpenLayers examples
>> (http://openlayers.org/dev/examples/). For instance:
>>
>> http://openlayers.org/dev/examples/wfs-states.js
>>
>> For this you need the code that it is in trunk (but see also below about
>> proxy).
>>
>> The easiest way to set the proxyHost is to create a setter for it in JSNI
>> code:
>>
>> public static native void setProxyHost(String host)/*-{
>>
>>  $wnd.OpenLayers.ProxyHost = host;
>>
>> }-*/;
>>
>> and then
>>
>> setProxyHost("myhost/here");
>>
>> However, the proxyHost should point at a proxy that is running on the
>> same domain as the javascript. There is a python proxy included with
>> the OpenLayers examples. You can try to get that running at the some
>> domain as the app you are working on.
>>
>> Currently, the GWT-OL lacks a java proxy servlet, but that should be
>> added to trunk soon. I can send you a copy of the new build when that
>> hits trunk.
>>
>> Greetings,
>> Edwin
>>
>> On 11 February 2010 17:55, Christopher Navarro <cna...@gm...>
>> wrote:
>> > Hi,
>> >
>> > I'm trying to read WFS features from a geoserver using gwt-openlayers
>> > and I
>> > can't seem to figure out where I am going wrong.
>> >
>> > Using straight OpenLayers/Javascript/HTML I have the following, which
>> > works:
>> >
>> > // Proxy setup to fix XMLHttpRequest domain matching
>> > OpenLayers.ProxyHost = "/cgi-bin/proxy.cgi?url=";
>> >
>> > // parameters for getting the WFS layer
>> > var params = { typename: "marketmaker:business_cu" };
>> > var options = {};
>> >
>> > // WFS Layer creation
>> > var layer = new OpenLayers.Layer.WFS( "WFS",
>> >           "http://mmweb.ncsa.uiuc.edu:8080/geoserver/wfs",
>> >           params, options );
>> >
>> > // add the layer
>> > map.addLayer( layer );
>> >
>> > My GWT-OpenLayers equivalent is:
>> >
>> > // parameters for wfs layer
>> > WFSParams wfsParams = new WFSParams();
>> > wfsParams.getJSObject().setProperty( "typename",
>> > "marketmaker:business_cu"
>> > );
>> >
>> > // no additional options
>> > WFSOptions wfsOptions = new WFSOptions();
>> >
>> > // WFS layer creation
>> > WFS wfsLayer = new WFS( "wfs", WFS_URL, wfsParams, wfsOptions );
>> >
>> > // add the layer
>> > map.addLayer( wfsLayer );
>> >
>> > Is there some way to inject the value of OpenLayers.ProxyHost using
>> > GWT-OpenLayers?  I'm not sure if that is the issue.  I am new to
>> > javascript
>> > and perhaps this is wrong, but I tried writing the value of
>> > OpenLayers.ProxyHost directly into the compiled javascript file that GWT
>> > creates.  Any help is appreciated.
>> >
>> > Regards,
>> > Chris
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > SOLARIS 10 is the OS for Data Centers - provides features such as
>> > DTrace,
>> > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>> > http://p.sf.net/sfu/solaris-dev2dev
>> > _______________________________________________
>> > Gwt-openlayers-users mailing list
>> > Gwt...@li...
>> > https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
>> >
>> >
>
>

Re: [Gwt-openlayers-users] WFS Layer

[Christopher N. <cna...@gm...>]

Thanks for your quick reply Edwin.  I successfully set the proxy host using
the JSNI code you provided and loaded my WFS layer.  I will look at what is
in trunk because I would prefer to use the WFS protocol.

I don't see any of the OpenLayers Strategies such as Cluster, BBOX, etc, is
support planned in the near term for these options?  I didn't see it among
the tickets in Trac.

Regards,
Chris

On Thu, Feb 11, 2010 at 4:36 PM, Edwin Commandeur <
com...@gm...> wrote:

> Hi Christopher,
>
> Without a proxy it is not possible for OpenLayers to do WFS requests,
> because of cross-domain restrictions on Javascript.
>
> Before going into ProxyHost: The recommended way to create a WFS layer
> is via WFSProtocol. We are intending to remove the WFS layer
> alltogether, as it appears to be the legacy way to talk to a WFS. You
> can look at the latest OpenLayers examples
> (http://openlayers.org/dev/examples/). For instance:
>
> http://openlayers.org/dev/examples/wfs-states.js
>
> For this you need the code that it is in trunk (but see also below about
> proxy).
>
> The easiest way to set the proxyHost is to create a setter for it in JSNI
> code:
>
> public static native void setProxyHost(String host)/*-{
>
>  $wnd.OpenLayers.ProxyHost = host;
>
> }-*/;
>
> and then
>
> setProxyHost("myhost/here");
>
> However, the proxyHost should point at a proxy that is running on the
> same domain as the javascript. There is a python proxy included with
> the OpenLayers examples. You can try to get that running at the some
> domain as the app you are working on.
>
> Currently, the GWT-OL lacks a java proxy servlet, but that should be
> added to trunk soon. I can send you a copy of the new build when that
> hits trunk.
>
> Greetings,
> Edwin
>
> On 11 February 2010 17:55, Christopher Navarro <cna...@gm...>
> wrote:
> > Hi,
> >
> > I'm trying to read WFS features from a geoserver using gwt-openlayers and
> I
> > can't seem to figure out where I am going wrong.
> >
> > Using straight OpenLayers/Javascript/HTML I have the following, which
> works:
> >
> > // Proxy setup to fix XMLHttpRequest domain matching
> > OpenLayers.ProxyHost = "/cgi-bin/proxy.cgi?url=";
> >
> > // parameters for getting the WFS layer
> > var params = { typename: "marketmaker:business_cu" };
> > var options = {};
> >
> > // WFS Layer creation
> > var layer = new OpenLayers.Layer.WFS( "WFS",
> >           "http://mmweb.ncsa.uiuc.edu:8080/geoserver/wfs",
> >           params, options );
> >
> > // add the layer
> > map.addLayer( layer );
> >
> > My GWT-OpenLayers equivalent is:
> >
> > // parameters for wfs layer
> > WFSParams wfsParams = new WFSParams();
> > wfsParams.getJSObject().setProperty( "typename",
> "marketmaker:business_cu"
> > );
> >
> > // no additional options
> > WFSOptions wfsOptions = new WFSOptions();
> >
> > // WFS layer creation
> > WFS wfsLayer = new WFS( "wfs", WFS_URL, wfsParams, wfsOptions );
> >
> > // add the layer
> > map.addLayer( wfsLayer );
> >
> > Is there some way to inject the value of OpenLayers.ProxyHost using
> > GWT-OpenLayers?  I'm not sure if that is the issue.  I am new to
> javascript
> > and perhaps this is wrong, but I tried writing the value of
> > OpenLayers.ProxyHost directly into the compiled javascript file that GWT
> > creates.  Any help is appreciated.
> >
> > Regards,
> > Chris
> >
> >
> ------------------------------------------------------------------------------
> > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> > http://p.sf.net/sfu/solaris-dev2dev
> > _______________________________________________
> > Gwt-openlayers-users mailing list
> > Gwt...@li...
> > https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
> >
> >
>

Re: [Gwt-openlayers-users] WFS Layer

[Edwin C. <com...@gm...>]

Hi Christopher,

Without a proxy it is not possible for OpenLayers to do WFS requests,
because of cross-domain restrictions on Javascript.

Before going into ProxyHost: The recommended way to create a WFS layer
is via WFSProtocol. We are intending to remove the WFS layer
alltogether, as it appears to be the legacy way to talk to a WFS. You
can look at the latest OpenLayers examples
(http://openlayers.org/dev/examples/). For instance:

http://openlayers.org/dev/examples/wfs-states.js

For this you need the code that it is in trunk (but see also below about proxy).

The easiest way to set the proxyHost is to create a setter for it in JSNI code:

public static native void setProxyHost(String host)/*-{

  $wnd.OpenLayers.ProxyHost = host;

}-*/;

and then

setProxyHost("myhost/here");

However, the proxyHost should point at a proxy that is running on the
same domain as the javascript. There is a python proxy included with
the OpenLayers examples. You can try to get that running at the some
domain as the app you are working on.

Currently, the GWT-OL lacks a java proxy servlet, but that should be
added to trunk soon. I can send you a copy of the new build when that
hits trunk.

Greetings,
Edwin

On 11 February 2010 17:55, Christopher Navarro <cna...@gm...> wrote:
> Hi,
>
> I'm trying to read WFS features from a geoserver using gwt-openlayers and I
> can't seem to figure out where I am going wrong.
>
> Using straight OpenLayers/Javascript/HTML I have the following, which works:
>
> // Proxy setup to fix XMLHttpRequest domain matching
> OpenLayers.ProxyHost = "/cgi-bin/proxy.cgi?url=";
>
> // parameters for getting the WFS layer
> var params = { typename: "marketmaker:business_cu" };
> var options = {};
>
> // WFS Layer creation
> var layer = new OpenLayers.Layer.WFS( "WFS",
>           "http://mmweb.ncsa.uiuc.edu:8080/geoserver/wfs",
>           params, options );
>
> // add the layer
> map.addLayer( layer );
>
> My GWT-OpenLayers equivalent is:
>
> // parameters for wfs layer
> WFSParams wfsParams = new WFSParams();
> wfsParams.getJSObject().setProperty( "typename", "marketmaker:business_cu"
> );
>
> // no additional options
> WFSOptions wfsOptions = new WFSOptions();
>
> // WFS layer creation
> WFS wfsLayer = new WFS( "wfs", WFS_URL, wfsParams, wfsOptions );
>
> // add the layer
> map.addLayer( wfsLayer );
>
> Is there some way to inject the value of OpenLayers.ProxyHost using
> GWT-OpenLayers?  I'm not sure if that is the issue.  I am new to javascript
> and perhaps this is wrong, but I tried writing the value of
> OpenLayers.ProxyHost directly into the compiled javascript file that GWT
> creates.  Any help is appreciated.
>
> Regards,
> Chris
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> Gwt-openlayers-users mailing list
> Gwt...@li...
> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users
>
>

[Gwt-openlayers-users] WFS Layer

[Christopher N. <cna...@gm...>]

Hi,

I'm trying to read WFS features from a geoserver using gwt-openlayers and I
can't seem to figure out where I am going wrong.

Using straight OpenLayers/Javascript/HTML I have the following, which works:

// Proxy setup to fix XMLHttpRequest domain matching
OpenLayers.ProxyHost = "/cgi-bin/proxy.cgi?url=";

// parameters for getting the WFS layer
var params = { typename: "marketmaker:business_cu" };
var options = {};

// WFS Layer creation
var layer = new OpenLayers.Layer.WFS( "WFS",
          "http://mmweb.ncsa.uiuc.edu:8080/geoserver/wfs",
          params, options );

// add the layer
map.addLayer( layer );

My GWT-OpenLayers equivalent is:

// parameters for wfs layer
WFSParams wfsParams = new WFSParams();
wfsParams.getJSObject().setProperty( "typename", "marketmaker:business_cu"
);

// no additional options
WFSOptions wfsOptions = new WFSOptions();

// WFS layer creation
WFS wfsLayer = new WFS( "wfs", WFS_URL, wfsParams, wfsOptions );

// add the layer
map.addLayer( wfsLayer );

Is there some way to inject the value of OpenLayers.ProxyHost using
GWT-OpenLayers?  I'm not sure if that is the issue.  I am new to javascript
and perhaps this is wrong, but I tried writing the value of
OpenLayers.ProxyHost directly into the compiled javascript file that GWT
creates.  Any help is appreciated.

Regards,
Chris

Re: [Gwt-openlayers-users] Problem with multiple Maps with Google Layer

[Cerávolo, R. V.B. <raf...@gm...>]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Just after I sent the last mail, I found the solution!<br>
<br>
The problem was that both maps was using the same instance of
MapOptions. When using a new instance of MapOptions (even if they are
identical) for each MapWidget, the problem does not happen any more!<br>
<br>
At least, I hope this mail helps others with this same issue.<br>
<br>
Regards,<br>
Rafael Cer&aacute;volo<br>
<br>
On 11/02/2010 11:17, "Cer&aacute;volo, Rafael V.B." wrote:
<blockquote cite="mid:4B7...@gm..." type="cite">
  <meta http-equiv="content-type"
 content="text/html; charset=ISO-8859-1">
Hi,<br>
  <br>
When showing multiple maps, with Google Maps as the base layer, at same
time, a problem occurs.<br>
  <br>
The second map that is added works fine, but the first map, lose all
control over their layers (including the base layer) and over the
navigation controls. When zooming the first map, the zoom actually
occurs on the second map.<br>
Also, the image of the zoom bar in the first map shows the zoom bar of
the second layer.<br>
  <br>
Other problem, is the Layer name. I named the google layer of the first
map as "Google 1" and the second as "Google 2". But the "Google 2"
appears in both layer switches.<br>
  <br>
I tested this issue with the gwt-openlayers-showcase, to make sure that
is not a issue with my application, and the problem is there as well!<br>
  <br>
I don't know if this is a problem just with GWT-OpenLayers or if it
exists in the original OpenLayers JavaScript.<br>
  <br>
Does any one had this problem too? And more important, does any one
know how the solution?<br>
  <br>
Attached is the screen-shot of the problem.<br>
  <br>
And below is the code I'm using. It is just the MapExample.java of the
showcase changed to add two GoogleMaps to the dockpanel.<br>
  <br>
Greetings,<br>
Rafael Cer&aacute;volo<br>
  <br>
------------------------------------------------<br>
  <b><tt>package org.gwtopenmaps.demo.openlayers.client.examples;<br>
  <br>
import java.util.ArrayList;<br>
  <br>
import org.gwtopenmaps.openlayers.client.LonLat;<br>
import org.gwtopenmaps.openlayers.client.Map;<br>
import org.gwtopenmaps.openlayers.client.MapOptions;<br>
import org.gwtopenmaps.openlayers.client.MapWidget;<br>
import org.gwtopenmaps.openlayers.client.control.LayerSwitcher;<br>
import org.gwtopenmaps.openlayers.client.control.MousePosition;<br>
import org.gwtopenmaps.openlayers.client.control.NavToolBar;<br>
import org.gwtopenmaps.openlayers.client.control.PanZoomBar;<br>
import org.gwtopenmaps.openlayers.client.layer.Google;<br>
import org.gwtopenmaps.openlayers.client.layer.Layer;<br>
import org.gwtopenmaps.openlayers.client.layer.TransitionEffect;<br>
import org.gwtopenmaps.openlayers.client.layer.WMS;<br>
import org.gwtopenmaps.openlayers.client.layer.WMSOptions;<br>
import org.gwtopenmaps.openlayers.client.layer.WMSParams;<br>
  <br>
import com.google.gwt.user.client.ui.DockPanel;<br>
import com.google.gwt.user.client.ui.Widget;<br>
  <br>
public class MapExample extends DockPanel {<br>
  <br>
&nbsp;&nbsp;&nbsp; private MapOptions defaultMapOptions;<br>
&nbsp;&nbsp;&nbsp; // private MapWidget mapWidget;<br>
&nbsp;&nbsp;&nbsp; private Map map;<br>
&nbsp;&nbsp;&nbsp; private ArrayList&lt;Widget&gt; widgets = new
ArrayList&lt;Widget&gt;();<br>
  <br>
&nbsp;&nbsp;&nbsp; public MapExample() {<br>
&nbsp;&nbsp;&nbsp; this.defaultMapOptions = new MapOptions();<br>
&nbsp;&nbsp;&nbsp; // In OL, the map gets PanZoom, Navigation, ArgParser, and
Attribution<br>
&nbsp;&nbsp;&nbsp; // Controls<br>
&nbsp;&nbsp;&nbsp; // by default. Do removeDefaultControls to remove these.<br>
&nbsp;&nbsp;&nbsp; this.defaultMapOptions.removeDefaultControls();<br>
&nbsp;&nbsp;&nbsp; this.defaultMapOptions.setNumZoomLevels(16);<br>
&nbsp;&nbsp;&nbsp; this.defaultMapOptions.setProjection("EPSG:4326");<br>
&nbsp;&nbsp;&nbsp; initMapWidget(this.defaultMapOptions);<br>
&nbsp;&nbsp;&nbsp; }<br>
  <br>
&nbsp;&nbsp;&nbsp; public MapExample(MapOptions options) {<br>
&nbsp;&nbsp;&nbsp; initMapWidget(options);<br>
&nbsp;&nbsp;&nbsp; }<br>
  <br>
&nbsp;&nbsp;&nbsp; private void initMapWidget(MapOptions options) {<br>
&nbsp;&nbsp;&nbsp; MapWidget mapWidget = new MapWidget("350px", "350px",
defaultMapOptions);<br>
&nbsp;&nbsp;&nbsp; this.map = mapWidget.getMap();<br>
&nbsp;&nbsp;&nbsp; add(mapWidget, DockPanel.CENTER);<br>
  <br>
&nbsp;&nbsp;&nbsp; MapWidget firstMap = new MapWidget("350px", "350px",
defaultMapOptions);<br>
&nbsp;&nbsp;&nbsp; add(firstMap, DockPanel.EAST);<br>
&nbsp;&nbsp;&nbsp; firstMap.getMap().addLayers(new Layer[] { new Google("Google 1") });<br>
&nbsp;&nbsp;&nbsp; firstMap.getMap().addControl(new PanZoomBar());<br>
&nbsp;&nbsp;&nbsp; firstMap.getMap().addControl(new NavToolBar());<br>
&nbsp;&nbsp;&nbsp; firstMap.getMap().addControl(new MousePosition());<br>
&nbsp;&nbsp;&nbsp; firstMap.getMap().addControl(new LayerSwitcher());<br>
&nbsp;&nbsp;&nbsp; firstMap.getMap().setCenter(new LonLat(-111.04, 45.68), 3);<br>
&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp; MapWidget secondMap = new MapWidget("350px", "350px",
defaultMapOptions);&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp; add(secondMap, DockPanel.WEST);<br>
&nbsp;&nbsp;&nbsp; secondMap.getMap().addLayers(new Layer[] { new Google("Google 2")
});<br>
&nbsp;&nbsp;&nbsp; secondMap.getMap().addControl(new PanZoomBar());<br>
&nbsp;&nbsp;&nbsp; secondMap.getMap().addControl(new NavToolBar());<br>
&nbsp;&nbsp;&nbsp; secondMap.getMap().addControl(new MousePosition());<br>
&nbsp;&nbsp;&nbsp; secondMap.getMap().addControl(new LayerSwitcher());<br>
  <br>
&nbsp;&nbsp;&nbsp; // Center and Zoom<br>
&nbsp;&nbsp;&nbsp; secondMap.getMap().setCenter(new LonLat(-111.04, 45.68), 3);<br>
&nbsp;&nbsp;&nbsp; }<br>
  <br>
&nbsp;&nbsp;&nbsp; public Map getMap() {<br>
&nbsp;&nbsp;&nbsp; return this.map;<br>
&nbsp;&nbsp;&nbsp; }<br>
  <br>
&nbsp;&nbsp;&nbsp; public void destroy() {<br>
&nbsp;&nbsp;&nbsp; this.map.destroy();<br>
&nbsp;&nbsp;&nbsp; for (int i = 0, max = widgets.size(); i &lt; max; i++) {<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; this.remove(widgets.get(i));<br>
&nbsp;&nbsp;&nbsp; }<br>
&nbsp;&nbsp;&nbsp; ;<br>
&nbsp;&nbsp;&nbsp; }<br>
  <br>
&nbsp;&nbsp;&nbsp; public void add(Widget w, DockLayoutConstant c) {<br>
&nbsp;&nbsp;&nbsp; super.add(w, c);<br>
&nbsp;&nbsp;&nbsp; this.widgets.add(w);<br>
&nbsp;&nbsp;&nbsp; }<br>
}</tt></b><br>
  <br>
  <br>
  <br>
</blockquote>
<br>
</body>
</html>

Re: [Gwt-openlayers-users] Wrapping XYZ Layer

[Edwin C. <com...@gm...>]

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
>
>

Re: [Gwt-openlayers-users] Wrapping XYZ Layer

[Andrew H. <ahh...@gm...>]

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
> >
> >
>