[Michael Bernstein]
| We seem to have disposed of the wildcard issue [snipped out
| below], and I'm looking forward to Eric's results, but does
| anyone else have any information about whether there is a
| practical upper limit on how many objects can be indexed and
| searched in a ZCatalog?
I
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
The dtml-in batching mechanisms are quite difficult to debug - the DTML
documentation I have has examples which break it and there's no indication
of why. It turns out the DT_In renderwb() code gobbles all exceptions from
the rendering
[Chris Withers]
| ...and is that specifically for BTree folders, or Zope BTree's in general?
I don't believe that B-Tree folders have those kinds of limitations by
general design. I'm more conserned that somewhere along the lines,
doing operations on a huge BTree Folder (Yes, in Zope) will be
Casey Duncan wrote:
If not, I will make a patch for DT_String to support this. The
beneficial side affect would be that dtml-comment could be "fixed" so
that its contents need not be parsable anymore, just like every other
language I know of.
With your patch applied, will nested
Hi Itai,
I'm sure there's something clever you could do here with
an attribute provider for you user object that supplied
__roles__ dynamically somehow, but I'd need to think
about that more... one easy way to limit who can
see different stuff is to use a wrapper around
your access methods
Steve Spicklemire wrote:
WITH [ QUERY ] LookupAttributesAndCheckForPermission(REQUEST) COMPUTE foo, bar, baz
where LookupAttributesAndCheckForPermission get's everything it needs out of
the REQUEST.
You could use
WITH CheckForPermission(REQUEST) and makeQuery() COMPUTE foo, bar, baz
Not sur ecompletely why yet, but in 2.3b2, I can't move or copy a
ZCatalog. There is one in the Membership interface, so as a result, no
workie there.
After deleteing int from teh membership interface folder, I get a
traceback complaining about too many arguments in checkRoles (3
Steve Alexander wrote:
With your patch applied, will nested dtml-comment tags still work?
dtml-comment
Some code commented out
dtml-comment
Documentation in a comment
/dtml-comment
Rest of code commented out
/dtml-comment
--
Steve Alexander
Software Engineer
Erik Enge wrote:
[Chris Withers]
| ...and is that specifically for BTree folders, or Zope BTree's in general?
I don't believe that B-Tree folders have those kinds of limitations by
general design. I'm more conserned that somewhere along the lines,
doing operations on a huge BTree
[Michael Bernstein]
| Erik Enge wrote:
|
| I don't believe that B-Tree folders have those kinds of limitations by
| general design. I'm more conserned that somewhere along the lines,
| doing operations on a huge BTree Folder (Yes, in Zope) will be slow.
|
| What sort of 'operations' do
Casey Duncan wrote:
Steve Alexander wrote:
With your patch applied, will nested dtml-comment tags still work?
dtml-comment
Some code commented out
dtml-comment
Documentation in a comment
/dtml-comment
Rest of code commented out
/dtml-comment
--
Tres Seaver wrote:
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
The dtml-in batching mechanisms are quite difficult to debug - the DTML
documentation I have has examples which break it and there's no indication
of why. It turns out the DT_In renderwb() code gobbles all
The module below works using the python compiler
class Testclass:
def setdata(self,val1,val2,val3):
self.data = [val1,val2,val3]
def updatedata(self, index):
self.data[index] = self.data[index]+1
def display(self):
print self.data
x = Testclass()
def
On Wed, 24 Jan 2001 [EMAIL PROTECTED] wrote:
Tres Seaver wrote:
Please post this as a "Bug w/ patch" to the Collector:
http://classic.zope.org:8080/Collector
That way we don't lose your fix in the list traffic (losing it
along with our marbles is another problem :)
Someone
Espen,
The files that external methods actually live in are not Python modules,
like normal Python modules. Though I haven't tried your example, it's
likely that your reference to __main__ is confusing the external method
machinery. Additionally, the output of "print" doesn't go to the remote
Ooops, replace "print self.data" with "return self.data" in the display
method of my Testclass.
- Original Message -
From: "Chris McDonough" [EMAIL PROTECTED]
To: "Espen Sorbye Frederiksen" [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, January 23, 2001 6:46 PM
Subject: Re:
[EMAIL PROTECTED] writes:
That (or rather Image.File) was where I started. I decided to go with
HTMLFile as a basis so we could have some DTML in the CSS file - but
overrode it so we weren't forced to have the .dtml extension (much happier
web designers that way :)
Thus, the only thing,
On 24 Jan 2001, at 9:43, [EMAIL PROTECTED] wrote:
Tres Seaver wrote:
Please post this as a "Bug w/ patch" to the Collector:
http://classic.zope.org:8080/Collector
That way we don't lose your fix in the list traffic (losing it
along with our marbles is another problem :)
Brad Clements wrote:
On 24 Jan 2001, at 9:43, [EMAIL PROTECTED] wrote:
Tres Seaver wrote:
Please post this as a "Bug w/ patch" to the Collector:
http://classic.zope.org:8080/Collector
That way we don't lose your fix in the list traffic (losing it
along with our marbles is
Dieter Maurer wrote:
[EMAIL PROTECTED] writes:
That (or rather Image.File) was where I started. I decided to go with
HTMLFile as a basis so we could have some DTML in the CSS file - but
overrode it so we weren't forced to have the .dtml extension (much happier
web designers that
On 24 Jan 2001, at 11:15, [EMAIL PROTECTED] wrote:
Brad Clements wrote:
I posted this same bug AND a patch as bug # 1566 on Aug 28th, 2000.
http://classic.zope.org:8080/Collector/1566/view
Sad to see its *still* pending
Well that's odd - I searched the collector for "dtml-in"
Im hacking around IEMethod and it uses an old style of class initialisation
in the __init__.py along the lines of:
misc_ = { 'imagef':'foo','imageg':'goo', }
lang_= { 'en':'lang_en','sv':'lang_sv', }
I want to put this into a modern style product initialisation
(context.registerClass).
Casey Duncan wrote:
OK, I have developed a new patch that almost completely fixes this
issue. In fact I am happier with it in general than my first patch.
There is only one flaw, although you can nest comments inside of one
another, and you can have any manner of broken dtml inside, if you
23 matches
Mail list logo
