On 27 October 2010 19:41, Vega <[email protected]> wrote: > Ok, but what handles the translation of "undo" event into actual > document.modify operation that should reverse the previous > document.modify? > I guess there's a previous delta which says "add element", but how you > map "add element" operation into "delete element" in order to undo? > > FYI the wave client uses code in org.waveprotocol.wave.model.undo<http://code.google.com/p/wave-protocol/source/browse?repo=libraries#hg/src/org/waveprotocol/wave/model/undo>to generate undo modifications.
I don't think it's something you need to worry about at all for robot operations, unless I misunderstand what you're trying to do. > On Oct 27, 6:13 am, Alex North <[email protected]> wrote: > > On 27 October 2010 06:41, Vega <[email protected]> wrote: > > > > > Another question - what happens if use adds an element to the blip > > > (like image) and then hits ctr+z (undo) ? How the undo event is > > > handled? > > > > An undo "event" is just like any other modification. The client submits > an > > operation to reverse the effect of whatever is being undone. It's not > > represented explicitly in the operations. For example, to undo a text > > insertion the client generates the corresponding text deletion operation. > > They all just look like text modifications to the robot gateway and > there's > > generally no way to tell whether the op was generated from a ctrl-z or > the > > user manually reversing their actions. > > > > Alex > > > > > > > > > On Oct 26, 7:37 pm, Vega <[email protected]> wrote: > > > > Thanks. > > > > Is it intended to group both Blip and Document operations under > > > > BlipOperationServices class? > > > > > > On Oct 25, 8:15 pm, Lennard de Rijk <[email protected]> wrote: > > > > > > > Hi, > > > > > > > On Mon, Oct 25, 2010 at 10:52 AM, Vega <[email protected]> wrote: > > > > > > Are there some example implementations for Robot API Operation > > > > > > starter project? I would like to contribute, but a bit of > explanation > > > > > > of what exactly should be done and a example would make a job a > lot > > > > > > easier. > > > > > > > You should be able to take a look at the operations that have been > > > > > implemented under [0]. Pick any operation from the list of > operations > > > that > > > > > are to be done, most of them speak for themselves (or find some > more > > > info at > > > > > [1]). If there is still a question about what the op should do or > how > > > it > > > > > should work just drop us a line on the list :). > > > > > > > Greetings, > > > > > Lennard > > > > > > > [0] > > >http://code.google.com/p/wave-protocol/source/browse/#hg/src/org/wave. > .. > > > > > [1] > http://code.google.com/apis/wave/extensions/robots/protocol.html > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Wave Protocol" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<wave-protocol%[email protected]> > <wave-protocol%2bunsubscr...@goog legroups.com> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/wave-protocol?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
