protux-devel
[Top][All Lists]
Advanced

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

Re: [Protux-devel] MHE is born !


From: Remon Sijrier
Subject: Re: [Protux-devel] MHE is born !
Date: Thu, 13 Jan 2005 16:26:37 +0100
User-agent: KMail/1.7.1

Hi all,

> Former MUE (Mustux Undo Engine), now more coherently called MHE
> (Mustux History Engine), a undo/redo engine that provides undo/redo
> (doh!), is finally born !
>
> actions will be implemented on demand. that means the more protux
> develops, more things can be done , undone and redone in protux.. The
> engine is there, ready to accept new actions.
>
> well, not exactly ready, but me and Remon are working on that

Thats right. :-)

The good news is that I, with (much) help from Luciano, worked the last days 
on MHE, and I think the core functionality of MHE is there.
Un and Redo is possible and after various tests the MHE seems to be stable and 
consistent even after a lot of un/redo's.

MHE accepts MustuxAction's which have 2 methods : do_action() and 
undo_action()
Every new action created in Protux inherit from MustuxAction and automatically 
we have un/redo available for that action :-)

The next good news is, that passing the MustuxAction's to/from the MHE is 
completely done via the JMB engine, which keeps coding in Protux very clear.
To make this possible, MustuxAction has seen some work last days as well and 
it all looks very nice and simple ;-)

In other words, MHE is ready for use!


Other good news:
Transition to qmake is finished now. Both libmustux and Protux can be compiled 
and installed by just one simple call:
./compile
(if not executable, set it by chmod +x compile)

Hmm, do we have bad news.
Well, no. :-)

Of course, a lot of work has still to be done to make all actions in Protux 
un/re-doable, but it can be implemented on demand from now on since JMB 
engine can handle both the old and new situation, nice no?


OK, just to let you know :-)

Remon





reply via email to

[Prev in Thread] Current Thread [Next in Thread]