Hmmm, if i understand, you want to change already existing (or not :)
)ZF elements, in order them to serve methods of Zend_Data Interface ?
Am i right ?
If so, we talk about the same data system, only differs its way of
integration through ZF.
As a personnal developper, at my house, i found it more reasonable not
to touch ZF components already written by dev. team :)
Anyway, we can mix all that mess, beggining by adapters, then, extending
ZF components.
Something like that...
Yeah ?
nerVo schrieb:
Yes, just an interface is perhaps better than a class.
But how do you "connect" your implemented object to data sources ?
You still need some kind of adapters and an abstraction layer, no ?
I keep in mind the datagrid example, which - i think - might just
take an object as a data-source.
This object may be an implementation through a source adapter.
[...]
As i'm working on a ZF implementation of PEAR quickform and datagrid,
i may be interested in developping such components for community.
An adaptor is only needed it the interface is not supported directly
by a class that consumes datasources. For PEAR's DataGrid component,
you'd need an adaptor, that's true.
However, if a Zend_Data Interface can be agreed upon, it would make a
lot of sense if all data-consuming and -retrieving ZF components would
make use of that interface, so adaptors would not be neccessary within
the ZF. Otherwise, we'd add unneccessary overhead.
CU
Markus
