such as...?
On 18 May 2011 23:49, Yuri Z <[email protected]> wrote: > Yep, and some more things too. > > 2011/5/19 Zachary “Gamer_Z.” Yaro <[email protected]> > >> IMHO better wave persistence and storage are needed before we should >> consider mass importing from Gwave. >> >> --Zachary “Gamer_Z.” Yaro >> >> >> On Wed, May 18, 2011 at 17:20, Soren Lassen <[email protected]> wrote: >> >> > There's some documentation about the data export features in the Data API >> > here: >> > >> > >> > >> http://www.waveprotocol.org/wave-apis/google-wave-data-api/raw-deltas-export >> > >> > >> http://groups.google.com/group/wave-protocol/browse_thread/thread/da20836f3552fe0b?pli=1 >> > >> > On Wed, May 18, 2011 at 2:13 PM, Ali Lown <[email protected]> wrote: >> > > Looking at the python interface: I can see the robot.fetch_wavelet >> > > method, but that only returns a snapshot at that point in time. >> > > >> > > How would I request the full history of the wave (wavelet?). >> > > >> > > Ali >> > > >> > > On 18 May 2011 20:51, Yuri Z <[email protected]> wrote: >> > >> >> > >> Google Wave Data API was modified to allow to request the whole >> history >> > of >> > >> the wave - which in effect allows to "import" it. But AFAIK no one is >> > >> working on a tool that would actually import the history into WIAB >> > deltas >> > >> store. >> > >> >> > >> 2011/5/18 Ali Lown <[email protected]> >> > >> >> > >> > On the old waveprotocol site task list, this is still listed as >> > waiting for >> > >> > google to implement export. >> > >> > >> > >> > Export has now been available for a while for waves, has any >> progress >> > been >> > >> > made on importing them? >> > >> > >> > >> > The HTML option, actually provides the data in a JSON form, is there >> > are >> > >> > parser for this already in the code base? >> > >> > >> > >> > Ali >> > >> > >> > > >> > >> >
