It looks like the latest version at http://seaside.gemstone.com/ss/GoogleMaps.html has a timestamp of 2010-03-02. Which version of Seaside are you using? Seaside 3.0 was released six months later (see http://news.squeak.org/2010/09/12/seaside-3-0-released/), so perhaps you should start with the Seaside that was current when that package was written. Try the Seaside One-Click Experience for 2.8.4 found at http://www.seaside.st/download/pharo#16819391.

On Sep 30, 2012, at 10:35 AM, Lorenzo Schiavina wrote:

Hi James

I installed Google maps, but I cannot see them because SU Library is missing; can you tell me how to load it?

Many thanks

Lorenzo

Da: seaside-bounces@lists.squeakfoundation.org [mailto:seaside-bounces@lists.squeakfoundation.org] Per conto di James Foster Inviato: domenica 30 settembre 2012 18.40 A: Seaside - general discussion Oggetto: Re: [Seaside] Is seaside supporting google maps API?

A quick Google search turns up the following:

http://forum.world.st/google-maps-api-v3-td3168030.html which references http://seaside.gemstone.com/ss/GoogleMaps.html.

James

On Sep 30, 2012, at 7:12 AM, Ernesto Bossi wrote:

Hi, i want to know if seaside has already implemented the Google API or it's being developed currently?

Thanks in advance

Ernesto

View this message in context: Is seaside supporting google maps API? Sent from the Seaside General mailing list archive at Nabble.com. _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

---

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

I answer myself: they are ok. The code is - by the way - for GoogleMap V2: "the Google Maps JavaScript API Version 2 has been officially deprecated as of May 19, 2010. The V2 API will continue to work until May 19, 2013"

Marten

Am 30.09.2012 20:06, schrieb Marten Feldtmann:

Are the archive ok, I tried to unzip them but always got errors !?

Marten

---

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Nice stuff and it worked out of the box - when I removed the code with the APIKey.

But I have a problem I can not solve: All the examples work as expected - but then I tried to call those examples from another page they do not work.

I've a simple JQM class with only this rendering method, but when pressing the button I only get this waiting progress icon and it does not work.

html div jqmHeader; jqmTheme: 'b'; with: [ html heading jqmTheme: 'b'; with: DateAndTime now asString. html anchor jqmIcon: 'info'; jqmIconNoText; callback: [self show: GMControlSimple new ]; with: 'Info'.

].

-- View this message in context: http://forum.world.st/Is-seaside-supporting-google-maps-API-tp4649635p464990... Sent from the Seaside General mailing list archive at Nabble.com.

On 2 October 2012 16:53, marten itlists@schrievkrom.de wrote:

To be more correct. If I register the application via WAAdmin the functionality is given(show: works), but the look and feel is gone. If I register it via JQMAdmin the look and feel is ok, but the functionality is gone.

JQM preloads the page before the transition so my guess is that the javascript map initialisation is not being called correctly. That said JQM rewrites html document addLoadScript: '' to initialise on page load, resulting in the correct code for JQM" However if the map library is using another Seaside or javascript page initialisation method that won't work correctly under JQM. See http://jquerymobile.seasidehosting.st/seaside/javascript/jquery-mobile/Event...

If my guess is correct you'd need to find out if the map library is initialised explicitly from within Seaside and if so use html document addLoadScript: type initialisation. If there is no explicit initialisation see if google supports explicit initialisation and add that to html document addLoadScript:

Hope this helps

Nick

Hello.

Maybe lack indicate *Google Component* as a child in his father component to be executed their #updateRoot? If I remember correctly this is necessary.

2012/10/2 Marten Feldtmann itlists@schrievkrom.de

I've noticed, that the Google Component has

updateRoot: anHtmlRoot

super updateRoot: anHtmlRoot. anHtmlRoot javascript url: 'https://maps.google.com/maps/api/js?sensor=false'.

which is actually not put in the header and/or not executed. As I understand the code above: it loads additional javascript stuff.

When I put this in the header (like jquery, jquery.css and jqm.js in my first component) actually I get some output.

Marten

Am 02.10.2012 18:35, schrieb Nick Ager:

...

On 2 October 2012 16:53, marten <itlists@schrievkrom.de mailto:itlists@schrievkrom.de> wrote:

To be more correct. If I register the application via WAAdmin the
functionality is given(show: works), but the look and feel is gone.

If I register it via JQMAdmin the look and feel is ok, but the functionality is gone.

JQM preloads the page before the transition so my guess is that the javascript map initialisation is not being called correctly. That said JQM rewrites html document addLoadScript: '' to initialise on page load, resulting in the correct code for JQM" However if the map library is using another Seaside or javascript page initialisation method that won't work correctly under JQM. See

http://jquerymobile.seasidehosting.st/seaside/javascript/jquery-mobile/Event...

If my guess is correct you'd need to find out if the map library is initialised explicitly from within Seaside and if so use html document addLoadScript: type initialisation. If there is no explicit initialisation see if google supports explicit initialisation and add that to html document addLoadScript:

Hope this helps

Nick

---

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

---

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Let me know your login and I add you the developer list.

Johan (sent from my mobile)

On 01 Oct 2012, at 00:57, Oscar E A Callaú oalvarez@dcc.uchile.cl wrote:

Hi Guys,

I remember to use google maps V3 for a simple tracker in a project (Seaside 3.0.X) the last year. I was using:

http://www.squeaksource.com/SeasideGoogleMapsV3/

Which is very simple, however It does not have all google map api features ported to Smalltalk code. This is because, I extended it to use GMPolyline (this extension is attached).

It would be great, If you can extend it to use more features, and post your updates.

Cheers

<Seaside-GoogleMapsV3-Extensions-OzC.3.mcz>

On Sep 30, 2012, at 15:50 , Marten Feldtmann itlists@schrievkrom.de wrote:

...

I answer myself: they are ok. The code is - by the way - for GoogleMap V2: "the Google Maps JavaScript API Version 2 has been officially deprecated as of May 19, 2010. The V2 API will continue to work until May 19, 2013"

Marten

Am 30.09.2012 20:06, schrieb Marten Feldtmann:

...

Are the archive ok, I tried to unzip them but always got errors !?

Marten

---

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

---

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

---

seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside