Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Angus Leeming wrote:
| > Abdelrazak Younes wrote:
| >>> I don't really get why you need a signal. Why can't a
| >>> BufferView.message function not call a WorkArea.message function?
| >>> There's a one-to-one correspondence, no?
| >>
| >> For now yes but I can very well imagine multiple WorkArea using the
| >> same BufferView.
| >>
| >> Use-case: a teacher wants to show how to write a LyX document. The
| >> student just have to watch on their WorkArea what the teacher is
| >> doing. Only one WorkArea could be read-write at a time. All other
| >> WorkAreas would be watch only.
| >>
| >> Sounds fun, doesn't it?
| > Sounds like pie in the sky ;-) Don't over-complicate things; you can
| > always switch to a signal when ytou've implemented your mulitple
| > WorkAreas.
|
| Man, I have worked so hard to remove the WorkArea dependency from
| BufferView and you want me to put it back?
| Beside, the code will be more complicated if I have to store the
| "owner" workarea. And final point, those message are just sugar and
| they conceptually can be displayed anywhere not just the WorkAreas.
If ther is a 1:1 relationshiop, delayed function calls can also be
used. <boost/function.hpp>
As Angus said, it's not a big deal and I suspect that most of the
message will be transfered to the frontend with some more cleanup
anyway. So I will commit the patch now and whenever there is not more
message to emit we can still delete this signal.
Abdel.
