[Google Wave APIs] Re: Less frequent updating

2009-11-01 Thread voidref

Yeah, I realized there was going to be no way of saving on the
bandwidth usage (a factor of magnitude more than processing power) by
either doing cron (polling with data I don't need) or by just ignoring
the keystrokes.

So I am going to have to just process on blip submitted, unless there
is a way I can change the messages I want to get at run time (is
there?).

That way I could just process the first few, and then fall back to
only blip submitted for larger edits.

It also sounds like cron jobs do not give you access to current state,
so that's a bust for that reason as well.

Thanks for the suggestion though!

Alan

On Oct 31, 8:46 am, David Nesting da...@fastolfe.net wrote:
 On Tue, Oct 27, 2009 at 10:21 PM, voidref void...@gmail.com wrote:
  For my syntax highlighting bot, I want the highlighting to be while
  typing is happening, however getting a notification on every character
  input will be a serious problem for bandwidth and processing.

 I don't believe you'll receive events for literally every character, but
 you'll receive them often.  I don't believe there's a way for your robot to
 see updated state about a blip without handling these events.  You can save
 on the processing requirements, though, by ignoring a document_changed event
 if you've just done one recently (in the last few seconds?).  Handle
 blip_submitted as well to ensure you didn't miss the last update to the
 blip.

 On Tue, Oct 27, 2009 at 11:37 PM, Austin Chau (Google employee) 

 api.aus...@google.com wrote:
  Cron job can recreate the blip context.  Check out the sample robot Stocky.
   It persists wave, wavelet and blip IDs, so that the cron call can later
  recreate the context.

 This doesn't seem to meet the requirements of the original poster: it sounds
 like he wants a way to access the *current* state of the blip, not the state
 that the blip was in the last time the robot saw it (when it got persisted
 to local storage).  Stocky does not need to see the current state of the
 blip in order to make its changes.

 David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread pamela (Google Employee)
I should make clear that there is a distinction between knowing when a
participant is inside the Wave client generally (as indicated by the green
dot) and actually viewing a particular Wave. The Wave client does not
provide any indicator when a participant is simply viewing a wave, for
privacy reasons.

It is possible for gadgets to figure out who is viewing a wave currently, as
gadgets can change the state of a Wave in view mode, but we expect that we
may enforce that gadgets can only change state when the entire blip is in
edit mode.

The general idea is that the Wave client should not reveal whether a user
has viewed a Wave, but the Wave client does reveal the fact that they are
currently logged in, and we may find a way to expose that in the API.

Hope that makes sense.

- pamela

On Sat, Oct 31, 2009 at 11:07 PM, Andrew Red andrewr...@gmail.com wrote:

 Could the first one be achieved by inserting a gadget, that has some
 javascript which changes data on the wave say every second or so, and if it
 stops changing the data, that person has stopped viewing the wave, that way,
 each gadget knows which users have the gadget open...

 Do I make any sense?

 Andrew


 On Sun, Nov 1, 2009 at 2:41 PM, pamela (Google Employee) 
 pamela...@gmail.com wrote:

 Regarding online presence - other developers have expressed their desire
 for that here:
 http://code.google.com/p/google-wave-resources/issues/detail?id=257

 Regarding diffs - I can see the desire for that, and we have discussed it
 on the team. Feel free to file a feature request.

 You may want to ask antimatter15 to share his diffing library or general
 technique, as well.

 - pamela

 On Sun, Nov 1, 2009 at 8:53 AM, lstak luc.stakenb...@gmail.com wrote:


 Hi,

 Based on some first gadgets I build, it would be useful if the Wave
 gadget API would support:

 - Online presence of participants in the wave. Currently you can only
 see who is a participant, but not if they are in the wave
 - the stateCallback provides the delta which caused the state change.
 This is useful when the Shared state is a large object and you only
 want to update a gadget based on the delta.

 e.g.

 function stateChanged(state, delta) {
  // state is the full state
  // delta is the changed part of the state
 }

 setStateCallback(stateChanged);


 Are there more developers who would find this useful?







 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Idea for Bot API

2009-11-01 Thread pamela (Google Employee)
We mentioned during a few recent presentations that we are looking at
integrating RegEx into extension installers. It would basically mean that a
developer could specify a RegEx that would trigger the addition of a robot
to a Wave -- so the user wouldn't need to explicitly add the robot, and the
robot would only be added when there was matching content. This is only
partly what you want, however.

We are also looking at letting you specify filters for each event in the
capabilities.xml, which sounds like it would satisfy your need.

- pamela


On Sat, Oct 31, 2009 at 9:23 PM, antimatter15 antimatte...@gmail.comwrote:


 I've been noticing how many bots are throwing Over Quota errors, and
 I think a way to potentially alleviate the issue is by making the
 API's events only occur when a certain string is found or a pattern is
 matched. It would certainly eliminate much of the wasted data spent in
 bandwidth and be more efficient with resources.
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread Andrew Red
I haven't played much with gadgets, but if they could do a XMLHttpRequest(),
they could tell a server when a user is on the wave...

It's just an idea for a back door, it should be easy to stop

Andrew

On Sun, Nov 1, 2009 at 9:00 PM, pamela (Google Employee) 
pamela...@gmail.com wrote:

 I should make clear that there is a distinction between knowing when a
 participant is inside the Wave client generally (as indicated by the green
 dot) and actually viewing a particular Wave. The Wave client does not
 provide any indicator when a participant is simply viewing a wave, for
 privacy reasons.

 It is possible for gadgets to figure out who is viewing a wave currently,
 as gadgets can change the state of a Wave in view mode, but we expect that
 we may enforce that gadgets can only change state when the entire blip is in
 edit mode.

 The general idea is that the Wave client should not reveal whether a user
 has viewed a Wave, but the Wave client does reveal the fact that they are
 currently logged in, and we may find a way to expose that in the API.

 Hope that makes sense.

 - pamela

 On Sat, Oct 31, 2009 at 11:07 PM, Andrew Red andrewr...@gmail.com wrote:

 Could the first one be achieved by inserting a gadget, that has some
 javascript which changes data on the wave say every second or so, and if it
 stops changing the data, that person has stopped viewing the wave, that way,
 each gadget knows which users have the gadget open...

 Do I make any sense?

 Andrew


 On Sun, Nov 1, 2009 at 2:41 PM, pamela (Google Employee) 
 pamela...@gmail.com wrote:

 Regarding online presence - other developers have expressed their desire
 for that here:
 http://code.google.com/p/google-wave-resources/issues/detail?id=257

 Regarding diffs - I can see the desire for that, and we have discussed it
 on the team. Feel free to file a feature request.

 You may want to ask antimatter15 to share his diffing library or general
 technique, as well.

 - pamela

 On Sun, Nov 1, 2009 at 8:53 AM, lstak luc.stakenb...@gmail.com wrote:


 Hi,

 Based on some first gadgets I build, it would be useful if the Wave
 gadget API would support:

 - Online presence of participants in the wave. Currently you can only
 see who is a participant, but not if they are in the wave
 - the stateCallback provides the delta which caused the state change.
 This is useful when the Shared state is a large object and you only
 want to update a gadget based on the delta.

 e.g.

 function stateChanged(state, delta) {
  // state is the full state
  // delta is the changed part of the state
 }

 setStateCallback(stateChanged);


 Are there more developers who would find this useful?










 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Less frequent updating

2009-11-01 Thread Trejkaz

On Sun, Nov 1, 2009 at 10:25 PM, Linc ala...@online.de wrote:

 Why not implement a counter or sth. so that you only react on everey
 3rd DOCUMENT_CHANGED.

Or some kind of capability saying that it only wants updates once
every 3 seconds, and however many changes occur within those 3 seconds
does not matter.  I think that would be clearer, and you'd get a
better idea of how many requests the app will be hit with (once per 3
seconds per subscribed wave?)

TX

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread cmdskp

Another solution is to alert the user before entering a wave that has
gadgets that 'requireViewerId' to the privacy issue and allow them to
view the wave with those gadgets disabled until they choose to
activate them or edit the wave.

Or disabling all gadgets until activated or wave edit.  This would be
more private(e.g. prevents IP harvesting on viewing) and allow the
feature of online status to gadgets in a wave when the user chooses.

However, the evil of constantly being asked (in a mini-message bar) to
'Activate Content' would have to be addressed by trusted/untrusted
preferences (much like NoScript does on a permanent basis for that
gadget or per wave).

On Nov 1, 10:00 am, pamela (Google Employee) pamela...@gmail.com
wrote:
 I should make clear that there is a distinction between knowing when a
 participant is inside the Wave client generally (as indicated by the green
 dot) and actually viewing a particular Wave. The Wave client does not
 provide any indicator when a participant is simply viewing a wave, for
 privacy reasons.

 It is possible for gadgets to figure out who is viewing a wave currently, as
 gadgets can change the state of a Wave in view mode, but we expect that we
 may enforce that gadgets can only change state when the entire blip is in
 edit mode.

 The general idea is that the Wave client should not reveal whether a user
 has viewed a Wave, but the Wave client does reveal the fact that they are
 currently logged in, and we may find a way to expose that in the API.

 Hope that makes sense.

 - pamela

 On Sat, Oct 31, 2009 at 11:07 PM, Andrew Red andrewr...@gmail.com wrote:
  Could the first one be achieved by inserting a gadget, that has some
  javascript which changes data on the wave say every second or so, and if it
  stops changing the data, that person has stopped viewing the wave, that way,
  each gadget knows which users have the gadget open...

  Do I make any sense?

  Andrew

  On Sun, Nov 1, 2009 at 2:41 PM, pamela (Google Employee) 
  pamela...@gmail.com wrote:

  Regarding online presence - other developers have expressed their desire
  for that here:
 http://code.google.com/p/google-wave-resources/issues/detail?id=257

  Regarding diffs - I can see the desire for that, and we have discussed it
  on the team. Feel free to file a feature request.

  You may want to ask antimatter15 to share his diffing library or general
  technique, as well.

  - pamela

  On Sun, Nov 1, 2009 at 8:53 AM, lstak luc.stakenb...@gmail.com wrote:

  Hi,

  Based on some first gadgets I build, it would be useful if the Wave
  gadget API would support:

  - Online presence of participants in the wave. Currently you can only
  see who is a participant, but not if they are in the wave
  - the stateCallback provides the delta which caused the state change.
  This is useful when the Shared state is a large object and you only
  want to update a gadget based on the delta.

  e.g.

  function stateChanged(state, delta) {
   // state is the full state
   // delta is the changed part of the state
  }

  setStateCallback(stateChanged);

  Are there more developers who would find this useful?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Text appended twice in blip

2009-11-01 Thread Karan Bhatnagar
Thank you Austin.
The workaround works for us as intended.

On Sun, Nov 1, 2009 at 4:16 AM, Austin Chau (Google employee) 
api.aus...@google.com wrote:

 Hi Karan,

 Sorry that this bug hit you as well, we have already filed a request for
 it.  You can track it with this bug report -


 http://code.google.com/p/google-wave-resources/issues/detail?id=354sort=-idcolspec=Stars%20ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20Internal

 We know exactly what is causing this and when fix is pushed to production
 we will let you guys know.

 In the mean while the workaround to not have doubling of the text you can
 do this -

 Blip newBlip = wavelet.appendBlip();
 newBlip.getDocument().delete();
 newBlip.getDocument().append(hello);

 This should only print the text once.

 Austin

 On Sat, Oct 31, 2009 at 10:53 AM, Karan Bhatnagar 
 karan.bhatna...@gmail.com wrote:

 FYI, about one week back it was working fine. The message was being
 displayed in the new blip just once as intended.
 Do I have to make some changes in the way I am appending the text  
 bundle.getWavelet().appendBlip().getDocument().append(SOME_STRING),
 do compensate of any API changes?


 On Sat, Oct 31, 2009 at 11:17 PM, Karan Bhatnagar 
 karan.bhatna...@gmail.com wrote:

 If this is because the logs show it both in *content *as well as *property
 *field?


 On Sat, Oct 31, 2009 at 11:13 PM, Karan Bhatnagar 
 karan.bhatna...@gmail.com wrote:

 Hi,
  I am facing a strange problem. My robot is trying to add a blip to the
 wave using:

  @Override
  public void processEvents(RobotMessageBundle bundle) {
   .
 bundle.getWavelet().appendBlip().getDocument().append(SOME_STRING);
  // where bundle is the object of RobotMessageBundle class
   .
 }

 in AppEngine logs, I can see:


 com.google.wave.api.AbstractRobotServlet serializeOperations: Outgoing 
 operations: 
 {javaClass:com.google.wave.api.impl.OperationMessageBundle,operations:{javaClass:java.util.ArrayList,list:[{index:-1,waveletId:googlewave.com!conv+root,blipId:null,javaClass:com.google.wave.api.impl.OperationImpl,property:{lastModifiedTime:-1,contributors:{javaClass:java.util.ArrayList,list:[]},waveletId:googlewave.com!conv+root,waveId:googlewave.com!w+Gss2nWBGN,parentBlipId:null,version:-1,creator:null,content:\nThis
  is the content of SOME_STRING 
 ,blipId:TBD0.9461425416166795,javaClass:com.google.wave.api.impl.BlipData,annotations:{javaClass:java.util.ArrayList,list:[]},elements:{map:{},javaClass:java.util.HashMap},childBlipIds:{javaClass:java.util.ArrayList,list:[]}},waveId:googlewave.com!w+Gss2nWBGN,type:WAVELET_APPEND_BLIP},{index:0,waveletId:googlewave.com!conv+root,blipId:TBD0.9461425416166795,javaClass:com.google.wave.api.impl.OperationImpl,property:This
  is the content of 
 SOME_STRING,waveId:googlewave.com!w+Gss2nWBGN,type:DOCUMENT_APPEND}]},version:4}



 but the message 'This is the content of SOME_STRING' appears twice in the 
 new blip as if it was appended twice.

 Any clue what is going on behind the scenes?


 Thanks.







 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread David Nesting
On Sun, Nov 1, 2009 at 3:00 AM, pamela (Google Employee) 
pamela...@gmail.com wrote:

 in view mode, but we expect that we may enforce that gadgets can only
 change state when the entire blip is in edit mode.


If the motivation behind this is to ensure privacy, keep in mind that the
gadget can always record this information to their own local storage, or you
can use traditional web bugs within the gadget.  The user just needs to edit
one blip with one of these gadgets to get all of their view history linked
to their identity.

David

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Create Search Engine To Search Waves

2009-11-01 Thread Eric Dorman

Hey guys,

Has anyone tried to create a search engine that lets you search for
specific waves that are tagged with a certain word?

Thanks  God Bless,
Eric
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Less frequent updating

2009-11-01 Thread voidref

@Linc: The problem is not the CPU or how much I send back (already
done that optimization), it's that on every DOC_CHANGED it sends a
very large amount of data over, wether I use it or not.

This won't be a problem when I can put my bot on my own site, it's
just a problem for the google apps limited free bandwidth.

What would be ideal is if I could get a delta instead of all the text
and all the annotations sent over.

What would also be ideal is if there was a client side api in
javascript I could use that mirrored the bot api somehow.

Or Client Side Bots!

@antimatter, yes, also an issue

@Trejkaz, that would also help



On Nov 1, 8:25 am, antimatter15 antimatte...@gmail.com wrote:
 Or maybe the issue is that you are getting DOCUMENT_CHANGED events
 even when the blip doesn't have code in it.

 On Nov 1, 7:23 am, Trejkaz trej...@gmail.com wrote:



  On Sun, Nov 1, 2009 at 10:25 PM, Linc ala...@online.de wrote:

   Why not implement a counter or sth. so that you only react on everey
   3rd DOCUMENT_CHANGED.

  Or some kind of capability saying that it only wants updates once
  every 3 seconds, and however many changes occur within those 3 seconds
  does not matter.  I think that would be clearer, and you'd get a
  better idea of how many requests the app will be hit with (once per 3
  seconds per subscribed wave?)

  TX
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread antimatter15

This is the code I use for my state diffing
http://antimatter15.com/wp/2009/08/wave2-a-higher-level-wave-gadget-state-api/,
rather than telling if something has been changed or added for
everything that is changed or added (I made this for very data-
intensive gadget and since the diffing needs a copy of the old data as
well, I tried to keep the size of the backups to a minimum). To use
it, just call wave2.statechange() from within your on state change
event handlers and use wave2.listen(substring for what to listen
for, callback function) and the callback will be called every time
something that begins with the certain substring changes.

On Nov 1, 9:16 am, David Nesting da...@fastolfe.net wrote:
 On Sun, Nov 1, 2009 at 3:00 AM, pamela (Google Employee) 

 pamela...@gmail.com wrote:
  in view mode, but we expect that we may enforce that gadgets can only
  change state when the entire blip is in edit mode.

 If the motivation behind this is to ensure privacy, keep in mind that the
 gadget can always record this information to their own local storage, or you
 can use traditional web bugs within the gadget.  The user just needs to edit
 one blip with one of these gadgets to get all of their view history linked
 to their identity.

 David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread Andrew Red
I was thinking about this last night, and I thought just to restrict
the information to the gadget to be anomous when the gadget loads, and only
when the user interacts with the gadget (press a link or button) to make all
the data available. The only problem with this is that the gadget could use
javascript to simulate pressing a button :(

Andrew

On Mon, Nov 2, 2009 at 7:21 AM, antimatter15 antimatte...@gmail.com wrote:


 This is the code I use for my state diffing

 http://antimatter15.com/wp/2009/08/wave2-a-higher-level-wave-gadget-state-api/
 ,
 rather than telling if something has been changed or added for
 everything that is changed or added (I made this for very data-
 intensive gadget and since the diffing needs a copy of the old data as
 well, I tried to keep the size of the backups to a minimum). To use
 it, just call wave2.statechange() from within your on state change
 event handlers and use wave2.listen(substring for what to listen
 for, callback function) and the callback will be called every time
 something that begins with the certain substring changes.

 On Nov 1, 9:16 am, David Nesting da...@fastolfe.net wrote:
  On Sun, Nov 1, 2009 at 3:00 AM, pamela (Google Employee) 
 
  pamela...@gmail.com wrote:
   in view mode, but we expect that we may enforce that gadgets can only
   change state when the entire blip is in edit mode.
 
  If the motivation behind this is to ensure privacy, keep in mind that the
  gadget can always record this information to their own local storage, or
 you
  can use traditional web bugs within the gadget.  The user just needs to
 edit
  one blip with one of these gadgets to get all of their view history
 linked
  to their identity.
 
  David
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: capabilites.xml is blank

2009-11-01 Thread Calum

Still have this problem...

On Oct 31, 8:19 pm, Calum calums1...@hotmail.co.uk wrote:
 http://thecalumscottbot.appspot.com/_wave/capabilities.xml

 The logs don't show anything unusual.

 On Oct 31, 4:18 pm, David Nesting da...@fastolfe.net wrote:

  Can you give us a link to it?  If you're running this in appengine, do the
  appengine logs give you any hints as to what might be happening?

  David

  On Fri, Oct 30, 2009 at 6:42 AM, Calum calums1...@hotmail.co.uk wrote:

   Does no one have any reason why this happens? It's still a blank XML
   file.

   On Oct 19, 12:13 am, Calum calums1...@hotmail.co.uk wrote:
For some reason, no matter what I do. Mycapabilities.xml file always
seems to be blank. I am using the Python SDK and I am told it's
supposed to automatically generate this file however it's blank.

Is this just a case of waiting for the file to be generated, or is
this an error?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Create Search Engine To Search Waves

2009-11-01 Thread Eric Dorman

What do you mean by search panel?

Were can I find more information about the search panel?

Thanks  God Bless,
Eric

On Nov 1, 3:35 pm, Sam Osborne sam.tosbo...@googlemail.com wrote:
 Try using the implemented search pane thingy and using:
 tag:yourtag
 (insert the tag you want to search for in the yourtag bit, for example, if
 I wanted to search for tag welcomewaves, I'd go
 tag:welcomewaves )

 2009/11/1 Eric Dorman dorman...@gmail.com





  Hey guys,

  Has anyone tried to create a search engine that lets you search for
  specific waves that are tagged with a certain word?

  Thanks  God Bless,
  Eric
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: Create Search Engine To Search Waves

2009-11-01 Thread Sam Osborne
As in, on the main Wave client, the middle pane.

2009/11/1 Eric Dorman dorman...@gmail.com


 What do you mean by search panel?

 Were can I find more information about the search panel?

 Thanks  God Bless,
 Eric

 On Nov 1, 3:35 pm, Sam Osborne sam.tosbo...@googlemail.com wrote:
  Try using the implemented search pane thingy and using:
  tag:yourtag
  (insert the tag you want to search for in the yourtag bit, for example,
 if
  I wanted to search for tag welcomewaves, I'd go
  tag:welcomewaves )
 
  2009/11/1 Eric Dorman dorman...@gmail.com
 
 
 
 
 
   Hey guys,
 
   Has anyone tried to create a search engine that lets you search for
   specific waves that are tagged with a certain word?
 
   Thanks  God Bless,
   Eric
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---



[Google Wave APIs] Re: would this be good for http://instructables.com/ and my site.

2009-11-01 Thread Ankur Oberoi
im not sure exactly what you are trying to suggest are u saying someone
should be working on embedding wave into the instructables.com site? if so,
i beleive your comment should be directed to those that create their webapp
so that it can be integrated at a lower level.

On Sat, Oct 31, 2009 at 8:50 PM, JamesM mcglashan.ja...@gmail.com wrote:


 would this be good for http://instructables.com/ because i am on
 http://instructables alot and when i saw google wave i saw google wave
 taking over http://instructables.com/ in my head so i thought that
 would not really be hard.

 so idear's that this could work for:

 orrangeboard,
 comments,
 instructables (the step by step diy guides) / Videos / slideshows /
 groups / and the rest,
 fourms,
 profiles,
 and much more.

 ok now instructables is a very good site and i am worried if they
 would be able to convurt the instructables into waves easly.

 and i think every instructable that is a video should include
 [ VIDEO ] [ SLIDE SHOW ] [ INSTRUCTABLE ] ECT

 so this can all be done easy enough, so why isnt it open soures yet
 why cant we just download a zip of the wave file system connected to
 google wave to connect to get live updates to save changes to keep
 wave working the best it can.

 with the zip folder only including
 wave needed files
 images to change to suit site,
 settings,
 and a simple php file to change those settings with a username and
 password to keep them safe.

 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Wave API group.
To post to this group, send email to google-wave-api@googlegroups.com
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en
-~--~~~~--~~--~--~---