[development] Table hook idea
gordon at heydon.com.au
Fri Nov 9 03:39:07 UTC 2007
No this is a replacement for theme('table') to give much better control.
David Metzler wrote:
> I don't know that this is relevant, but I've been writing general form
> api helper functions that embed form fields in a table via a field-set
> (e.g. everything in a column is checkbox) and merge the returned form
> values back into an array based on a field naming convention.
> Right now this is part of a php 5 dependent module, (xml_ui) and so not
> really ready for syndication.
> But if you find it helpful, I'd certainly be willing to share code with
> you. (also won't be offended if you don't use it).
> For me, form fields within a table is more interesting than hook_table,
> but hey, I'm just one guy.
> On Nov 8, 2007, at 4:55 AM, Gordon Heydon wrote:
>> Gerhard Killesreiter wrote:
>>> Earl Miles schrieb:
>>>> Gordon Heydon wrote:
>>>>> Once drupal 6 is out I am going to be continuing my development of
>>>>> merging theme(table) to the formapi. I have gotten the #pre_render
>>>>> the formapi so that we can generate the table from a drupal_render().
>>>> I am really against merging theme('table') and formapi for two reasons:
>>>> 1) I've already written that theme('table') is harmful to themers, in
>>>> general. I want to see less use of it, not more.
>>>> 2) I feel very strongly that we do *too* much display-oriented work in
>>>> fapi and we need to do less. We need to separate that work, not combine
>>>> it more. Yes, we need to do it in such a way that we retain the power
>>>> that we have, but right now we are giving the module developer power at
>>>> the expense of the themer. This is a trend I am actively attempting to
>>> I am fearing the performance implications...
>> Yes, that is on my mind as well. But I hope that it is no worse than the
>> the current system, but we will not know that until it is done.
More information about the development