Kevin Dangoor wrote: > It's an interesting point, though. It may be possible, with a little > API smoothing, to make *all widgets* usable in places where you'd > currently have to use a form. If that sounds good to people, it's > worth opening a ticket on... opinions? >
Last week I've made a small syntax highlighter widget just for fun :-) but I haven't put it inside a form and I couldn't see it from my tg app but only from the widget browser, can this be the reason? If so, that's not what I was expecting. If I understand it right you have designed widget with the idea that they should all be included inside a form, but the system you have made is so nice that I would like to use them also for other purposes. IMHO there should be a clear distinction between form/form fields widget and other widgets that don't require a form (and hence a validator) like Ronald grid widget, syntax highlighter and so on. Maybe a Widget base class, a ValidableWidget (for form fields), a CompoundWidget (for forms and generics widgets made up by other widgets). I'm sure I'm getting something wrong, sorry. Ciao Michele
