Perhaps I'm misunderstanding the implications of basing Zope2.12 on ZTK eggs. I was under the impression it would allow sites to be developed in a similar way to how its done in Zope3, ie placing your site in instance/lib/python/<site> and wiring it all together using the site.zcml now present in the Zope2.12 instance/etc dir. It seems like it should be possible, but maybe not.<br>
<br><div class="gmail_quote">On Thu, Dec 24, 2009 at 11:20 PM, Andreas Jung <span dir="ltr"><<a href="mailto:lists@zopyx.com">lists@zopyx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div class="im"><br>
Jim Pharis wrote:<br>
> I'm trying to wrap my head around what the changes in Zope2.12 can<br>
> mean for how I develop in Zope2 now. I've developed things in<br>
> Zope3 and am getting stuck attempting the same methods in Zope2.12.<br>
> So I see now that etc/ now has a site.zcml. But what is missing is<br>
> the package-includes directory that provides the wiring to zcml<br>
> directives in the varies packages. Why are those configurations<br>
> missing from Zope2.12.2 etc/?<br>
</div>Sorry, I can not follow - but Zope 2 and Zope 3 are not compatible in<br>
any way.<br>
- -aj<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.10 (Darwin)<br>
Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
<br>
iEYEARECAAYFAks0PYwACgkQCJIWIbr9KYxAPACffzJnlM2SFGU2I2a0FbVnICbn<br>
e6wAoKNXl3YrvBU7wMrRE/aMnatb+FT+<br>
=0ADb<br>
-----END PGP SIGNATURE-----<br>
<br>
</blockquote></div><br>