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

[jamesmikedupont at googlemail.com]

well, the idea was to see if it would load faster than an applet.
we will see what the performance will be like.
at least I am learning the josm code better, I have identified some
areas that might be able to be optimized.
an applet will take a while to load, the webpage promises to maybe
faster, it is also possble to do server side rendering and processing.
the attraction is that you can move code transparently from the client
to the server, and there is a a nice debugger.
mike


On Wed, May 26, 2010 at 10:36 PM, Frederik Ramm <frederik at remote.org> wrote:
> Hi,
>
> jamesmikedupont at googlemail.com wrote:
>>
>> gwt is a java to javascript compiler that promises to allow us to port
>> parts of the josm to an very thin client,
>> i have the absolute basics (just points) being displayed now, check it
>> out.
>
> Forgive my being thick but I still don't see the point. Surely Javascript
> that has been auto-generated from JOSM Java code will never be able to match
> a proper editor devised in Javascript from the ground up, and there have
> been impressive steps in that direction (chrschmidt's OpenLayers based
> feature editor comes to mind).
>
> If one wants more than that, one can run JOSM as an applet in the browser.
>
> Is there really any hope that you will arrive at a anything remotely usable
> by modifying JOSM so that it is a better basis for auto-generating
> Javascript code? This sounds very much like wishful thinking to me. I mean
> you're free to try of course, I'm sure it is an interesting experiment ;-)
>
> And Avar, if one wanted some kind of more or less clean engine/library as a
> basis for other projects, JOSM would be the worst choice in my eyes. Much
> better to start with either the JOSM-NG codebase or the existing Java osmlib
> that has been built for Traveling Salesman!
>
> Bye
> Frederik
>
> --
> Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"
>