Saturday 15 January 2011

google mirror api - Can you allow a user to REPLY to a card and not have a card appear with their response text in the timeline? -


I have a bundle (maybe even with a timeline card) Take action with the answer and the user With the text "Peanut Butter and Jelly Sandwich", a new timeline card appears on a black background on the glass when it says "Peanut Butter and Jelly Sandwich". When watching the playground, a card appears similar to the user's avatar on the left (like Abe Lincoln template example), and the text on the right.

We call this new card a reminder card, because it reminds the user that the text they wrote and permission to send.

I did not include that reminder card in the timeline.

Is there a custom glass behavior to answer this lesson that the user has given a text? Does it count against our API Milan, or is it a freebie and some have accused Google about the account?

There is no way to answer and implement any kind of document to prevent the demonstration of this reminder. Card?

Here is the document that seems to encourage nonverting repetitive actions, which can be inspired by this reminder card behavior.

Answer, REPLY_ALL - Voice Answers Do not use voice answers to capture a limited set of options that are targeted to catch voice-free form input, such as possible in games Trick.

(New MenuEmploy (.) SetAction ("REPLY"));

"Answer" timeline items are automatically inserted by the glass client and its Have ownership set to your Glassware: This means that you have to read / write full on this timeline item.

It is up to your glassware to apply the process of timeline items and some styles. Timeline items are also useful for the user because it answers the user to "delete" if necessary. If the answer does not make sense in your glassware, then remove the timeline items while processing to remove the user from the timeline.

Regarding API quota, when you send the actual request, retrieving the timeline item for the API, the glass producing "REPLY" does not use your quota.

No comments:

Post a Comment