Hi all,
I'm doing a project of CMS with Zope and Plone. I'd like to understand clearly the architecture of Zope but I think that's a hard work for me. It will much easier if I have the documentation about how did Zope corporation design it, the modeling with UML of Zope, Structural Diagrams,
On Apr 4, 2005, at 15:22, Chris Withers wrote:
Sidnei da Silva wrote:
Look for CMFSetupExtensions on the collective.
Why am I not suprised...
Why couldn't this just have been fed into the real CMFSetup?!
+1 for extending CMFSetup instead of functionality in all kinds of
strange places.
Oh well, I
[EMAIL PROTECTED] wrote at 2005-4-4 11:37 -0400:
> ...
>As I think I'd mentionned, I get the Zope default home home page (Welcome to
>Zope, etc ...), but with a big warning at the top telling me that I don't
>have an administrative user setup and so on ... Which is obviously not true
>:)
Fine. But
Sidnei da Silva wrote:
| Good question ;)
|
[...]
Sorry, I meant instead of the try: except, just import from
Products.CMFCore.tests.utils as there's another try:except in there.
Also a good question ;)
1.) I just want to add the except part to utils, not the try/except
2.) I prefer to see the c
| Good question ;)
|
| All I know is that
|
| - CMF uses that pattern in all test files
|
| - 'Products.CMFCore.foo' seems to work with any testing setup
|
| - with my setup 'CMFCore.foo' doesn't work if I run tests outside test.py
Sorry, I meant instead of the try: except, just import from
Pr
Florent Guillaume wrote:
CMFSetup.utils.ConfiguratorBase seems to be used as a single base class
for both import configurators and export configurators. But it seems to
me that the methods are either for import or for export, never both. I'd
like to split it in two classes.
There are only config
Sidnei da Silva wrote:
| 2.) adding BBBTransaction to CMFCore.tests.base.utils and using this in
| tests:
|
| try:
| import transaction
| except ImportError:
| # BBB: for Zope 2.7
| from Products.CMFCore.tests.base.utils import transaction
Why not just import from CMFCore.test.base.u
Hi,
CMFSetup.utils.ConfiguratorBase seems to be used as a single base class
for both import configurators and export configurators. But it seems to
me that the methods are either for import or for export, never both. I'd
like to split it in two classes.
Comments?
Florent
--
Florent Guillaume, N
Hi Florent!
Florent Guillaume wrote:
yuppie <[EMAIL PROTECTED]> wrote:
2.) test_DiscussionReply.py
- while most test modules include tests for a corresponding module of
the product, these are tests for a single collector issue
- the tests are not really unit tests, more something like integratio
| 1.) fixing the bugs in BBBTransaction ;)
|
| 2.) adding BBBTransaction to CMFCore.tests.base.utils and using this in
| tests:
|
| try:
| import transaction
| except ImportError:
| # BBB: for Zope 2.7
| from Products.CMFCore.tests.base.utils import transaction
Why not just import f
Hi Florent!
Florent Guillaume wrote:
yuppie <[EMAIL PROTECTED]> wrote:
3.) Zope 2.8 warnings
'Zope2' is not available in Zope 2.7 and 'Zope' is deprecated in Zope
2.8. Same with 'transaction' and 'get_transaction'.
Has anybody a better idea to resolve it than this way:
[...]
I was thinking of:
t
yuppie <[EMAIL PROTECTED]> wrote:
> 2.) test_DiscussionReply.py
>
> - while most test modules include tests for a corresponding module of
> the product, these are tests for a single collector issue
>
> - the tests are not really unit tests, more something like integration tests
Well there are
yuppie <[EMAIL PROTECTED]> wrote:
> 3.) Zope 2.8 warnings
>
> 'Zope2' is not available in Zope 2.7 and 'Zope' is deprecated in Zope
> 2.8. Same with 'transaction' and 'get_transaction'.
>
> Has anybody a better idea to resolve it than this way:
>
> http://cvs.zope.org/Products/CMFCore/tests/ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
> 1.) CMFStaging tests
>
> For a while now, I see 6 CMFStaging tests failing. Can anybody confirm
> they are broken? Does anybody use CMFStaging and knows how to fix these
> tests?
We use it. I don't actually consider it to be part of
As I think I'd mentionned, I get the Zope default home home page (Welcome to
Zope, etc ...), but with a big warning at the top telling me that I don't
have an administrative user setup and so on ... Which is obviously not true
:)
Further reading has suggested that the problem might be because the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
> Lennart Regebro wrote:
>
>>> 3.) Zope 2.8 warnings
>>>
>>> 'Zope2' is not available in Zope 2.7 and 'Zope' is deprecated in Zope
>>> 2.8. Same with 'transaction' and 'get_transaction'.
>>>
>>> Has anybody a better idea to resolve it th
Lennart Regebro wrote:
3.) Zope 2.8 warnings
'Zope2' is not available in Zope 2.7 and 'Zope' is deprecated in Zope
2.8. Same with 'transaction' and 'get_transaction'.
Has anybody a better idea to resolve it than this way:
Well, the deprecation procedures and warning is there to tell you that
you a
> 3.) Zope 2.8 warnings
>
> 'Zope2' is not available in Zope 2.7 and 'Zope' is deprecated in Zope
> 2.8. Same with 'transaction' and 'get_transaction'.
>
> Has anybody a better idea to resolve it than this way:
Well, the deprecation procedures and warning is there to tell you that
you are using
Hi!
1.) CMFStaging tests
For a while now, I see 6 CMFStaging tests failing. Can anybody confirm
they are broken? Does anybody use CMFStaging and knows how to fix these
tests?
2.) test_DiscussionReply.py
- while most test modules include tests for a corresponding module of
the product, these are
Florent Guillaume wrote:
Chris Withers wrote:
Sidnei da Silva wrote:
> Look for CMFSetupExtensions on the collective.
Why am I not suprised...
Why couldn't this just have been fed into the real CMFSetup?!
Actually this code is quite specialized (to Archetypes and other stuff),
it doesn't have its
Chris Withers wrote:
Sidnei da Silva wrote:
> Look for CMFSetupExtensions on the collective.
Why am I not suprised...
Why couldn't this just have been fed into the real CMFSetup?!
Actually this code is quite specialized (to Archetypes and other stuff),
it doesn't have its place in CMFSetup proper.
Sidnei da Silva wrote:
Look for CMFSetupExtensions on the collective.
Why am I not suprised...
Why couldn't this just have been fed into the real CMFSetup?!
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
__
Florent Guillaume wrote:
Yes, I think I'll be doing some cleanups in it if you don't object.
And probably apply
http://www.artima.com/weblogs/viewpost.jsp?thread=101968 to the code in
general... I really have a problem with Tres's style ;)
What bothers me a little bit is the date on the article
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
chrisw
- "Limit the roles that can create specified types of content.",
[Accepted] http://www.zope.org/Collectors/CMF/114
gregweb
- "CMFUid.U
24 matches
Mail list logo