I've come across an itch. I'm tired of having to go through the mailing
archives to find what i need. The search interface at egroups, is a bit
slow and cumbersome. The one at ntlpd is much nicer, but i'd like to
have my own so i can point an archiver/search interface at any mailman
mailing list.
I was reading over on linuxworld about some of Nick's complaints against
zope. one of them was the lack of ZClasses being able to autogenerate
forms for their property sheets. i wrote up some dtml methods which do
just that, see
http://lists.zope.org/pipermail/zope/2000-July/029325.html
(i woul
Speaking of the calendar tag, which I'm very grateful for.
I noticed that changing the mode setting in one browser was seen in all
others.
calendar.py
line ~323:
def render(self, md):
self.mode = 'month'
Forcing the mode to month seems to work. The view will be month unless the
url c
Here is a small patch to make the lovely calendar tag play nice with
DT_Util.namespace() in Zope 2.2:
$ diff -c lib/python/Products/Calendar/CalendarTag.py \
lib/python/Products/Calendar/CalendarTag.py.org
*** lib/python/Products/Calendar/CalendarTag.py Sun Jul 16 21:39:27 2000
--- lib/pyth
Dieter Maurer wrote:
> I saw this only when buggy HTML was generated.
> When I viewed the HTML source my Netscape browser sometimes
> showed me blinking parts that located the errors.
Nope, this was with IE...
I viewed source and sure enough, it ended after a few lines.
I guess it might have so
Chris Withers writes:
> I'm still debugging and writing the navtree code I've mentioned before
> and I've noticed that not infrequently, when rendering a page that
> causes and error, I get a half rendered page rather than a nice Zope
> error page.
>
> This is a bit waffly to put into the c
Hello,
I've reviewed the introduction to the fishbowl process
and its description of creating a project proposal wiki
document and such, and the full process a project should
take. However, I have 2 very small but useful additions
to Zope I wish to make. Both additions are already av
I've put together an alternative, pared down approach to doing python
debugging inside emacs - pdbtrack:
http://www.zope.org/Wikis/klm/PDBTrack
Once loaded, pdbtrack watches your (comint) process interaction
buffers for the pdb stacktrace. When it sees it, and can find the
file containing the
