Il 02/01/2012 17:00, Abdelrazak Younes ha scritto:
I have a pending patch that introduces Qt signals in Buffer and
BufferView, I'll try to cleanup and commit that one.
Ok, I don't know what changes will be introduced by this patch of
yours, anyway, please, drop a message on the list about the implied
changes on the code.
It's just a patch that converts Buffer::changed() and all to Qt
signals and so gets rid of WorkAreaManager and GuiDelegates.
Ok, so, unless my memory is being unfaithful to me:
1) we dropped boost::signal() for compilation performance reasons
(AFAICR, someone said that it was pulling 7K lines of code into each
compilation unit)
2) we introduced WorkAreaManager and other equivalent features via
custom dedicated classes
3) now we go back to signals, but in the Qt flavour.
This time I guess we don't have the problems of boost::signal, because
Qt is much more polymorphic oriented, rather than being template-oriented ?
However, I guess the immediate drawback will be that each class willing
to issue signals, will have to be a derivate of QObject, and have in its
declaration some weird Qt macros, such as Q_OBJECT and similar ?
AFAICR, the original boost signals didn't have any constraints/impact
like that on the code.
Just to know, thanks.
T.
