I agree 100% about the creating my own formcontrols, and I do it now, but if a lot of plugin authors have to do this, we could end up with a lot of different formcontrols which duplicate a lot of code due to a small inconsistency. Maybe I'm just a stickler for simplicity and uniformity.
WRT to the table support: yes, good point, I forgot people would use it for lazy layout. I was actually thinking about using it for tabulating saved data (in this case logs) in an easy way and wasn't looking at FormUI as purely a form tool (though it's name does kind of give it's function away ;-) ). I suppose a table form control is probably unnecessary given the risks of bad practise and the infrequent use. On Sat, May 30, 2009 at 3:51 PM, Arthus Erea <[email protected]> wrote: > > Remember, you are free to create your own formcontrols to be packaged > with plugins/themes if the defaults do not satisfy you. > > Colin wrote: >> No probs. >> >> As we're on the topic of improving FormUI, I've got a couple of my own >> suggestions: >> >> 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. > > Tables should be used for tabular data, NOT as a lazy way to lay stuff out. > > I am a strong -1 on introducing table support into FormUI. > > > > -- Colin Seymour Blog: http://www.colinseymour.co.uk Tech Stuff: http://www.lildude.co.uk --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
