Jake Press wrote: > I have done a quick google and grep of my latest project (RC1) to no > avail. > Where is the method "getHtmlContent" defined?
The getHtmlContent() is just an example. The $form->getObject() returns the object associated with the current form. So getHmltContent() is just a method of this object model class. > > Are you saying the auto forms goodness will not support read-only > fields at all? If it's a read-only form field, the you can add a disabled HTML attribute to the widget. Fabien > > By 'auto forms' i mean the magic around printing the form-object and > having the form laid out for you: > <?php echo $form ?> > > Thanks > > > On May 16, 8:24 pm, Fabien POTENCIER <[EMAIL PROTECTED] > project.com> wrote: >> The form system generate form widgets for editable fields. If you want >> to output a field from a Propel form, you can use : >> >> <?php echo $form->getObject()->getHtmlContent() ? >> >> Fabien >> >> Jake Press wrote: >>> With the recent removal of sfWidgetFormIdentity, where does this leave >>> us with creating fields that are not editable by the user? ie only for >>> display purposes >>> I could be mistaken but as far as i can see, the only thing we can do >>> is set a raw 'readonly' attribute on our fields? >>> - This will not work on all fields of course, for starters the HTML >>> SELECT element does not support this :) >>> I would have expected a nicer setReadonly() or similar method at the >>> widget and maybe even the form level - to have a field or entire form >>> rendered read-only. >>> Thoughts? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
