[ge-talk] file versioning

[Ari Haviv]

Well the undo history would look like a tree which would list the
changes and then you'd drag and drop changes to the branch you want in
the order you want.

The program would label the changes such as "line" and date/time.

And of course this would work the same way for audio, video, word
processor, spreadsheet, etc. Any app where you design in a structured
way.

On 1/22/07, Paul van Nugteren <pmvannugteren at eml.cc> wrote:
> Try Wonderbrush : ) but your imagination is correct IMO, but the other
> side is that undo/redo is start-finish, no branching, how would the sw
> know how to redo, in what direction? It's the same thing with
> subdirectories, which one you choose? There is no auto : )
>
> On Mon, 22 Jan 2007 15:12:08 -0500, "Ari Haviv" <arielbhaviv at gmail.com>
> said:
> > well I have seen a graphical diff program but it would probably be too
> > complex for video and I can't even imagine audio
> >
> > This was my dream. In a photo app you have an undo history. Now every
> > change would be saved as a new dot version. So now you have unlimited
> > undo even after you close the file or send to someone else.
> > You draw a triangle. then you think "maybe it will look better to draw
> > a circle on the right or a square on the left. So you fork the file
> > and have one branch with the circle and the other with the square. You
> > decide the circle branch looks better so you continue with that and
> > draw other other shapes. Later on you send the file with all the
> > versions to your partner and she says 'you know, I really think it
> > would be better with the square." So she follows the square branch,
> > keeps the other shapes and changes and throws out the work on the
> > circle to create a new image. Ah now that works.
> >
> > On 1/21/07, Paul van Nugteren <pmvannugteren at eml.cc> wrote:
> > > Sure, just be informed that binary files like images and such can't or
> > > can't be easily diff'ed.
> > >
> > > On Sat, 20 Jan 2007 21:39:20 -0500, "Ari Haviv" <arielbhaviv at gmail.com>
> > > said:
> > > > Most software developers are familiar with versioning systems such as
> > > > CVS, Subversion or Mercurial. You maintain previous versions, you
> > > > fork, you merge. What I'm thinking about and want to bring to the
> > > > table is having this concept for any large project including documents
> > > > and multimedia files. And it should be easy to use.
> > > > _______________________________________________
> > > > glasselevator-talk mailing list
> > > > glasselevator-talk at bug-br.org.br
> > > > http://www.bug-br.org.br/mailman/listinfo/glasselevator-talk
> > >
> > >
> > >
> > > http://www.fastmail.fm
> > >
> > > _______________________________________________
> > > glasselevator-talk mailing list
> > > glasselevator-talk at bug-br.org.br
> > > http://www.bug-br.org.br/mailman/listinfo/glasselevator-talk
> > >
> > _______________________________________________
> > glasselevator-talk mailing list
> > glasselevator-talk at bug-br.org.br
> > http://www.bug-br.org.br/mailman/listinfo/glasselevator-talk
>
>
>
> http://www.fastmail.fm
>
> _______________________________________________
> glasselevator-talk mailing list
> glasselevator-talk at bug-br.org.br
> http://www.bug-br.org.br/mailman/listinfo/glasselevator-talk
>