RE: [PEAR-DEV] HTML Controls
| From: | James Hurst | Date: | Mon, 26 Nov 2001 17:57:51 +0000 |
| Subject: | RE: [PEAR-DEV] HTML Controls | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-3119@lists.php.net to get a copy of this message | ||
> This was our goal too.
> With Adam Daniel, we were thinking about such an API. I think
> this is doable
> within HTML_QuickForm but it will require some modifications.
OK. How would you feel about automatic state maintenance though? i.e:
$txtName = new text("txtName");
..at which point $txtName->getValue() already contains any matching value in
G, P or C, and that value is automatically inserted when you call
$txtName->toHTML();
Does this sound like something that is generally a good default behaviour?
Or can you envisage people not liking it?
Also, what is the historical difference between HTML_QuickForm and
HTML_OOH_Form? It seems as though the latter is newer, but covers a lot of
common ground with the former.
I have to say that your project seems very cool (the templates stuff sounds
excellent), but I think that I have different priorities. I guess you could
sum up my intentions as 'providing a php version of the ASP.NET
webcontrols'. This might not sound very different on the surface, but there
are many subtle differences such as naming conventions. My api doesn't
distinguish between 'input type="text"' and 'textarea', but instead
there is
a 'TextBox' class with a 'TextMode' property that you can set to
'MultiLine'.
By sticking to these conventions, people familiar with ASP.NET will feel
right at home with my controls. Obviously my stuff wont be quite as large
and complex as ASP.NET, but you get the idea.
So you can see why I fear that my project isn't exactly compatible with the
existing code, - even if the reasoning is quite selfish.
This therefore raises the question - Would people be OK with another HTML
control style package that aimed to provide an API similar to that of
ASP.NET, and was independent of the existing packages? Would this just cause
too much confusion for PEAR users, or is extra choice welcome?
The list of controls available would be:
Button
CheckBox
CheckBoxList
HyperLink
Image
Label
ListBox
ListControl
ListItem
ListItemCollection
RadioButton
RadioButtonList
TextBox
If the response is generally enthusiastic, then I will make a point to use
the PEAR conventions with a view to submitting it once it is pretty much
there. If not, I'll keep out of your way and let (or perhaps even help) you
guys carry on with your valuable projects.
Cheers.
James Hurst.
mailto:james@projects.new-media.co.uk
// "Better lives have been lived in the margins,
// locked in the prisons and lost on the gallows than
// have ever been enshrined in palaces." - Propagandhi 2001