David E Jones wrote:
On Feb 18, 2008, at 8:26 AM, Adrian Crum wrote:
David E Jones wrote:
On Feb 17, 2008, at 10:33 AM, Adrian Crum wrote:
One thing those discreet elements will never do that higher level
widgets can do -change their behavior based upon their contents.
The screenlet's handling of a contained form's pagination menu is an
example of that.
A good example of balance between high/low level might be to have
some more generic pagination widget instead of having to go through
the screenlet widget.
That's a great suggestion! I was thinking along the same lines while I
was working on the screenlet widget.
The problem with the form widget is that it has gotten very
monolithic. The pagination menu code is intertwined with the rest of
the code, so manipulating the pagination menu is impossible. I was
thinking at the time that I'd like to refactor that so that the form
widget pagination is contained in a Menu subwidget - which can be
extracted and manipulated, or replaced.
You're absolutely right. It would be more flexible if there were
external pagination options. Having pagination as part of the Form
Widget is similar to having pagination as part of the screenlet.
Although... if the Form Widget does it's own query in an action that may
not work so well (or it might work fine... hmmmm...). Anyway, it would
be interesting to look into.
The way the screenlet widget handles that now (and I plan on changing
that) is it runs the form widget's actions before displaying the
pagination menu. That results in running the form widget's actions twice
- so I'd like to work on that more and get a 'smarter' implementation done.
I'll make a note of what we've discussed so far and work on it after I
finish up some of the other things I have going on.
-Adrian
