I can use rules to describe 99% of my User Interface, but I still need a very special algorithm for the last 1%. Can RapidUI cope with that?
Yes. This requires what I call a ‘transition point’ between traditional (sequential) programming and rapidUI. The rapidUI mechanism allows the control flow to seamlessly leave rule based coding, execute code of your own and reenter the rule based world. You can mix and match rules and methods/properties/events and use the best of both worlds simultaneously.