[Seaside] Re: Is seaside supporting google maps API?
Gastón Dall' Oglio
gaston.dalloglio at gmail.com
Wed Oct 3 11:54:28 UTC 2012
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 at schrievkrom.de>
> I've noticed, that the Google Component has
> updateRoot: anHtmlRoot
> super updateRoot: anHtmlRoot.
> url: 'https://maps.google.com/maps/api/js?sensor=false'.
> which is actually not put in the header and/or not executed. As I
> When I put this in the header (like jquery, jquery.css and jqm.js in my
> first component) actually I get some output.
> Am 02.10.2012 18:35, schrieb Nick Ager:
>> On 2 October 2012 16:53, marten <itlists at schrievkrom.de
>> <mailto:itlists at 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
>> JQM preloads the page before the transition so my guess is that the
>> JQM rewrites html document addLoadScript: '' to initialise on page load,
>> resulting in the correct code for JQM" However if the map library is
>> won't work correctly under JQM. See
>> 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
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside