be a happy man.
Have a look at bebop.protocol in PyPI. It's still a preminary version but
it does exactly what you want.
Regards,
Uwe
Dr. Uwe Oestermeier
Institut für Wissensmedien
Knowledge Media Research Center
Konrad-Adenauer-Str
Dr. Uwe Oestermeier
Institut für Wissensmedien
Knowledge Media Research Center
Konrad-Adenauer-Str. 40
D-72072 Tuebingen
Germany
[EMAIL PROTECTED]
Tel. +49 7071 979-208
Fax +49 7071 979-100
___
Zope3-dev
need to consider trade-offs.
Regards,
Uwe
Dr. Uwe Oestermeier
Institut für Wissensmedien
Knowledge Media Research Center
Konrad-Adenauer-Str. 40
D-72072 Tuebingen
Germany
[EMAIL PROTECTED]
Tel. +49 7071 979-208
Fax +49 7071 979-100
call last):
File stdin, line 1, in ?
IOError: [Errno 2] No such file or directory: '/tmp/asdf'
:)
Why not rename the temp file to a place in the blob directory?
That would also avoid the copy operation.
Uwe
Dr. Uwe Oestermeier
()
d.write('Test')
d.flush()
os.rename(d.name, '/Users/uo/blobs/asdf')
open('/Users/uo/blobs/asdf').read()
'Test'
os.path.exists('/tmp/asdf')
False
Uwe
Dr. Uwe Oestermeier
Institut für Wissensmedien
Knowledge Media Research Center
opinion it makes
sense to leave the
Python API (independent of ZODB and locations etc.) in zope.fssync and the
web-based API
(with security and location aware pickler) in zope.app.fssync.
Regards,
Uwe
Dr. Uwe Oestermeier
Institut
Jim Fulton [EMAIL PROTECTED] wrote:
We need to either remove zope.app.fssync.file, or, if we think that
fssync is moving along well enough, we need to move
zope.app.ffile.fssync to a separate project in some namespace
package, such as zope.app.filefssync.
fssync is too experimental to
Jim Fulton [EMAIL PROTECTED] wrote:
Since you're the one working on this, I'll defer to you on this
detail. :)
Ok, then I will move the things to zope.app.fssync.
Uwe
Dr. Uwe Oestermeier
Institut für Wissensmedien
Knowledge
not been maintained.
Perhaps the maintenance can be made easier if we can change the code
without deprecation warnings. Nobody seems to have used fssync in the last
two years.
Regards,
Uwe
Dr. Uwe Oestermeier
Institut für Wissensmedien
Dr. Uwe Oestermeier
Institut für Wissensmedien
Knowledge Media Research Center
Konrad-Adenauer-Str. 40
D-72072 Tuebingen
Germany
[EMAIL PROTECTED]
Tel. +49 7071 979-208
Fax +49 7071 979-100
probably the best to use an existing tool
like Trac which is dedicated to the need of programmers.
Regards,
Uwe
Dr. Uwe Oestermeier
Institut für Wissensmedien
Knowledge Media Research Center
Konrad-Adenauer-Str. 40
D-72072 Tuebingen
Hi,
have a look at the rest2html function in
http://svn.zope.org/*checkout*/zope3org/trunk/src/zorg/restsupport/__init__.py?content-type=text
which uses the zope.app.renderer.rest module.
Regards,
Uwe
___
Zope3-dev mailing list
of each LivePage request.
Feel free to contact me if this looks interesting to you.
Regards,
Uwe
Dr. Uwe Oestermeier
Institut für Wissensmedien
Knowledge Media Research Center
Konrad-Adenauer-Str. 40
D-72072 Tuebingen
Germany
[EMAIL
comments demo app:
http://svn.zope.org/*checkout*/zope3org/trunk/src/zorg/live/demo/comment/README.txt
Unfortunately the documentation is far from complete, but I can work on it
if there is a concrete need.
-Uwe
Dr. Uwe Oestermeier
Florent Guillaume wrote:
I didn't follow Dominik's suggestion of using IModificationDescription
because I feel this a case sufficiently fundamental that we really
want a subclass.
I agree with Dominik that this justification is somewhat vague, but I
think that it really doesn't matter
Dr. Uwe Oestermeier
Institut für Wissensmedien
Knowledge Media Research Center
Konrad-Adenauer-Str. 40
D-72072 Tuebingen
Germany
[EMAIL PROTECTED]
Tel. +49 7071 979-208
Fax +49 7071 979-100
___
Zope3-dev mailing list
Hi,
Stefan Martin and I have written a proposal for a reimplementation of the
container views.
http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ConfigurableContainerViews
We would like to work on this at the NeckarSprint next week, so any
feedback is welcome.
Regards,
Uwe
Benji York wrote:
I'll be releasing some code today that does most of what this proposal
wants for any collection of objects, not specifically container views
(because you'll often want to represent tabular data that doesn't exist
in any particular container). It would fairly easy to build a
Philipp von Weitershausen wrote:
I smell a proposal :).
I cannot promise to write this proposal in the next two weeks, but I will
try to write one before the NeckarSprint (6-9. Oct) takes place. The
implementation of user objects would be a manageable sprint task.
-- Uwe
Tim Peters wrote:
Zope3 3.1's
bin/mkzeoinstance seems to work now,
I dedected another problem: bin/runzeo doesn't start ZEO.
This script calls ZEO/runzeo.py which has a main function but no
if __name__ == __main__ :
main()
at the end. Has this already been fixed in the mentioned internal
Hello,
today I downloaded the Zope-3.1.0c2 release candidate and played a little
bit with it.
I noticed that the bin/mkzeoinstance script is broken and returns
Traceback (most recent call last):
File ./mkzeoinstance, line 40, in ?
from ZEO.mkzeoinst import ZEOInstanceBuilder
I found no
/oestermeier/NeckarSprint
As a zope.org member you can edit the page with
http://www.zope.org/Members/oestermeier/NeckarSprint/editform
Please contact me, if you have questions or suggestions.
Hope to see you...
Uwe
Dr. Uwe Oestermeier
[EMAIL PROTECTED] wrote:
What is the missing event bug?
Currently no modification event is fired if one uploads new file content
via ZMI.
In a former mail I proposed to fire the event in File.setData,
alternatively it can be fired by the upload view.
Would this be for 3.2? Keep in mind that we
[EMAIL PROTECTED] wrote:
I'm 99% sure that this event model will not be sufficient for object
versioning.
Why?
Because there is no guarantee that all relevant modifications are
accompanied by events?
Because the events do not carry enough information?
I think these problems can be solved, but
[EMAIL PROTECTED] wrote:
Because there is no guarantee that all relevant modifications are
accompanied by events?
Right
But this problem is not unique to versioning. If you cannot rely on events
there is also no guarantee that your catalogs are always up to date.
Therefore I'm planning a
Ooops! I just saw that my previous posting on the other thread has become
obsolete to a large degree.
[EMAIL PROTECTED] wrote:
I suggest we generalize this a bit. I suggest that the ObjectModified
event could accept one or more modification descriptions (hints?).
Some examples:
Dieter Maurer wrote:
Sounds good, but I am nevertheless convinced that we
want finer grain control -- almost as fine (but probably with other
means) as the idxs argument to catalog_object (which controls
precisely which indexes should be reindexed). We will probably
replace the selection of
Garrett Smith wrote:
I think ValueChangedEvent would be a good addition to the forms
machinery. But if you need something like that now, I'd recommend using
your own edit view class.
That would be a solution for the moment, but in the future I would like to say that my
application provides
Garrett Smith wrote:
I'd see this being something like a ValueChangedEvent that specified the
object, schema, field name, old value, and new value. This would be a
nice way to bolt on validation without modifying the schema.
Yes, that's exactly what I need for versioning.
Anyone needing more
to generate an IObjectContentModifiedEvent in the File._setData method and
not the view classes?
Cheers,
Uwe
Dr. Uwe Oestermeier
Institut fr Wissensmedien
Knowledge Media Research Center
Konrad-Adenauer-Str. 40
D-72072 Tuebingen
l versionable
attributes in my application would become unnecessary. This would also make updates of
catalogs more efficient.
Regards
Uwe Oestermeier
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/a
31 matches
Mail list logo
