Re: Generic undo stack for GTK+

I do agree that there should be no UI related thing on Undo/Redo Implementation, if any.
Easy Undo/Redo framework are usually based on Inheritance... but in GLib, inheritance is not an easy way for Gtk users (in plain C GObject anyway).
Using vala or another object oriented binding to Gtk, it could be helpfull and easy, but in plain GObject C, i think that nobody would end-up using this.
And for completeness, it should provide two models, one with a group of stacks (for multi-undo stacks applications) and one with a group of trees (for more complex undo/redo schemas)...
Anyway, i don't see the value of adding it to GLib, as undo frameworks are only an abstraction, and users end-up doing the painfull job of implementing undo commands for every type of objects or actions they are putting in the stack or the tree.

2010/6/17 Michael Natterer <mitch gimp org>
On Wed, 2010-06-16 at 22:01 +0200, Holger Berndt wrote:
> Some time ago, there was some discussion about a generic undo stack in
> GTK+ [1]. The talk back then didn't result in more concrete API
> discussion. As undo/redo is part of the GTK+ Roadmap [2], I now shot
> ahead and created an undo proposal page [3] for that. Comments are very
> welcome.

If at all, this should definitely be in GLib. GIMP for example
has strict core/ui separation, with the core not even knowing
what GTK+ is, and of course undo is part of the core object


gtk-devel-list mailing list
gtk-devel-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]