-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for a tips, I have looked on the Guide you suggested. I think I understand the concepts, but still missing something. To make the simplest case, 1. I started with fresh instance prepared by the paster, 2. created this source: # src/my.py class Contact(object): "blah blah" firstName = "aaaa" c = Contact() 3. to the sys.path in bin/instance added the "/path/to/src" (which contains my.py), 4. started instance and checked, that the /path/to/src is on loaded sys.path, 5. pointed browser to localhost:8091/c/firstName . Resource c not found, Zope says. Yes, it can't be SO simple, but please, what should I do? Thanks for your patience.. David Lennart Regebro napsal(a):
On Sat, Mar 7, 2009 at 23:21, David Zejda <dvid@atlas.cz> wrote:
And now, please, what to do now, to have a few python lines somewhere in the egg dir, which the zope would know how to deal with?
The "egg dir" as you call it is a Python module, and you put Python code there. Zope knows how to deal with it, that is not the problem. What you need to do is get the Python code to deal with Zope. :)
And on what url will be the "hello world" available then?
That is completely up to you. :)
The question now, is this Zope 3 or Zope 2?
For Zope 3, you should probably get a book. http://worldcookery.com/ There was another book to in the beginning of Zope 3, but I don't know it has been updated. You could also, for Zope 3, opt to use Grok, which is a framework built on Zope 3 that makes Zope 3 easier: http://grok.zope.org/
For Zope 2, you can start here: http://docs.zope.org/zope2/zdgbook/source/ Then, you should probably buy the above book too. Zope 3 technologies are getting very common in Zope 2.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkm25GQACgkQ3oCkkciamVFQ0QCeOHfaWDV4dSvM+TaZKyIyNpKC JpEAn0R65e8asVaogcfaCeQF5qDoj1vb =FtXB -----END PGP SIGNATURE-----