s, each one person bigger than the last.
You can use transactions and subtransactions to juggle database size,
memory usage, and temp file usage.
--
Karl Anderson [EMAIL PROTECTED] http://www.monkey.org/~kra/
___
Zope-Dev maillist - [EMAI
y
Bobo-Exception-Line: 57
Bobo-Exception-Type: Method Not Allowed
Bobo-Exception-Value: bobo exception
Connection: close
Content-Location: http://viii.dclxvi.org/blog/
Ms-Author-Via: DAV
X-Powered-By: Zope (www.zope.org), Python (www.python.org)
Cont
attributes on
"app.foo.PXML.firstChild()" and "app.foo.PXML.firstChild.parentNode()"
won't persist. Same goes if you traverse to these nodes via the
web-exposed URLs of these methods. Perhaps you're trying to persist
changes to Zope attributes on those nodes?
--
Ka
nd presumably well-known XML
query syntax, and which would work throughout the database because
Zope objects would support DOM.
This is all speculation, and I personally don't know much right now
about XML database interfaces and how finished or well-regarded they
are.
--
Karl Anderson
x27;},)
I added the dummy permission and action becuase the contents view
doesn't display without them.
This seems to work, and these meta types aren't displayed in the add
list for the container view (becuase I don't have the 'Dummy' perm),
which is what I want. But s
This turns out to be a memory leak in ParsedXML. DOM references
created during a parse aren't released.
We hope to have a new release very soon that fixes this.
Restarting Zope is a temporary workaround - DOM refs retrieved from
the DB aren't being leaked.
--
Kar
roblem is not ParsedXML but Zope itself or my bad methods.
Not necessarily - it's been mentioned that PyXML requires releasing
nodes after they're done, so I'd expect this if you replaced
ParsedXML's DOM with PyXML's without adding the release.
--
Karl Anderson
he GC, and you do seem to have DOM
objects lying around. I'd like to see your code, is it short enough
to post? Or you can chuck it into the collector or ParsedXML tracker.
For debugging purporses, I'd suggest simplifying by supplying an XML
string directly, rather than from an extern
ct (or if its nescessary). its hard to say since
> acquisition is being used to help with the dom tree.
Acquisition is what we're currently using to avoid circular
references.
--
Karl Anderson [EMAIL PROTECTED]
___
Zop
Godefroid Chapelle <[EMAIL PROTECTED]> writes:
> Karl Anderson a écrit :
> > Another thing to keep in mind is that the ParsedXML *product* is a DOM
> > tree and a management interface around it. The management interface
> > only gives you a convenient UI and a pla
able to just
instantiate a management wrapper when I want a management interface,
and then just throw it away, without bothering to add it to a folder.
--
Karl Anderson [EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTE
date the
spam and eggs fields of everyting in a subtree every friday, an XML
parser and/or DOM tree and/or transform working on a single XML
representation of the subtree checked out to the local filesystem
seems like the easiest entry point.
I'm probably straying from the proposal here.
uman-editable text formats sounds like StructuredText; when I
think of StructuredText I think "simple DOM serialization".
Is there a particular set of tools or editing paradigms that we have
in mind when we say that a non-XML representation is suited for client
side tools?
This is the way tha
rmat, query,
and manipulate XML.
Parsed XML consists of a DOM storage, a builder that uses PyExpat to
parse XML into the DOM, and a management proxy product that provides
Zope management features for a DOM tree.
--
Karl Anderson [EMAI
g.
There's a similar project called psilib that was discussed in xml.com:
<http://www.xml.com/pub/a/2000/03/22/psi/index.html>
--
Karl Anderson [EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECT
(self, i):
return self.__getattr__("__getitem__")(i)
--
Karl Anderson [EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross pos
The Parsed XML project is now public and ready for input. Parsed XML
is the successor to XMLDocument. We have a wiki at
<http://www.zope.org/Wikis/DevSite/Projects/ParsedXML>.
[EMAIL PROTECTED] is also a good place for discussion at this time.
--
Karl Anderson
7;. Which
isn't that bad, really.
What I really want is for the different fora to just be interfaces on
the information. I'm not sure how, it isn't that realistic, I can't
think of an implementation without it getting overfeatured. Something
like wiki edits being reflected i
/DailyChurn/> -
it's generated by scanning their IRC channel.
--
Karl Anderson [EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML en
rec.bicycles.soc - when the article count gets to 200-300, I read the
2-10 articles that I'm probably interested in, and miss the 95% which
is almost always noise.
That's why I resist moving to other fora. I've never seen one that
lets me use better tools.
Okay, my download finish
ral for using non-Zopish
subobjects that get used by the publishing process?
--
Karl Anderson [EMAIL PROTECTED] http://www.pobox.com/~kra/
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
27;t think it is a good desing from the perspective of OOP
I had some hassles with this recently. There's a HOWTO at:
http://www.zope.org/Members/gtk/containers
Can you create the child zclass from the manage screen inside the
parent zclass?
Does the parent zclass inherit from
22 matches
Mail list logo
