Re: [Zope3-dev] RE: Zope3-dev Digest, Vol 28, Issue 41

2005-11-24 Thread Paul Winkler
On Thu, Nov 24, 2005 at 12:01:58PM +0100, Fabrice Monaco wrote:
> Hi,
> 
> I saw a new architectur of Zope 3, In Zope 3 integrate concept of adapter. I
> think that is good idea, but I think that concept is false beacause in
> python language don't support the class "interface", is necessary for
> respect the Design Pattern. Do you think who would be better to do to evolve
> language python for support the class "interface" also java?

I think you're missing a big point - namely, zope.interfaces and the
extensive usage of it throughout zope 3.

There have been proposals to add interfaces to the Python core,
but nothing has been decided yet. See for example
http://python.org/peps/pep-0245.html
which is getting a bit old (it predates zope 3).

Other projects are using zope.interfaces, too - 
at least Twisted is.

-- 

Paul Winkler
http://www.slinkp.com
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



[Zope3-dev] RE: Zope3-dev Digest, Vol 28, Issue 41

2005-11-24 Thread Fabrice Monaco
Hi,

I saw a new architectur of Zope 3, In Zope 3 integrate concept of adapter. I
think that is good idea, but I think that concept is false beacause in
python language don't support the class "interface", is necessary for
respect the Design Pattern. Do you think who would be better to do to evolve
language python for support the class "interface" also java?

best regards,
Fabrice Monaco

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: jeudi 24 novembre 2005 11:21
To: zope3-dev@zope.org
Subject: Zope3-dev Digest, Vol 28, Issue 41


Send Zope3-dev mailing list submissions to
zope3-dev@zope.org

To subscribe or unsubscribe via the World Wide Web, visit
http://mail.zope.org/mailman/listinfo/zope3-dev
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]

You can reach the person managing the list at
[EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Zope3-dev digest..."


Today's Topics:

   1. RE: RFC: Reunite Zope 2 and Zope 3 in the source
  coderepository (Roger Ineichen)
   2. Re: Retaining ease of customisation (Jean-Marc Orliaguet)
   3. RE: RFC: Reunite Zope 2 and Zope 3 in the source
  coderepository (Roger Ineichen)
   4. RE: RFC: Reunite Zope 2 and Zope 3 in the source
  coderepository (Philipp von Weitershausen)
   5. Re: [Zope-dev] Re: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3
  inthe source code repository (Philipp von Weitershausen)
   6. RE: RFC: Reunite Zope 2 and Zope 3 in the source
  coderepository (Philipp von Weitershausen)
   7. RE: RFC: Reunite Zope 2 and Zope 3 in the
  sourcecoderepository (Roger Ineichen)
   8. Re: RFC: Reunite Zope 2 and Zope 3 in the source code
  repository (Martijn Faassen)


--

Message: 1
Date: Thu, 24 Nov 2005 09:57:42 +0100
From: "Roger Ineichen" <[EMAIL PROTECTED]>
Subject: RE: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3 in the source
coderepository
To: "'Philipp von Weitershausen'" <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>
Cc: 'Dominik Huber' <[EMAIL PROTECTED]>, zope3-dev@zope.org,
zope-dev@zope.org
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain;   charset="us-ascii"

Hi Philipp

[...]
> Stephan Richter wrote:
> > I totally disagree. I, as a Zope 3 developer, have to learn
> Zope 2 and Five.
>
> What makes you think so? I, for one, have not the slightest
> clue of how zope.wfmc works.
> Still I'm able to contribute to Zope 3, am I not? If I
> refactor something, I might even
> have to touch zope.wfmc, but for the most part this could be
> very superficial.

That's not true. E.g. if you register interfaces with bad
docstrings, you will break the zope.app.apidoc package functional
tests or other wrong registrations will fail in broken links etc.

I think it's not that easy and functional tests will become a
hard part to maintain in the future if we mix both framework.

> And if
> not, I have some trusty community members who can help me on a branch.

That's excatly what we don't whant. We are not able to develope
and ask others for fixes. This whon't work.

Btw, what's next.
Do we have to merge CMF, Plone and CPS also into the core
only because other whon't be able to develop with otherwise.

Common, if somebody is not able to install Zope3, Zope2 and Five,
I dont' think he will be able to help. I'm really afraid about the
idea if a merge will be the part where developer bring to the Zope3
core development.

Btw, I can't here reasons like that. Every half year there is another
reason what we should do for Zope2 developer so that they will
contribute more. I think you don't speak for all of them and belive that
a good skilled developer is able to get ver easy into the Zope3 development.

Do you really think it's easier for Zope2 developer to get into Zope3
only because the code lives in the same repsoitory. You draw the
picture a little bit to easy. I think if somebody will become a Zope3
developer he has to learn the totly new framework first. And not only
download the code.

Regards
Roger Ineichen


> It's been this way for years now, there's no compelling
> reason why it should change.
>
> Philipp
>
>
> 
> This message was sent using IMP, the Internet Messaging Program.
> ___
> Zope3-dev mailing list
> Zope3-dev@zope.org
> Unsub:
> http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch
>
>



--

Message: 2
Date: Thu, 24 Nov 2005 09:48:43 +0100
From: Jean-Marc Orliaguet <[EMAIL PROTECTED]>
Subject: Re: [Zope3-dev] Retaining ease of customisation
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
zope3-dev@zope.org, [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-T