Alex,
Thanks. If I understand you correctly, then one example ADT is
ObservableBasicMap
Looks lik
org.waveprotocol.wave.model.supplement.DocumentBasedGadgetState
Going further up the chain, in
WaveletBasedSupplement and
org.waveprotocol.wave.model.supplement.SupplementedWaveImpl
have a notion of gadget state which is implemented using the
DocumentBasedGadgetState
So maybe if: I create a SupplementedWaveImpl (maybe it is by default)
for each of the "editing conversations" and then use their gadget
state for
metadata storage, that might be one approach.
Charles
On Dec 8, 4:26 pm, Alex North <[email protected]> wrote:
> You should be able to store this in the Wave.
>
> The standard way is to use a data document. A data document is just any
> document that's not a blip. Examples of data already represented in data
> documents includes the conversation structure, per-user data, tags, spell
> suggestions (not all of these are implemented in WIAB yet).
>
> If you intend the metadata to be concurrently editable then you need to
> think carefully about how to represent it to play well with Wave's
> operational transform algorithm. There are a few people on this list very
> experienced in that design who I'm sure would be happy to review a proposal.
> You can find examples of basic data structures embedded in wave in the
> org.waveprotocol.wave.model.adt package, and search for references to those
> interfaces to find application models using them.
>
> Alex
>
> On 9 December 2010 04:37, cearl <[email protected]> wrote:
>
>
>
>
>
>
>
> > Hi,
> > I am trying to understand the best place in which to store additional
> > information related to a wave conversation.
> > The application is one in which users are concurrently annotating and
> > discussing edit operations on a video. I would like to simply have the
> > ability to have the conversations (waves) cross reference each other.
> > Seems that I could store this as metadata for each wave; or perhaps
> > the simpler thing to do is to just store this information in the
> > application itself (outside the wave model). Perhaps I am over-
> > thinking this and this information could be placed into a document in
> > the first blip (say) and simply not rendered.
>
> > --
> > 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%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].
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.
