modul

[Julien Cigar]

Hello,

I have a "core" CMS-like home made package which I'd like to modularize it a bit to be reusable.
I wondered what would be the "cleanest" approach regarding the templates and the @view_config decorators?
At the moment I have a couple of @view_config(..., renderer='blabla:templates/foo.pt') and I'd like to put the templates in a dedicated packages and config.include() them
I was thinking of a renderer="%{default}:/foo.pt" witjh a view deriver which check the presence of "%{default}" and replace it...

Any comment ? :)

Thanks!
Julien

[Bert JW Regeer]

Pyramid has an asset override system: https://docs.pylonsproject.org/projects/pyramid/en/latest/narr/assets.html#overriding-assets

--
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discus...@googlegroups.com.
To post to this group, send email to pylons-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/c15e6dcf-cd6b-4c2d-9b3e-3f72d37e26f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.