Hi Norbert,
> What do you mean by "...starting writing a new integration..."? Do you change the gemsource implementation or do you start from scratch? In any case I'm interested and can help of it is needed.
At first, I wanted to convert the gemsource implementation to Seaside30 and Maps APIv3.
Making it work for Seaside3.0 is quite trivial (duno about changing to API v3) but I soon realized it's not exactly how I want the implementation to be.
My vision is to have the google maps api more integrated with how Seaside's javascript generation works.
To clarify that, I think it's best to take a look at the first incantation I just published on
http://www.squeaksource.com/SeasideGoogleMapsV3There are already 3 examples that implement the same examples as in Google's documentation. The script generation should look familiar if you often use the Javascript generation in Seaside.
The reason I prefer this way of working is that I have had good experience integrating external Javascript with Seaside-generated Javascript, the latter being necessary if the script itself has to be generated from a database or if the script requires Seaside callbacks in it.
Well, it's still in it's infancy at the moment, but I'm progressing well and hope the vision I have will prove to work ;-)
Of course, any help is much appreciated. Just drop me a note and I will add you to the developer's list.
Best wishes!
Johan_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
