Hi,

  i have a problem: i want to extend a propel behavior, and in order
to this, I want to bundle my changes into a plugin. The plugin will
contain some hooks, helpers and a component or partial ( html
layout ); I would like to use the component in the admin generator,
but i don't know how to do this. ( extend admin theme? is their a
simpler and more elegant way? ).
  in more concrete: i want to extend
sfPropelActAsNestedSetBehaviorPlugin with a component to add easy a
new node as a child or sibling => for this i need a html layout ( let
say a drop down list to specify the "parent" and a check box to
specify if the node will be added as a child or as a sibling to the
selected "parent" node ). In admin generator I would like to use this
component in the 'edit' section: also the component maybe needs some
parameters ( like the name of the input fields, peer,
perr_method... ), but maybe i can guess all the paramters getting the
current module. I wouldn't like to copy the component for each module
in part... ( i would like to use this component in several modules:
whenever i need a nested set, and bundle it into a plugin as an
extension for the current sfPropelActAsNestedSetBehaviorPlugin ).
  how can i solve this?

regards,
  Rich

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to