On Fri, May 23, 2008 at 4:09 PM, Mark Ramm <[EMAIL PROTECTED]> wrote:
>
> I would like to depricate the dotted notation on template lookups, and
> just use search paths.
>
awesome +1 on that.

> So we would stop doing
>
> @expose("myproject.templates.index")
>
> and just do
>
> @expose("index")
>
> Because the ./myproject/templates/ directory would be in the search
> path for genshi.
>
> The same would be true of mako.
>
> There are some advantages of the search-path system, but the core
> advantage is that it's the same as pylons, and it's more like the
> "standard" way that genshi and mako would be used.
>
I read this a while ago and it totally convinced me
http://wiki.pylonshq.com/display/pylonscookbook/Template+plugins+(for+developers)
under "History, dotted notation vs URI notation, and the future"

As noted on that doc the dot-style URLs are buffet based and the /
notation used by pylons is a modified buffet, which means that if TG
is moving (or supporting both) buffet spec itself should be modified.

> I also think it would make sense to support:
>
> @expose(index)
>
> Where index is a GenshiTemplate object.
>
I can see the usecase for that. although it should get implemented in
a way that mako doesn't gets left out.

> I'm planning on working on the template rendering stuff this weekend,
> so that we can support our current API on top of Pylons new rendering
> functions (without buffet).
>
I need to take a look at 0.9.7 on that part because 0.9.6's uses a
modified buffet.
> What do people think?
>
> --
> Mark Ramm-Christensen
> email: mark at compoundthinking dot com
> blog: www.compoundthinking.com/blog
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" 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/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to