Produits Entr'ouvert » Authentic 2

For a real template I would go for an empty class Plugin(authentic2.foobar.BasePlugin) (well, as empty as possible, we probably need get_apps); ditto for models, I would prefer it done like django apps, just a "# add your models in this file" line.

I am note sure about it, but could the plugin_enabled decorator find its way into authentic?

s/Uperrcase/Uppercase/.

Frédéric Péters a écrit :

For a real template I would go for an empty class Plugin(authentic2.foobar.BasePlugin) (well, as empty as possible, we probably need get_apps); ditto for models, I would prefer it done like django apps, just a "# add your models in this file" line.

Ok for the models.py file (and the admin.py too) but for the __init__.py and its plugin class I'm more inclined to let as much hooks visible, as there is not much documentation on them for now.

I am note sure about it, but could the plugin_enabled decorator find its way into authentic?

Not so easy as it depends on the plugin specific ENABLED settings. I could make the enabled status part of the signature of the plugin class with some kind of is_enabled(cls) method, and use it in a generic decorator which would receive the name of the plugin as a parameter but it seems a lot of work for something that each plugin can do his own way.

Fine, then for method signatures, but is the content of service_list and logout_list really necessary? It seems confusing, especially as it embeds actual questions (the "# utils.get_actions() ?" line).

Ok, thanks; I believe this is fine as is.