StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POMaking a Proxy Class
primarykey
Id
6500686
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-06-28T01:33:48.353
FavoriteCount
0
LastActivityDate
2011-06-30T13:53:11.050
LastEditDate
2011-06-30T13:53:11.050
LastEditorUserId
396223
OwnerUserId
396223
ParentId
0
PostTypeId
1
Score
2
ViewCount
435
LastEditorDisplayName
text
Body
I'm trying to do a Proxy class that allow me to set custom values to different sfForm's. I have to do it this way because php dosn't have multiple inheritance (all sfForm extends some Base* made by doctrine) and I'm always copy-pasting the same code to sfForm configure() method. Up to now I made the class but couldn't make it work. I know i have to pass the object by reference but i'm stuck! Here is what I made <pre><code>class FormProxy { private $_form; private $_formatter; public function __construct(sfForm &$form, $params = array()) { $this->_form = $form; if(count($params)>0) $this->set ($params); } public function set($array = array()){ if (count($array) == 0){ return; } if(isset ($array['formatter'])){ $this->setFormatter($array['formatter']); } if(isset ($array['CSRFProtection'])){ $this->disableCSRFProtection(); } return $this; } public function setForm(sfForm &$form){ $this->_form = $form; return $this; } public function & getForm(){ $this->init(); return $this->_form; } public function getFormatter(){ return $this->_formatter; } public function setFormatter($formatter = null){ $this->_formatter = $formatter; return $this; } private function init(){ if($this->_formatter != null){ $decorator = new sfWidgetFormSchemaFormatterLocal($form->getWidgetSchema(), $form->getValidatorSchema()); $form->getWidgetSchema()->addFormFormatter($this->_formatter, $decorator); $form->getWidgetSchema()->setFormFormatterName($this->_formatter); } } public function disableCSRFProtection(){ $this->_form->disableCSRFProtection(); } } </code></pre> I know the proxy class could be static, but for now it's the same. Edit: My problem is that when I do <pre><code> $proxy = new FormProxy(new ClientForm(), array( 'formatter' => 'custom', 'CSRFProtection' => false, )); $form = $proxy->getForm(); </code></pre> the changes made into the FormProxy doesn't seem applied outside (in the $form variable). I think this is because I'm not handling very good the reference of the $form, but tried in different ways with negative outcomes . 
Tags
<php><symfony1>
Title
Making a Proxy Class
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USPabloks
UserOwnerUserId
1. USPabloks
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POMaking a Proxy Class
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POMaking a Proxy Class
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COWhy not move the code that you need for all forms to BaseFormDoctrine, which is inherited by all form classes?
 singulars
 PostPostId
 POMaking a Proxy Class
 UserUserId
 USDziamid
2. COBecause: if I do another project have to copy-paste all over again, if upgrade version the same, and I don't find it very "elegant" to do. I know this isn't the end of the world, but if i can do it properly, i would try :)
 singulars
 PostPostId
 POMaking a Proxy Class
 UserUserId
 USPabloks

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.