13 messages in com.googlegroups.google-gadgets-apiRe: __MODULE_ID__: how static is it?| From | Sent On | Attachments |
|---|---|---|
| gurkesaft | 08 Jun 2006 14:36 | |
| Seige | 09 Jun 2006 10:48 | |
| gurkesaft | 10 Jun 2006 13:20 | |
| Seige | 10 Jun 2006 13:29 | |
| Google Employee | 11 Jun 2006 08:10 | |
| gurkesaft | 11 Jun 2006 08:41 | |
| Google Employee | 11 Jun 2006 10:24 | |
| gurkesaft | 12 Jun 2006 07:07 | |
| Seige | 12 Jun 2006 08:15 | |
| Google Employee | 12 Jun 2006 16:41 | |
| gurkesaft | 13 Jun 2006 07:31 | |
| gurkesaft | 13 Jun 2006 07:33 | |
| jjru...@gmail.com | 25 Jun 2006 07:04 |
| Subject: | Re: __MODULE_ID__: how static is it?![]() |
|---|---|
| From: | gurkesaft (jack...@gmail.com) |
| Date: | 06/12/2006 07:07:09 AM |
| List: | com.googlegroups.google-gadgets-api |
Hallo Ralph,
You can't speak German? How on earth do you yell at people when you're angry?
Speaking of, I've tried to make IE yell at me about my javascript cookies, but I can't unless I tell it to prompt for 1st party cookies. You can try it with my gadget if you like:
http://jack.sankey.googlepages.com/
Every time you "x" off an item, it should try to write a cookie. If I understand correctly, ig, upon loading grabs the source-code for the gadget and shoves it in with the rest of the html. The only cookie functionality I use is javascript setting and getting from your machine locally. I can't see how IE would recognize that my javascript code isn't from google. Are you perhaps referring to a different (more common / more useful) use of cookies than what I'm doing? I'm probably not using them in the way most people do, mainly because I don't know a thing about them :)
Thanks for all your help. I really appreciate this forum!
Jack
PS- the way to make google/ig forget things is to
(a) find a slow internet connection (b) move lots of modules around as fast as possible and then close the window quickly or refresh the page
Sometimes it forgets when I remove a module, too (I'm constantly adding/removing developer.xml). You have to be faster than the ig's upload attempts. This was especially a big problem for my script because on many days it takes about a second to upload this long string I'm using, and if you're "x"ing off a bunch of items very quickly, you're making a lot of prefs.set() calls with large prefs strings. There was a sort of internet storm one day, and I couldn't get it to remember anything without waiting 3 seconds in between clicks. That's all fixed now with my cookie code. Unless you're accessing ig from two computers simultaneously :)




