-----BEGIN PGP SIGNED MESSAGE-----
Chris McDonough wrote:
> On 4/28/09 3:01 AM, Malthe Borch wrote:
>> I think we should reconsider the way we decide on views and related
>> components. Perhaps using a routes-like approach, e.g.
>> for=".interfaces.IHelpCenter .interfaces.IDocument"
>> (to target documents inside the help center section). Or whatever
>> language/abstraction that can fit the bill. Note that to match this
>> "for" clause, something more than a simple component lookup is
> A fish doesnt know from wet, but I think if you were to want to go after some
> dispatch like this, you might as well just use some URL dispatch thing like
> Routes itself, because it ties the traversal path (at least in some abstract
> sense) to a view. And once you do that, you might as well just use a regex
> against the path itself to make it more flexible.
Or use something like repoze.uripace which does the "pattern match"
against the path and adds keys to the environment. Hmm, we might extend
the request factory to use those keys to establish the marker interface
/ "layer" of the request.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Repoze-dev mailing list