Re: [Zope3-Users] Re: [Zope-dev] Zope 3.4.0 candidate 1 Released
Nabble provides a web forum bridge to the mailing lists. I use both the mailing list and the forums, depending on which forum/computer I'm using at the time. Here are the links: http://www.nabble.com/Zope-f6706.html http://www.nabble.com/Grok-f28342.html We've also embedded the Grok-Nabble forum inside the grok web site: http://grok.zope.org/community/grok-web-forums Grok is categorized under "Web Development Framework" and "Python" on Nabble, but all of the Zope lists are only categorized under "Content Management Systems". Whoever has the keys to the Zope/Nabble registration should perhaps change the categorization to "Web Development Framework" and "Python" and "Content Management Systems".___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: [Zope-dev] Zope 3.4.0 candidate 1 Released
Hermann Himmelbauer wrote: Am Donnerstag, 27. März 2008 18:26 schrieb Kurt Zitze: if you want to raise the userbase of zope, the first and most obvious thing to do is, get a forum running! mailing lists are bu*** and completly out of date. it is max cumbersome to login into your email account to do a post and so on, i think i dont need to enumerate all the disadvantages of a mailing list compared to a forum. i am even not aware of how to replay to a Well, all I can say to this is: Please do not split up the userbase by opening some extra web forum. I personally dislike forums, they are often cumbersome to use, therefore I prefer mailing lists a lot. I think the chances of this happening are virtually zero. :) Although I don't like forums that much, it is true that newbies and specific users tend to use them. To satisfy both sides, I can think of a forum that has a gateway to this mailing list. If I remember it right, Plone has such a thing (perhaps it could be used somehow?). This forum would then also serve as a pretty looking archive, which is also a good thing. So does Zope. See nabble.com and news.gmane.org. and if you finaly have one, put it on the start site, not like this mailing list that is so to say hidden! It's true, that Zope3 and Zope3 support ist somehow hidden in the Zope website. But AFAIK a new Zope website is currently under development, which will probably solve all these issues. Indeed. We should see some movement on this over the weekend. everything in zope is not obvious, at least not to me. everything has to be found out in hours of studying the sources! reading the books, using google to find sources that arent linked nowhere. i stumbled over nabble, i stumbled over nearly everythink i essentialy have to know! Well, the learning curve is really steep, that's true. I personally also did have to study the sources quite often. Phillips book did help, but often only after a personal advice from himself or after studying the sources. The real problem for me was that Zope 3 is all about a new software development concept, namely, the component design with interfaces / adapters / utilities etc. This is something that the Joe Average programmer is not used to, so he does not really know how to map his ideas to a componentized architecture. I don't know how to deal with this problem, perhaps a theoretical book about componentized software design could help; On the other hand newbies like to start right away and don't want to study a complicated design book beforehand. I think this is the problem that Grok attempts to address. Another issue is the ZMI. Most people, who begin Zope3, start out with Phillips book or similar documentation which uses and adapts the ZMI. However, many people sooner or later come to the conclusion that the ZMI can not be configured to their needs, things get very complicated and people are frustrated. Many people, such like me, then have a look at a ZMI-less design (e.g. z3.pagelet, z3c.form etc.), which works better for many projects. Anyway, after approx. 1 year of Zope 3 development, I can say that going through these hassles and problems was definitely worth it. Moreover, I think, Zope 3 is very much "work in progress" and I'm expecting many things to come that will solve the issues above and make the entry step easier. Zope 3 is also one of the most advanced and powerful development frameworks in existence - in any language. I miss the Component Architecture so much when I do Java. ;) Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: [Zope-dev] Zope 3.4.0 candidate 1 Released
Chris Shenton wrote: "Martijn Faassen" <[EMAIL PROTECTED]> writes: On the rest of your rant, I agree that the beginner experience for Zope 3 is suboptimal. Work is slowly progressing towards a new website for Zope. As an alternative you might like to look at Grok (grok.zope.org), which is based on Zope 3 as well but may be somewhat easier to get started with. That said, our documentation is far from complete yet, and we don't have a forum either. :) I've been poking around the edges of Plone for a while and Plone3 makes the learning wall even steeper than Plone 2. So last weekend I got Grok, followed the tutorial, and had an application up in a day that took me a week in Plone3. Grok seems a great way for me to get into Zope without worrying about all the details yet. Kudos to the Grok team for such a pleasant product, and for some REALLY good tutorials. Thanks! Grok and Plone are not exactly competitors. You're not comparing apples and apples at all. :) I think Plone can learn a lot from Grok's philosophy and that the two projects can share a lot more infrastructure, though. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope-dev] Zope 3.4.0 candidate 1 Released
Hey, On Fri, Mar 28, 2008 at 5:30 PM, Chris Shenton <[EMAIL PROTECTED]> wrote: [snip] > Kudos to the Grok team for such a pleasant product, and for some REALLY > good tutorials. Thanks! Thanks for the kudos! I hope to see you on grok-dev if you aren't there already! Regards, Martijn ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope-dev] Zope 3.4.0 candidate 1 Released
"Martijn Faassen" <[EMAIL PROTECTED]> writes: > On the rest of your rant, I agree that the beginner experience for > Zope 3 is suboptimal. Work is slowly progressing towards a new website > for Zope. As an alternative you might like to look at Grok > (grok.zope.org), which is based on Zope 3 as well but may be somewhat > easier to get started with. That said, our documentation is far from > complete yet, and we don't have a forum either. :) I've been poking around the edges of Plone for a while and Plone3 makes the learning wall even steeper than Plone 2. So last weekend I got Grok, followed the tutorial, and had an application up in a day that took me a week in Plone3. Grok seems a great way for me to get into Zope without worrying about all the details yet. Kudos to the Grok team for such a pleasant product, and for some REALLY good tutorials. Thanks! ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: [Zope-dev] Zope 3 on Jython - Google Summer of Code
On Mar 27, 2008, at 11:51 PM, Georgy Berdyshev wrote: Hello Zope developers and Zope community! I am applying with "Zope 3 on Jython improvements" to Google Summer of Code. Yay! It would be really a great help to receive some feedback on this undertaking from the community and also developers of Zope! Then this is a good place to post. :) Although I suggest limiting the discussion to zope-dev. Please have a look at the following thread on the Zope GSoC malinglist: http://mail.zope.org/pipermail/gsoc/2008-March/000136.html There aren't many details there, so it's hard to comment. Some high-level comments: - I suggest making porting C speed-ups a very low (non-existent) priority. - I expect security proxies to be one of the greatest challenges. Maybe you can make them a low-priority by focussing initially on Zope 3 applications that don't use them, like grok. - I'd be inclined to take a bottom-up approach. So, rather than trying to get the Zope 3 "application" (a.k.a. Zope-management interface, a.k.a Rotterdam skin, a.k.a zope.app.zcmlfiles) working, focus instead on zope.interface, zope.component, and zope.publisher. (Notice I didn't mention ZODB. :) Are there wsgi servers for jython? Jim -- Jim Fulton Zope Corporation ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope-dev] Zope 3.4.0 candidate 1 Released
Marius Gedminas wrote: how bout a zope3 page on myspace?lol Just write a Facebook app that interacts with the list archives ;-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope-dev] Zope 3.4.0 candidate 1 Released
On Thu, Mar 27, 2008 at 01:38:06PM -0400, Benji York wrote: > Kurt Zitze wrote: >> if you want to raise the userbase of zope, the first and most obvious >> thing to do is, get a forum running! mailing lists are bu*** and >> completly out of date. it is max cumbersome to login into your email >> account to do a post and so on, i think i dont need to enumerate all >> the disadvantages of a mailing list compared to a forum. > > forums (and capitalization) are way too cumbersome we should switch to > texting each other with our mobile phones how bout a zope3 page on myspace?lol *shudder* Marius Gedminas -- The death rate on Earth is: (computing) One per person. signature.asc Description: Digital signature ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope-dev] Zope 3.4.0 candidate 1 Released
Am Donnerstag, 27. März 2008 18:26 schrieb Kurt Zitze: > if you want to raise the userbase of zope, the first and most obvious thing > to do is, get a forum running! mailing lists are bu*** and completly > out of date. it is max cumbersome to login into your email account to do a > post and so on, i think i dont need to enumerate all the disadvantages of a > mailing list compared to a forum. i am even not aware of how to replay to a Well, all I can say to this is: Please do not split up the userbase by opening some extra web forum. I personally dislike forums, they are often cumbersome to use, therefore I prefer mailing lists a lot. Although I don't like forums that much, it is true that newbies and specific users tend to use them. To satisfy both sides, I can think of a forum that has a gateway to this mailing list. If I remember it right, Plone has such a thing (perhaps it could be used somehow?). This forum would then also serve as a pretty looking archive, which is also a good thing. > and if you finaly have one, put it on the start site, not like this mailing > list that is so to say hidden! It's true, that Zope3 and Zope3 support ist somehow hidden in the Zope website. But AFAIK a new Zope website is currently under development, which will probably solve all these issues. > everything in zope is not obvious, at least not to me. everything has to be > found out in hours of studying the sources! reading the books, using google > to find sources that arent linked nowhere. i stumbled over nabble, i > stumbled over nearly everythink i essentialy have to know! Well, the learning curve is really steep, that's true. I personally also did have to study the sources quite often. Phillips book did help, but often only after a personal advice from himself or after studying the sources. The real problem for me was that Zope 3 is all about a new software development concept, namely, the component design with interfaces / adapters / utilities etc. This is something that the Joe Average programmer is not used to, so he does not really know how to map his ideas to a componentized architecture. I don't know how to deal with this problem, perhaps a theoretical book about componentized software design could help; On the other hand newbies like to start right away and don't want to study a complicated design book beforehand. Another issue is the ZMI. Most people, who begin Zope3, start out with Phillips book or similar documentation which uses and adapts the ZMI. However, many people sooner or later come to the conclusion that the ZMI can not be configured to their needs, things get very complicated and people are frustrated. Many people, such like me, then have a look at a ZMI-less design (e.g. z3.pagelet, z3c.form etc.), which works better for many projects. Anyway, after approx. 1 year of Zope 3 development, I can say that going through these hassles and problems was definitely worth it. Moreover, I think, Zope 3 is very much "work in progress" and I'm expecting many things to come that will solve the issues above and make the entry step easier. Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Skin and Cookie Path - Zope 3 bug?
Hi, In my Zope3-based site, I use the SessionCredentialsPlugin to extract my authentication information. This plugin also sets a cookie. Together with the cookie name, content and host, a path is stored. This path contains the skin, which I enter in my URL, e.g. for: http://localhost:8080/++skin++MySkin/mysite/ cookie path: /++skin++MySkin Interestingly, "mysite" is not in the path. The problem is that if I now access my site without the skin, a second cookie with the path "/" is created. If I previously authenticated, the authentication is lost. However, If I access the site without the skin beforehand, and after that with the skin, there are also 2 cookies created, but the cookie content is equal, only the path differs. And if I use Zope3 behind apache (virtual host), the site and the skin is included, e.g. "/mysite/++skin++MySkin". So, it seems, there's something buggy or I misconfigured something. I searched around in the SessionCredentialsPlugin source but could not find the code which creates the cookie. How can I solve this issue? Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
AW: {Spam?} Re: [Zope3-Users] Problem with z3c.form / z3c.formui packages
Hi Thierry
> Betreff: {Spam?} Re: [Zope3-Users] Problem with z3c.form /
> z3c.formui packages
>
> On mer, 2008-03-19 at 06:33 -0700, garz wrote:
>
>
> have some views for some content:
> class
> SomeContentDisplayForm(z3c.formui.layout.FormLayoutSupport,
> z3c.form.form.DisplayForm):
> fields = z3c.form.field.Fields(ISomeConcent)
> class SomeContentEditForm(z3c.formui.layout.FormLayoutSupport,
> z3c.form.form.EditForm):
> fields = z3c.form.field.Fields(ISomeConcent)
>
> if i try to use the view, a componentlookuperror is raised:
> IFieldWidgets cant be looked up
>
> i thought, the errors source was the BrowserRequest,
> which should be marked
> with the skin-type. if it was it should look up the
> adapter from the right
> layer. so i think something is wrong with my skin registration.
Does your skin or at least one super class use IFormLayoutSupport?
> could please somebody help me. i'm stuck with the problem. :(
Can you tell that kind of fields the schema defines?
Probably there is not widget for one of this fields configured.
Or you can check which fields makes prtobelms with using the select
filter:
fields = z3c.form.field.Fields(ISomeConcent).select('oneWidget')
Try to find the field which makes problems. And then you can
take a look if z3c.form provides a IWidget configured for that
field.
A good thing is alos debug and find out if your request really
provides the FormLayoutSupport. You can do this in the __init__
of your z3c.form class e.g.:
def __init__(self, context, request):
import pdb;pdb.set_trace()
super(MyForm, self).__init__(context, request)
Also make sure that the configure.zcml of z3c.formui
is included in your project. And you need to define the
skin with soemthing like:
> I think I had the same problem while using z3c.form
> "DisplayForm" subclass.
> Problem disappeared by using an "EditForm" subclass and
> setting form's mode to "DISPLAY_MODE"...
Seems defently a missing widget if other widget adapter will
be found for the same form.
Hope that helps
Regards
Roger Ineichen
> Thierry
>
> --
> This message has been scanned for viruses and dangerous
> content by MailScanner
