[dev] traditional view app best practices

[Chuck Hagenbuch]

Quoting Ralf Lang <lang at b1-systems.de>:

>> > This is okay and probably right for the "right now", but what we
>> > (I?) really want is to move to forms generated by reusable
>> > Horde_View widgets and stored with Horde_Rdo, with validation to be
>> > refactored out of Horde_Form into a separate library (and probably
>> > integrated with Horde_Rdo).
>
> Wouldn't this tie content validation too strong together with relational/sql
> databases? Maybe one could provide Rdo-like interfaces for Ldap or Kolab or
> [some other datastore] if needed. That said, I really like Rdo and have
> (ab)used it a couple of times. Encapsulating Rdo_Base items inside some
> controlling class probably helps me stop over-using the magic getters.

I did not mean that the validation should be tightly coupled to  
Horde_Rdo - it'll be possible to use it without Rdo. But I think Rdo  
should provide easy integration with it.

-chuck