Jeff Shell wrote:
I agree that better integration with external data should be a
priority for Zope. But what does that mean? In theory, if something's
a Python object it should work with Zope 3 with relative ease... If
that's not the case, perhaps we need to look at how much work is
required to
On 2/16/06, Shane Hathaway [EMAIL PROTECTED] wrote:
Jeff Shell wrote:
I agree that better integration with external data should be a
priority for Zope. But what does that mean? In theory, if something's
a Python object it should work with Zope 3 with relative ease... If
that's not the
Jeff Shell wrote:
Am I the only person who uses apidoc to look up what can be done with
ZCML? Because honestly, finding out what directives are available and
getting decent documentation about ZCML directives is the easiest
thing in Zope 3. Understanding what's going on or what the real
Philipp von Weitershausen wrote:
Chris Withers wrote:
[aside... hmmm, crossposting, maybe time to merge zope-dev and
zope3-dev? most stuff seems to be relevent to both nowadays]
+10
You know, I once had a proposal. Uh, never mind :)
Well, what needs to happen for it to be done?
To be
Benji York wrote:
Chris Withers wrote:
maybe time to merge zope-dev and zope3-dev?
-1
They're still different enough that most traffic on one is not
interesting to the majority of subscribers to the other.
Can you explain what lead you to this conclusion?
It seems to be the complete
I have made my own i keyword index, it works fine when only querying it
but if I query an other index in the same query I get an error.
MyKeywordIndex.apply() returns what
zope.index.keyword.KeywordIndex.search() returns
this is the values that cause the error:
[(3, BTrees._IFBTree.IFBucket([(1,
On Feb 15, 2006, at 11:52 PM, Jeff Shell wrote:
A Zope that was basically zope.publisher, zope.component,
zope.interface, zope.schema, and tal/tales (and maybe 'transaction')
would be ideal.
+1
I guess this is all kindof rambling. I just don't see any benefit to
me. I'd rather see any
Gary Poster wrote:
What if we still deprecated browser:layer but
kept a redefined version of browser:skin? Then your zcml--
interface
interface=.interfaces.ShanghaiSkin
type=zope.publisher.interfaces.browser.IBrowserSkinType
/
utility
On Feb 16, 2006, at 6:49 AM, Sasha Vincic wrote:
I have made my own i keyword index, it works fine when only
querying it
but if I query an other index in the same query I get an error.
MyKeywordIndex.apply() returns what
zope.index.keyword.KeywordIndex.search() returns
this is the values
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shane Hathaway wrote:
Jeff Shell wrote:
I agree that better integration with external data should be a
priority for Zope. But what does that mean? In theory, if something's
a Python object it should work with Zope 3 with relative ease... If
Gary Poster wrote:
On Feb 16, 2006, at 12:09 AM, Philipp von Weitershausen wrote:
[...interface... change counter-counter-proposal...]
I think that's a very nice improvement over the previous spellings. I
had to review the zope.app.component.interface.provideInterface code,
but yes, it
On Feb 16, 2006, at 10:52 AM, Benji York wrote:
One downside to the expanded interface directive is that it hides
the fact that a utility is also being created. I actually prefer
the browser:skin version because it totally hides the underlying
atomic operations, but the
Gary Poster wrote:
On Feb 16, 2006, at 10:52 AM, Benji York wrote:
One downside to the expanded interface directive is that it hides the
fact that a utility is also being created. I actually prefer the
browser:skin version because it totally hides the underlying atomic
operations, but
Jeff Shell wrote:
I thought this uniformity of a development model was the Zope 3
message. Am I wrong?
Yes, you're wrong. To create the home page, web developers are directed
to put a page template in ZODB. This is completely different from what
you do. What should they do instead? I
On Thu, Feb 16, 2006 at 02:16:05AM -0700, Jeff Shell wrote:
I think that Zope 2 suffered heavily from the too many ways to do it
when it came to ways of doing development, and there were gulfs
between each style. Each style had its plusses too. ZClasses certainly
had an appreciative audience
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2006-02-13 I wrote a mail to Zope3-User (factory - but object is not
initialized)
for a content component I have programmed a factory to be sure numeric
fields have 0.0. If I add an object without numeric values the
introspectors tells me these
On Thu, Feb 16, 2006 at 01:19:38AM -0700, Jeff Shell wrote:
Am I the only person who uses apidoc to look up what can be done with
ZCML?
I dunno if it's just me, but http://localhost:8080/++apidoc++
is 404 on a fresh 3.2 instance.
Aside from that, I noticed that the help popup in the ZMI
On Thu, Feb 16, 2006 at 12:31:46PM -0500, Paul Winkler wrote:
On Thu, Feb 16, 2006 at 01:19:38AM -0700, Jeff Shell wrote:
Am I the only person who uses apidoc to look up what can be done with
ZCML?
I dunno if it's just me, but http://localhost:8080/++apidoc++
is 404 on a fresh 3.2
Hi!
there is a bug in TAL interpreter (zope2.8 / zope2.9), the following markup
div tal:attributes=a python:'é'; b python:u'é'.../div
(which mixes unicode- and non unicode-encoded attributes) generates an
exception::
result = self.pt_render(extra_context=bound_names)
File
Jean-Marc Orliaguet wrote:
Martijn Faassen wrote:
[snip]
It had unit tests, and the regex stuff that I was referring to may be
interesting - it ports the regexes from Zope's TALES to Javascript so
that the parsing of tales expressions works the same.
This is the module that has the regex
Martijn Faassen wrote:
I don't think it has an implementation of string TALES expressions.
It's parsing anything that's actually *inside* the attributes you add
on HTML with tal, such as detecting whether a TALES expression type
identifier is used ('string:' or 'python:', say), or
I am new to Zope3, but I have background knowledge in J2EE.
So, I would like to know the forms of communication between distributed
components or distributed components and clients. As far as I know, Zope
focusses on HTML communication, also allowing XML-RPC calls to
components. But is this
On Thu, Feb 16, 2006 at 07:06:03PM +0100, Jean-Marc Orliaguet wrote:
Yes, that's what I mean. Clearsilver is a good example. There are
several advantages:
- the data structures are platform-independent (they can be encoded in
JSON, C, python), and they can be easily converted from one
Paul Winkler wrote:
On Thu, Feb 16, 2006 at 07:06:03PM +0100, Jean-Marc Orliaguet wrote:
Yes, that's what I mean. Clearsilver is a good example. There are
several advantages:
- the data structures are platform-independent (they can be encoded in
JSON, C, python), and they can be easily
Chris McDonough wrote:
On Feb 15, 2006, at 11:52 PM, Jeff Shell wrote:
A Zope that was basically zope.publisher, zope.component,
zope.interface, zope.schema, and tal/tales (and maybe 'transaction')
would be ideal.
+1
I guess this is all kindof rambling. I just don't see any benefit to
me.
On Thu, Feb 16, 2006 at 08:05:56PM +0100, Jean-Marc Orliaguet wrote:
I think that the principles stated in that article, of clean separation
between model and view (called encapsulation) are more important than
the template's actual syntax. But the syntax is important too since
it's humans
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: The web-page 'force build' button was pressed by '':
Build Source Stamp: None
Blamelist:
BUILD FAILED: failed failed slave lost
sincerely,
-The
[EMAIL PROTECTED] wrote:
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Windows 2000
zc-bbwin.
This was apparently caused by the machine/process being restarted or
loosing network access. I'll restart the test.
--
Benji York
Senior Software Engineer
Zope Corporation
So my plea is: If we're going to have more than one way to do it,
let's please not invent lots of special magical things that
just work in one mode of development and have to be laboriously
rewritten in the other mode of development. It makes the border
between modes of working too hard to
Fred Drake wrote:
I would prefer not. We've used resourceDirectory to support things
like webcams. The image(s) uploaded by the cams might not always be
there, but the containing path is. It's nice not having Zope start
Good point.
If it was sugar for a set of resource directives, this
It seems to me that some of the tension around zcml arises because, on
the one hand, everyone wants it to be as simple as possible, and on the
other, too much simplicity of the language makes some things very
tedious, which encourages magic shortcuts via new directives.
To let out some of the
On Fri, Feb 17, 2006 at 01:17:22AM +0100, Philipp von Weitershausen wrote:
Either way, resource definitions are not quite the goal of my proposal
so I'll leave it out of there. Perhaps Paul or whoever has the need for
it would like to implement a resourcesFromDirectory directive...
I'll see if
One thing I havent got my mind around yet:
I notice that zodb is fairly
active about calling __getstate__ and __setstate__.
When a container gets pickled to be put into zodb, what happens to the subtree? Is it just left as a big
clump of stuff for the garbage collector to deal with?
On 2/16/06, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
Either way, resource definitions are not quite the goal of my proposal
so I'll leave it out of there. Perhaps Paul or whoever has the need for
it would like to implement a resourcesFromDirectory directive...
Right; this should
Ok everyone: it is a zope bug.
The following should be included in zope.app.schema.fields.zcml:
content class=zope.schema.Date
factory
id=zope.schema.Date
title=Date Field
description=Date Field /
require like_class=zope.schema.Orderable /
require
Benji York wrote:
One downside to the expanded interface directive is that it hides the
fact that a utility is also being created. I actually prefer the
browser:skin version because it totally hides the underlying atomic
operations, but the interface-also-registers-a-utility version
36 matches
Mail list logo
