2010/8/24 Felix <address@hidden>
From: Arthur Maciel <address@hidden>
Subject: [Chicken-users] Qt egg - understanding it
Date: Mon, 23 Aug 2010 23:15:04 -0300
Unfortunately not without generating a huge pile of wrapper code (see
> Isn't it possible to directly map every procedure/slot of a Qt widget into
> an equivalent Scheme code?
"Smoke", which does that for PyQt). The qt egg we currently have takes
advantage of the fact that properties can be dynamically changed, but
(currently) only explicitly wrapped methods can be invoked. Some
widget-classes are available directly for convenience, though, but the
selection is (currently) more or less arbitrary.