[OSM-dev] start of gwtosm the google webtoolkit port of josm

[jamesmikedupont at googlemail.com]

OK,
I have not been able to get the client side connection running,
so I moved the http request to the java server side and not the client
requests the uri via rpc and gets the data.
now the program works, it can fetch an osm url and render it, the bbox
is not calculated right yet, but that will be next.

mike

On Mon, May 31, 2010 at 7:38 PM, jamesmikedupont at googlemail.com
<jamesmikedupont at googlemail.com> wrote:
> Today, I was able to get the zoom, and bounding boxes to be
> dynamically be changed.
> next to add in the ability to load data from the api server.
> mike
>
> On Wed, May 26, 2010 at 8:19 PM, jamesmikedupont at googlemail.com
> <jamesmikedupont at googlemail.com> wrote:
>> Hi,
>>
>> I have refactored some core classes in josm to run in gwt.
>> this includes most of  data classes. I am porting the graphic output
>> to use gwt graphics and svg output.
>> Goal is to get the josm core code running in gwt, first the display
>> code and then to build the the edit functions.
>> there are ways to move also rendering to the server side, and the code
>> is all java, compiled by gwt into javascript using a canvas object and
>> svg data.
>>
>> here is a screen-shot :
>> http://www.scribd.com/doc/32005145/Example-Out-of-gwt-osm-port
>>
>> code here:
>> http://github.com/h4ck3rm1k3/GWTOsm
>> git clone git at github.com:h4ck3rm1k3/GWTOsm.git
>>
>> I am using eclipse gwt plugins :
>> http://dl.google.com/eclipse/plugin/3.5 -
>> http://dl.google.com/eclipse/plugin/3.5
>>
>> and also the gwt-2.0.3 http://code.google.com/webtoolkit/gettingstarted.html
>> and the two graphics libs
>> the canvas and the vaadin gwtgraphcsi >
>>  <inherits name='com.google.gwt.widgetideas.WidgetIdeas' />
>>        <inherits name='org.vaadin.gwtgraphics.GWTGraphics'/>
>>
>> Currently having problems with http requests, is using a static xml
>> loaded into as a resource.
>> need to rework the xml parsing, sax does not seem to be directly supported.
>>
>> but you can at least see node positions being displayed.
>>
>> more to come, all help is welcome. please help test and write test
>> cases for josm core code.
>> the more tests we have, the easier it is to port the code.
>>
>> mike
>>
>