Benji York wrote:
Martin Aspeli wrote:
o In zope.testbrowser, [snip] having the ability to select nodes
by XPATH would be incredibly useful
Yep, I and others have thought the same thing.
I imagine an existing
library would be available to make this reasonably easy to implement?
With
Philipp von Weitershausen wrote:
Benji York wrote:
Martin Aspeli wrote:
o In zope.testbrowser, [snip] having the ability to select nodes
by XPATH would be incredibly useful
Yep, I and others have thought the same thing.
I imagine an existing
library would be available to make this
Benji York wrote:
Martin Aspeli wrote:
o In zope.testbrowser, [snip] having the ability to select nodes
by XPATH would be incredibly useful
Yep, I and others have thought the same thing.
I imagine an existing
library would be available to make this reasonably easy to implement?
With
Philipp von Weitershausen wrote:
Jim suggested a different strategy with Zope 5
(http://mail.zope.org/pipermail/zope3-dev/2006-February/018415.html).
The little bits and pieces that make up Zope 3 (the zope.* packages)
would be developed more or less independently of Zope-the-app-server
(which
--On 26. Juni 2006 11:25:05 +0100 Chris Withers [EMAIL PROTECTED]
wrote:
Philipp von Weitershausen wrote:
It's dead from a maintenance point of view. If you still want to
maintain it, be our guest. But you yourself said that maintaining too
many branches is madness.
My point is that
A small question/idea.
When making svn:externals in Nuxeo, we always use https. That way
trees can still be checked out anonymously, but still modified.
in Zope, threes are checked out with svn+ssh, but externals use svn.
That means that when you want to modify for example Five, you need to
Philipp von Weitershausen wrote:
Except that ElementTree doesn't really have XPath support nor an HTML
parser
Disappointing.
perhaps Zope 3 will ship with lxml at some point...
Perhaps Z3 will be egg-based at some point and we won't have to ship
dependencies.
--
Benji York
Senior
Chris Withers wrote:
Philipp von Weitershausen wrote:
Jim suggested a different strategy with Zope 5
(http://mail.zope.org/pipermail/zope3-dev/2006-February/018415.html).
The little bits and pieces that make up Zope 3 (the zope.* packages)
would be developed more or less independently of
Benji York wrote:
Perhaps Z3 will be egg-based at some point and we won't have to ship
dependencies.
+10. Having our own copies of docutils and pytz, for example, irritates
the heck out of me.
Philipp
___
Zope3-dev mailing list
Zope3-dev@zope.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
A small question/idea.
When making svn:externals in Nuxeo, we always use https. That way
trees can still be checked out anonymously, but still modified.
in Zope, threes are checked out with svn+ssh, but externals use
On 6/26/06, Tres Seaver [EMAIL PROTECTED] wrote:
- -1. The externals are just that, external to the Zope project.
Uhm. I have a hard time seeing Five and lib/python/zope as external to Zope.
When we get to an egg-based Zope install, I think such a gesture would
map onto check out the source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
On 6/26/06, Tres Seaver [EMAIL PROTECTED] wrote:
- -1. The externals are just that, external to the Zope project.
Uhm. I have a hard time seeing Five and lib/python/zope as external to
Zope.
They are managed as separate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dmitry Vasiliev wrote:
Benji York wrote:
Philipp von Weitershausen wrote:
Dmitry Vasiliev wrote:
Log message for revision 68818:
Fixed issue 525: DateWidget ru-format
- type=text value=2002-12-02 12:30:00 /
+ type=text
On Monday 26 June 2006 17:12, Tres Seaver wrote:
not onlyt that, but I don't believe that '2002 12 2 12:30:00' is a
valid date representation in *any* standard locale. The
dashes-with-leading-zeros should be the default (it is the stock ISO
date format).
This has nothing to do with an ISO.
On Jun 26, 2006, at 5:12 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dmitry Vasiliev wrote:
Benji York wrote:
...
Why does the display of the default DateTime widget change?
DatetimeWidget now use zope.i18n for parse and format values so the
display is the same
Hi,
I've got a situation where a form submit will eventually end up in an
action that does (in Zope 2):
context.REQUEST.RESPONSE.redirect('/path/to/foo/#bar')
This works fine through the web, but using zope.testbrowser, the # gets
converted to %23 (which is the correct urlencoding
On Monday 26 June 2006 19:29, Martin Aspeli wrote:
This works fine through the web, but using zope.testbrowser, the # gets
converted to %23 (which is the correct urlencoding of #). The url
/pat/to/foo/%23bar is not valid, and I get a 404.
I have experienced this error with our namespaces
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Hi,
I've got a situation where a form submit will eventually end up in an
action that does (in Zope 2):
context.REQUEST.RESPONSE.redirect('/path/to/foo/#bar')
This works fine through the web, but using
18 matches
Mail list logo