Menu
▾
▴
gwt-openlayers-devl — Developer list. Fairly active.
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
(3) |
Mar
(51) |
Apr
(8) |
May
(8) |
Jun
|
Jul
(3) |
Aug
(8) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(1) |
Feb
(21) |
Mar
(13) |
Apr
(8) |
May
(4) |
Jun
(3) |
Jul
(2) |
Aug
(11) |
Sep
(10) |
Oct
(1) |
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Farrukh N. <fa...@we...> - 2010-08-24 13:18:02
|
+1 on the proposed resolution of issue 48: https://sourceforge.net/apps/trac/gwt-openlayers/ticket/48 Kudos to Andrew for the terrific work to implement the proposed resolution. Kudos to Edwin and other dev team members for a lot of good work leading up to 0.5 release. BTW, we should consider getting a free hosted JIRA license for the project. It would be so much better than TRAC. Lots of SF projects are doing that these days that SF should just get a blanket deal with Atlassian. On 08/24/2010 07:43 AM, Edwin Commandeur wrote: > Hi all, > > Andrew Hughes has been working hard to get things ready for a 0.5 > release. One open issue is merging Andrew's fantastic work to make > proper use of Maven onto the default branch. You can check out the > improvements and see the new project dir layout by cloning the > 'trac_ticket_48' branch. > > PLEASE MAIL IT TO THE DEV LIST WITHIN 2 or 3 DAYS IF YOU WANT TO GIVE > FEEDBACK ON THE MERGE!!! If you are not okay with the merge then > please provide arguments about the how and why. > > All in all we think is a huge win, so we hope you'll feel the same way. > > There will be three modules in the new project structure: > gwt-openlayers (parent) > gwt-openlayers-client (what is now gwt-ol) > gwt-openlayers-showcase > > After checking out the project you can simply import the modules for > project into Eclipse as an existing Maven project (requires the > m2eclipse plugin). The documentation will be updated to describe how > to debug it all without the Google Eclipse Plugin and how to get the > showcase to work with the Google Eclipse Plugin (should work with new > versions of GEP). > > Building the jar: > >> cd gwt-openlayers-client >> mvn package (or mvn install) >> > Running the showcase: > >> cd gwt-openlayers-showcase >> mvn gwt:run >> > Building the new website > >> cd gwt-openlayers >> mvn site (requires mvn install of gwt-openlayers-client, to also build JavaDoc and link it in site). >> > Eventually the proxy in gwt-openlayers-client will be moved to > gwt-openlayers-server. This is in line with gwt-maven conventions. > > Building the project with Ant is no longer supported, as we want to > focus on getting everyting right with Maven. Also, the project website > will be generated from Maven. > -- Regards, Farrukh Najmi Web: http://www.wellfleetsoftware.com |
|
From: Edwin C. <com...@gm...> - 2010-08-24 11:43:30
|
Hi all, Andrew Hughes has been working hard to get things ready for a 0.5 release. One open issue is merging Andrew's fantastic work to make proper use of Maven onto the default branch. You can check out the improvements and see the new project dir layout by cloning the 'trac_ticket_48' branch. PLEASE MAIL IT TO THE DEV LIST WITHIN 2 or 3 DAYS IF YOU WANT TO GIVE FEEDBACK ON THE MERGE!!! If you are not okay with the merge then please provide arguments about the how and why. All in all we think is a huge win, so we hope you'll feel the same way. There will be three modules in the new project structure: gwt-openlayers (parent) gwt-openlayers-client (what is now gwt-ol) gwt-openlayers-showcase After checking out the project you can simply import the modules for project into Eclipse as an existing Maven project (requires the m2eclipse plugin). The documentation will be updated to describe how to debug it all without the Google Eclipse Plugin and how to get the showcase to work with the Google Eclipse Plugin (should work with new versions of GEP). Building the jar: > cd gwt-openlayers-client > mvn package (or mvn install) Running the showcase: > cd gwt-openlayers-showcase > mvn gwt:run Building the new website > cd gwt-openlayers > mvn site (requires mvn install of gwt-openlayers-client, to also build JavaDoc and link it in site). Eventually the proxy in gwt-openlayers-client will be moved to gwt-openlayers-server. This is in line with gwt-maven conventions. Building the project with Ant is no longer supported, as we want to focus on getting everyting right with Maven. Also, the project website will be generated from Maven. Greetings, Edwin Commandeur |
|
From: Edwin C. <com...@gm...> - 2010-08-23 21:50:03
|
Hi Andrew, I have been reading up on the Maven site generator and it's actually really cool! I like this apt format (almost plain text). The only things I kinda missed (but not really) were: - an out-of-the box search function for the documentation - an option to convert apt files to pdf directly. (The Doxia convertor can't seem to do it http://maven.apache.org/doxia/doxia-tools/doxia-converter/index.html) For GWT-OL I think we could do without these: If the docs are single page sites then the browser search function suffices (all the better!) and if we need something like pdf we can do it through an intermediary format. By also generating the site with Maven we really use Maven to the fullest and we wouldn't need an extra dependency on sth like Sphinx, which requires installing Python, Python's setup tools etc for Windows users. The new Maven layout makes it really easy to get started, so I can say I am really happy with all your work. Also, I now have Eclipse Helios running with HgEclipse and m2eclipse, which makes for an excellent dev environment. Just pushed a minor bugfix for MapImpl :)... I will start moving the documentation from Trac to the Maven site, which should be able to replace the goofy site we have now. Greetings, Edwin On 23 August 2010 02:28, Andrew Hughes <ahh...@gm...> wrote: > What do you think about this? > http://maven.apache.org/plugins/maven-site-plugin/examples/site-deploy-to-sourceforge.net.html > > On Sun, Aug 22, 2010 at 10:22 AM, Andrew Hughes <ahh...@gm...> wrote: >> >> Good News! I have sucessfully deployed a timed snapshot to sonatype... >> >> http://oss.sonatype.org/content/repositories/snapshots/org/gwtopenmaps/openlayers/ >> >> >> On Sun, Aug 22, 2010 at 10:20 AM, Andrew Hughes <ahh...@gm...> >> wrote: >>> >>> Howdy, >>> Sphinx and the Maven Sites seem to be the same thing (different >>> implementation but very much the same). I don't know anything about Sphinx >>> so I can't compare the two. I'll have to talk about this with you before the >>> 0.5 release :) >>> Here are some examples of maven sites I found: >>> http://ejb3unit.sourceforge.net/ >>> http://www.hibernatespatial.org/ >>> http://logging.apache.org/log4j/1.2/ >>> >>> If you want to try run the site for the trac_ticket_48 branch just run >>> 'mvn site' (note that some links will be broken as when it's still awaiting >>> deployment all the ./target paths get in the way). >>> :) >>> >>> On Sat, Aug 21, 2010 at 5:56 AM, Edwin Commandeur >>> <com...@gm...> wrote: >>>> >>>> Hi Andrew, >>>> >>>> That is great that you already put out a request to make the gwt-ol >>>> jar available in the Maven repos! >>>> >>>> Just to make sure you have all the rights for GWT-OL I have given you >>>> project admin rights. If you'd rather not have project admin rights >>>> then I you have to give me a shout out and I will revert it. >>>> >>>> After you have deprecated the default tip I will pull everything from >>>> Hg and start some work on GWT-OL again. >>>> >>>> One thing I would like to do is use Sphinx for documentation and site >>>> generation (http://sphinx.pocoo.org/). There are already some other >>>> open source geo projects that use Sphinx. The new MapServer site is >>>> created with Sphinx for instance (see http://www.mapserver.org/) and >>>> GeoServer is also using it (see http://docs.geoserver.org/2.0.1/user/, >>>> at the bottom). Sphinx, a tool written in Python, is really easy to >>>> setup using easy install, and that even worked flawlessly on my >>>> Windows box. >>>> >>>> Yes, Maven can generate a project website, but Sphinx gives far nicer >>>> docs out-of-the-box that can be searched as well. What is your take on >>>> this? >>>> >>>> Greetings, >>>> Edwin >>>> >>>> On 19 August 2010 23:30, Andrew Hughes <ahh...@gm...> wrote: >>>> > Coming soon.... v0.5 :) >>>> > >>>> > ---------- Forwarded message ---------- >>>> > From: Andrew Hughes (JIRA) <is...@so...> >>>> > Date: Fri, Aug 20, 2010 at 1:42 AM >>>> > Subject: [JIRA] Created: (OSSRH-709) GWT-OpenLayers (GWT Wrapper for >>>> > OpenLayers JavaScript Library) >>>> > To: ahh...@gm... >>>> > >>>> > >>>> > GWT-OpenLayers (GWT Wrapper for OpenLayers JavaScript Library) >>>> > -------------------------------------------------------------- >>>> > >>>> > Key: OSSRH-709 >>>> > URL: http://issues.sonatype.org/browse/OSSRH-709 >>>> > Project: Support - Open Source Project Repository Hosting >>>> > Issue Type: New Project >>>> > Reporter: Andrew Hughes >>>> > Assignee: Juven Xu >>>> > >>>> > >>>> > Id like to release this project out into central for public >>>> > consumption. >>>> > Cheers. >>>> > >>>> > Also, the colleague on the project owns the domain 'gwtopenmaps.org', >>>> > see >>>> > http://openlayers.gwtopenmaps.org/ >>>> > >>>> > I will try and get this released, signed and pushed up ASAP... I will >>>> > put >>>> > Jira comments on this issue to report progress. Cheers. >>>> > >>>> > -- >>>> > This message is automatically generated by JIRA. >>>> > - >>>> > If you think it was sent incorrectly contact one of the >>>> > administrators: >>>> > http://issues.sonatype.org/secure/Administrators.jspa >>>> > - >>>> > For more information on JIRA, see: >>>> > http://www.atlassian.com/software/jira >>>> > >>>> > >>>> > >>>> > >>> >> > > |
|
From: Edwin C. <com...@gm...> - 2010-08-19 18:21:43
|
Hi Andrew, All for the better if you have progressed on #48. 12 months between releases is way too long indeed :( Greetings, Edwin On 18 August 2010 12:35, Andrew Hughes <ahh...@gm...> wrote: > Thanks Edwin, > I must confess I did more work on the #trac_ticket_48 branch - naughty me. > This was two things... > 1. I merged the default tip onto the branch (i.e. they are in sync) > 2. I added a heap of maven configuration for maven based releases, this is > something I would really like to do for 0.5.... get a proper release out the > door and into central. It will also make releasing much easier in the future > - hence we should look foward to major, minor AND bug fix releases :) 12 > months between releases with soooooo many new features, fixes e.t.c. is too > long :) > I'll push ahead and try and get this working asap. > Cheers :) > > On Tue, Aug 17, 2010 at 10:57 PM, Edwin Commandeur > <com...@gm...> wrote: >> >> Hi Andrew, >> >> You are absolutely right, that we should get out a 0.5 release. You >> should have the rights to do a release (or alpha release if you like), >> but I don't know if you would be okay to arrange the release. >> >> - panel control => +1 for move to 0.6 (all widget toolkits have >> toolbars that are far nicer than the Panel) >> - #48 => if you can merge this, I would be all for that! >> - other enhancements => +1 for move to 0.6 >> >> Thanks for all the hard work you have already put into 0.5! >> >> Sorry for the low activity on my side lately. I hope to get things >> rolling again soon... >> >> Greetings, >> Edwin >> >> On 17 August 2010 08:35, Andrew Hughes <ahh...@gm...> wrote: >> > Hi All, >> > I'd like to propose that we try and get a new release of >> > gwt-openlayers. Unless I am mistaken the 0.4 tag was created 12 Months >> > ago >> > :O >> > According to trac 0.5 now has... 30 closed issues, 7 of which are >> > defects. >> > Remaining in 0.5.... >> > There are currently 6 Active tickets.... 5 enhancements, and one defect. >> > Ticket #41 "Panel Control Not Working" >> > - https://sourceforge.net/apps/trac/gwt-openlayers/ticket/41 >> > >> > I notice that Edwin changed the milestone from 0.5 to 0.6 and then back >> > to >> > 0.5... can this be moved onto 0.6? >> > >> > Ticket #48 "Project Identifies and Multi Module Maven >> > setup" https://sourceforge.net/apps/trac/gwt-openlayers/ticket/48 >> > >> > This work's been completed on the >> > >> > branch... http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/46f69b5f9bd5 it >> > has not been merged with the default/tip yet. I can merge this NOW if >> > people >> > want (it will help with the release too)? But if people don't want this >> > in >> > 0.5 I can also merge later (onto 0.6). I don't care either way 0.5 or >> > 0.6 >> > but I don't want 0.5 to get held up any longer. >> > >> > Ticket's #20, #51, #1, #13 are all enhancements and I don't believe they >> > should hold up a 0.5 release. Can we please move this into 0.6. >> > In summary.... Questions: >> > Should I merge down #48 to help with the (maven) release? >> > Can ticket #41, #48, #20, #51, #1, #13 be moved into 0.6 so that the 0.5 >> > release can go ahead? >> > If the answer is NO, then can I please do an alpha release... >> > 0.5-alpha1? >> > CHEERS :) >> > >> > >> > ------------------------------------------------------------------------------ >> > This SF.net email is sponsored by >> > >> > Make an app they can't live without >> > Enter the BlackBerry Developer Challenge >> > http://p.sf.net/sfu/RIM-dev2dev >> > _______________________________________________ >> > Gwt-openlayers-devl mailing list >> > Gwt...@li... >> > https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-devl >> > >> > > > |
|
From: Andrew H. <ahh...@gm...> - 2010-08-18 10:35:31
|
Thanks Edwin, I must confess I did more work on the #trac_ticket_48 branch - naughty me. This was two things... 1. I merged the default tip onto the branch (i.e. they are in sync) 2. I added a heap of maven configuration for maven based releases, this is something I would really like to do for 0.5.... get a proper release out the door and into central. It will also make releasing much easier in the future - hence we should look foward to major, minor AND bug fix releases :) 12 months between releases with soooooo many new features, fixes e.t.c. is too long :) I'll push ahead and try and get this working asap. Cheers :) On Tue, Aug 17, 2010 at 10:57 PM, Edwin Commandeur < com...@gm...> wrote: > Hi Andrew, > > You are absolutely right, that we should get out a 0.5 release. You > should have the rights to do a release (or alpha release if you like), > but I don't know if you would be okay to arrange the release. > > - panel control => +1 for move to 0.6 (all widget toolkits have > toolbars that are far nicer than the Panel) > - #48 => if you can merge this, I would be all for that! > - other enhancements => +1 for move to 0.6 > > Thanks for all the hard work you have already put into 0.5! > > Sorry for the low activity on my side lately. I hope to get things > rolling again soon... > > Greetings, > Edwin > > On 17 August 2010 08:35, Andrew Hughes <ahh...@gm...> wrote: > > Hi All, > > I'd like to propose that we try and get a new release of > > gwt-openlayers. Unless I am mistaken the 0.4 tag was created 12 Months > ago > > :O > > According to trac 0.5 now has... 30 closed issues, 7 of which are > defects. > > Remaining in 0.5.... > > There are currently 6 Active tickets.... 5 enhancements, and one defect. > > Ticket #41 "Panel Control Not Working" > > - https://sourceforge.net/apps/trac/gwt-openlayers/ticket/41 > > > > I notice that Edwin changed the milestone from 0.5 to 0.6 and then back > to > > 0.5... can this be moved onto 0.6? > > > > Ticket #48 "Project Identifies and Multi Module Maven > > setup" https://sourceforge.net/apps/trac/gwt-openlayers/ticket/48 > > > > This work's been completed on the > > branch... > http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/46f69b5f9bd5 > it > > has not been merged with the default/tip yet. I can merge this NOW if > people > > want (it will help with the release too)? But if people don't want this > in > > 0.5 I can also merge later (onto 0.6). I don't care either way 0.5 or 0.6 > > but I don't want 0.5 to get held up any longer. > > > > Ticket's #20, #51, #1, #13 are all enhancements and I don't believe they > > should hold up a 0.5 release. Can we please move this into 0.6. > > In summary.... Questions: > > Should I merge down #48 to help with the (maven) release? > > Can ticket #41, #48, #20, #51, #1, #13 be moved into 0.6 so that the 0.5 > > release can go ahead? > > If the answer is NO, then can I please do an alpha release... 0.5-alpha1? > > CHEERS :) > > > > > ------------------------------------------------------------------------------ > > This SF.net email is sponsored by > > > > Make an app they can't live without > > Enter the BlackBerry Developer Challenge > > http://p.sf.net/sfu/RIM-dev2dev > > _______________________________________________ > > Gwt-openlayers-devl mailing list > > Gwt...@li... > > https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-devl > > > > > |
|
From: Edwin C. <com...@gm...> - 2010-08-17 13:28:00
|
Hi Andrew, You are absolutely right, that we should get out a 0.5 release. You should have the rights to do a release (or alpha release if you like), but I don't know if you would be okay to arrange the release. - panel control => +1 for move to 0.6 (all widget toolkits have toolbars that are far nicer than the Panel) - #48 => if you can merge this, I would be all for that! - other enhancements => +1 for move to 0.6 Thanks for all the hard work you have already put into 0.5! Sorry for the low activity on my side lately. I hope to get things rolling again soon... Greetings, Edwin On 17 August 2010 08:35, Andrew Hughes <ahh...@gm...> wrote: > Hi All, > I'd like to propose that we try and get a new release of > gwt-openlayers. Unless I am mistaken the 0.4 tag was created 12 Months ago > :O > According to trac 0.5 now has... 30 closed issues, 7 of which are defects. > Remaining in 0.5.... > There are currently 6 Active tickets.... 5 enhancements, and one defect. > Ticket #41 "Panel Control Not Working" > - https://sourceforge.net/apps/trac/gwt-openlayers/ticket/41 > > I notice that Edwin changed the milestone from 0.5 to 0.6 and then back to > 0.5... can this be moved onto 0.6? > > Ticket #48 "Project Identifies and Multi Module Maven > setup" https://sourceforge.net/apps/trac/gwt-openlayers/ticket/48 > > This work's been completed on the > branch... http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/46f69b5f9bd5 it > has not been merged with the default/tip yet. I can merge this NOW if people > want (it will help with the release too)? But if people don't want this in > 0.5 I can also merge later (onto 0.6). I don't care either way 0.5 or 0.6 > but I don't want 0.5 to get held up any longer. > > Ticket's #20, #51, #1, #13 are all enhancements and I don't believe they > should hold up a 0.5 release. Can we please move this into 0.6. > In summary.... Questions: > Should I merge down #48 to help with the (maven) release? > Can ticket #41, #48, #20, #51, #1, #13 be moved into 0.6 so that the 0.5 > release can go ahead? > If the answer is NO, then can I please do an alpha release... 0.5-alpha1? > CHEERS :) > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Gwt-openlayers-devl mailing list > Gwt...@li... > https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-devl > > |
|
From: Andrew H. <ahh...@gm...> - 2010-08-17 06:35:43
|
Hi All, I'd like to propose that we try and get a new release of gwt-openlayers. Unless I am mistaken the 0.4 tag was created 12 Months ago :O According to trac 0.5 now has... 30 closed issues, 7 of which are defects. Remaining in 0.5.... There are currently 6 Active tickets.... 5 enhancements, and one defect. Ticket #41 "Panel Control Not Working" - https://sourceforge.net/apps/trac/gwt-openlayers/ticket/41 I notice that Edwin changed the milestone from 0.5 to 0.6 and then back to 0.5... can this be moved onto 0.6? Ticket #48 "Project Identifies and Multi Module Maven setup" https://sourceforge.net/apps/trac/gwt-openlayers/ticket/48 This work's been completed on the branch... http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/46f69b5f9bd5 it has not been merged with the default/tip yet. I can merge this NOW if people want (it will help with the release too)? But if people don't want this in 0.5 I can also merge later (onto 0.6). I don't care either way 0.5 or 0.6 but I don't want 0.5 to get held up any longer. Ticket's #20, #51, #1, #13 are all enhancements and I don't believe they should hold up a 0.5 release. Can we please move this into 0.6. In summary.... Questions: Should I merge down #48 to help with the (maven) release? Can ticket #41, #48, #20, #51, #1, #13 be moved into 0.6 so that the 0.5 release can go ahead? If the answer is NO, then can I please do an alpha release... 0.5-alpha1? CHEERS :) |
|
From: Edwin C. <com...@gm...> - 2010-07-13 22:01:19
|
Hi all, Recently Francesco Izzi was so kind to create a GWT-OpenLayers IRC channel on freenode. (http://webchat.freenode.net/, channel: gwt-openlayers). There some issues that concern GWT-OL in the large and I would like to meet up on IRC to discuss these. If we could arrange for all / most active devs to be on IRC in the near future that would be nice. The issues are: - Moving completely to Maven and utilizing it better for GWT-OL - Creating a new and improved showcase (Andrew has already worked on that and looked at Google App Engine as deployment options) - In Which directions should we move forward with GWT-OL 0.6 (or should it be 1.0 directly?) - Should we try to become an OSGeo project? - Intellectual property of GWT-OL: should we have CLA's? What do you all think? Does anyone have a suggestion for a good online tool for picking a time to meet up? On IRC itself: When I think about it, it seems a nice medium for arriving at decisions between a limited number of people and for firing questions by outsiders to insiders, but I am also a bit sceptical as it appears to me that it is easy to lose track of IRC history (more so than tickets in Trac, which have a discussion thread attached, and to which developers can respond more spread out over time) Greetings, Edwin |
|
From: Andrew H. <ahh...@gm...> - 2010-07-05 13:29:21
|
Hey, thanks heaps for looking at it :)
The reason for using a multi module project is because it is multi module :)
In the case of gwt-openlayers there are conceptually two modules
gwt-openlayers and gwt-openlayers-showcase. The two modules have a
relationship (hence why they are grouped in one (parent) project). You will
find that ./gwt-openlayers-showcase/pom.xml has the following dependency...
<http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/46f69b5f9bd5/gwt-openlayers-showcase/pom.xml#l14>
<dependencies>
<http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/46f69b5f9bd5/gwt-openlayers-showcase/pom.xml#l15>
<dependency>
<http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/46f69b5f9bd5/gwt-openlayers-showcase/pom.xml#l16>
<groupId>${project.groupId}</groupId>
<http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/46f69b5f9bd5/gwt-openlayers-showcase/pom.xml#l17>
<artifactId>gwt-openlayers</artifactId>
<http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/46f69b5f9bd5/gwt-openlayers-showcase/pom.xml#l18> <version>${project.version}</version>
<http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/46f69b5f9bd5/gwt-openlayers-showcase/pom.xml#l19>
</dependency>
The predecessor managed the relationship by copying the jar into ./lib and
launching the showcase as an eclipse project. There is no need to maually
build and copy something into the lib dir with maven multi module projects.
Maven's dependency management and build lifecycle does this for you. There
are a few flaws with doing this manually...
- You can modify gwt-openlayers and break the showcase unknowingly.
- gwt-openlayers and the showcase don't share the same lifecycle
- The two projects/modules don't share a recognised configuration
standard
- Unit tests aren't run on both during a single lifecycle iteration
- Releases should occur atomic for both modules/projects (as they are
linked)
- Documentation should be linked (normally to the release)
- The readme, is now deprecated by common practice :)
- The gwt-openlayers-showcase now demonstrates how to consume
gwt-openlayers in a maven project (but you could argue this to be totally
irrelevant).
Cheers :)
p.s. I still have to get my head around GAE+Maven and SourceForge+Maven
site:deploy.
On Mon, Jul 5, 2010 at 10:28 PM, Couzic Mikael <mik...@gm...>wrote:
> Hi Andrew,
>
>
> I've tried the new structure and it is definitively an improvement !
>
> However, I don't understand the use of a multi-module project (I've never
> used it myself). Intuitively I pictured 2 different projects, the showcase
> depending on the lib. What are the benefits of the multi-module approach ?
>
>
> Mikael Couzic
>
>
>
> 2010/6/30 Andrew Hughes <ahh...@gm...>
>
>> Hi Guys,
>>
>> I made some rather large changes to the structure of the project to
>> support maven multi module structure (including the existing showcase).
>> Currently this is committed against a named branch 'trac_ticket_48' which I
>> have pushed up the the server.
>>
>> All appears to work well. If anyone wants to try this out you will need...
>>
>> swtich to the branch
>>
>> hg update trac_ticket_48
>>
>> Then you should be able to do a complete build from maven....
>>
>> mvn install
>>
>> and run the developer mode showcase...
>>
>> cd gwt-openlayers-showcase
>> mvn gwt:run
>>
>>
>> If you want to work with this in eclipse, then you will need the m2eclipse
>> plugin and File -> Import Project -> Maven -> Existing Maven Project. But
>> you will no doubt have this setup already for the (now pre-dated)
>> gwt-showcase project ;)
>>
>>
>> Please give feedback.
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> _______________________________________________
>> Gwt-openlayers-devl mailing list
>> Gwt...@li...
>> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-devl
>>
>>
>
|
|
From: Andrew H. <ahh...@gm...> - 2010-06-30 15:18:18
|
Hi Guys, I made some rather large changes to the structure of the project to support maven multi module structure (including the existing showcase). Currently this is committed against a named branch 'trac_ticket_48' which I have pushed up the the server. All appears to work well. If anyone wants to try this out you will need... swtich to the branch hg update trac_ticket_48 Then you should be able to do a complete build from maven.... mvn install and run the developer mode showcase... cd gwt-openlayers-showcase mvn gwt:run If you want to work with this in eclipse, then you will need the m2eclipse plugin and File -> Import Project -> Maven -> Existing Maven Project. But you will no doubt have this setup already for the (now pre-dated) gwt-showcase project ;) Please give feedback. |
|
From: Edwin C. <com...@gm...> - 2010-06-03 14:20:55
|
Cool! Thanks for picking this up and the detailed description in Trac. Greetings, Edwin On 3 June 2010 16:02, Andrew Hughes <ahh...@gm...> wrote: > Hi Edwin + Everyone Else, > @See https://sourceforge.net/apps/trac/gwt-openlayers/ticket/47 > Please use trac to comment/contribute. > Cheers. > --AH > > On Thu, Jun 3, 2010 at 11:00 PM, Edwin Commandeur > <com...@gm...> wrote: >> >> Hi Andrew, >> >> I have been looking at the Trac tickets and trying to get together a >> list of things to fix before getting 0.5 out, which is long overdue, >> so it should really get out this month or next month. >> >> In that context I thought the new showcase might be a nice feature for >> a 0.6 release (upcoming is 0.5). Can you make a ticket for it in Trac >> (http://sourceforge.net/apps/trac/gwt-openlayers/)? >> >> How are your plans on commiting showcase changes? Do you want to wait >> for GWT 2.1 M1 to be in the Maven repo? >> >> Sorry, for not testing out the distribution management stuff yet. >> >> Greetings, >> Edwin > > |
|
From: Edwin C. <com...@gm...> - 2010-06-03 13:55:56
|
Hi Andrew, I have been looking at the Trac tickets and trying to get together a list of things to fix before getting 0.5 out, which is long overdue, so it should really get out this month or next month. In that context I thought the new showcase might be a nice feature for a 0.6 release (upcoming is 0.5). Can you make a ticket for it in Trac (http://sourceforge.net/apps/trac/gwt-openlayers/)? How are your plans on commiting showcase changes? Do you want to wait for GWT 2.1 M1 to be in the Maven repo? Sorry, for not testing out the distribution management stuff yet. Greetings, Edwin |
|
From: Edwin C. <com...@gm...> - 2010-05-25 19:39:10
|
Hi Andrew, Maybe it is a nice time to stop supporting the Ant build. At the time Ant was the fastest way that I could get the test cases running and there already was an Ant script. The Ant script can be used to build the GWT-OpenLayers jar, but IMHO Maven is the preferred way. With Maven we do not need to worry about setting paths to any dependencies as it can pull GWT jars from the Maven repos :). I will try to get the test cases running with Maven (possibly using Ant runner), so we can get rid of the Ant script and stop maintaining different ways to build GWT-OL, as that is extra work + possibly confusing. Nice to hear about your experiences with GWT MVP. We are using Spring for depency injection on the server side, but I have no experience with GIN DI on the client side. I looked it up and there is some very minimal mentioning of GIN on the two articles about large scale application development in the GWT documentation, but no code illustrations. I probably have to look at the Google IO 2009 presentation for mo re info, or look at some blog posts. For now Ext-GWT MVC works fine, but on future projects I would like to try MVP. Greetings, Edwin On 25 May 2010 17:20, Andrew Hughes <ahh...@gm...> wrote: > Success, but I'm going to bed in a minute - it's very late here! > I moved the source beneath ./gwt-openlayers, created a new module > ./gwt-openlayers-showcase and have setup all of the maven dependencies > gwt==2.0.3, java==1.6, openlayers==2.9.1. There is a stubb project > in gwt-openlayers-showcase. Everything builds+runs e.t.c. > The big question is, what should we do about ant support? What I have done > will most likely break the ant scripts :/ But the showcase did look like it > was dependent on maven to build gwt-openlayers.jar anyway. > Very tired, happy to checkin once the ant stuff is confirmed either way :) > Cheers, > AH > > On Tue, May 25, 2010 at 10:27 PM, Andrew Hughes <ahh...@gm...> wrote: >> >> Hi Edwin, >> >> On Tue, May 25, 2010 at 6:01 PM, Edwin Commandeur >> <com...@gm...> wrote: >>> >>> Hi Andrew, >>> >>> Moving the code base down a directory as you suggest is definitely a >>> good idea! It was a mistake to have the src dir at the same level as >>> the showcase dir. >> >> Excellent! >> >>> >>> Better a long descriptive name (gwt-openlayers-showcase) than a short >>> name that is less descriptive :). >> >> Agreed! >> >>> >>> Are you taking the actual GWT showcase code as a skeleton? Is that >>> code free to use that way? The showcase makes use of generators, >>> aren't those generating stuff you are missing? >>> >> >> I believe it's free for use, but do not remove the copyright comments from >> the source. I am missing the generator code. Generators look amazing, but I >> don't fully understand them and don't have the time to learn them :( >>> >>> There are two things that would be nice to have, which are not in the >>> standard GWT showcase: 1) Tooltips over the tree items to provide a >>> short description of the example; 2) A search function for easily >>> looking up examples. >>> >> >> Tooltip's would be nice. Perhaps it is possible to add a google search to >> the site to search the examples? I am not sure but that might be easiest, >> self updating and work best. >> >>> >>> Interesting that you are using the Google/IO MVP solution. Is that the >>> solution that is explained on the GWT tutorial? I have been using >>> Ext-GWT's MVC, which I found very easy to use in practice and it seems >>> to require a lot less boilerplate code. The major thing I dislike >>> about using Ext-GWT's MVC is that logic ends up in classes that extend >>> Ext-GWT classes. However, it seems a bit painful excercise to tear >>> apart the View and the Presenter, as in the plain GWT solution. Do you >>> really benefit from that in practice? Acting upon the view appears to >>> be very tied to the view implementation. Also, the GWT solution seems >>> to be more abstract, leaving the developers to implement Presenters >>> and Views in their own ways (which may be a good or a bad thing). In >>> our apps the models are the data transfer objects, there are >>> controllers for each cluster of functionality (controllers register on >>> a dispatcher), and the controllers know about the different views, >>> which may update themselves in response to events dispatched by the >>> controller. They views have a method for creating the UI and methods >>> for acting upon it. The controllers contain stuff that you might want >>> to unit test. It does seem that it is easy to create an Ext-GWT like >>> MVC framework using HandlerManager, Handlers and adding simple >>> abstract View class. >>> >> >> The Google MVP pattern is pretty simple (we're using gwt-presenter). The >> bit you need to understand is how it's NOT boilerplated together. All of the >> GWT "best practices" use Gin to @Inject class constructors with what they >> need to exist. They call it "the new new". To be blunt, Gin is really a way >> (using annotations and generators) to produce factories, but obviously >> without the work. I am very happy with it - it only has one known drawback.. >> you still need to boilerplate views to view's via presenters when using the >> uibinder. But that's a worthwhile trade off. >> I might get working on the moving e.t.c in a minute and see if I can get >> something working tonight. >> Cheers >> Andrew >> >>> >>> Greetings, >>> Edwin >>> >>> On 25 May 2010 01:42, Andrew Hughes <ahh...@gm...> wrote: >>> > Hi Edwin, >>> > The 2.1-M1 "MVP" *looks* to target developers on the google app engine >>> > who >>> > want a sping backend. We are using the Google I/O 2009 MVP solution - >>> > it's >>> > really really good! I'm trying hard to get the gwtshowcase working - >>> > but >>> > they have some classes that aren't released with the user or dev jars! >>> > I >>> > will probably raise this as an issue with GWT as I feel they are >>> > releasing >>> > reference/source code that won't work against any gwt releases. >>> > Do you think we can move the current code base down one directory? >>> > So that this gives... >>> > ./pom.xml (parent pom) >>> > ./gwt-openlayers (gwt-openlayers jar) >>> > ./gwt-openlayers-showcase (gwt-openlayers-showcase war) this is a long >>> > name >>> > but it is consistent with other things like the app engine url e.t.c. >>> > This will make it easier for me to get to work :) >>> > --AH >>> > On Tue, May 25, 2010 at 6:14 AM, Edwin Commandeur >>> > <com...@gm...> wrote: >>> >> >>> >> Hi Andrew, >>> >> >>> >> Couldn't find any good info on the new MVP either. I hoped it wasn't >>> >> the MVP they describe in the GWT tutorial >>> >> (http://code.google.com/webtoolkit/articles/mvp-architecture.html), >>> >> because I don't think that is a nice solution. I was more hoping that >>> >> they had a proper eventBus instead of hijacking HandlerManager for >>> >> that, and a little less convoluted solution. >>> >> >>> >> Greetings, >>> >> Edwin >>> >> >>> >> On 23 May 2010 12:49, Andrew Hughes <ahh...@gm...> wrote: >>> >> > Hi Edwin, >>> >> > Thanks heaps for your reply :) >>> >> > FYI: >>> >> > The 2.1-M1 MVP looks nothing like the existing "MVP Best Practices" >>> >> > we've >>> >> > seen come out of google. The only doco I can find is >>> >> > >>> >> > this http://blog.springsource.com/2010/05/19/spring-google-appengine/ >>> >> > and it >>> >> > looks to me like it's about data retrieval from the server! Perhaps >>> >> > I am >>> >> > wrong, we will have to see. >>> >> > I'll try and update the showcase once I find out where the GWT >>> >> > missing >>> >> > classes are! >>> >> > >>> >> > Cheers. >>> >> > --AH >>> >> > >>> >> > >>> >> > On Sat, May 22, 2010 at 8:23 PM, Edwin Commandeur >>> >> > <com...@gm...> wrote: >>> >> >> >>> >> >> Hi Andrew, >>> >> >> >>> >> >> Great you are putting effort into the showcase. The showcase was >>> >> >> put >>> >> >> together a long time back and with the new MVP framework in GWT 2.1 >>> >> >> I >>> >> >> was thinking of trying that out, but you already have something >>> >> >> going. >>> >> >> One thing I would also like to put in the showcase is a working >>> >> >> 'show >>> >> >> source panel' that uses a syntax highlighting lib like >>> >> >> http://alexgorbatchev.com/wiki/SyntaxHighlighter >>> >> >> >>> >> >> As you know, the showcase was not setup as a Maven project, but as >>> >> >> a >>> >> >> GWT Eclipse plugin project so it would easily run in Eclipse. Right >>> >> >> now you can just open it as an existing GWT Eclipse project, >>> >> >> possibly >>> >> >> change the version of GWT your using and code away. However, I am a >>> >> >> big fan of Maven and would be in faovour of Maven if it can work in >>> >> >> such a way that is easy to run and debug the showcase using the GWT >>> >> >> development mode. >>> >> >> >>> >> >> Having the showcase in the cloud would be a big plus! +1 for that >>> >> >> >>> >> >> +1 for the zero-arg constructor (if Javadoc explains the how and >>> >> >> why) >>> >> >> >>> >> >> RPC of geometry objects would be possible if >>> >> >> a) if we create a GeometryFactory which can take an OpenLayers >>> >> >> geometry, copy all the content to a GWT-OL geometry object >>> >> >> >>> >> >> b) if we create geometries that do not wrap Javascript objects, but >>> >> >> that are converted to OpeneLayers geometry objects when they are >>> >> >> provided as arguments to GWT-OL functions. >>> >> >> >>> >> >> Option b) would be very nice. We should investigate if we can use >>> >> >> the >>> >> >> current objects and no longer let them extend >>> >> >> OpenLayersObjectWrapper, >>> >> >> but let them be native GWT classes implementing IsSerializable (all >>> >> >> the implementations of the methods would change as well). Anywhere >>> >> >> the >>> >> >> objects would then be provided to OpenLayers as arguments there >>> >> >> should >>> >> >> be some GeometryConverter under the hood that copies all properties >>> >> >> to >>> >> >> an OL geometry. >>> >> >> See also: >>> >> >> >>> >> >> >>> >> >> http://code.google.com/webtoolkit/doc/latest/FAQ_Server.html#Does_the_GWT_RPC_system_support_the_use_of_java.io.Serializable >>> >> >> >>> >> >> Greetings, >>> >> >> Edwin >>> >> >> >>> >> >> >>> >> >> On 22 May 2010 10:26, Andrew Hughes <ahh...@gm...> wrote: >>> >> >> > Hi Edwin, >>> >> >> > I'd really like to do some work on the showcase. What I would >>> >> >> > like is >>> >> >> > too... >>> >> >> > >>> >> >> > Take the GWT Showcase application source and replace their >>> >> >> > examples >>> >> >> > with >>> >> >> > ours >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> > (see http://ongwt.googlecode.com/svn/trunk/com.google.gwt.sample.showcase.Showcase/Showcase.html) >>> >> >> > I'm close to getting this working but the (compile time >>> >> >> > annotations >>> >> >> > for >>> >> >> > the >>> >> >> > generators are relying on gwt classes that aren't in the OEM jars >>> >> >> > - >>> >> >> > should >>> >> >> > be able to get this working soon enough). >>> >> >> > Deploy the GWT-OpenLayers Showcase to the google app engine. I >>> >> >> > took >>> >> >> > the >>> >> >> > liberty of registering "gwt-openlayers" (and I need to find out >>> >> >> > how I >>> >> >> > can >>> >> >> > share this with you). >>> >> >> > Populate the showcase with examples.... >>> >> >> > >>> >> >> > This might be just me but I really do feel this should also be a >>> >> >> > maven >>> >> >> > module. I find it very difficult to work with the showcase >>> >> >> > project in >>> >> >> > it's >>> >> >> > current state. >>> >> >> > Just a few other things... >>> >> >> > We need client/server rpc serialization of geometry objects. I >>> >> >> > know >>> >> >> > you >>> >> >> > said >>> >> >> > you had been working on this, any chance I could see how you're >>> >> >> > trying >>> >> >> > todo >>> >> >> > this? >>> >> >> > We use the UiBinder heaps in our app, the way it applies styles >>> >> >> > and >>> >> >> > layout >>> >> >> > means that the MapWidget should offer a zero arg default >>> >> >> > constructor. >>> >> >> > I >>> >> >> > don't believe there is any requirements from OpenLayers for width >>> >> >> > and >>> >> >> > height >>> >> >> > on init. I think a zero arg constructor might be a good idea (I >>> >> >> > do >>> >> >> > have >>> >> >> > a >>> >> >> > workaround) >>> >> >> > Cheers. >>> >> > >>> >> > >>> > >>> > >> > > |
|
From: Edwin C. <com...@gm...> - 2010-05-25 08:31:27
|
Hi Andrew, Moving the code base down a directory as you suggest is definitely a good idea! It was a mistake to have the src dir at the same level as the showcase dir. Better a long descriptive name (gwt-openlayers-showcase) than a short name that is less descriptive :). Are you taking the actual GWT showcase code as a skeleton? Is that code free to use that way? The showcase makes use of generators, aren't those generating stuff you are missing? There are two things that would be nice to have, which are not in the standard GWT showcase: 1) Tooltips over the tree items to provide a short description of the example; 2) A search function for easily looking up examples. Interesting that you are using the Google/IO MVP solution. Is that the solution that is explained on the GWT tutorial? I have been using Ext-GWT's MVC, which I found very easy to use in practice and it seems to require a lot less boilerplate code. The major thing I dislike about using Ext-GWT's MVC is that logic ends up in classes that extend Ext-GWT classes. However, it seems a bit painful excercise to tear apart the View and the Presenter, as in the plain GWT solution. Do you really benefit from that in practice? Acting upon the view appears to be very tied to the view implementation. Also, the GWT solution seems to be more abstract, leaving the developers to implement Presenters and Views in their own ways (which may be a good or a bad thing). In our apps the models are the data transfer objects, there are controllers for each cluster of functionality (controllers register on a dispatcher), and the controllers know about the different views, which may update themselves in response to events dispatched by the controller. They views have a method for creating the UI and methods for acting upon it. The controllers contain stuff that you might want to unit test. It does seem that it is easy to create an Ext-GWT like MVC framework using HandlerManager, Handlers and adding simple abstract View class. Greetings, Edwin On 25 May 2010 01:42, Andrew Hughes <ahh...@gm...> wrote: > Hi Edwin, > The 2.1-M1 "MVP" *looks* to target developers on the google app engine who > want a sping backend. We are using the Google I/O 2009 MVP solution - it's > really really good! I'm trying hard to get the gwtshowcase working - but > they have some classes that aren't released with the user or dev jars! I > will probably raise this as an issue with GWT as I feel they are releasing > reference/source code that won't work against any gwt releases. > Do you think we can move the current code base down one directory? > So that this gives... > ./pom.xml (parent pom) > ./gwt-openlayers (gwt-openlayers jar) > ./gwt-openlayers-showcase (gwt-openlayers-showcase war) this is a long name > but it is consistent with other things like the app engine url e.t.c. > This will make it easier for me to get to work :) > --AH > On Tue, May 25, 2010 at 6:14 AM, Edwin Commandeur > <com...@gm...> wrote: >> >> Hi Andrew, >> >> Couldn't find any good info on the new MVP either. I hoped it wasn't >> the MVP they describe in the GWT tutorial >> (http://code.google.com/webtoolkit/articles/mvp-architecture.html), >> because I don't think that is a nice solution. I was more hoping that >> they had a proper eventBus instead of hijacking HandlerManager for >> that, and a little less convoluted solution. >> >> Greetings, >> Edwin >> >> On 23 May 2010 12:49, Andrew Hughes <ahh...@gm...> wrote: >> > Hi Edwin, >> > Thanks heaps for your reply :) >> > FYI: >> > The 2.1-M1 MVP looks nothing like the existing "MVP Best Practices" >> > we've >> > seen come out of google. The only doco I can find is >> > this http://blog.springsource.com/2010/05/19/spring-google-appengine/ >> > and it >> > looks to me like it's about data retrieval from the server! Perhaps I am >> > wrong, we will have to see. >> > I'll try and update the showcase once I find out where the GWT missing >> > classes are! >> > >> > Cheers. >> > --AH >> > >> > >> > On Sat, May 22, 2010 at 8:23 PM, Edwin Commandeur >> > <com...@gm...> wrote: >> >> >> >> Hi Andrew, >> >> >> >> Great you are putting effort into the showcase. The showcase was put >> >> together a long time back and with the new MVP framework in GWT 2.1 I >> >> was thinking of trying that out, but you already have something going. >> >> One thing I would also like to put in the showcase is a working 'show >> >> source panel' that uses a syntax highlighting lib like >> >> http://alexgorbatchev.com/wiki/SyntaxHighlighter >> >> >> >> As you know, the showcase was not setup as a Maven project, but as a >> >> GWT Eclipse plugin project so it would easily run in Eclipse. Right >> >> now you can just open it as an existing GWT Eclipse project, possibly >> >> change the version of GWT your using and code away. However, I am a >> >> big fan of Maven and would be in faovour of Maven if it can work in >> >> such a way that is easy to run and debug the showcase using the GWT >> >> development mode. >> >> >> >> Having the showcase in the cloud would be a big plus! +1 for that >> >> >> >> +1 for the zero-arg constructor (if Javadoc explains the how and why) >> >> >> >> RPC of geometry objects would be possible if >> >> a) if we create a GeometryFactory which can take an OpenLayers >> >> geometry, copy all the content to a GWT-OL geometry object >> >> >> >> b) if we create geometries that do not wrap Javascript objects, but >> >> that are converted to OpeneLayers geometry objects when they are >> >> provided as arguments to GWT-OL functions. >> >> >> >> Option b) would be very nice. We should investigate if we can use the >> >> current objects and no longer let them extend OpenLayersObjectWrapper, >> >> but let them be native GWT classes implementing IsSerializable (all >> >> the implementations of the methods would change as well). Anywhere the >> >> objects would then be provided to OpenLayers as arguments there should >> >> be some GeometryConverter under the hood that copies all properties to >> >> an OL geometry. >> >> See also: >> >> >> >> http://code.google.com/webtoolkit/doc/latest/FAQ_Server.html#Does_the_GWT_RPC_system_support_the_use_of_java.io.Serializable >> >> >> >> Greetings, >> >> Edwin >> >> >> >> >> >> On 22 May 2010 10:26, Andrew Hughes <ahh...@gm...> wrote: >> >> > Hi Edwin, >> >> > I'd really like to do some work on the showcase. What I would like is >> >> > too... >> >> > >> >> > Take the GWT Showcase application source and replace their examples >> >> > with >> >> > ours >> >> > >> >> > >> >> > (see http://ongwt.googlecode.com/svn/trunk/com.google.gwt.sample.showcase.Showcase/Showcase.html) >> >> > I'm close to getting this working but the (compile time annotations >> >> > for >> >> > the >> >> > generators are relying on gwt classes that aren't in the OEM jars - >> >> > should >> >> > be able to get this working soon enough). >> >> > Deploy the GWT-OpenLayers Showcase to the google app engine. I took >> >> > the >> >> > liberty of registering "gwt-openlayers" (and I need to find out how I >> >> > can >> >> > share this with you). >> >> > Populate the showcase with examples.... >> >> > >> >> > This might be just me but I really do feel this should also be a >> >> > maven >> >> > module. I find it very difficult to work with the showcase project in >> >> > it's >> >> > current state. >> >> > Just a few other things... >> >> > We need client/server rpc serialization of geometry objects. I know >> >> > you >> >> > said >> >> > you had been working on this, any chance I could see how you're >> >> > trying >> >> > todo >> >> > this? >> >> > We use the UiBinder heaps in our app, the way it applies styles and >> >> > layout >> >> > means that the MapWidget should offer a zero arg default constructor. >> >> > I >> >> > don't believe there is any requirements from OpenLayers for width and >> >> > height >> >> > on init. I think a zero arg constructor might be a good idea (I do >> >> > have >> >> > a >> >> > workaround) >> >> > Cheers. >> > >> > > > |
|
From: Edwin C. <com...@gm...> - 2010-05-22 10:53:33
|
Hi Andrew, Great you are putting effort into the showcase. The showcase was put together a long time back and with the new MVP framework in GWT 2.1 I was thinking of trying that out, but you already have something going. One thing I would also like to put in the showcase is a working 'show source panel' that uses a syntax highlighting lib like http://alexgorbatchev.com/wiki/SyntaxHighlighter As you know, the showcase was not setup as a Maven project, but as a GWT Eclipse plugin project so it would easily run in Eclipse. Right now you can just open it as an existing GWT Eclipse project, possibly change the version of GWT your using and code away. However, I am a big fan of Maven and would be in faovour of Maven if it can work in such a way that is easy to run and debug the showcase using the GWT development mode. Having the showcase in the cloud would be a big plus! +1 for that +1 for the zero-arg constructor (if Javadoc explains the how and why) RPC of geometry objects would be possible if a) if we create a GeometryFactory which can take an OpenLayers geometry, copy all the content to a GWT-OL geometry object b) if we create geometries that do not wrap Javascript objects, but that are converted to OpeneLayers geometry objects when they are provided as arguments to GWT-OL functions. Option b) would be very nice. We should investigate if we can use the current objects and no longer let them extend OpenLayersObjectWrapper, but let them be native GWT classes implementing IsSerializable (all the implementations of the methods would change as well). Anywhere the objects would then be provided to OpenLayers as arguments there should be some GeometryConverter under the hood that copies all properties to an OL geometry. See also: http://code.google.com/webtoolkit/doc/latest/FAQ_Server.html#Does_the_GWT_RPC_system_support_the_use_of_java.io.Serializable Greetings, Edwin On 22 May 2010 10:26, Andrew Hughes <ahh...@gm...> wrote: > Hi Edwin, > I'd really like to do some work on the showcase. What I would like is too... > > Take the GWT Showcase application source and replace their examples with > ours > (see http://ongwt.googlecode.com/svn/trunk/com.google.gwt.sample.showcase.Showcase/Showcase.html) > I'm close to getting this working but the (compile time annotations for the > generators are relying on gwt classes that aren't in the OEM jars - should > be able to get this working soon enough). > Deploy the GWT-OpenLayers Showcase to the google app engine. I took the > liberty of registering "gwt-openlayers" (and I need to find out how I can > share this with you). > Populate the showcase with examples.... > > This might be just me but I really do feel this should also be a maven > module. I find it very difficult to work with the showcase project in it's > current state. > Just a few other things... > We need client/server rpc serialization of geometry objects. I know you said > you had been working on this, any chance I could see how you're trying todo > this? > We use the UiBinder heaps in our app, the way it applies styles and layout > means that the MapWidget should offer a zero arg default constructor. I > don't believe there is any requirements from OpenLayers for width and height > on init. I think a zero arg constructor might be a good idea (I do have a > workaround) > Cheers. |
|
From: Edwin C. <com...@gm...> - 2010-05-02 20:51:19
|
Hi Hans, Did you try the suggestions by Jon Britton? Appararently he got it working with the latest snapshot (see gwt-ol website for link). I found an older post by Carsten in the mailing list who got OSM working as well and gave some example code. The wrapper code is just a very thin, easy to understand layer (have a look at some of the Layer classes), so if you know how it works in Javascript it should be a small step to work out how it works in GWT, or how it should work in GWT. If I look at the OpenLayers code for a simple OSM map (http://openlayers.org/dev/examples/) it should be as easy to add an OSM layer to the map as: layer = new OpenLayers.Layer.OSM( "Simple OSM Map"); map.addLayer(layer); However, if I look at the OSM implementation in GWT-OL it is returning an OSM layer like this: return new $wnd.OpenLayers.Layer.OSM.Mapnik(name) This is a constructor as it appears in http://www.openstreetmap.org/openlayers/OpenStreetMap.js, which calls the plain OSM constructor, but adds some extra (perhaps unwanted) options. It is unclear to me at this point, when to use or when not to use the 'OpenStreetMap.js' code. This dependency is not in any of the current OpenLayers examples I could find on http://openlayers.org/dev/examples/, and I always found it a bit murky why OSM is hosting their own little library on top of OpenLayers instead of contributing it to OL core. The advanced OSM examples of OpenLayers are not even using OSM for the rasters, but a WMS layer portraying OSM data. Possibly, this is necessary to do the advanced features, but even if you just want the OSM layers as background you could consider adding them as WMS layers as in the Advanced OSM example. If anybody knows what is the present best way to use OSM with OpenLayers please let me know. I guess we do not want to break code that already depends on the existing OSM, but we do want to get up-to-date. Greetings, Edwin Commandeur 2010/5/2 Hans Terje Møller <han...@ho...>: > Hi. > > I worte to you a few weeks ago about using OSM in gwt-openlayers. Do you > know about someone in your development group that could help me understand > how to use the OSM class? > If you do, please send me their e-mail adress. > > Thanks in advance! > > Regards, > Hans Terje Møller > |
|
From: Edwin C. <com...@gm...> - 2010-04-30 18:33:38
|
Hi Andrew, silly of me indeed :)... I get it now. As long as each developer stores his or her username/password in the local settings.xml that should work! The example fragment could be included in a comment for copying/pasting into settings.xml. Very nice way of putting maven to work. We need to test it, but it seems like a great addition to the project. Have a nice weekend! Greetings, Edwin P.S. I have been working a bit on the proxy, but haven't checked anything in yet. It seemed the current copy/paste code (which is quite an ugly piece of code) failed because it did not pass the Content-Length header. See the HTTP 1/1 spec: The presence of a message-body in a request is signaled by the inclusion of a Content-Length or Transfer-Encoding header field in the request's message-headers. and For compatibility with HTTP/1.0 applications, HTTP/1.1 requests containing a message-body MUST include a valid Content-Length header field unless the server is known to be HTTP/1.1 compliant. On 30 April 2010 18:28, Andrew Hughes <ahh...@gm...> wrote: > looks like it might need to add the following to the pom.xml, does > 'frs.sourceforge.net:/home/frs/project/o/op/openlayers_gwt' look right to > you? > > <distributionManagement> > <repository> > <id>openlayers_gwt</id> > > <name>OpenLayers GWT Sourceforge Releases</name> > > <url>scp://frs.sourceforge.net:/home/frs/project/o/op/openlayers_gwt/maven/releases</url> > </repository> > <snapshotRepository> > <id>openlayers_gwt</id> > > <name>OpenLayers GWT Sourceforge Snapshots</name> > > > <url>scp://frs.sourceforge.net:/home/frs/project/o/op/openlayers_gwt/maven/snapshots</url> > <layout>legacy</layout> > </snapshotRepository> > > <site> > > <id>openlayers_gwt</id> > > <name>OpenLayers GWT Sourceforge Sites</name> > > > <url>scp://frs.sourceforge.net:/home/frs/project/o/op/openlayers_gwt/maven/sites</url> > > </site> > > </distributionManagement> > > You will also need to add your sf username and password to your > ~/.m2/settings.xml (using . > <?xml version="1.0" encoding="UTF-8"?> > <settings> > <servers> > <server> > <id>openlayers_gwt</id> > <username>ecommand,openlayers_gwt</username> > <password>myvoiceismypassword</password> > </server> > </servers> > </settings> > I haven't tested yet... but that should do everything from snapshots, > releases, repository hosting and site deployment (like javadoc's e.t.c). > :) > > On Sat, May 1, 2010 at 1:42 AM, Andrew Hughes <ahh...@gm...> wrote: >> >> Howdy :) >> >> On Sat, May 1, 2010 at 12:24 AM, Edwin Commandeur >> <com...@gm...> wrote: >>> >>> hi Andrew, >>> >>> Do I understand it well that it is necessary for distribution >>> management that the snapshots are available via ftp / scp? Currently >>> the latest snapshot is available in a folder on the website over http. >> >> Now that would be silly :) Maven only needs ftp / scp to perform the >> deploy (i.e. publish/write). Maven (or ant+ivy) projects can then fetch the >> dependency via http. Edwin uploads via ftp or scp but he download via http - >> maven will do the same. It's good todo maven snapshot deploys as it manages >> the complicated nature of snapshot versioning - even snapshots have >> versioning. Also, it takes about 1min to setup providing you know the scp:// >> url. >> >>> >>> All GWT-OL developers have the rights to do acces the web environment >>> hosted by SF. Just use your own SF account and follow the instructions >>> here: https://sourceforge.net/apps/trac/sourceforge/wiki/Project%20web >>> (see also the developer docs for this link) >>> >>> If a snapshot has to be available over ftp/scp for the outside world >>> then we need to evaluate the options. As far as I know the released >>> files are only avaiable via the web (the SF download site or a link to >>> it) and not via ftp/scp for the outside world, but maybe someone knows >>> more. Any suggestions are welcome... >>> >> >> I suggest you have a good weekend! :) >> >>> >>> Greetings, >>> Edwin >>> >>> On 30 April 2010 02:57, Andrew Hughes <ahh...@gm...> wrote: >>> > Heya, >>> > Can I suggest we add some <distrobutionManagement> to the pom.xml? Then >>> > we >>> > can deploy snapshot builds directly from maven, we can also deploy a >>> > release >>> > and consuming project's and repository managers can consume them via a >>> > <repository> in their pom's? >>> > This is probably about 5mins work if you want me to do it, but I will >>> > need a >>> > user/pass and scp or ftp url (scp would be preferred). >>> > Cheers >>> > --AH >>> > >>> > On Fri, Apr 30, 2010 at 5:25 AM, Edwin Commandeur >>> > <com...@gm...> wrote: >>> >> >>> >> Hi Andrew, >>> >> >>> >> Right now it's pretty primitive and I upload them by hand :(... >>> >> >>> >> That is via scp/ ftp see the dev manual about GWT-OL website, which >>> >> links to SF documentation. >>> >> >>> >> Greetings, >>> >> Edwin >>> >> >>> >> On 29 April 2010 16:16, Andrew Hughes <ahh...@gm...> wrote: >>> >> > Hey, how do you deploy to /latest ? is that via scp / ftp / manual >>> >> > upload ? >>> >> > What do sf offer in terms of maven snapshot deploy locations? >>> >> > Cheers :) >>> >> > >>> >> > On Fri, Apr 23, 2010 at 7:28 AM, Edwin Commandeur >>> >> > <com...@gm...> wrote: >>> >> >> >>> >> >> Hi John, >>> >> >> >>> >> >> Check the Layer.addOptions method in the latest source: >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> http://gwt-openlayers.sourceforge.net/latest/openlayers_gwt-0.5-SNAPSHOT.jar >>> >> >> >>> >> >> Greetings, >>> >> >> Edwin >>> >> >> >>> >> >> On 20 April 2010 15:59, Jon Britton <jon...@go...> >>> >> >> wrote: >>> >> >> > Hi, >>> >> >> > Currently the Layer.addOptions(..) method is not available in >>> >> >> > gwt-openlayers. I've created a ticket for this, but would really >>> >> >> > appreciate >>> >> >> > any updates regarding this issue. >>> >> >> > Thanks! >>> >> >> > Jon >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> > ------------------------------------------------------------------------------ >>> >> >> > Download Intel® 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 mailing list >>> >> >> Gwt...@li... >>> >> >> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users >>> >> > >>> >> > >>> > >>> > >> > > |
|
From: Edwin C. <com...@gm...> - 2010-04-30 14:54:25
|
hi Andrew, Do I understand it well that it is necessary for distribution management that the snapshots are available via ftp / scp? Currently the latest snapshot is available in a folder on the website over http. All GWT-OL developers have the rights to do acces the web environment hosted by SF. Just use your own SF account and follow the instructions here: https://sourceforge.net/apps/trac/sourceforge/wiki/Project%20web (see also the developer docs for this link) If a snapshot has to be available over ftp/scp for the outside world then we need to evaluate the options. As far as I know the released files are only avaiable via the web (the SF download site or a link to it) and not via ftp/scp for the outside world, but maybe someone knows more. Any suggestions are welcome... Greetings, Edwin On 30 April 2010 02:57, Andrew Hughes <ahh...@gm...> wrote: > Heya, > Can I suggest we add some <distrobutionManagement> to the pom.xml? Then we > can deploy snapshot builds directly from maven, we can also deploy a release > and consuming project's and repository managers can consume them via a > <repository> in their pom's? > This is probably about 5mins work if you want me to do it, but I will need a > user/pass and scp or ftp url (scp would be preferred). > Cheers > --AH > > On Fri, Apr 30, 2010 at 5:25 AM, Edwin Commandeur > <com...@gm...> wrote: >> >> Hi Andrew, >> >> Right now it's pretty primitive and I upload them by hand :(... >> >> That is via scp/ ftp see the dev manual about GWT-OL website, which >> links to SF documentation. >> >> Greetings, >> Edwin >> >> On 29 April 2010 16:16, Andrew Hughes <ahh...@gm...> wrote: >> > Hey, how do you deploy to /latest ? is that via scp / ftp / manual >> > upload ? >> > What do sf offer in terms of maven snapshot deploy locations? >> > Cheers :) >> > >> > On Fri, Apr 23, 2010 at 7:28 AM, Edwin Commandeur >> > <com...@gm...> wrote: >> >> >> >> Hi John, >> >> >> >> Check the Layer.addOptions method in the latest source: >> >> >> >> >> >> >> >> http://gwt-openlayers.sourceforge.net/latest/openlayers_gwt-0.5-SNAPSHOT.jar >> >> >> >> Greetings, >> >> Edwin >> >> >> >> On 20 April 2010 15:59, Jon Britton <jon...@go...> wrote: >> >> > Hi, >> >> > Currently the Layer.addOptions(..) method is not available in >> >> > gwt-openlayers. I've created a ticket for this, but would really >> >> > appreciate >> >> > any updates regarding this issue. >> >> > Thanks! >> >> > Jon >> >> > >> >> > >> >> > ------------------------------------------------------------------------------ >> >> > Download Intel® 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 mailing list >> >> Gwt...@li... >> >> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users >> > >> > > > |
|
From: Mikael C. <mik...@cl...> - 2010-04-07 09:42:31
|
Hi all, I'm going to try to wrap some MapFish client javasript, my aim is to get something similar to this example : http://demo.mapfish.org/mapfishsample/1.2/demos/geostat/geostat.html Has anyone ever tried to wrap MapFish ? -- Mikael |
|
From: Edwin C. <com...@gm...> - 2010-03-30 09:21:05
|
Hi Stefan, Thanks for noticing that the Toolbar classes extend Control instead of Panel. You are right in that they should extend Panel! Could you make a ticket for that in Trac. That would be a simple thing to change. In addition the inconsistent spelling of Toolbar/ToolBar should also be corrected IMHO. I always think that Toolbar is one word and should therefore not be camelcased, but as long as it is consistent it is fine. NavigationHistory is not in the GWT-OL 0.2 jar that is available on SF. Perhaps, you have a modified version of that jar with source code for that Control. As it is the goal to wrap OL as extensively as possible (ideally completely, except for legacy ways to do things in OL) the NavigationHistory Control should be added to trunk. Browsing the source on SF I saw the latest tag is 8 months ago. Time to find some time for wrapping things up to get 0.5 out (move some Trac tickes to 0.6)! Greetings, Edwin On 30 March 2010 09:01, Stefan Printz <qui...@us...> wrote: > Hello, > > For two years I took advantage of GWT-OL in version 0.2. I will now switch > to the current version. In version 0.2, I use the NavigationHistory, there > is a reason that those in the current version no longer exists? If not, I > would like to set them again. > In the controls, I noticed that the classes NavToolBar and EditingToolbar > extends from controllers. In OpenLayers these classes are extends from > OpenLayers.Control.Panel. > I would like to change this and commit or something speaks against it? > > Greetings, > Stefan > > ------------------------------------------------------------------------------ > Download Intel® 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-devl mailing list > Gwt...@li... > https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-devl > > |
|
From: Stefan P. <qui...@us...> - 2010-03-30 08:01:51
|
Hello, For two years I took advantage of GWT-OL in version 0.2. I will now switch to the current version. In version 0.2, I use the NavigationHistory, there is a reason that those in the current version no longer exists? If not, I would like to set them again. In the controls, I noticed that the classes NavToolBar and EditingToolbar extends from controllers. In OpenLayers these classes are extends from OpenLayers.Control.Panel. I would like to change this and commit or something speaks against it? Greetings, Stefan |
|
From: Edwin C. <com...@gm...> - 2010-03-25 16:25:59
|
Hi Mikael, After pulling the latest changes from Hg, I saw that you committed the DefferedCommand fix. However, Eclipse started to bark at the override annotation. I looked it up and Command is an interface, so technichally the execute method is implemented in the anonymous Command class rather than overridden. So, although the Maven build completes successfully, I would propose to remove the override annotation as it gives an error in Eclipse. I am not sure why the Eclipse java builder complains, while the builder invoked by Maven (javac?) doesn't. See also this blogpost: http://blogs.sun.com/ahe/entry/override Would you mind if I removed the override annotation? Greetings, Edwin |
|
From: Mikael C. <mik...@cl...> - 2010-03-15 17:55:16
|
Hi Edwin, No problem, it's my fault, it will teach me to push my commits on time ! I think I didn't break any of your code, but maybe you'll want to check. BTW Poul, from my tests I have come to the conclusion that OL doesn't work well with WFS v1.1, so I used v1.0. Maybe you should try that. Mikael 2010/3/15 Edwin Commandeur <com...@gm...> > Hi Mikael, > > Sorry for the toe stepping. I will not push the additional setters for > version, srsName and will await your changes. > > As for the proxy. I am not so literate with servlets, so I am reading > up and experimenting a bit. The resourceUrl/targetUrl for GET/POST > should be replaced by one parameter I think (e.g., remoteUrl) and the > method should be inferred from the request to the proxy. Are you good > with servlets? Would you have time to work on the proxy servlet? > > Greetings, > Edwin > > 2010/3/15 Mikael Couzic <mik...@cl...>: > > Hi guys, > > > > I'm looking at your mails right now, it reminded me I had some work on > WFS > > protocol I hadn't pushed. I'm afraid we're stepping on each other's toes, > so > > please hold on while I look at it and I'll get back to you soon. > > > > Mikael > > > > > > 2010/3/15 Edwin Commandeur <com...@gm...> > >> > >> Hi Poul, > >> > >> I checked and it seems it are not the options where it goes wrong in > >> the BasicWFS example. When I post the WFS query generated by the > >> wfsExample layer with Poster (a Firefox add-on) then I get back a WFS > >> FeatureCollection, but when the WFS query goes through the > >> gwtOpenLayersProxy I get an error message: > >> > >> <ows:Exception exceptionCode="MissingParameterValue" locator="request"> > >> <ows:ExceptionText>Could not determine geoserver request from http > >> request POST /geoserver/wfs HTTP/1.1 (...) </ows:ExceptionText> > >> > >> Sth seems go wrong with proxying the request. > >> > >> Do you use the gwtOpenLayersProxy, the OL Python proxy, or some other > >> proxy? > >> > >> Are all the options you specify necessary? It seems that you are > >> passing the default geometryName and srsName, only a non-default WFS > >> version. The schema location is optional and in the OL example the > >> schema location is not used. Maybe only specifying the non-default WFS > >> version is enough for you. > >> > >> Greetings, > >> Edwin > >> > >> On 15 March 2010 14:17, paweluz <pa...@tl...> wrote: > >> > Let me now if it helps :) > >> > I am curies do you also get an error while using WFS and VECTOR layer > >> > like this: > >> > > >> > uncaught exception: [Exception... "Component returned failure code: > >> > 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIXMLHttpRequest.send]" > nsresult: > >> > "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: > >> > http://openlayers.org/api/2.8/OpenLayers.js :: anonymous :: line > 1081" data: > >> > no] > >> > > >> > or is this only in my case... > >> > > >> > Please let me know... > >> > Poul > >> > > >> > > >> > > >> > Dnia 15 marca 2010 13:47 Edwin Commandeur <com...@gm... > > > >> > napisał(a): > >> > > >> >> Hi Poul, > >> >> > >> >> Thanks! I had come to the point where I could see the WFS request > >> >> being made, but got an error message from geoserver that I needed to > >> >> look into to get the BasicWFS working. I will look at your changes > and > >> >> addn additional setters to WFSProtocol. > >> >> > >> >> Greetings, > >> >> Edwin > >> >> > >> >> > >> >> On 15 March 2010 13:03, paweluz <pa...@tl...> wrote: > >> >> > Hi Edwin! > >> >> > > >> >> > I have seen your newest changes on GWT in > >> >> > > >> >> > > >> >> > > http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/rev/17787e046d5e > >> >> > > >> >> > I have to say it does not work form me. I have to add some > additional > >> >> > information to finally see the vector layer on the map... > >> >> > > >> >> > My Vector Layer definition looks like this: > >> >> > > >> >> > private void createVectorLayer(){ > >> >> > WFSProtocolOptions wfsProtocolOptions = new > >> >> > WFSProtocolOptions(); > >> >> > > >> >> > wfsProtocolOptions.setUrl("http://localhost:8080/geoserver/wfs"); > >> >> > wfsProtocolOptions.setFeatureType("tasmania_roads"); > >> >> > > >> >> > wfsProtocolOptions.setFeatureNameSpace(" > http://www.openplans.org/topp"); > >> >> > > >> >> > wfsProtocolOptions.getJSObject().setProperty("srsName", > >> >> > "EPSG:4326"); > >> >> > wfsProtocolOptions.getJSObject().setProperty("version", > >> >> > "1.1.0"); > >> >> > wfsProtocolOptions.getJSObject().setProperty("geometryName", > >> >> > "the_geom"); > >> >> > wfsProtocolOptions.getJSObject().setProperty("schema", > >> >> > " > http://localhost:8080/geoserver/wfs/DescribeFeatureType?version=1.1.0&typename=topp:tasmania_roads > "); > >> >> > > >> >> > WFSProtocol wfsProtocol = new > WFSProtocol(wfsProtocolOptions); > >> >> > String url = wfsProtocol.getUrl(); > >> >> > url.length(); > >> >> > VectorOptions vectorOptions = new VectorOptions(); > >> >> > vectorOptions.getJSObject().setProperty("protocol", > >> >> > wfsProtocol.getJSObject()); > >> >> > vectorOptions.setProtocol(wfsProtocol); > >> >> > vectorOptions.setStrategies(new Strategy[]{new > >> >> > BBoxStrategy()}); > >> >> > vectorLayer = new Vector("My Vector Layer", vectorOptions); > >> >> > }} > >> >> > > >> >> > I do not know if you can see your Vector layer. If not try my > >> >> > approach... Hope I helped... > >> >> > > >> >> > Cheers and thanks for developing GWT-OL :) > >> >> > Poul, > >> >> > > >> >> > > >> >> > >> > > >> > >> > >> > ------------------------------------------------------------------------------ > >> Download Intel® 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-devl mailing list > >> Gwt...@li... > >> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-devl > > > > > > > > -- > > Mikael Couzic > > Pôle Business Intelligence > > Groupe Cliris > > > -- Mikael Couzic Pôle Business Intelligence Groupe Cliris |
|
From: Edwin C. <com...@gm...> - 2010-03-15 15:12:35
|
Hi Mikael, Sorry for the toe stepping. I will not push the additional setters for version, srsName and will await your changes. As for the proxy. I am not so literate with servlets, so I am reading up and experimenting a bit. The resourceUrl/targetUrl for GET/POST should be replaced by one parameter I think (e.g., remoteUrl) and the method should be inferred from the request to the proxy. Are you good with servlets? Would you have time to work on the proxy servlet? Greetings, Edwin 2010/3/15 Mikael Couzic <mik...@cl...>: > Hi guys, > > I'm looking at your mails right now, it reminded me I had some work on WFS > protocol I hadn't pushed. I'm afraid we're stepping on each other's toes, so > please hold on while I look at it and I'll get back to you soon. > > Mikael > > > 2010/3/15 Edwin Commandeur <com...@gm...> >> >> Hi Poul, >> >> I checked and it seems it are not the options where it goes wrong in >> the BasicWFS example. When I post the WFS query generated by the >> wfsExample layer with Poster (a Firefox add-on) then I get back a WFS >> FeatureCollection, but when the WFS query goes through the >> gwtOpenLayersProxy I get an error message: >> >> <ows:Exception exceptionCode="MissingParameterValue" locator="request"> >> <ows:ExceptionText>Could not determine geoserver request from http >> request POST /geoserver/wfs HTTP/1.1 (...) </ows:ExceptionText> >> >> Sth seems go wrong with proxying the request. >> >> Do you use the gwtOpenLayersProxy, the OL Python proxy, or some other >> proxy? >> >> Are all the options you specify necessary? It seems that you are >> passing the default geometryName and srsName, only a non-default WFS >> version. The schema location is optional and in the OL example the >> schema location is not used. Maybe only specifying the non-default WFS >> version is enough for you. >> >> Greetings, >> Edwin >> >> On 15 March 2010 14:17, paweluz <pa...@tl...> wrote: >> > Let me now if it helps :) >> > I am curies do you also get an error while using WFS and VECTOR layer >> > like this: >> > >> > uncaught exception: [Exception... "Component returned failure code: >> > 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIXMLHttpRequest.send]" nsresult: >> > "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: >> > http://openlayers.org/api/2.8/OpenLayers.js :: anonymous :: line 1081" data: >> > no] >> > >> > or is this only in my case... >> > >> > Please let me know... >> > Poul >> > >> > >> > >> > Dnia 15 marca 2010 13:47 Edwin Commandeur <com...@gm...> >> > napisał(a): >> > >> >> Hi Poul, >> >> >> >> Thanks! I had come to the point where I could see the WFS request >> >> being made, but got an error message from geoserver that I needed to >> >> look into to get the BasicWFS working. I will look at your changes and >> >> addn additional setters to WFSProtocol. >> >> >> >> Greetings, >> >> Edwin >> >> >> >> >> >> On 15 March 2010 13:03, paweluz <pa...@tl...> wrote: >> >> > Hi Edwin! >> >> > >> >> > I have seen your newest changes on GWT in >> >> > >> >> > >> >> > http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/rev/17787e046d5e >> >> > >> >> > I have to say it does not work form me. I have to add some additional >> >> > information to finally see the vector layer on the map... >> >> > >> >> > My Vector Layer definition looks like this: >> >> > >> >> > private void createVectorLayer(){ >> >> > WFSProtocolOptions wfsProtocolOptions = new >> >> > WFSProtocolOptions(); >> >> > >> >> > wfsProtocolOptions.setUrl("http://localhost:8080/geoserver/wfs"); >> >> > wfsProtocolOptions.setFeatureType("tasmania_roads"); >> >> > >> >> > wfsProtocolOptions.setFeatureNameSpace("http://www.openplans.org/topp"); >> >> > >> >> > wfsProtocolOptions.getJSObject().setProperty("srsName", >> >> > "EPSG:4326"); >> >> > wfsProtocolOptions.getJSObject().setProperty("version", >> >> > "1.1.0"); >> >> > wfsProtocolOptions.getJSObject().setProperty("geometryName", >> >> > "the_geom"); >> >> > wfsProtocolOptions.getJSObject().setProperty("schema", >> >> > "http://localhost:8080/geoserver/wfs/DescribeFeatureType?version=1.1.0&typename=topp:tasmania_roads"); >> >> > >> >> > WFSProtocol wfsProtocol = new WFSProtocol(wfsProtocolOptions); >> >> > String url = wfsProtocol.getUrl(); >> >> > url.length(); >> >> > VectorOptions vectorOptions = new VectorOptions(); >> >> > vectorOptions.getJSObject().setProperty("protocol", >> >> > wfsProtocol.getJSObject()); >> >> > vectorOptions.setProtocol(wfsProtocol); >> >> > vectorOptions.setStrategies(new Strategy[]{new >> >> > BBoxStrategy()}); >> >> > vectorLayer = new Vector("My Vector Layer", vectorOptions); >> >> > }} >> >> > >> >> > I do not know if you can see your Vector layer. If not try my >> >> > approach... Hope I helped... >> >> > >> >> > Cheers and thanks for developing GWT-OL :) >> >> > Poul, >> >> > >> >> > >> >> >> > >> >> >> ------------------------------------------------------------------------------ >> Download Intel® 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-devl mailing list >> Gwt...@li... >> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-devl > > > > -- > Mikael Couzic > Pôle Business Intelligence > Groupe Cliris > |
|
From: Mikael C. <mik...@cl...> - 2010-03-15 14:31:53
|
Hi guys, I'm looking at your mails right now, it reminded me I had some work on WFS protocol I hadn't pushed. I'm afraid we're stepping on each other's toes, so please hold on while I look at it and I'll get back to you soon. Mikael 2010/3/15 Edwin Commandeur <com...@gm...> > Hi Poul, > > I checked and it seems it are not the options where it goes wrong in > the BasicWFS example. When I post the WFS query generated by the > wfsExample layer with Poster (a Firefox add-on) then I get back a WFS > FeatureCollection, but when the WFS query goes through the > gwtOpenLayersProxy I get an error message: > > <ows:Exception exceptionCode="MissingParameterValue" locator="request"> > <ows:ExceptionText>Could not determine geoserver request from http > request POST /geoserver/wfs HTTP/1.1 (...) </ows:ExceptionText> > > Sth seems go wrong with proxying the request. > > Do you use the gwtOpenLayersProxy, the OL Python proxy, or some other > proxy? > > Are all the options you specify necessary? It seems that you are > passing the default geometryName and srsName, only a non-default WFS > version. The schema location is optional and in the OL example the > schema location is not used. Maybe only specifying the non-default WFS > version is enough for you. > > Greetings, > Edwin > > On 15 March 2010 14:17, paweluz <pa...@tl...> wrote: > > Let me now if it helps :) > > I am curies do you also get an error while using WFS and VECTOR layer > like this: > > > > uncaught exception: [Exception... "Component returned failure code: > 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIXMLHttpRequest.send]" nsresult: > "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: > http://openlayers.org/api/2.8/OpenLayers.js :: anonymous :: line 1081" > data: no] > > > > or is this only in my case... > > > > Please let me know... > > Poul > > > > > > > > Dnia 15 marca 2010 13:47 Edwin Commandeur <com...@gm...> > napisał(a): > > > >> Hi Poul, > >> > >> Thanks! I had come to the point where I could see the WFS request > >> being made, but got an error message from geoserver that I needed to > >> look into to get the BasicWFS working. I will look at your changes and > >> addn additional setters to WFSProtocol. > >> > >> Greetings, > >> Edwin > >> > >> > >> On 15 March 2010 13:03, paweluz <pa...@tl...> wrote: > >> > Hi Edwin! > >> > > >> > I have seen your newest changes on GWT in > >> > > >> > > http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/rev/17787e046d5e > >> > > >> > I have to say it does not work form me. I have to add some additional > information to finally see the vector layer on the map... > >> > > >> > My Vector Layer definition looks like this: > >> > > >> > private void createVectorLayer(){ > >> > WFSProtocolOptions wfsProtocolOptions = new > WFSProtocolOptions(); > >> > wfsProtocolOptions.setUrl("http://localhost:8080/geoserver/wfs > "); > >> > wfsProtocolOptions.setFeatureType("tasmania_roads"); > >> > wfsProtocolOptions.setFeatureNameSpace(" > http://www.openplans.org/topp"); > >> > > >> > wfsProtocolOptions.getJSObject().setProperty("srsName", > "EPSG:4326"); > >> > wfsProtocolOptions.getJSObject().setProperty("version", > "1.1.0"); > >> > wfsProtocolOptions.getJSObject().setProperty("geometryName", > "the_geom"); > >> > wfsProtocolOptions.getJSObject().setProperty("schema", " > http://localhost:8080/geoserver/wfs/DescribeFeatureType?version=1.1.0&typename=topp:tasmania_roads > "); > >> > > >> > WFSProtocol wfsProtocol = new WFSProtocol(wfsProtocolOptions); > >> > String url = wfsProtocol.getUrl(); > >> > url.length(); > >> > VectorOptions vectorOptions = new VectorOptions(); > >> > vectorOptions.getJSObject().setProperty("protocol", > wfsProtocol.getJSObject()); > >> > vectorOptions.setProtocol(wfsProtocol); > >> > vectorOptions.setStrategies(new Strategy[]{new > BBoxStrategy()}); > >> > vectorLayer = new Vector("My Vector Layer", vectorOptions); > >> > }} > >> > > >> > I do not know if you can see your Vector layer. If not try my > approach... Hope I helped... > >> > > >> > Cheers and thanks for developing GWT-OL :) > >> > Poul, > >> > > >> > > >> > > > > > ------------------------------------------------------------------------------ > Download Intel® 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-devl mailing list > Gwt...@li... > https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-devl > -- Mikael Couzic Pôle Business Intelligence Groupe Cliris |
8 messages has been excluded from this view by a project administrator.
