Owen, If the formcontrol were used to display truly tabular data I would fully support it.
However, Colin's suggestion, together with his other points about layout, seemed to be pointing to a presentational use. Especially since he said it would be like a "fieldset." Your suggestion of a table with different rows certainly seems viable. If the control is used for displaying data like that, I can definitely support it. I've even had instances where such a control would be useful, so I can see utility to that control. But it shouldn't be used as a way to align labels. ~Arthus On May 31, 2009, at 12:09 PM, Owen Winkler wrote: > > Arthus Erea wrote: >> >> Colin wrote: >>> >>> 1. How about table support? I've taken a quick look and I suspect >>> this can be done in a similar way to the fieldset functionality, >>> just >>> a bit more complex. >>> >> What possible use do tables have within forms? FormUI is for creating >> forms, not for creating other types of data. > > There are many calls for tabular data with multiple column control > support in plugins. > > As a simple example, imagine a plugin that aggregates feeds. This > plugin could provide a table as part of its UI to configure the > feeds it > aggregates and in what manner they are retrieved. Coulmns could > potentially contain: Feed URL, Type (atom/rss), Poll Frequency (in > seconds) > > This type of control would be very useful, if even to allow simple > tuple > entries. > >> Tables should be used for tabular data, NOT as a lazy way to lay >> stuff out. >> > > Using the above description, the only way I can imagine a tabular > display could be used to layout things lazily is if each option of the > plugin was a row with two columns, one being an option key and one > being > an option value. This wouldn't allow for separate validation on each > row entry, and would likely be a less ideal interface than the plugin > deserves. > > Nonetheless, the utility of a tabular interface element put to correct > use is too great to toss it out completely because someone might use > it > for the wrong reason -- similar to how the HTML spec still has the > <table> tag for tabular data, even though you're not supposed to use > it > for layout. > > Owen > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
