Re: [Foxgui-users]switching fox to the signal/slot mechnism from gtkmm

[Ivica L. <le...@fl...>]

Mathew Robertson <ma...@op...> writes:

> 2. Do you mean libsigc or libsigc++?

libsigc++. I thought libsigc and libsigc++ are synonyms?

> 3. signal/slot mechanism requires more code (not less) than the
> message-system, for any non-trivial application (ie more than hello
> world, for example, PathFinder)

Ok, I'll study PathFinder first and see how could it be translated to
signal/slot system.
 
> 4. '... small number of errors...'   -huh? 

I'm doing less mistakes with signal/slot mechanism than with
target/messages (might be I'm still trying to adapt it).

> It would be a quite a large amount of work to convert FOX to
> signal/slot.  I would first look at wrapping every important FOX
> class (like FXObject, FXWindow, etc) with the equivalent wrapping
> mechanism, ie convert all the FXMAPFUNC(..) instances to
> xxx.connect(..) calls.

I'm crippling FOX to the minimum required to compile hello world.  If
I find out that I can't convert this without help from some
perl/sed/awk script I'll give up (I'm curious, not fanatic).