On Thu, 2006-01-26 at 14:53 +0100, Stefane Fermigier wrote:
I have made a little update on the Zope article on Wikipedia:
http://en.wikipedia.org/wiki/Zope
Great!
Here is the diff:
http://en.wikipedia.org/w/index.php?title=Zopediff=36787848oldid=36094466
It would probably be very
Hi,
is there a chance we can get rid of the Refresh button on the standard
forms? Every now and then, I hit the wrong one. And I do not see a clear
need for the refresh.
Christian
--
gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany
www.gocept.com - [EMAIL PROTECTED] -
Christian Theune wrote:
On Fri, 2006-01-27 at 09:33 +0100, Michael Haubenwallner wrote:
'Refresh' should be called 'Reset' -- in fact resetting the form
contents to the original loaded values
('Reset' is also the buttons default value displayed in the browser)
Well. That's not what the
Hi,
On Fri, 2006-01-27 at 09:39 +0100, Michael Haubenwallner wrote:
Christian Theune wrote:
On Fri, 2006-01-27 at 09:33 +0100, Michael Haubenwallner wrote:
'Refresh' should be called 'Reset' -- in fact resetting the form
contents to the original loaded values
('Reset' is also the
Hi,
(this is about zope.schema)
I assumed that the fields Bytes and ASCII have some distinction. The
ASCII field explicitly checks for every character to have an ordinal
value lower than 127.
Bytes however does a cast in fromUnicode(u) that does str(u). This will
break if there are non-ascii
Dieter Maurer wrote:
Stephan Richter wrote at 2006-1-26 10:16 -0500:
but ZCML meta directives and
schemas are so easy to use.
I do not yet know ZCML...
In my experience it is indeed fairly easy to extend ZCML; it's a pretty
nice system that way.
When I have read your book I was scared
Christian Theune wrote:
Hi,
is there a chance we can get rid of the Refresh button on the standard
forms? Every now and then, I hit the wrong one. And I do not see a clear
need for the refresh.
+1 on getting rid of the refresh button.
What others say about reset (refresh?) buttons:
On Fri, 27 Jan 2006 00:39:41 -0800, Michael Haubenwallner [EMAIL PROTECTED]
wrote:
Christian Theune wrote:
On Fri, 2006-01-27 at 09:33 +0100, Michael Haubenwallner wrote:
'Refresh' should be called 'Reset' -- in fact resetting the form
contents to the original loaded values
('Reset' is
Jim Fulton wrote:
Also, on a related note, I've been somewhat impressed lately
with the way people have been able to twist ConfigParser beyond
its apparent capabilities in both Paste Deploy and in our prototype
buildout system. In particular, we've been able to create hierarchical
sections by
Obviously I'm blind. I found the __traceback_info__ code a few lines
down.
Obviously they are used for slightly different things.
Obviously I'm going to investigate again, why the __traceback_info__
elements don't appear.
Mea culpa,
Christian
--
gocept gmbh co. kg - forsterstraße 29 - 06112
On Jan 27, 2006, at 5:16 AM, Christian Theune wrote:
Hi,
(this is about zope.schema)
I assumed that the fields Bytes and ASCII have some distinction. The
ASCII field explicitly checks for every character to have an ordinal
value lower than 127.
Bytes however does a cast in fromUnicode(u)
On Fri, 2006-01-27 at 18:46 -0200, Sidnei da Silva wrote:
On Fri, Jan 27, 2006 at 09:37:03PM +0100, Christian Theune wrote:
| Is it intentional that there is a distinction? It took me quite a while
| to actually notice that minore difference and come to the conclusion
| that there are two
Local grants (i. e. roles/permissions granted to local users of a
site) don't work properly for objects with objects fields (i. e. when
trying to acces objects that have somefield=Object(...) entries in
their interface definition).
I have provided a short description of the problem below and have
Hi,
On Fri, 2006-01-27 at 20:34 +0100, Christian Theune wrote:
Obviously I'm blind. I found the __traceback_info__ code a few lines
down.
Obviously they are used for slightly different things.
Obviously I'm going to investigate again, why the __traceback_info__
elements don't appear.
I
On Fri, 27 Jan 2006 14:58:02 -, Alexander Limi [EMAIL PROTECTED] wrote:
Please don't include the Reset functionality in HTML forms. It is
absolutely useless, and is considered one of the classic usability
mistakes. Just say no, kids!
Agreed. Hands up anyone who ever clicked one?
On Fri, 2006-01-27 at 20:47 +, Martin Aspeli wrote:
On Fri, 27 Jan 2006 14:58:02 -, Alexander Limi [EMAIL PROTECTED] wrote:
Please don't include the Reset functionality in HTML forms. It is
absolutely useless, and is considered one of the classic usability
mistakes. Just say
Martijn Faassen wrote at 2006-1-27 13:21 +0100:
...
Five actually adds a 'five' namespace, which I think is very useful --
it clearly marks which directives are only there for Zope 2 and thus you
cannot expect them to work in Zope 3. Not having namespaces would make
this a lot harder to mark,
Hi Christian,
[...]
I'd love to know if there is a strong feeling towards those
blue-background-titles.
See the proposed changes attached as a patch to
zope/app/rotterdam/zope3_tablelayout.css.
Regards,
Christian
btw,
do you know that there is a /++skin++Boston/ skin?
Regards
Roger
On 1/27/06, Christian Theune [EMAIL PROTECTED] wrote:
I did. That's why I'm posting. I had to go through that form again. :)
Even worse, those are the first submit button for many pages, so
that's what gets submitted when you hit Enter. That's even easier
to do than clicking the button itself.
Christian Theune wrote:
Hi,
somehow there is a mixup between using __traceback_supplement__ and
__traceback_info__.
In Zope 2, I'm used to use __traceback_info__. In Zope 3 it seems like
the exception formatters use __traceback_supplement__. However, quite
some code in Zope 3.2 uses
20 matches
Mail list logo
