[Google Wave APIs] Re: New FAQ: What annotations are supported by the Google Wave Client?
Thanks Pamela! =)
On Dec 5, 7:53 am, "pamela (Google Employee)"
wrote:
> Hi cmdskp-
>
> Apologies; I also am not able to set it manually (even after realizing
> that it's actually "conv/contentcreationtime"). I based its existence
> on what Tweety does, and examining the annotations in the Tweety
> blips. I'm looking into why it doesn't work to set it manually.
>
> For the meantime, I've removed it from the FAQ. I've also added a note
> that yes, annotation names are case sensitive.
>
> - pamela
>
> On Wed, Dec 2, 2009 at 3:48 PM, cmdskp wrote:
> > Thanks! I hadn't known about "contentcreationtime" - exactly what I
> > would like to ensure the creation date/time remains to before my robot
> > edited a blip on being added to a wave much later.
>
> > Is the value in milliseconds like the example on the FAQ? (It's got 3
> > extra zeros)
>
> > I tried the following (with values of "0", "1249309218000",
> > "1249309218", etc.) and I couldn't get the client to show a date/time
> > other than the last edit date on the blip:
>
> > if (tempEventType==EventType.BLIP_SUBMITTED) {
> > Blip tempBlip = tempEvent.getBlip();
> > List tempCreationTimes = tempBlip.getDocument
> > ().getAnnotations("contentcreationtime");
> > if (tempCreationTimes.isEmpty()) {
> > tempBlip.getDocument().setAnnotation("contentcreationtime",
> > "1249309218");
> > } else {
> > for (Annotation tempCreationTime : tempCreationTimes) {
> > LOG.warning("contentcreationtime
> > "+tempCreationTime.getValue());
> > }
> > }
> > }
>
> > Perhaps I'm just misunderstanding things. =) Could you add a note on
> > if the annotation names are case-sensitive?
>
> > On Dec 2, 3:33 am, "pamela (Google Employee)"
> > wrote:
> >> Just posted a new FAQ about supported annotations:
>
> >>http://wave-api-faq.appspot.com/#annotations
>
> >> Comments/suggestions welcome.
>
> >> - pamela
>
> > --
>
> > 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-...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-wave-api+unsubscr...@googlegroups.com.
> > For more options, visit this group
> > athttp://groups.google.com/group/google-wave-api?hl=en.
>
>
--
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-...@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.
Re: [Google Wave APIs] Re: New FAQ: What annotations are supported by the Google Wave Client?
Hi cmdskp-
Apologies; I also am not able to set it manually (even after realizing
that it's actually "conv/contentcreationtime"). I based its existence
on what Tweety does, and examining the annotations in the Tweety
blips. I'm looking into why it doesn't work to set it manually.
For the meantime, I've removed it from the FAQ. I've also added a note
that yes, annotation names are case sensitive.
- pamela
On Wed, Dec 2, 2009 at 3:48 PM, cmdskp wrote:
> Thanks! I hadn't known about "contentcreationtime" - exactly what I
> would like to ensure the creation date/time remains to before my robot
> edited a blip on being added to a wave much later.
>
> Is the value in milliseconds like the example on the FAQ? (It's got 3
> extra zeros)
>
> I tried the following (with values of "0", "1249309218000",
> "1249309218", etc.) and I couldn't get the client to show a date/time
> other than the last edit date on the blip:
>
> if (tempEventType==EventType.BLIP_SUBMITTED) {
> Blip tempBlip = tempEvent.getBlip();
> List tempCreationTimes = tempBlip.getDocument
> ().getAnnotations("contentcreationtime");
> if (tempCreationTimes.isEmpty()) {
> tempBlip.getDocument().setAnnotation("contentcreationtime",
> "1249309218");
> } else {
> for (Annotation tempCreationTime : tempCreationTimes) {
> LOG.warning("contentcreationtime
> "+tempCreationTime.getValue());
> }
> }
> }
>
> Perhaps I'm just misunderstanding things. =) Could you add a note on
> if the annotation names are case-sensitive?
>
>
> On Dec 2, 3:33 am, "pamela (Google Employee)"
> wrote:
>> Just posted a new FAQ about supported annotations:
>>
>> http://wave-api-faq.appspot.com/#annotations
>>
>> Comments/suggestions welcome.
>>
>> - pamela
>
> --
>
> 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-...@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.
>
>
>
--
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-...@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: New FAQ: What annotations are supported by the Google Wave Client?
The users cursor position sadly are not available currently to robots
(on tests with DOCUMENT_CHANGED) - only a selection start/end show up
as an annotation and the users cursor position can be anywhere.
I ran this quick test again there, on both the sandbox and preview -
and no annotations show for cursor position. If someone has managed
to get the actual caret position of a user (and on what event) please
let us know.
if (tempEventType==EventType.DOCUMENT_CHANGED) {
Blip tempBlip = tempEvent.getBlip();
StringBuilder tempMessage = new StringBuilder();
TextView tempTextView = tempBlip.getDocument();
List tempAnnotations = tempTextView.getAnnotations();
tempMessage.append("\nTotal annotations: "+tempAnnotations.size()
+"\n");
for (Annotation tempAnnotation : tempAnnotations) {
tempMessage.append("\tAnnotation: "+tempAnnotation.getName()+"
value="+tempAnnotation.getValue()+" range="+tempAnnotation.getRange
().getStart()+" "+tempAnnotation.getRange().getEnd()+"\n");
}
LOG.warning(tempMessage.toString());
}
On Dec 2, 11:42 pm, qMax wrote:
> There also exist annotations denoting users cursors and selections,
> these are mentioned in "conversation manifest" document.
>
> I wonder if a robot _set_ such annotations - will it change cursor
> position/selection?
>
> On 2 дек, 09:33, "pamela (Google Employee)"
> wrote:
>
> > Just posted a new FAQ about supported annotations:
>
> >http://wave-api-faq.appspot.com/#annotations
>
> > Comments/suggestions welcome.
>
> > - pamela
>
>
--
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-...@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: New FAQ: What annotations are supported by the Google Wave Client?
There also exist annotations denoting users cursors and selections, these are mentioned in "conversation manifest" document. I wonder if a robot _set_ such annotations - will it change cursor position/selection? On 2 дек, 09:33, "pamela (Google Employee)" wrote: > Just posted a new FAQ about supported annotations: > > http://wave-api-faq.appspot.com/#annotations > > Comments/suggestions welcome. > > - pamela -- 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-...@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: New FAQ: What annotations are supported by the Google Wave Client?
Thanks! I hadn't known about "contentcreationtime" - exactly what I
would like to ensure the creation date/time remains to before my robot
edited a blip on being added to a wave much later.
Is the value in milliseconds like the example on the FAQ? (It's got 3
extra zeros)
I tried the following (with values of "0", "1249309218000",
"1249309218", etc.) and I couldn't get the client to show a date/time
other than the last edit date on the blip:
if (tempEventType==EventType.BLIP_SUBMITTED) {
Blip tempBlip = tempEvent.getBlip();
List tempCreationTimes = tempBlip.getDocument
().getAnnotations("contentcreationtime");
if (tempCreationTimes.isEmpty()) {
tempBlip.getDocument().setAnnotation("contentcreationtime",
"1249309218");
} else {
for (Annotation tempCreationTime : tempCreationTimes) {
LOG.warning("contentcreationtime
"+tempCreationTime.getValue());
}
}
}
Perhaps I'm just misunderstanding things. =) Could you add a note on
if the annotation names are case-sensitive?
On Dec 2, 3:33 am, "pamela (Google Employee)"
wrote:
> Just posted a new FAQ about supported annotations:
>
> http://wave-api-faq.appspot.com/#annotations
>
> Comments/suggestions welcome.
>
> - pamela
--
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-...@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.
