Hello,
I've a wierd problem which is supposed to be plain simple but I can't see
it...
Zope3 gives on startup:
File /home/florian/Desktop/zope/lib/python/CS/user_management/views.py,
line 2, in ?
from interfaces import IRegistrationForm
File
Lennart Regebro [EMAIL PROTECTED] writes:
On 2/28/06, Reinhold Strobl [EMAIL PROTECTED] wrote:
Hi,
I would like to know, if components must always be persistent.
Well, in general, only local components, or components who need to
store data needs persistence.
--
Lennart Regebro,
At 2:46 PM +0100 2/28/06, Lennart Regebro wrote:
On 2/28/06, Reinhold Strobl [EMAIL PROTECTED] wrote:
where do I put application logic???
Ööööh. In Python code? :-)
I have the feeling I don't understand the question.
I think I understand the question. Most of the tutorials show
how to
Thanks for the reply. But how would you implement previously described task with
the calculator?
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users
ksmith99 wrote:
I would add ZPT, skins and increasingly formlib to the list of things to
learn. +1 on demos vs. tutorials. A good working demo functions as both a
tutorial and a testimonial.
I think right off the bat, the bookmarker app should be incrementally
expanded. Evolving the app
Graham Stratton wrote:
What I want to be able to do is to simply create many 'sites' within a
single instance. What matters is that each site can have its own
appearance and users (editors).
Now, I'm not sure that my sites actually need to be true Zope3 sites.
Maybe I just need to have a
It would be very nice if there were a faq or other doc addressing
all of
these scalability-related questions systematically for someone like
me
who understands what a relational database is doing for them (in
return
for squashing all their objects). It seems I'm not the only one with
Other apps that start off easy but can grow increasinly complex fast.
* blog
* wiki
Wiki is already there (ZWiki ported to Zope3). Hard to call it demo, but
worth looking into. Other candidates:
* photo (media) album
* bug tracker
* shoping basket (pluggable)
* simple library
On Tue, 2006-02-28 at 17:52 +0100, Lennart Regebro wrote:
On 2/28/06, Reinhold Strobl [EMAIL PROTECTED] wrote:
Thanks for the reply. But how would you implement previously described task
with
the calculator?
I would implement it as a view on whatever object I want to view it
on. Which
