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

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

Lothar Scholz <ll...@we...> writes:

> Are you sure you read the section in the FAQ that explains why this
> message passing algorithm was choosen ?

Aha and as unexpirienced in that area I don't think:

  Templates are instantiated at compile time.  This means it's going
  to be difficult to hook up objects which are only known at run time
  [like e.g. loading a custom control from a DLL].
  
  To connect a message source and a target, you actually construct a
  connector object that is parameterized by the target; you can not do
  this unless you know the type of the target [This is because
  pointer-to-member-of-class types can only be downcast!].
  
  Hard to serialize, because a pointer-to-member-of-class contains a
  function-pointer when the member is not a virtual.

are good reasons for not using signal/slot mechanism from libsigc (I
would appreciate more examples since I would like to write portable
applications but I'm stuck on FreeBSD and Linux). Signal/slot idea is
tempting from my point of view (easy to accept, less user code, small
number off errors), and some Qt users I talked to said they would be
very tempted to use GUI library that doesn't require some kind of moc
and acts as gtkmm (other reasons to switch were: good documentation,
lgpl, very few dependencies, active development).

Now, I'm not trying to say what Jeroen is doing is wrong and I'm not
trying to do something about it. I'm just asking would it be hard (how
hard) to convert FOX to use signal/slot mechanism and where should I
be careful when (possibly) doing that conversion as hobby project. I
hope that's not off topic on this list.

Btw. Are there any usable GUI builders for FOX?