On 1 Jul 2004, at 23:16, Joerg Heinicke wrote:
On 01.07.2004 10:37, oceatoon wrote:
Hello everyone Thanks for the answers, and the paths to solutions
I went through Tim Larson's explanation, and GUI model that really give
great ground for dynamic implementation, but also come with a certain
complexity that I beleive would take me more time to overcome, and I don't
necessarely need so much freedom in the definition since my definition file
is fixed (I have a fixed number of widgets). But it gave me the idea to simply generate my CForms with complete
Definition file, and then do the selection of what I want or don't want to
show by XSLT processing the template file.
if anybody knows if this will be problematic, Warn me before the useless
work is done ;) Thanks for the thoughts.
It *can* cause problems, e.g. when you hide widgets that have validation errors or are required, so union widget would be the better solution. But you are right, the GUI model sample is to complex. Maybe I have enough spare time tomorrow.
I for one, can make neither head nor tail of the union|struct|new|class widgets.
I think they'd allow me to make a more powerful form for the Query Bean stuff, so I'd love to see some simpler examples if you get the time.
regards Jeremy
--------------------------------------------------------
If email from this address is not signed
IT IS NOT FROM MEAlways check the label, folks !!!!! --------------------------------------------------------
smime.p7s
Description: S/MIME cryptographic signature
