Hey Francesco, Thank you, I had my suspicions, that this would be the case.
I understand now, but I would still like this to be prevented, since the model is only meant for internal plugin usage. The programmer can Interface with responding data via a class/object, so in this case it doesn't need those files to be created in the project-lib. Again, Thank you On 15 mrt, 14:46, Francesco Levorato <flev...@flevour.net> wrote: > On Tue, Mar 15, 2011 at 9:51 AM, Ariaan Bruinsma > > <ariaanbruin...@gmail.com> wrote: > > Is there a configuration I can make in the plugin, that will prevent > > rebuilding of the filter and form classes in the project-space? > > > Hope someone can clarify this for me, because I don't understand why > > those classes are being generated in the first place. > > Hi Ariaan, > as far as I understand your problem, this is normal and you actually > want to be like it is. > The generated classes need to be generated in the lib directory > outside the plugin, so the users (aka other developers) who will use > your plugin, will be able to modify the plugins behaviour avoiding any > direct modifications to your plugin. > I would suggest to check out the sfGuardUser plugin classes structure > to better understand what I mean. > Let me know if it's unclear, > Francesco > -- > francesco levorato aka flevourhttp://flevour.net/- @flevour > "Now while the blood is hot you should make your way with vigour to > better things." (Seneca) -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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 symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
