Hi Stephan. Could a Zope3 branch be set up in the zope repository so
that your enhanced tables code can be added to the branch (so contents
view refactored using it)? The contents view class could be the model
for using the tables package in zope3. In fact, it could be become the
base class with overrides to columns for custom views to provide sorting
and batching (with the capability of displaying DC data).
I like the idea of using divs to create generic presentation structures
with batching and sorting capability. I had similar thoughts of
modifying zc.tables to do something similar (after reading the code).
Has anyone an opinion about Boston vs Rotterdam as default skin and
the need for a generic batching utility? I think at some point, it is
time to say out with the old and in with the new - particularly since
viewlets factor largely in skinning (and skinning flexibility). I think
if this is what is advocated for skinning, Zope3 ought to be presented
with a default skin that uses this approach. Many thanks.
Stephan Richter wrote:
On Monday 21 August 2006 15:14, David Pratt wrote:
Hi. I am wondering if zc.tables could not be incorporated into Zope3
trunk. My rational for its inclusion is so that the contents views may
be refactored to use it. The current contents view makes little sense
without batching and sorting. The ZMI could really use this basic face
lift to bring it in line with the fundamental views provided in its
Zope2 counterpart. I'd also suggest that the Boston skin be given
preference over rotterdam as the default skin for zope.
zc.table still needs an iteration or two before it is ready for the trunk. I
have started a branch for another iteration, but it will take me a while to
complete. My goal is to cleanly include some of my enhancements (already
checked in for demonstration), to generalize the code and make a "div" based
Zope3-users mailing list