On 07/31/2014 06:33 AM, Christopher Lozinski wrote:
On 7/30/14, 10:50 PM, Fernando Martins wrote:
I don't know about ZTK, Grok.
Okay so that tells you what ZTK and Grok are.  Back to your application.
I never needed it directly and I wonder if it was not a case of over-engineering that helped zope's community fragmentation.

I don't know why grok did not succeed.

On 7/30/14, 10:50 PM, Fernando Martins wrote:
(I use my own security roles in the database) .
Well that is very interesting.  One of my biggest complaints about Zope
2 was the security model.  Security was on the instances.   Not possible
to just make security declarations on the classes, without having to
also declare it on the instances.   So I am hugely curious about your
security model.    The grok security model, while better than ZTK, still
leaves a lot to be desired.  Fortunately it is quite easy to replace.
it's just an application specific security "model". some pages (or parts of it) are merely for admin roles (which have a group of people associated). In other cases, it is the data (records, which belong to the creator, or corresponding team, or related maintainers. Has it happens, the roles are part of the data of the application and naturally used to manage the data or pages or parts of it. For the pages, it is hard-coded. Each page has associated a single Python script (business rules) that produces all data as a single class which includes attributes like isAdmin, isEditor. Nothing general purpose.

On 7/30/14, 10:50 PM, Fernando Martins wrote:
although most likely my application will have to be ported to tomcat
(using jython) in the short term.
Why tomcat?  I would think that there would be many native python web
servers you could use.  Have you considered Pyramid.
It also uses the ZODB and traversal.
politics. it is supported by IT. zope is not. nothing wrong with zope itself.

Zope maillist  -  Zope@zope.org
**   No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to