Continued, hit enter by mistake:
propel:
sf_templating_behaviour_plugin:
_attributes: { phpName: sfTemplatingEntry, withForms: false,
withFilters: false }
Now, I'm not familiar enough with propel to be able to implement that
straightaway myself. I have looked at symfony's current implementation
(which is to simply iterate over all tables in the database map), so
if Propel's builder were to be altered to include a static property
which indicates whether forms and filters to be build, adding a simple
check and a continue should suffice, right?
On Aug 9, 12:38 am, Crafty_Shadow <[email protected]> wrote:
> The current implementation of the symfony forms system is too
> forceful. I am sure, many of you would agree that there are quite a
> few instances when building a form/filter class the corresponding
> model in not only unneeded but can make for quite an inconvenience.
>
> Take plugins for example, more often than not a plugin that does some
> kind of database manipulation does not need form classes built, on the
> account that it deals with a specific problem in a specific way. There
> is even less need for the filter classes, as they're useful almost
> only for the admin generator.
>
> There should be an easy and straightforward way to disable building
> forms/filters for a specific model.
> The most obvious approach would be some kind of an extra _attributes
> key, for example:
>
> propel:
> sf_templating_behaviour_plugin:
> _attributes:
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
