I'm proud to announce "Gadget-to-Gadget Communication", otherwise known as PubSub, which is a killer new beta feature that's currently available for you all to try out!
==== What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
PubSub allows multiple gadgets on the same page to send and receive data from each other. In other words, you can now build a gadget that communicates back and forth with one another. This introduces a brand new concept and strategy involved when writing gadgets. Information is no longer constrained to fit inside a single gadget. Instead, you can now split up various pieces of information amongst multiple gadgets and allow them to communicate with each other to paint a bigger picture. Gadgets now have the ability to be more closely integrated with one another and present a network of information to users. If users only care about one particular segment, they can simply remove or minimize any gadgets containing extraneous information that they don't care about.
==== How does PubSub work?
PubSub is a new framework which allows 'publisher' gadgets on iGoogle to communicate changes to 'subscriber' gadgets that have declared interest in those changes. This is currently available only on iGoogle and publisher/subscriber gadgets must be on the same page. For a list of current issues and limitations, see more information below.
*Note:* As a beta feature, documentation on PubSub is not currently linked to from the Google Gadgets API developer guide or anywhere else.
==== What's a BETA-feature?
It's an early release of a feature in order get valuable feedback from real gadget developers (all of you) about the current design along with some ideas on how to make it better. We can't promise that you won't encounter any bugs since it's still a beta. However, when any changes arise, we'll notify everyone about the change by posting it to this thread. We're thrilled to hear your opinions on the design as well as any creative ideas on how to use it. If you have any questions or comments, please let us know.
In the meantime, here's the current list of limitations and known issues: -- Need more practical examples. Coming soon. -- Does not work in Safari. Works correctly in Firefox and IE. -- Only works in iGoogle. Does not work on third-party websites or other container pages such as Google Desktop. -- Only available to type="html" and type="html-inline" gadgets. -- Does not work consistently when multiple inlined (type="html- inline") "subscriber" gadgets exist on the same page in iGoogle. -- Moving (drag/dropping) a "subscriber" gadget to a different position in iGoogle creates an error. PubSub ceases to work afterwards. -- The "finance_symbol" channel described in the documentation is currently broken. -- Publisher gadgets cannot pass empty strings to subscriber gadgets. -- JavaScript error is sometimes thrown when loading gadgets on iGoogle. -- Browser 'Stop' buttons sometimes have strange flickering behavior.
====
As always, please reply back with any feedback or comments you may have. We'd love to hear from you!
Y'all just make this too much fun! I'm looking forward to playing around with this feature. I did create a quick and dirty little gadget that takes an address, gecodes it and publishes the lat/long in the geoinfo group as a test. It works with the existing Listening Map. Will do more later. The URL is http://mikeg101.googlepages.com/mylocation.xml
Things I have noticed...
1. I installed the PubSub tab to start playing around. My Gadgets insists that nothing is cached, but I had a heck of a time getting by the cache on my new gadget on the PubSub tab. Had to do things like remove the gadget, add it back, reload it and just keep hoping. I have not noticed this on other tabs. not yet anyway. I'm using Firefox 2.0.0.6.
2. Will group names be reserved like channel names? It looks like geoinfo will become a standard group name for talking to maps. Or is it up to developers to coordinate this?
3. It's late and I can't recall my third point, so I'll close by saying that this is cool stuff! Thanks!
On Aug 23, 6:52 pm, "Dann (Google Employee)" <d...@google.com> wrote:
> I'm proud to announce "Gadget-to-Gadget Communication", otherwise > known as PubSub, which is a killer new beta feature that's currently > available for you all to try out!
> ==== > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> PubSub allows multiple gadgets on the same page to send and receive > data from each other. In other words, you can now build a gadget that > communicates back and forth with one another. This introduces a brand > new concept and strategy involved when writing gadgets. Information > is no longer constrained to fit inside a single gadget. Instead, you > can now split up various pieces of information amongst multiple > gadgets and allow them to communicate with each other to paint a > bigger picture. Gadgets now have the ability to be more closely > integrated with one another and present a network of information to > users. If users only care about one particular segment, they can > simply remove or minimize any gadgets containing extraneous > information that they don't care about.
> ==== > How does PubSub work?
> PubSub is a new framework which allows 'publisher' gadgets on iGoogle > to communicate changes to 'subscriber' gadgets that have declared > interest in those changes. This is currently available only on > iGoogle and publisher/subscriber gadgets must be on the same page. > For a list of current issues and limitations, see more information > below.
> *Note:* As a beta feature, documentation on PubSub is not currently > linked to from the Google Gadgets API developer guide or anywhere > else.
> ==== > What's a BETA-feature?
> It's an early release of a feature in order get valuable feedback from > real gadget developers (all of you) about the current design along > with some ideas on how to make it better. We can't promise that you > won't encounter any bugs since it's still a beta. However, when any > changes arise, we'll notify everyone about the change by posting it to > this thread. We're thrilled to hear your opinions on the design as > well as any creative ideas on how to use it. If you have any > questions or comments, please let us know.
> In the meantime, here's the current list of limitations and known > issues: > -- Need more practical examples. Coming soon. > -- Does not work in Safari. Works correctly in Firefox and IE. > -- Only works in iGoogle. Does not work on third-party websites or > other container pages such as Google Desktop. > -- Only available to type="html" and type="html-inline" gadgets. > -- Does not work consistently when multiple inlined (type="html- > inline") "subscriber" gadgets exist on the same page in iGoogle. > -- Moving (drag/dropping) a "subscriber" gadget to a different > position in iGoogle creates an error. PubSub ceases to work > afterwards. > -- The "finance_symbol" channel described in the documentation is > currently broken. > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > -- JavaScript error is sometimes thrown when loading gadgets on > iGoogle. > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> ====
> As always, please reply back with any feedback or comments you may > have. We'd love to hear from you!
I tried the modified version of example given on the page. Both gadget I made are publisher as well as subscriber.
1) Most of time message are updated . But it get cached and on reload it did not work. I closed igoogle cleared cache and it worked after that (most of the time).
2) Surprising two time it didn't get the mentioned height for gadget (on IE -6.0.2900 & Firefox-2.0.0.6 ). It displayed in small size with scroll bars .
> I'm proud to announce "Gadget-to-Gadget Communication", otherwise > known as PubSub, which is a killer new beta feature that's currently > available for you all to try out!
> ==== > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> PubSub allows multiple gadgets on the same page to send and receive > data from each other. In other words, you can now build a gadget that > communicates back and forth with one another. This introduces a brand > new concept and strategy involved when writing gadgets. Information > is no longer constrained to fit inside a single gadget. Instead, you > can now split up various pieces of information amongst multiple > gadgets and allow them to communicate with each other to paint a > bigger picture. Gadgets now have the ability to be more closely > integrated with one another and present a network of information to > users. If users only care about one particular segment, they can > simply remove or minimize any gadgets containing extraneous > information that they don't care about.
> ==== > How does PubSub work?
> PubSub is a new framework which allows 'publisher' gadgets on iGoogle > to communicate changes to 'subscriber' gadgets that have declared > interest in those changes. This is currently available only on > iGoogle and publisher/subscriber gadgets must be on the same page. > For a list of current issues and limitations, see more information > below.
> *Note:* As a beta feature, documentation on PubSub is not currently > linked to from the Google Gadgets API developer guide or anywhere > else.
> ==== > What's a BETA-feature?
> It's an early release of a feature in order get valuable feedback from > real gadget developers (all of you) about the current design along > with some ideas on how to make it better. We can't promise that you > won't encounter any bugs since it's still a beta. However, when any > changes arise, we'll notify everyone about the change by posting it to > this thread. We're thrilled to hear your opinions on the design as > well as any creative ideas on how to use it. If you have any > questions or comments, please let us know.
> In the meantime, here's the current list of limitations and known > issues: > -- Need more practical examples. Coming soon. > -- Does not work in Safari. Works correctly in Firefox and IE. > -- Only works in iGoogle. Does not work on third-party websites or > other container pages such as Google Desktop. > -- Only available to type="html" and type="html-inline" gadgets. > -- Does not work consistently when multiple inlined (type="html- > inline") "subscriber" gadgets exist on the same page in iGoogle. > -- Moving (drag/dropping) a "subscriber" gadget to a different > position in iGoogle creates an error. PubSub ceases to work > afterwards. > -- The "finance_symbol" channel described in the documentation is > currently broken. > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > -- JavaScript error is sometimes thrown when loading gadgets on > iGoogle. > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> ====
> As always, please reply back with any feedback or comments you may > have. We'd love to hear from you!
3. Would we need a new channel to publish the user entered location (non-geocoded), i.e., "New Orleans LA" ? Or would it be published on rawquery? The subscriber gadgets would most likely use this in their title or perhaps in error messages (No observations near ...).
Thanks.
On Aug 24, 1:22 am, mikeg <mikeg...@gmail.com> wrote:
> Y'all just make this too much fun! I'm looking forward to playing > around with this feature. I did create a quick and dirty little > gadget that takes an address, gecodes it and publishes the lat/long in > the geoinfo group as a test. It works with the existing Listening > Map. Will do more later. The URL ishttp://mikeg101.googlepages.com/mylocation.xml
> Things I have noticed...
> 1. I installed the PubSub tab to start playing around. My Gadgets > insists that nothing is cached, but I had a heck of a time getting by > the cache on my new gadget on the PubSub tab. Had to do things like > remove the gadget, add it back, reload it and just keep hoping. I > have not noticed this on other tabs. not yet anyway. I'm using > Firefox 2.0.0.6.
> 2. Will group names be reserved like channel names? It looks like > geoinfo will become a standard group name for talking to maps. Or is > it up to developers to coordinate this?
> 3. It's late and I can't recall my third point, so I'll close by > saying that this is cool stuff! Thanks!
> On Aug 23, 6:52 pm, "Dann (Google Employee)" <d...@google.com> wrote:
> > Hey everyone!
> > I'm proud to announce "Gadget-to-Gadget Communication", otherwise > > known as PubSub, which is a killer new beta feature that's currently > > available for you all to try out!
> > ==== > > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> > PubSub allows multiple gadgets on the same page to send and receive > > data from each other. In other words, you can now build a gadget that > > communicates back and forth with one another. This introduces a brand > > new concept and strategy involved when writing gadgets. Information > > is no longer constrained to fit inside a single gadget. Instead, you > > can now split up various pieces of information amongst multiple > > gadgets and allow them to communicate with each other to paint a > > bigger picture. Gadgets now have the ability to be more closely > > integrated with one another and present a network of information to > > users. If users only care about one particular segment, they can > > simply remove or minimize any gadgets containing extraneous > > information that they don't care about.
> > ==== > > How does PubSub work?
> > PubSub is a new framework which allows 'publisher' gadgets on iGoogle > > to communicate changes to 'subscriber' gadgets that have declared > > interest in those changes. This is currently available only on > > iGoogle and publisher/subscriber gadgets must be on the same page. > > For a list of current issues and limitations, see more information > > below.
> > *Note:* As a beta feature, documentation on PubSub is not currently > > linked to from the Google Gadgets API developer guide or anywhere > > else.
> > ==== > > What's a BETA-feature?
> > It's an early release of a feature in order get valuable feedback from > > real gadget developers (all of you) about the current design along > > with some ideas on how to make it better. We can't promise that you > > won't encounter any bugs since it's still a beta. However, when any > > changes arise, we'll notify everyone about the change by posting it to > > this thread. We're thrilled to hear your opinions on the design as > > well as any creative ideas on how to use it. If you have any > > questions or comments, please let us know.
> > In the meantime, here's the current list of limitations and known > > issues: > > -- Need more practical examples. Coming soon. > > -- Does not work in Safari. Works correctly in Firefox and IE. > > -- Only works in iGoogle. Does not work on third-party websites or > > other container pages such as Google Desktop. > > -- Only available to type="html" and type="html-inline" gadgets. > > -- Does not work consistently when multiple inlined (type="html- > > inline") "subscriber" gadgets exist on the same page in iGoogle. > > -- Moving (drag/dropping) a "subscriber" gadget to a different > > position in iGoogle creates an error. PubSub ceases to work > > afterwards. > > -- The "finance_symbol" channel described in the documentation is > > currently broken. > > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > > -- JavaScript error is sometimes thrown when loading gadgets on > > iGoogle. > > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> > ====
> > As always, please reply back with any feedback or comments you may > > have. We'd love to hear from you!
Thanks for your trying it out and providing feedback! Nice work on integrating the geocoder. Mind if we borrow it and update our previous example? It certainly beats manually entering in lat/long values. I always end up in an ocean somewhere ;)
Regarding your comments: 1. Sorry, there's a known bug with the developer gadget. Disabling gadget caching is currently broken. We should have a fix up by next week. Here's the existing thread in case you're curious: http://groups.google.com/group/Google-Gadgets-API/browse_thread/threa...
Sometimes refreshing the inner gadget iframe (right click => refresh) seems to refresh changes. Give it a shot and see if that works.
2. Good question. Right now, group names are not reserved, meaning you can define these however you want. This would be a good experiment to try: -- Create two gadgets that publishes a channel with the same name but assigned to unique groups. -- Create a subscriber gadget that listens to one of the channels and specify the group. -- Send out an update from each publisher gadget. -- Determine if the subscriber picks up the message coming from both publishers or only the one from the specified group.
3. Thanks! We think this stuff is pretty cool too and your feedback will help us make it even cooler ;)
Cheers, Dann
On Aug 23, 11:22 pm, mikeg <mikeg...@gmail.com> wrote:
> Y'all just make this too much fun! I'm looking forward to playing > around with this feature. I did create a quick and dirty little > gadget that takes an address, gecodes it and publishes the lat/long in > the geoinfo group as a test. It works with the existing Listening > Map. Will do more later. The URL ishttp://mikeg101.googlepages.com/mylocation.xml
> Things I have noticed...
> 1. I installed the PubSub tab to start playing around. My Gadgets > insists that nothing is cached, but I had a heck of a time getting by > the cache on my new gadget on the PubSub tab. Had to do things like > remove the gadget, add it back, reload it and just keep hoping. I > have not noticed this on other tabs. not yet anyway. I'm using > Firefox 2.0.0.6.
> 2. Will group names be reserved like channel names? It looks like > geoinfo will become a standard group name for talking to maps. Or is > it up to developers to coordinate this?
> 3. It's late and I can't recall my third point, so I'll close by > saying that this is cool stuff! Thanks!
> On Aug 23, 6:52 pm, "Dann (Google Employee)" <d...@google.com> wrote:
> > Hey everyone!
> > I'm proud to announce "Gadget-to-Gadget Communication", otherwise > > known as PubSub, which is a killer new beta feature that's currently > > available for you all to try out!
> > ==== > > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> > PubSub allows multiple gadgets on the same page to send and receive > > data from each other. In other words, you can now build a gadget that > > communicates back and forth with one another. This introduces a brand > > new concept and strategy involved when writing gadgets. Information > > is no longer constrained to fit inside a single gadget. Instead, you > > can now split up various pieces of information amongst multiple > > gadgets and allow them to communicate with each other to paint a > > bigger picture. Gadgets now have the ability to be more closely > > integrated with one another and present a network of information to > > users. If users only care about one particular segment, they can > > simply remove or minimize any gadgets containing extraneous > > information that they don't care about.
> > ==== > > How does PubSub work?
> > PubSub is a new framework which allows 'publisher' gadgets on iGoogle > > to communicate changes to 'subscriber' gadgets that have declared > > interest in those changes. This is currently available only on > > iGoogle and publisher/subscriber gadgets must be on the same page. > > For a list of current issues and limitations, see more information > > below.
> > *Note:* As a beta feature, documentation on PubSub is not currently > > linked to from the Google Gadgets API developer guide or anywhere > > else.
> > ==== > > What's a BETA-feature?
> > It's an early release of a feature in order get valuable feedback from > > real gadget developers (all of you) about the current design along > > with some ideas on how to make it better. We can't promise that you > > won't encounter any bugs since it's still a beta. However, when any > > changes arise, we'll notify everyone about the change by posting it to > > this thread. We're thrilled to hear your opinions on the design as > > well as any creative ideas on how to use it. If you have any > > questions or comments, please let us know.
> > In the meantime, here's the current list of limitations and known > > issues: > > -- Need more practical examples. Coming soon. > > -- Does not work in Safari. Works correctly in Firefox and IE. > > -- Only works in iGoogle. Does not work on third-party websites or > > other container pages such as Google Desktop. > > -- Only available to type="html" and type="html-inline" gadgets. > > -- Does not work consistently when multiple inlined (type="html- > > inline") "subscriber" gadgets exist on the same page in iGoogle. > > -- Moving (drag/dropping) a "subscriber" gadget to a different > > position in iGoogle creates an error. PubSub ceases to work > > afterwards. > > -- The "finance_symbol" channel described in the documentation is > > currently broken. > > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > > -- JavaScript error is sometimes thrown when loading gadgets on > > iGoogle. > > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> > ====
> > As always, please reply back with any feedback or comments you may > > have. We'd love to hear from you!
You are welcome to use my geocoder gadget as an example. Just let me know if you come across a way to improve it.
I'm going to blame the group question on the late hours last night. Like the docs say, groups bundle transactions. I did some tests and it doesn't matter what group name is used in the publisher or subscriber or if they even match as long as the pref/channel names match.
On Aug 24, 1:41 pm, "Dann (Google Employee)" <d...@google.com> wrote:
> Thanks for your trying it out and providing feedback! Nice work on > integrating the geocoder. Mind if we borrow it and update our > previous example? It certainly beats manually entering in lat/long > values. I always end up in an ocean somewhere ;)
> Regarding your comments: > 1. Sorry, there's a known bug with the developer gadget. Disabling > gadget caching is currently broken. We should have a fix up by next > week. Here's the existing thread in case you're curious:http://groups.google.com/group/Google-Gadgets-API/browse_thread/threa...
> Sometimes refreshing the inner gadget iframe (right click => refresh) > seems to refresh changes. Give it a shot and see if that works.
> 2. Good question. Right now, group names are not reserved, meaning > you can define these however you want. This would be a good > experiment to try: > -- Create two gadgets that publishes a channel with the same name but > assigned to unique groups. > -- Create a subscriber gadget that listens to one of the channels and > specify the group. > -- Send out an update from each publisher gadget. > -- Determine if the subscriber picks up the message coming from both > publishers or only the one from the specified group.
> 3. Thanks! We think this stuff is pretty cool too and your feedback > will help us make it even cooler ;)
> Cheers, > Dann
> On Aug 23, 11:22 pm, mikeg <mikeg...@gmail.com> wrote:
> > Y'all just make this too much fun! I'm looking forward to playing > > around with this feature. I did create a quick and dirty little > > gadget that takes an address, gecodes it and publishes the lat/long in > > the geoinfo group as a test. It works with the existing Listening > > Map. Will do more later. The URL ishttp://mikeg101.googlepages.com/mylocation.xml
> > Things I have noticed...
> > 1. I installed the PubSub tab to start playing around. My Gadgets > > insists that nothing is cached, but I had a heck of a time getting by > > the cache on my new gadget on the PubSub tab. Had to do things like > > remove the gadget, add it back, reload it and just keep hoping. I > > have not noticed this on other tabs. not yet anyway. I'm using > > Firefox 2.0.0.6.
> > 2. Will group names be reserved like channel names? It looks like > > geoinfo will become a standard group name for talking to maps. Or is > > it up to developers to coordinate this?
> > 3. It's late and I can't recall my third point, so I'll close by > > saying that this is cool stuff! Thanks!
> > On Aug 23, 6:52 pm, "Dann (Google Employee)" <d...@google.com> wrote:
> > > Hey everyone!
> > > I'm proud to announce "Gadget-to-Gadget Communication", otherwise > > > known as PubSub, which is a killer new beta feature that's currently > > > available for you all to try out!
> > > ==== > > > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> > > PubSub allows multiple gadgets on the same page to send and receive > > > data from each other. In other words, you can now build a gadget that > > > communicates back and forth with one another. This introduces a brand > > > new concept and strategy involved when writing gadgets. Information > > > is no longer constrained to fit inside a single gadget. Instead, you > > > can now split up various pieces of information amongst multiple > > > gadgets and allow them to communicate with each other to paint a > > > bigger picture. Gadgets now have the ability to be more closely > > > integrated with one another and present a network of information to > > > users. If users only care about one particular segment, they can > > > simply remove or minimize any gadgets containing extraneous > > > information that they don't care about.
> > > ==== > > > How does PubSub work?
> > > PubSub is a new framework which allows 'publisher' gadgets on iGoogle > > > to communicate changes to 'subscriber' gadgets that have declared > > > interest in those changes. This is currently available only on > > > iGoogle and publisher/subscriber gadgets must be on the same page. > > > For a list of current issues and limitations, see more information > > > below.
> > > *Note:* As a beta feature, documentation on PubSub is not currently > > > linked to from the Google Gadgets API developer guide or anywhere > > > else.
> > > ==== > > > What's a BETA-feature?
> > > It's an early release of a feature in order get valuable feedback from > > > real gadget developers (all of you) about the current design along > > > with some ideas on how to make it better. We can't promise that you > > > won't encounter any bugs since it's still a beta. However, when any > > > changes arise, we'll notify everyone about the change by posting it to > > > this thread. We're thrilled to hear your opinions on the design as > > > well as any creative ideas on how to use it. If you have any > > > questions or comments, please let us know.
> > > In the meantime, here's the current list of limitations and known > > > issues: > > > -- Need more practical examples. Coming soon. > > > -- Does not work in Safari. Works correctly in Firefox and IE. > > > -- Only works in iGoogle. Does not work on third-party websites or > > > other container pages such as Google Desktop. > > > -- Only available to type="html" and type="html-inline" gadgets. > > > -- Does not work consistently when multiple inlined (type="html- > > > inline") "subscriber" gadgets exist on the same page in iGoogle. > > > -- Moving (drag/dropping) a "subscriber" gadget to a different > > > position in iGoogle creates an error. PubSub ceases to work > > > afterwards. > > > -- The "finance_symbol" channel described in the documentation is > > > currently broken. > > > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > > > -- JavaScript error is sometimes thrown when loading gadgets on > > > iGoogle. > > > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> > > ====
> > > As always, please reply back with any feedback or comments you may > > > have. We'd love to hear from you!
This will obviously be a powerful and popular feature... the question is what to use it for? I would be curious as to what ideas people have? Or what the plans are, if there are any, to create publisher gadgets, and what information they would give? Early insight into that would be great!
Just a thought, may be rubbish: Would it be possible to have a reversed communication flow? Ie where subscribers are still aware of publishers and publishers are still not aware of subscribers - and thend reverse it, so the subscriber gadgets are sending information to the publisher gadget. Subscribers could attach themselves to a publisher gadget which would collate the various information from the subscribers.
Cool feature :) Jody
On Aug 24, 12:52 am, "Dann (Google Employee)" <d...@google.com> wrote:
> I'm proud to announce "Gadget-to-Gadget Communication", otherwise > known as PubSub, which is a killer new beta feature that's currently > available for you all to try out!
> ==== > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> PubSub allows multiple gadgets on the same page to send and receive > data from each other. In other words, you can now build a gadget that > communicates back and forth with one another. This introduces a brand > new concept and strategy involved when writing gadgets. Information > is no longer constrained to fit inside a single gadget. Instead, you > can now split up various pieces of information amongst multiple > gadgets and allow them to communicate with each other to paint a > bigger picture. Gadgets now have the ability to be more closely > integrated with one another and present a network of information to > users. If users only care about one particular segment, they can > simply remove or minimize any gadgets containing extraneous > information that they don't care about.
> ==== > How does PubSub work?
> PubSub is a new framework which allows 'publisher' gadgets on iGoogle > to communicate changes to 'subscriber' gadgets that have declared > interest in those changes. This is currently available only on > iGoogle and publisher/subscriber gadgets must be on the same page. > For a list of current issues and limitations, see more information > below.
> *Note:* As a beta feature, documentation on PubSub is not currently > linked to from the Google Gadgets API developer guide or anywhere > else.
> ==== > What's a BETA-feature?
> It's an early release of a feature in order get valuable feedback from > real gadget developers (all of you) about the current design along > with some ideas on how to make it better. We can't promise that you > won't encounter any bugs since it's still a beta. However, when any > changes arise, we'll notify everyone about the change by posting it to > this thread. We're thrilled to hear your opinions on the design as > well as any creative ideas on how to use it. If you have any > questions or comments, please let us know.
> In the meantime, here's the current list of limitations and known > issues: > -- Need more practical examples. Coming soon. > -- Does not work in Safari. Works correctly in Firefox and IE. > -- Only works in iGoogle. Does not work on third-party websites or > other container pages such as Google Desktop. > -- Only available to type="html" and type="html-inline" gadgets. > -- Does not work consistently when multiple inlined (type="html- > inline") "subscriber" gadgets exist on the same page in iGoogle. > -- Moving (drag/dropping) a "subscriber" gadget to a different > position in iGoogle creates an error. PubSub ceases to work > afterwards. > -- The "finance_symbol" channel described in the documentation is > currently broken. > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > -- JavaScript error is sometimes thrown when loading gadgets on > iGoogle. > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> ====
> As always, please reply back with any feedback or comments you may > have. We'd love to hear from you!
Added rawquery channel to the mylocation gadget. The rawquery is used to publish the user entered address. Lat and long were already published. This allows the google news subscriber demo to grab news about the location you enter. It also allows subscriber gadgets to put a descriptive location in the title or gadget body. Is this proper us of the rawquery channel? The mylocation gadget can be found at http://mikeg101.googlepages.com/mylocation.xml
Did some more experimentation with the nearby marine weather observations gadget. It listens for lat, long and rawquery as a group. I've been using this gadget as well as the map and news subscriber demos to test out mylocation. The weather gadget is at http://mikeg101.googlepages.com/nearby_stations_subscriber.xml
This may be my problem, but figured I'd report it. When I move the nearby_stations_subscriber.xml gadget to a new location on the page, I get stuck in a loop of the following messages: (using Firefox 2.0.0.6)
I'm still wondering what we can do with this technology. Some ideas that come to mind... a. stock portfolio. -- click stock to publish its symbol to subscribers that might provide graphs, news, analysis, sec info, etc for the stock. b. my location that allows the user to control any number of geographically oriented subscribers - weather, restaurants, stores, other nearby services. c. I know there is more... publish products with separate subscribers that return news, prices, reviews, etc. d. maybe even something on movies or other entertainment.
What do y'all think? Where will this take us? It's bed time.
On Aug 23, 6:52 pm, "Dann (Google Employee)" <d...@google.com> wrote:
> I'm proud to announce "Gadget-to-Gadget Communication", otherwise > known as PubSub, which is a killer new beta feature that's currently > available for you all to try out!
> ==== > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> PubSub allows multiple gadgets on the same page to send and receive > data from each other. In other words, you can now build a gadget that > communicates back and forth with one another. This introduces a brand > new concept and strategy involved when writing gadgets. Information > is no longer constrained to fit inside a single gadget. Instead, you > can now split up various pieces of information amongst multiple > gadgets and allow them to communicate with each other to paint a > bigger picture. Gadgets now have the ability to be more closely > integrated with one another and present a network of information to > users. If users only care about one particular segment, they can > simply remove or minimize any gadgets containing extraneous > information that they don't care about.
> ==== > How does PubSub work?
> PubSub is a new framework which allows 'publisher' gadgets on iGoogle > to communicate changes to 'subscriber' gadgets that have declared > interest in those changes. This is currently available only on > iGoogle and publisher/subscriber gadgets must be on the same page. > For a list of current issues and limitations, see more information > below.
> *Note:* As a beta feature, documentation on PubSub is not currently > linked to from the Google Gadgets API developer guide or anywhere > else.
> ==== > What's a BETA-feature?
> It's an early release of a feature in order get valuable feedback from > real gadget developers (all of you) about the current design along > with some ideas on how to make it better. We can't promise that you > won't encounter any bugs since it's still a beta. However, when any > changes arise, we'll notify everyone about the change by posting it to > this thread. We're thrilled to hear your opinions on the design as > well as any creative ideas on how to use it. If you have any > questions or comments, please let us know.
> In the meantime, here's the current list of limitations and known > issues: > -- Need more practical examples. Coming soon. > -- Does not work in Safari. Works correctly in Firefox and IE. > -- Only works in iGoogle. Does not work on third-party websites or > other container pages such as Google Desktop. > -- Only available to type="html" and type="html-inline" gadgets. > -- Does not work consistently when multiple inlined (type="html- > inline") "subscriber" gadgets exist on the same page in iGoogle. > -- Moving (drag/dropping) a "subscriber" gadget to a different > position in iGoogle creates an error. PubSub ceases to work > afterwards. > -- The "finance_symbol" channel described in the documentation is > currently broken. > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > -- JavaScript error is sometimes thrown when loading gadgets on > iGoogle. > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> ====
> As always, please reply back with any feedback or comments you may > have. We'd love to hear from you!
I can think of a gadget that someone with a lot more skill than I have might be able to do, however, I think manipulation of the data from another source might be an intellectual property / copyright violation (?)
On Aug 29, 2:10 am, mikeg <mikeg...@gmail.com> wrote:
> Added rawquery channel to the mylocation gadget. The rawquery is used > to publish the user entered address. Lat and long were already > published. This allows the google news subscriber demo to grab news > about the location you enter. It also allows subscriber gadgets to > put a descriptive location in the title or gadget body. Is this > proper us of the rawquery channel? The mylocation gadget can be found > athttp://mikeg101.googlepages.com/mylocation.xml
> Did some more experimentation with the nearby marine weather > observations gadget. It listens for lat, long and rawquery as a > group. I've been using this gadget as well as the map and news > subscriber demos to test out mylocation. The weather gadget is athttp://mikeg101.googlepages.com/nearby_stations_subscriber.xml
> This may be my problem, but figured I'd report it. When I move the > nearby_stations_subscriber.xml gadget to a new location on the page, I > get stuck in a loop of the following messages: (using Firefox > 2.0.0.6)
> I'm still wondering what we can do with this technology. Some ideas > that come to mind... > a. stock portfolio. -- click stock to publish its symbol to > subscribers that might provide graphs, news, analysis, sec info, etc > for the stock. > b. my location that allows the user to control any number of > geographically oriented subscribers - weather, restaurants, stores, > other nearby services. > c. I know there is more... publish products with separate subscribers > that return news, prices, reviews, etc. > d. maybe even something on movies or other entertainment.
> What do y'all think? Where will this take us? It's bed time.
> On Aug 23, 6:52 pm, "Dann (Google Employee)" <d...@google.com> wrote:
> > Hey everyone!
> > I'm proud to announce "Gadget-to-Gadget Communication", otherwise > > known as PubSub, which is a killer new beta feature that's currently > > available for you all to try out!
> > ==== > > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> > PubSub allows multiple gadgets on the same page to send and receive > > data from each other. In other words, you can now build a gadget that > > communicates back and forth with one another. This introduces a brand > > new concept and strategy involved when writing gadgets. Information > > is no longer constrained to fit inside a single gadget. Instead, you > > can now split up various pieces of information amongst multiple > > gadgets and allow them to communicate with each other to paint a > > bigger picture. Gadgets now have the ability to be more closely > > integrated with one another and present a network of information to > > users. If users only care about one particular segment, they can > > simply remove or minimize any gadgets containing extraneous > > information that they don't care about.
> > ==== > > How does PubSub work?
> > PubSub is a new framework which allows 'publisher' gadgets on iGoogle > > to communicate changes to 'subscriber' gadgets that have declared > > interest in those changes. This is currently available only on > > iGoogle and publisher/subscriber gadgets must be on the same page. > > For a list of current issues and limitations, see more information > > below.
> > *Note:* As a beta feature, documentation on PubSub is not currently > > linked to from the Google Gadgets API developer guide or anywhere > > else.
> > ==== > > What's a BETA-feature?
> > It's an early release of a feature in order get valuable feedback from > > real gadget developers (all of you) about the current design along > > with some ideas on how to make it better. We can't promise that you > > won't encounter any bugs since it's still a beta. However, when any > > changes arise, we'll notify everyone about the change by posting it to > > this thread. We're thrilled to hear your opinions on the design as > > well as any creative ideas on how to use it. If you have any > > questions or comments, please let us know.
> > In the meantime, here's the current list of limitations and known > > issues: > > -- Need more practical examples. Coming soon. > > -- Does not work in Safari. Works correctly in Firefox and IE. > > -- Only works in iGoogle. Does not work on third-party websites or > > other container pages such as Google Desktop. > > -- Only available to type="html" and type="html-inline" gadgets. > > -- Does not work consistently when multiple inlined (type="html- > > inline") "subscriber" gadgets exist on the same page in iGoogle. > > -- Moving (drag/dropping) a "subscriber" gadget to a different > > position in iGoogle creates an error. PubSub ceases to work > > afterwards. > > -- The "finance_symbol" channel described in the documentation is > > currently broken. > > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > > -- JavaScript error is sometimes thrown when loading gadgets on > > iGoogle. > > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> > ====
> > As always, please reply back with any feedback or comments you may > > have. We'd love to hear from you!
Hey, I was wondering why you choose to control the channels ? A more flexible approach could have been to let the publisher declare a channel along with its properties and subscribers can subscribe to particular publisher channels.
This way developers could come up with interesting gadgets more easily. Like, there could be a gadget (style controller) which takes user colour schema preferences as input and all the listeners can update the style when style controller announces that the style is changed.
regards, Tony
On Aug 24, 4:52 am, "Dann (Google Employee)" <d...@google.com> wrote:
> I'm proud to announce "Gadget-to-Gadget Communication", otherwise > known as PubSub, which is a killer new beta feature that's currently > available for you all to try out!
> ==== > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> PubSub allows multiple gadgets on the same page to send and receive > data from each other. In other words, you can now build a gadget that > communicates back and forth with one another. This introduces a brand > new concept and strategy involved when writing gadgets. Information > is no longer constrained to fit inside a single gadget. Instead, you > can now split up various pieces of information amongst multiple > gadgets and allow them to communicate with each other to paint a > bigger picture. Gadgets now have the ability to be more closely > integrated with one another and present a network of information to > users. If users only care about one particular segment, they can > simply remove or minimize any gadgets containing extraneous > information that they don't care about.
> ==== > How does PubSub work?
> PubSub is a new framework which allows 'publisher' gadgets on iGoogle > to communicate changes to 'subscriber' gadgets that have declared > interest in those changes. This is currently available only on > iGoogle and publisher/subscriber gadgets must be on the same page. > For a list of current issues and limitations, see more information > below.
> *Note:* As a beta feature, documentation on PubSub is not currently > linked to from the Google Gadgets API developer guide or anywhere > else.
> ==== > What's a BETA-feature?
> It's an early release of a feature in order get valuable feedback from > real gadget developers (all of you) about the current design along > with some ideas on how to make it better. We can't promise that you > won't encounter any bugs since it's still a beta. However, when any > changes arise, we'll notify everyone about the change by posting it to > this thread. We're thrilled to hear your opinions on the design as > well as any creative ideas on how to use it. If you have any > questions or comments, please let us know.
> In the meantime, here's the current list of limitations and known > issues: > -- Need more practical examples. Coming soon. > -- Does not work in Safari. Works correctly in Firefox and IE. > -- Only works in iGoogle. Does not work on third-party websites or > other container pages such as Google Desktop. > -- Only available to type="html" and type="html-inline" gadgets. > -- Does not work consistently when multiple inlined (type="html- > inline") "subscriber" gadgets exist on the same page in iGoogle. > -- Moving (drag/dropping) a "subscriber" gadget to a different > position in iGoogle creates an error. PubSub ceases to work > afterwards. > -- The "finance_symbol" channel described in the documentation is > currently broken. > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > -- JavaScript error is sometimes thrown when loading gadgets on > iGoogle. > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> ====
> As always, please reply back with any feedback or comments you may > have. We'd love to hear from you!
yes-- this is the obvious design and we started with this originally. Unfortunately, the problem is that authors would each pick different names, and ultimately not be able to communicate with each other. In the long run, we wanted to develop a community of gadgets that can actually communicate in practice, but where the authors did not know about each other's gadgets.
in this regard, Google is acting as a clearinghouse-- we understand that this is role comes with the responsibility to listen carefully to channel name proposals and quickly get these into production. In the meantime, the 'testNNN' channels are available for testing purposes.
so: go ahead and flesh out your style name proposal, try to build consensus with other gadget authors, and we'll add this to the official list of channel names and values.
hope this helps, adam Architect, Google Gadgets
On Aug 31, 5:21 am, thampan <tony.tham...@gmail.com> wrote:
> Hey, > I was wondering why you choose to control the channels ? A more > flexible approach could have been to let the publisher declare a > channel along with its properties and subscribers can subscribe to > particular publisher channels.
> This way developers could come up with interesting gadgets more > easily. Like, there could be a gadget (style controller) which takes > user colour schema preferences as input and all the listeners can > update the style when style controller announces that the style is > changed.
> regards, > Tony
> On Aug 24, 4:52 am, "Dann (Google Employee)" <d...@google.com> wrote:
> > Hey everyone!
> > I'm proud to announce "Gadget-to-Gadget Communication", otherwise > > known as PubSub, which is a killer new beta feature that's currently > > available for you all to try out!
> > ==== > > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> > PubSub allows multiple gadgets on the same page to send and receive > > data from each other. In other words, you can now build a gadget that > > communicates back and forth with one another. This introduces a brand > > new concept and strategy involved when writing gadgets. Information > > is no longer constrained to fit inside a single gadget. Instead, you > > can now split up various pieces of information amongst multiple > > gadgets and allow them to communicate with each other to paint a > > bigger picture. Gadgets now have the ability to be more closely > > integrated with one another and present a network of information to > > users. If users only care about one particular segment, they can > > simply remove or minimize any gadgets containing extraneous > > information that they don't care about.
> > ==== > > How does PubSub work?
> > PubSub is a new framework which allows 'publisher' gadgets on iGoogle > > to communicate changes to 'subscriber' gadgets that have declared > > interest in those changes. This is currently available only on > > iGoogle and publisher/subscriber gadgets must be on the same page. > > For a list of current issues and limitations, see more information > > below.
> > *Note:* As a beta feature, documentation on PubSub is not currently > > linked to from the Google Gadgets API developer guide or anywhere > > else.
> > ==== > > What's a BETA-feature?
> > It's an early release of a feature in order get valuable feedback from > > real gadget developers (all of you) about the current design along > > with some ideas on how to make it better. We can't promise that you > > won't encounter any bugs since it's still a beta. However, when any > > changes arise, we'll notify everyone about the change by posting it to > > this thread. We're thrilled to hear your opinions on the design as > > well as any creative ideas on how to use it. If you have any > > questions or comments, please let us know.
> > In the meantime, here's the current list of limitations and known > > issues: > > -- Need more practical examples. Coming soon. > > -- Does not work in Safari. Works correctly in Firefox and IE. > > -- Only works in iGoogle. Does not work on third-party websites or > > other container pages such as Google Desktop. > > -- Only available to type="html" and type="html-inline" gadgets. > > -- Does not work consistently when multiple inlined (type="html- > > inline") "subscriber" gadgets exist on the same page in iGoogle. > > -- Moving (drag/dropping) a "subscriber" gadget to a different > > position in iGoogle creates an error. PubSub ceases to work > > afterwards. > > -- The "finance_symbol" channel described in the documentation is > > currently broken. > > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > > -- JavaScript error is sometimes thrown when loading gadgets on > > iGoogle. > > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> > ====
> > As always, please reply back with any feedback or comments you may > > have. We'd love to hear from you!
> yes-- this is the obvious design and we started with this originally. > Unfortunately, the problem is that authors would each pick > different names, and ultimately not be able to communicate with > each other. In the long run, we wanted to develop a community > of gadgets that can actually communicate in practice, but where > the authors did not know about each other's gadgets.
> in this regard, Google is acting as a clearinghouse-- we understand > that this is role comes with the responsibility to listen carefully > to channel name proposals and quickly get these into production. > In the meantime, the 'testNNN' channels are available for testing > purposes.
> so: go ahead and flesh out your style name proposal, try to build > consensus with other gadget authors, and we'll add this to the > official list of channel names and values.
> hope this helps, > adam > Architect, Google Gadgets
> On Aug 31, 5:21 am, thampan <tony.tham...@gmail.com> wrote:
> > Hey, > > I was wondering why you choose to control the channels ? A more > > flexible approach could have been to let the publisher declare a > > channel along with its properties and subscribers can subscribe to > > particular publisher channels.
> > This way developers could come up with interesting gadgets more > > easily. Like, there could be a gadget (style controller) which takes > > user colour schema preferences as input and all the listeners can > > update the style when style controller announces that the style is > > changed.
> > regards, > > Tony
> > On Aug 24, 4:52 am, "Dann (Google Employee)" <d...@google.com> wrote:
> > > Hey everyone!
> > > I'm proud to announce "Gadget-to-Gadget Communication", otherwise > > > known as PubSub, which is a killer new beta feature that's currently > > > available for you all to try out!
> > > ==== > > > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> > > PubSub allows multiple gadgets on the same page to send and receive > > > data from each other. In other words, you can now build a gadget that > > > communicates back and forth with one another. This introduces a brand > > > new concept and strategy involved when writing gadgets. Information > > > is no longer constrained to fit inside a single gadget. Instead, you > > > can now split up various pieces of information amongst multiple > > > gadgets and allow them to communicate with each other to paint a > > > bigger picture. Gadgets now have the ability to be more closely > > > integrated with one another and present a network of information to > > > users. If users only care about one particular segment, they can > > > simply remove or minimize any gadgets containing extraneous > > > information that they don't care about.
> > > ==== > > > How does PubSub work?
> > > PubSub is a new framework which allows 'publisher' gadgets on iGoogle > > > to communicate changes to 'subscriber' gadgets that have declared > > > interest in those changes. This is currently available only on > > > iGoogle and publisher/subscriber gadgets must be on the same page. > > > For a list of current issues and limitations, see more information > > > below.
> > > *Note:* As a beta feature, documentation on PubSub is not currently > > > linked to from the Google Gadgets API developer guide or anywhere > > > else.
> > > ==== > > > What's a BETA-feature?
> > > It's an early release of a feature in order get valuable feedback from > > > real gadget developers (all of you) about the current design along > > > with some ideas on how to make it better. We can't promise that you > > > won't encounter any bugs since it's still a beta. However, when any > > > changes arise, we'll notify everyone about the change by posting it to > > > this thread. We're thrilled to hear your opinions on the design as > > > well as any creative ideas on how to use it. If you have any > > > questions or comments, please let us know.
> > > In the meantime, here's the current list of limitations and known > > > issues: > > > -- Need more practical examples. Coming soon. > > > -- Does not work in Safari. Works correctly in Firefox and IE. > > > -- Only works in iGoogle. Does not work on third-party websites or > > > other container pages such as Google Desktop. > > > -- Only available to type="html" and type="html-inline" gadgets. > > > -- Does not work consistently when multiple inlined (type="html- > > > inline") "subscriber" gadgets exist on the same page in iGoogle. > > > -- Moving (drag/dropping) a "subscriber" gadget to a different > > > position in iGoogle creates an error. PubSub ceases to work > > > afterwards. > > > -- The "finance_symbol" channel described in the documentation is > > > currently broken. > > > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > > > -- JavaScript error is sometimes thrown when loading gadgets on > > > iGoogle. > > > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> > > ====
> > > As always, please reply back with any feedback or comments you may > > > have. We'd love to hear from you!
Here's what I'm thinking... I have some basic links like Weather & Headlines preset in a TagCloud. I also have an input for queries outside of these basics. There are Subscibers ready to display the content from the TagCloud (or input).
But also an AI Robot that also does text to speech on some of the content. The robot can be programmed with intelligent response and can learn.
> Looking thru the PubSub examples. I'm getting some ideas. > How would you change to New Search into an Image Search?
> On Aug 31, 6:52 am, adam sah <adam....@gmail.com> wrote:
> > yes-- this is the obvious design and we started with this originally. > > Unfortunately, the problem is that authors would each pick > > different names, and ultimately not be able to communicate with > > each other. In the long run, we wanted to develop a community > > of gadgets that can actually communicate in practice, but where > > the authors did not know about each other's gadgets.
> > in this regard, Google is acting as a clearinghouse-- we understand > > that this is role comes with the responsibility to listen carefully > > to channel name proposals and quickly get these into production. > > In the meantime, the 'testNNN' channels are available for testing > > purposes.
> > so: go ahead and flesh out your style name proposal, try to build > > consensus with other gadget authors, and we'll add this to the > > official list of channel names and values.
> > hope this helps, > > adam > > Architect, Google Gadgets
> > On Aug 31, 5:21 am, thampan <tony.tham...@gmail.com> wrote:
> > > Hey, > > > I was wondering why you choose to control the channels ? A more > > > flexible approach could have been to let the publisher declare a > > > channel along with its properties and subscribers can subscribe to > > > particular publisher channels.
> > > This way developers could come up with interesting gadgets more > > > easily. Like, there could be a gadget (style controller) which takes > > > user colour schema preferences as input and all the listeners can > > > update the style when style controller announces that the style is > > > changed.
> > > regards, > > > Tony
> > > On Aug 24, 4:52 am, "Dann (Google Employee)" <d...@google.com> wrote:
> > > > Hey everyone!
> > > > I'm proud to announce "Gadget-to-Gadget Communication", otherwise > > > > known as PubSub, which is a killer new beta feature that's currently > > > > available for you all to try out!
> > > > ==== > > > > What is "Gadget-to-Gadget Communication", a.k.a. PubSub?
> > > > PubSub allows multiple gadgets on the same page to send and receive > > > > data from each other. In other words, you can now build a gadget that > > > > communicates back and forth with one another. This introduces a brand > > > > new concept and strategy involved when writing gadgets. Information > > > > is no longer constrained to fit inside a single gadget. Instead, you > > > > can now split up various pieces of information amongst multiple > > > > gadgets and allow them to communicate with each other to paint a > > > > bigger picture. Gadgets now have the ability to be more closely > > > > integrated with one another and present a network of information to > > > > users. If users only care about one particular segment, they can > > > > simply remove or minimize any gadgets containing extraneous > > > > information that they don't care about.
> > > > ==== > > > > How does PubSub work?
> > > > PubSub is a new framework which allows 'publisher' gadgets on iGoogle > > > > to communicate changes to 'subscriber' gadgets that have declared > > > > interest in those changes. This is currently available only on > > > > iGoogle and publisher/subscriber gadgets must be on the same page. > > > > For a list of current issues and limitations, see more information > > > > below.
> > > > *Note:* As a beta feature, documentation on PubSub is not currently > > > > linked to from the Google Gadgets API developer guide or anywhere > > > > else.
> > > > ==== > > > > What's a BETA-feature?
> > > > It's an early release of a feature in order get valuable feedback from > > > > real gadget developers (all of you) about the current design along > > > > with some ideas on how to make it better. We can't promise that you > > > > won't encounter any bugs since it's still a beta. However, when any > > > > changes arise, we'll notify everyone about the change by posting it to > > > > this thread. We're thrilled to hear your opinions on the design as > > > > well as any creative ideas on how to use it. If you have any > > > > questions or comments, please let us know.
> > > > In the meantime, here's the current list of limitations and known > > > > issues: > > > > -- Need more practical examples. Coming soon. > > > > -- Does not work in Safari. Works correctly in Firefox and IE. > > > > -- Only works in iGoogle. Does not work on third-party websites or > > > > other container pages such as Google Desktop. > > > > -- Only available to type="html" and type="html-inline" gadgets. > > > > -- Does not work consistently when multiple inlined (type="html- > > > > inline") "subscriber" gadgets exist on the same page in iGoogle. > > > > -- Moving (drag/dropping) a "subscriber" gadget to a different > > > > position in iGoogle creates an error. PubSub ceases to work > > > > afterwards. > > > > -- The "finance_symbol" channel described in the documentation is > > > > currently broken. > > > > -- Publisher gadgets cannot pass empty strings to subscriber gadgets. > > > > -- JavaScript error is sometimes thrown when loading gadgets on > > > > iGoogle. > > > > -- Browser 'Stop' buttons sometimes have strange flickering behavior.
> > > > ====
> > > > As always, please reply back with any feedback or comments you may > > > > have. We'd love to hear from you!
On Aug 26, 4:32 am, jodyflorian <jody.flor...@gmail.com> wrote:
> This will obviously be a powerful and popular feature... the question > is what to use it for? I would be curious as to what ideas people > have? Or what the plans are, if there are any, to create publisher > gadgets, and what information they would give? Early insight into that > would be great!
My first thought on reading about this was a project management page - possibly integrated into Google Apps. You would have separate gadgets for time sheets, projects, tasks, etc, and a way to "drill down", if you will, to the data you need to see. I am by no means knowledgeable in programming but that thought is why I'm here. Hope it helps.
> Just a thought, may be rubbish: Would it be possible to have a > reversed communication flow?
That was my first thought when I played with the map on the test page. When I recenter the map, could the controller show the lat/long of the new center?
> On Aug 26, 4:32 am, jodyflorian <jody.flor...@gmail.com> wrote:
> > This will obviously be a powerful and popular feature... the question > > is what to use it for? I would be curious as to what ideas people > > have? Or what the plans are, if there are any, to create publisher > > gadgets, and what information they would give? Early insight into that > > would be great!
> My first thought on reading about this was a project management page - > possibly integrated into Google Apps. You would have separate gadgets > for time sheets, projects, tasks, etc, and a way to "drill down", if > you will, to the data you need to see. I am by no means knowledgeable > in programming but that thought is why I'm here. Hope it helps.
> > Just a thought, may be rubbish: Would it be possible to have a > > reversed communication flow?
> That was my first thought when I played with the map on the test page. > When I recenter the map, could the controller show the lat/long of the > new center?
Hey - like most of my co-posters in this thread I believe this new
feature has a lot of potential.
I'd like to show you an example project where I took my two existing
gadgets Picasa Mini Browser and Picasa Mini Gallery and made them work
together with PubSub.
However - there's still some issues with the PubSub feature so it's
not working 100% (yet); but here's a link to a shared tab along with
some notes on the problems:
Interesting stuff is google gadgets. Here at OpenSpan we have managed
to integrate, in real time, enterprise desktop applications with
google gadgets. Not only can we integrate unrelated gadgets with
themselves or other applications running on a users desktop but we can
do so without you having to use the gadget to gadget API's.
An example might be, you have gadgets for mapping or tracking or
finance that automatically tacks a customer account / record from a
mainframe app, clarify, siebel or other windows/web apps.
It looks really cool. Contact me if you want to see it. francis.carden
"-at-" openspan.com
|
