I think it is a lot of work to have to maintain a plugin for multiple ORM's.
It would be nice, but I don't think it is realistic. You should spend a few
hours porting sfGuardDoctrinePlugin functionality to sfGuardPlugin as a new
branch/version of the plugin.
- Jon
On Dec 13, 2007 8:31 AM, Ian P.
gimler wrote:
> yes but we can rewrite the plugins step by step so i would rewrite the
> sfGuard ;)
>
> for few days a user on the mailing list has the problem that he miss
> some functions in sfGuardPlugin that has sfGuardDoctrinePlugin
Well, if an API is drawn up and decided for sfGuard, it s
yes but we can rewrite the plugins step by step so i would rewrite the
sfGuard ;)
for few days a user on the mailing list has the problem that he miss
some functions in sfGuardPlugin that has sfGuardDoctrinePlugin
my problem is descipted in this ticket:
http://trac.symfony-project.com/ticket/266
gimler wrote:
> what do you think?
> have anybody another idea?
>
Conceptually, a fantastic idea.
It kinda results in abstracting the abstraction, but in this case, I
don't think it'sa bad idea.
Finding people with the time to refactor all these plugins would be the
main issue I imagine.
-
