[Grok-dev] Traverser, Request and URL mess

Souheil CHELFOUH trollfot at gmail.com
Thu Mar 4 09:44:49 EST 2010


If you only need one fixed URL to answer without the ++whatever++
added, you can simply directlyProvides the interface in your request.
This will save you time

2010/3/4 Jeroen Michiel <jmichiel at yahoo.com>:
>
>
> Martijn Faassen-2 wrote:
>>
>> [snip]
>> We're talking about the ability to generate a URL to something in
>> another skin, correct? I.e. to generate a link to the application's URL,
>> and the application is *not* in the admin UI skin of course. The other
>> situation where this happens would be if you would want the root of the
>> site to redirect to the admin UI (which is in the ++grokui++ skin). But
>> we have the added complexity that ++grokui++ is its own namespace here,
>> instead of ++skin++grokui.
>> [snip]
>>
>
> Sorry to dig up an 'old' thread, but I'm running into the exact same problem
> here!
> I'm working on the YUI/AJAX tutorial, and I want to use an edit form in 2
> different skins, the default and an AJAX skin. I'm also using megrok.layout,
> so I can define 2 different layouts for both skins: the default skin with
> the HTML head, body tags and the menu and stuff, and the ajax skin with
> nothing but the page data, so I can load the form html with an AJAX request
> and insert it in my page.
>
> Of course, this requires me being able to apply the AJAX skin to the ajax
> request, and I was thinking of just adding ++skin++ajax/ to my url's...
>
> I guess the only 'elegant' solution is to write a IBeforeTraverseEvent
> subscriber that checks it there is a HTTP_X_REQUESTED_WITH header set and
> then apply the ajax skin, right?
>
> Maybe this would be a good idea for a very small megrok.ajax package?
> --
> View this message in context: http://old.nabble.com/Traverser%2C-Request-and-URL-mess-tp25823604p27781397.html
> Sent from the Grok mailing list archive at Nabble.com.
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev
>


More information about the Grok-dev mailing list