[Zope-dev] zIRCon is now IRCGate

2000-12-12 Thread Carlos Neves

Since Ty Sarna pointed out that there is another thingy out there labeled as
Zircon, I have changed the products name to the original project ID, IRCGate.

Yes, I know, I should have checked. (oops, I did it again ;) )

Thank you, Ty Sarna, and my apologies to anyone who already got zIRCon.

 -- 
"Kill processes, not people."
- Larry Cohen

Carlos Neves
[EMAIL PROTECTED]

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )




Re: [Zope-dev] Pending bugs in collector - how do I send this patch?

2000-12-12 Thread Martijn Pieters

On Mon, Dec 11, 2000 at 03:16:51PM -0500, Brad Clements wrote:
 I have found a bug in ZSQL methods that is describe by this collector 
 item:
 
 http://classic.zope.org:8080/Collector/718/view
 
 This item was posted over a year ago! The bug is still in the program, so 
 I'm guessing that DC folks are too busy to get to this.

Hi Brad,

That looks like a damn good catch! The best thing you can do is create a
new Collector entry and just say that this is a fix to collector item 718.
This way your fix will not be overlooked so easily.

-- 
Martijn Pieters
| Software Engineer  mailto:[EMAIL PROTECTED]
| Digital Creations  http://www.digicool.com/
| Creators of Zope   http://www.zope.org/
-

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )




[Zope-dev] Converters.py field2date() and :ignore_empty

2000-12-12 Thread Brad Clements

If I have ignore_empty set in a variable name of type date, field2date() 
fails if the returned value is truly empty.

I think field2date() should return None rather than trying to call DateTime 
with an empty string.

I keep making this patch to each Zope release, but would like to talk 
about a more permanant and "correct" solution. What do others think?



Brad Clements,[EMAIL PROTECTED]   (315)268-1000
http://www.murkworks.com  (315)268-9812 Fax
netmeeting: ils://ils.murkworks.com   AOL-IM: BKClements

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )




[Zope-dev] ZPatterns: persistant objects hold DataSkin-Items - KeyError: _v_dm_

2000-12-12 Thread Ulrich Eck

hi out there,

i use zpatterns/specialists for a Network-Documentation Tool.

I'm writing a Product which controls the relations between specialists
and manages multible actions (edit/new/delete) for ZPatterns DataSkinObjects
(DSO).

I have a Product-Instance of ZTWM (ZTransactionWorkflowManager) in my
application root which is a Folder by itself and holds as folder-objects its
'Transactions' (in this case a Transaction starts at the first edit-action
and lasts
til the last submit of a form with valid entries - e.g finish transaction.)

It behaves like a Wizard (PTK) with next/back/cancel/finish buttons and
reads
out the DataSkinPropertysheet for creating the edit/new forms on the fly.

One can also define relations between the specialists an they are used to
edit
Foreign Keys.

small painting here:

\application-root
--\Person(specialist for persons)
--\Komponent (specialist for komponents)
--\ZTWM(my TransactionWorkflowMangager - Folder)
 \1(first transaction -Folder)
---\1 (first transaction object - Folder)
| ds_object (attribute which references the DSO)
| more info on the current Transaction object
---\2 (second Transaction object)
| ds_object (attribute which references the DSO)
| more info on the current Transaction object
\2 (second Transaction)
...

so far about how it should work  ..

For each TransactionObject (TO) I save the Object I retrieved with
"specialist.getItem(id) == DataSkinObject(DSO)"
as attribute "ds_object" to the TransactionObject.

After I restarted Zope and want to replay/finish a transaction,

i get an KeyError, Value _v_dm_

the prefix _v_ stands for not pickeable (afaik)
dm for datamanager ?!?

ok .. i put a TO in the Transaction, get the actual DSO,
call the transactionmanagers editor function and a form with correct values
is displayed,
 i can  edit this form and call the DSO manage_changeProperties method from
the
transactionmanager.

when i don't finish a transaction and restart zope i still have my
transactions with proper
values saved in my TransactionManager - except the property "ds_object" wich
was assigned
to the DSO at TO-creation

when i try to set/get an attribute i get the KeyError of  "_v_dm " ...

I can deal arround that if i reget the DSO from the specialist in every
function which deals with DSO's.

is there a better way to

a) tell my TransactionManager that my attribute "ds_object" is not pickeable
(e.g. call it  _v_ds_object)
 and how to know if zope is restarted ?!?!?
or
b) store this object persistantly in my TO without showing it in the
folder-structure but behave like a DSO
 set/get attributes through Skinscripts

hope that i described clearly enough where my problem is ...

thanks for your reply

Ulrich Eck
net-labs


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )




[Zope-dev] Python 2 (Zope Unicode) support for 2.2.4

2000-12-12 Thread Steve Alexander

Hi Folks,

I've modified Toby Dickenson's patch to let Zope work with Python 2 so
that it patches against Zope 2.2.4.

  http://www.zope.org/Members/stevea/unicode_for_224.patch.gz


Toby's page about using unicode and Python 2 with Zope is here:

  http://www.zope.org/Members/htrd/wstring

--
Steve Alexander
Software Engineer
Cat-Box limited
http://www.cat-box.net

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )




[Zope-dev] [ZPatterns] DataSkin object ownership

2000-12-12 Thread BS

Do DataSkins have ownership? I want to give multiple users the ability to
add objects to a rack and only allow the 'owner' to view/edit the object.
When a user adds a DataSkin to a rack does he get ownership of the object?
I can't seem to get the ownership information for these objects. Is there a
way to do this?

BTW - I'm talking about virtual object that totally live in MySQL.

Thanks,
-Ben


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )




Re: [Zope-dev] [ZPatterns] DataSkin object ownership

2000-12-12 Thread Phillip J. Eby

At 08:04 PM 12/12/00 -0500, BS wrote:
Do DataSkins have ownership? I want to give multiple users the ability to
add objects to a rack and only allow the 'owner' to view/edit the object.
When a user adds a DataSkin to a rack does he get ownership of the object?
I can't seem to get the ownership information for these objects. Is there a
way to do this?

DataSkins stored in Racks do not participate in the Zope ownership
mechanism, nor the creation of the 'Owner' role.  This is because they are
not being stored via the normal ObjectManager protocols.  If you want this
behavior, you'll need to use Folders w/Customizer support, which let you
use most of DataSkins' dynamic features with "almost ordinary" Zope objects.

BTW - I'm talking about virtual object that totally live in MySQL.

Folders w/Customizer Support require the DataSkins' primary storage to be
in the ZODB.



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )