From njc at bigpond.net.au  Tue Sep  4 05:18:49 2001
From: njc at bigpond.net.au (Nathan Callahan)
Date: Fri Feb 10 19:39:23 2006
Subject: [Pipet Users] Command line frontend
Message-ID: <200109040918.FAA14467@www.bioinformatics.org>

Hi,

Been following the lists for some time now, anxiously awaiting a new 
piper release so that I can try it out.

But anyway.  I came across a project some time ago (and then promptly 
lost), which may be of interest called Kaptain.  It is a general 
graphical wrapper for command line programs for KDE.

http://kaptain.sourceforge.net/

BTW I have tried to get the CVS versions working on a few occasions and 
always run into difficulty somewhere along the line... Didn't want to 
bother anyone, as, although I think piper is an incredibly interesting 
project, i don't have the time to really help at the moment, so I 
haven't been that excited about getting it working.

Regards,
	Nathan Callahan


From jeff at bioinformatics.org  Tue Sep  4 07:58:59 2001
From: jeff at bioinformatics.org (J.W. Bizzaro)
Date: Fri Feb 10 19:39:23 2006
Subject: [Pipet Users] Command line frontend
References: <200109040918.FAA14467@www.bioinformatics.org>
Message-ID: <3B94C203.AD76558C@bioinformatics.org>

Hi Nathan.  Thanks for the link.  I think there is a lot that we can glean
from Kaptain.

> BTW I have tried to get the CVS versions working on a few occasions and
> always run into difficulty somewhere along the line...

CVS versions haven't been working for a while.  The broker has been
extensively reworked by Jarl, and before we put it back into CVS (and call it
0.0.2), we're asking people on the list to test it out:

  http://bioinformatics.org/~jarl/piper-0.0.2-test1.tar.gz

So far, I've got one compiling problem, which may be due to my version of GCC
(C++ standards).

Cheers.
Jeff
-- 
J.W. Bizzaro                                jeff@bioinformatics.org
Director, Bioinformatics.org        http://bioinformatics.org/~jeff
"As we enjoy great advantages from the inventions of others, we
should be glad of an opportunity to serve others by any invention
of ours; and this we should do freely and generously."
                   -- Benjamin Franklin
--


From faassen at vet.uu.nl  Sun Sep  9 12:37:56 2001
From: faassen at vet.uu.nl (Martijn Faassen)
Date: Fri Feb 10 19:39:23 2006
Subject: [Pipet Users] Comments to Zope
In-Reply-To: <3B646D88.70800@xs4all.nl>
References: <3B5EBB1E.BCD4132B@bioinformatics.org> <0107251400450I.02438@fermi.eeel.nist.gov> <3B646D88.70800@xs4all.nl>
Message-ID: <20010909183756.A24368@vet.uu.nl>

Jarl van Katwijk wrote:
> I still have a hard time understanding the scope of Zope.

Hi there; long time Zope developer jumping in randomly.

Zope's scope is rather broad, so it depends on what you want to do. I'd
seem to me you'd be most interested in things like the ZODB and ZEO;
which are the object database and a way to transparently cluster one.
        
> I've been
> playing a bit with the web interface, and looked at some code. So far I
> understand Zope has a singel network consisting of Zope Objects. Or is
> there more going on, are there any other 'node type' in Zope, or
> hiarchic structures of some kind? Also I cant find how the functionality
> of the 'nodes' in Zope is arranged. Is it all done by the
> ExtensionClass? And what limit's are there in the functionality that can
> be plugged into the Zope objects?

Zope objects are basically just random Python object. They all must
derive from ExtensionClass (until some future version of Python, possibly
2.2 makes this go away), and Persistent. Frequently they use Acquisition
as well.

Persistent makes your object persistent. It's almost transparent, except
that you shouldn't modify mutable object attributes without modifying the
persistence machinery (you can do this simply by assigning it to itself
after changing it: self.mylist.append('foo'); self.mylist = self.mylist)

This is good stuff on the ZODB and how to program for it:

http://www.amk.ca/zodb/guide/

You can use the ZODB and ZEO separately from the rest of Zope.

> About the security model so far I got the impression Zope is handling
> access control by a very long and specific rules list, like in
> Zope-2.4.0-src/lib/python/AccessControl. The access system compared to
> that of Piper is way more detailed and differnent because it's 'node'
> oriented, and that of Piper being 'area' oriented. Has Zope an
> equivalent like groups? Also Piper does not manage the acccess between
> nodes in a singel execution zone. Can access control be disabled on
> induvidual node level?

You can disable access control for objects, yes. I'm not sure what you mean
by groups. There is a 'role' mechanism.

Regards,

Martijn