Chris Withers wrote:
> Jim Fulton wrote:
>
>>
>> This isn't really URL parsing, it's traversal. It's easy to plug in
>> different traversal adapters.
>
>
> Are there any examples of this or docs?
>
> Chris - sorry if I'm missing something obvious :-S
>
I am also very interested in learning ab
Jim Fulton wrote:
This isn't really URL parsing, it's traversal. It's easy to plug in
different traversal adapters.
Are there any examples of this or docs?
Chris - sorry if I'm missing something obvious :-S
--
Simplistix - Content Management, Zope & Python Consulting
- http://www
Andreas Elvers wrote:
Chris Withers wrote:
Jim Fulton wrote:
This is a matter of policy. It is straightforward to change. Many
people hate
@@ and the ++view++name syntax. They will often arrange their item
and view
names so that they don't overlap.
How hard is it to plug in different u
Chris Withers wrote:
Jim Fulton wrote:
This is a matter of policy. It is straightforward to change. Many
people hate
@@ and the ++view++name syntax. They will often arrange their item
and view
names so that they don't overlap.
How hard is it to plug in different url parsing? It's often so
Jim Fulton wrote:
This is a matter of policy. It is straightforward to change. Many people
hate
@@ and the ++view++name syntax. They will often arrange their item and
view
names so that they don't overlap.
How hard is it to plug in different url parsing? It's often something
people want to
Jeff Rush wrote:
Frank Burkhardt wrote:
On Tue, Dec 13, 2005 at 02:02:05PM +0100, Andreas Elvers wrote:
what the rationale of @@ anyway ? I've searched for a definition for
this in the Developer Handbook and elsewhere but it's hard to search
for @@ and view.
@@ marks a given path componen
Stephan Richter wrote:
On Tuesday 13 December 2005 08:02, Andreas Elvers wrote:
what the rationale of @@ anyway ? I've searched for a definition for
this in the Developer Handbook and elsewhere but it's hard to search
for @@ and view.
For insight or pointer to documentation or source to this m
Andreas Elvers wrote:
what the rationale of @@ anyway ?
One of the reasons is that it creates a name space. If you have a view
of a container named "foo" what happens if you create an object in the
container also named "foo"? Does the object hide the view, or does the
view hide the object
Hi,
On Tue, Dec 13, 2005 at 02:02:05PM +0100, Andreas Elvers wrote:
> Hi all,
>
> what the rationale of @@ anyway ? I've searched for a definition for
> this in the Developer Handbook and elsewhere but it's hard to search
> for @@ and view.
(To all Gurus: Please correct me, if I'm wrong)
@@ mar
On Tuesday 13 December 2005 08:02, Andreas Elvers wrote:
> what the rationale of @@ anyway ? I've searched for a definition for
> this in the Developer Handbook and elsewhere but it's hard to search
> for @@ and view.
>
> For insight or pointer to documentation or source to this matter I'd be
> ver
10 matches
Mail list logo
