[Zope3-dev] ZPTPage.content_type make editable?
Hi, I'd like to change ZPTPage editform and make content_type field editable. (content_type is defined in IRenderZPTPage) Because sometimes zptpage's content_type value is inappropriate, for example, when I change object name from "foo.html" to "foo.xml", etc. I'd appreciate any suggestions. Thanks. -- Yusei Tahara ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Display widget for IText and ITextLine
Hi, > do you want the widget to display the value and then > pass the original value back in? If so, you could just use an > EditWidget in its disabled / read-only mode. Yes, right. I want to display value and pass the value to next page. So, my use case is to display value from request. My zpt code is """ """ And I expect the following html, but if I use IText or ITextLine, the result is difference. """ Zope """ Some display widgets can render a hidden input tag by hidden() method (For example, a widget for IChoice), but DisplayWidget cannot. And another problem is about to display value from request. Some display widgets can get value from request by _toFieldValue(), then we only call __call__ method for display value. but DisplayWidget cannot get value by itself. We always need to get value from request explicitly and pass the value to setRenderedValue method. These difference between widgets are obscure to me(and probably most beginners).I think widgets for frequently used fields should be same behavior. Thank you, -- Tahara Yusei [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Display widget for IText and ITextLine
Hi, When I made a confirmation form using formlib, I found that there is no specified widget for IText and ITextLine field.DisplayWidget(which is default for IField) was too poor to make confirmation page. The widget cannot get value from request and cannot make hidden tag. I would like to make a default display widget for IText field. Can I add it to zope.app.form.browser package? Any ideas, help is appreciated. Thank you, -- TAHARA Yusei [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Working on the 3.3.0rc1 release
Hi. At Tue, 12 Sep 2006 17:43:27 +0200, Christian Theune wrote: > Then this is a small reminder to Yusei, that the 3.3 branch has been > tagged for RC candidate and only *very critical* changes are allowed to > go there until we do the release. Oups, Sorry I missed the announcement. I'll be more careful in the future. Thank you. -- Tahara Yusei [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] gadfly adapter configuration
Hi. At Wed, 28 Sep 2005 16:56:58 +0300, Velko Ivanov wrote: > > Hello, > > > I tested gadly adapter then I got ForbiddenAttribute error. > > > > I think it may needs additional configuration to gadflyda.zcml. > > If you are using the UI grant tool to specify permissions for your > principal, the problem is that ZopeConnection and ZopeCursor are not > locatable objects and access is uncoditionally denied. > There was a thread on that recently, plus a submission to the bug collector. I didn't know the problem around DA and locatable, but it's very helpful to me, thank you! My problem is different from above mentioned. It was occured when I tested my sql query in test form in gadfly adapter and I found a cause of problem. I was mistaken in my last post. When DA gets own connection object, it uses __call__ method for getting connection directly instead of zapi.getUtility. Since DA was proxied, connection is proxied either. As a result, GadflyAdapterConnection and GadflyAdapterCursor have no permission declaration, then ForbiddenAttribute occur. Best Regards, -- Tahara Yusei [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] gadfly adapter configuration
Hello. I tested gadly adapter then I got ForbiddenAttribute error. I think it may needs additional configuration to gadflyda.zcml. Best Regards, -- Tahara Yusei [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Schema field interfaces
At Tue, 6 Sep 2005 09:03:47 -0400, Stephan Richter wrote: > We do not support mutable schemas at this point, since they are broken. The > biggest problem is that they are not correctly persisted. Oh, I see. Could you give me a pointer about this problem? and I'd like to know where is broken part of zope3, because I can't find it from unittest or issue collector. Thank you very much. -- TAHARA Yusei [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Schema field interfaces
Hi. I have used mutable schema and found a problem about schema interfaces. Many field interfaces does not override attributes (default, missing_value, etc..) that is provided by IField. Because these attributes are Field and there is no adapter from Field to IInputWidget, can not display action.html. I think all field interfaces should replace Field attribute to their own field class like IInt. -- Tahara Yusei [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
