On Dec 18, 2008, at 6:36 PM, Mike Orr wrote:
file - controllers/semi_static.py
controller - SemiStaticController
method - faq
Note that you can customize the controller name if desired by dropping
a line into semi_static.py like so:
__controller__ = 'MyClassController'
Cheers,
Ben
I can't seem to reply to the 'group', so i'm emailing the group
address and 2 vocal people, hoping for the best. apologies if you get
this 2x.
something that i would LOVE to see in routes, is this:
right now, routes maps like this:
map.connect( 'faq_page', 'faq', controller='semi_static',
On Thu, Dec 18, 2008 at 4:44 PM, Jonathan Vanasco jonat...@findmeon.com wrote:
I can't seem to reply to the 'group', so i'm emailing the group
address and 2 vocal people, hoping for the best. apologies if you get
this 2x.
something that i would LOVE to see in routes, is this:
right now,
I've suspended my changes in light of Ben's new API, which is now
partly implemented.
I don't understand what exactly minimization means, and how
eliminating it changes Routes. Section 3.1 of the manual says:
1 m.connect(':controller/:action/:id', action='view', id=4)
2
3 # Will match all of
-Ursprüngliche Nachricht-
Von: pylons-discuss@googlegroups.com
[mailto:[EMAIL PROTECTED] Im Auftrag von Ben Bangert
Gesendet: Samstag, 24. November 2007 00:35
An: pylons-discuss@googlegroups.com
Betreff: Re: Routes user survey
On Nov 23, 2007, at 1:37 AM, Mike Orr wrote:
I've
Andrew Smart wrote:
-Ursprüngliche Nachricht-
Von: pylons-discuss@googlegroups.com
[mailto:[EMAIL PROTECTED] Im Auftrag von Ben Bangert
Gesendet: Samstag, 24. November 2007 00:35
An: pylons-discuss@googlegroups.com
Betreff: Re: Routes user survey
On Nov 23, 2007, at 1:37 AM, Mike
redirect routes need some detailed design.
a) There should be an easy way to define internal redirects.
Important thing here is that the destination url should be defined
using routes by itself. I am not sure about the syntax, but url_for
need not be available at the moment (for
On Nov 23, 2007 6:19 AM, Paweł Stradomski [EMAIL PROTECTED] wrote:
Well, I think the current solution (function being passed by the framework to
routes) is better, as it gives more flexibility. Throwin an exception would
force just a single way of informing the framework about redirects - and
please don't get rid of url_for(controller='foo', action='bar') I use
that all the time, and although I know that url_for('named route') does
look more elegant, if you get rid of the former behavior, then we're
left having to name all of our controller/actions pairs. To me this
looks like
On Nov 23, 2007 7:34 AM, Paweł Stradomski [EMAIL PROTECTED] wrote:
W liście Mike Orr z dnia piątek 23 listopada 2007:
On Nov 23, 2007 6:19 AM, Paweł Stradomski [EMAIL PROTECTED] wrote:
Well, I think the current solution (function being passed by the
framework to routes) is better, as it
W liście Mike Orr z dnia piątek 23 listopada 2007:
On Nov 23, 2007 5:46 AM, Paweł Stradomski [EMAIL PROTECTED] wrote:
W liście Marcin Kasperski z dnia piątek 23 listopada 2007:
redirect routes need some detailed design.
If we had a separate redirect layer, where would it reside? As a
On Nov 23, 2007 5:46 AM, Paweł Stradomski [EMAIL PROTECTED] wrote:
W liście Marcin Kasperski z dnia piątek 23 listopada 2007:
redirect routes need some detailed design.
I think that this does not belong to routes - but to pylons in general.
In fact I believe that redirect function in routes
W liście Marcin Kasperski z dnia piątek 23 listopada 2007:
redirect routes need some detailed design.
a) There should be an easy way to define internal redirects.
Important thing here is that the destination url should be defined
using routes by itself. I am not sure about the syntax,
Mike Orr wrote:
On Nov 23, 2007 5:46 AM, Paweł Stradomski [EMAIL PROTECTED] wrote:
W liście Marcin Kasperski z dnia piątek 23 listopada 2007:
redirect routes need some detailed design.
I think that this does not belong to routes - but to pylons in general.
In fact I believe that redirect
On Nov 23, 2007 4:30 AM, Marcin Kasperski
[EMAIL PROTECTED] wrote:
c) In case of internal redirects it may make sense to handle
'invisible redirect' (just picking the destination object using the
redirected-to route without generating any redirect to the browser)
as one of the
W liście Mike Orr z dnia piątek 23 listopada 2007:
On Nov 23, 2007 6:19 AM, Paweł Stradomski [EMAIL PROTECTED] wrote:
Well, I think the current solution (function being passed by the
framework to routes) is better, as it gives more flexibility. Throwin an
exception would force just a
On Nov 23, 2007, at 1:37 AM, Mike Orr wrote:
A few of us have been kicking around ideas for improving Routes. I've
got an API proposal at
http://wiki.pylonshq.com/display/routes/Proposed+Changes
I'd like some feedback from those who use Routes heavily on whether
you use the less-common
17 matches
Mail list logo
