I wanted to let everyone know that I've got basic Google Maps support done,
along with a TMap control, and it will be available soon:

http://www.elevatesoft.com/maptestide.png
http://www.elevatesoft.com/maptestrun.png

I just need to finish up some of the wrapper code for the map properties.

You can perform basic mapping, including using geocoder functionality to
translate addresses into locations, all in Object Pascal code.  EWB handles
the dynamic loading of the Google Maps API, and has events that are fired
when its loaded.  EWB also handles making sure that only one copy of the API
is loaded.

The native map instance is also exposed, in case you need to perform some
functionality that is in the API, but not surfaced in the control.  The most
of the API is declared in the WebDOM unit, but not all of it is used in the
control yet.

Finally, as part of these changes, I finally got around to adding JS
namespace support in the external class interfaces to the compiler, so you
can now do something like this:

  external TGoogleMapOptions emit google.maps.MapOptions = class
     public
        { Properties }
        property backgroundColor: String read write;
        property center: TGoogleLatLng read write;
...............

So, no more need for wonky nested class properties just to be able to emit
JS namespaces.

Tim Young
Elevate Software
www.elevatesoft.com

Excellent, I shall look forward to that when I get back from my holidays

Chris Holland
[Team Elevate]

On 29/06/2015 14:21, Tim Young [Elevate Software] wrote:
> I wanted to let everyone know that I've got basic Google Maps support
> done, along with a TMap control, and it will be available soon:
>
> http://www.elevatesoft.com/maptestide.png
> http://www.elevatesoft.com/maptestrun.png
>
> I just need to finish up some of the wrapper code for the map properties.
>
> You can perform basic mapping, including using geocoder functionality to
> translate addresses into locations, all in Object Pascal code.  EWB
> handles the dynamic loading of the Google Maps API, and has events that
> are fired when its loaded.  EWB also handles making sure that only one
> copy of the API is loaded.
>
> The native map instance is also exposed, in case you need to perform
> some functionality that is in the API, but not surfaced in the control.
> The most of the API is declared in the WebDOM unit, but not all of it is
> used in the control yet.
>
> Finally, as part of these changes, I finally got around to adding JS
> namespace support in the external class interfaces to the compiler, so
> you can now do something like this:
>
>    external TGoogleMapOptions emit google.maps.MapOptions = class
>       public
>          { Properties }
>          property backgroundColor: String read write;
>          property center: TGoogleLatLng read write;
> ..............
>
> So, no more need for wonky nested class properties just to be able to
> emit JS namespaces.
>
> Tim Young
> Elevate Software
> www.elevatesoft.com

Wish this forum had a LIKE 'button'.

Great!  Will this make it into the next build?