Re: [Protux-devel] MHE is born !

[reinhard]

hi,

great news, so I wanted to check the engine, but got compile errors:

...
...

g++ -c -pipe -w -g -D_REENTRANT  -DUSE_MUSTUX_DEBUGGER -DQT_THREAD_SUPPORT 
-DQT_SHARED -DQT_NO_DEBUG -I/usr/lib/qt3/mkspecs/linux-g++ -I. 
-I/usr/local/include/libmustux -I/usr/lib/qt3//include -Itmp/ -o 
tmp/CopyClipAction.o src/mustuxactions/CopyClipAction.cc
g++ -c -pipe -w -g -D_REENTRANT  -DUSE_MUSTUX_DEBUGGER -DQT_THREAD_SUPPORT 
-DQT_SHARED -DQT_NO_DEBUG -I/usr/lib/qt3/mkspecs/linux-g++ -I. 
-I/usr/local/include/libmustux -I/usr/lib/qt3//include -Itmp/ -o 
tmp/SplitClipAction.o src/mustuxactions/SplitClipAction.cc
src/mustuxactions/SplitClipAction.cc: In member function `virtual int 
SplitClipAction::prepare_actions()':
src/mustuxactions/SplitClipAction.cc:40: error: `split_clip' undeclared (first 
use this function)
src/mustuxactions/SplitClipAction.cc:40: error: (Each undeclared identifier is 
reported only once for each function it appears in.)
src/mustuxactions/SplitClipAction.cc: In member function `virtual int 
SplitClipAction::do_action()':
src/mustuxactions/SplitClipAction.cc:48: error: `add_clip' undeclared (first 
use this function)
src/mustuxactions/SplitClipAction.cc:50: error: `remove_clip' undeclared 
(first use this function)
src/mustuxactions/SplitClipAction.cc: In member function `virtual int 
SplitClipAction::undo_action()':
src/mustuxactions/SplitClipAction.cc:58: error: `remove_clip' undeclared 
(first use this function)
src/mustuxactions/SplitClipAction.cc:60: error: `add_clip' undeclared (first 
use this function)
make: *** [tmp/SplitClipAction.o] Error 1
g++ -c -pipe -w -g -D_REENTRANT  -DUSE_MUSTUX_DEBUGGER -DQT_THREAD_SUPPORT 
-DQT_SHARED -DQT_NO_DEBUG -I/usr/lib/qt3/mkspecs/linux-g++ -I. 
-I/usr/local/include/libmustux -I/usr/lib/qt3//include -Itmp/ -o 
tmp/SplitClipAction.o src/mustuxactions/SplitClipAction.cc
src/mustuxactions/SplitClipAction.cc: In member function `virtual int 
SplitClipAction::prepare_actions()':
src/mustuxactions/SplitClipAction.cc:40: error: `split_clip' undeclared (first 
use this function)
src/mustuxactions/SplitClipAction.cc:40: error: (Each undeclared identifier is 
reported only once for each function it appears in.)
src/mustuxactions/SplitClipAction.cc: In member function `virtual int 
SplitClipAction::do_action()':
src/mustuxactions/SplitClipAction.cc:48: error: `add_clip' undeclared (first 
use this function)
src/mustuxactions/SplitClipAction.cc:50: error: `remove_clip' undeclared 
(first use this function)
src/mustuxactions/SplitClipAction.cc: In member function `virtual int 
SplitClipAction::undo_action()':
src/mustuxactions/SplitClipAction.cc:58: error: `remove_clip' undeclared 
(first use this function)
src/mustuxactions/SplitClipAction.cc:60: error: `add_clip' undeclared (first 
use this function)
make: *** [tmp/SplitClipAction.o] Error 1
address@hidden protux]$



any idea?
maybe a missing file in cvs?

greetings
reinhard




On Thursday 13 January 2005 16:26, Remon Sijrier wrote:
> 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
>
>
>
> _______________________________________________
> Protux-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/protux-devel