yuppie wrote:
To get rid of the intermediate [0], use
'properties': {KEY: 'props',
CONVERTER: self._convertToUnique},
'entry-local-roles': {KEY: 'elrs', DEFAULT: ((),),
CONVERTER: self._convertToUnique
the Actions in an XML file. Conflicts
between Actions have to be resolved on set-up time, not when
listFilteredActionsFor() is called.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See
as the other packages and we still have to change it in
fundamental ways. Though these changes might not always be fully
backwards compatible, I believe we should keep merging them into the
CMF-1_5-branch.
Cheers, Yuppie
___
Zope-CMF maillist - Zope
registered in a property of
CMFDefault's PropertyTool.
It does feel wrong that you have to register OpaqueItem attributes to
make them work correctly. I'd rather like to see a solution similar to
that for Zope 3 annotations: Storing all opaque items in one attribute.
Cheers, Yuppie
cents. Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
*why* you hate it? warnings.warn is used in many
places, so if there is a good reason not to use it other code should be
changed as well.
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
steps can be done without breaking Zope 2.7 compatibility.
I'd like to start with this on the HEAD and backport it to the 1.5
branch as soon as it is mature enough.
Any comments?
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF
for me using latest
CMF-1_5-branch and Zope 2.8.0 final.
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
propose to wait one or two weeks with the beta.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
that are 100% backwards compatible.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Christian Heimes wrote:
yuppie wrote:
I'm not sure I understand what you propose:
- Just changing queryMethodID signature and calls?
- Or also adding the TemplateMixin stuff to CMFCore?
- Or also adding an UI for that to CMFDefault?
I'm proposing at least the first point in your list
= Folder.manage_main.__of__(self)
+return m(self, client, REQUEST, **kw)
Globals.InitializeClass(Scripts)
Why is this fix just in the CMF-1_4-branch?
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman
-release version of) CMF 1.6.
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
for its absence. The CMF 1.5 branch will thus be the EOL
for sites which chose to continue running Zope 2.7.x.
+1
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF
. The HEAD is
still very similar to CMF 1.5, but raises errors if you use deprecated code.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug
and would love to hear your plans and
to discuss them. Unfortunately I can't make this work part of one of my
customer projects, so I can't spend as much time on CMFSetup development
as I would like to.
Cheers,
Yuppie
___
Zope-CMF maillist
Christian Heimes wrote:
yuppie wrote:
But AFAICS it doesn't make much sense for the CMF to duplicate a
feature that Zope 2.8/Five provides already.
You are right but we can't use new Zope 2.8 features at the moment. It
would delay Plone 2.1 and introduce new dependencies.
I was just
'
means 'old ActionInformation' and is deprecated since CMF 1.3. But
DCWorkflow still depends on it, so there are no deprecation warnings.
I guess you have to modify getExprContext *and* getOAI for Plone.
Cheers,
Yuppie
___
Zope-CMF maillist
Hi Christian!
I'm fine with the proposed change, but I would prefer to have _getOAI
and _getExprContext in *one* place: ActionProviderBase.
Cheers,
Yuppie
[I quote the complete mail because it didn't make it to the list:]
Christian Heimes wrote:
yuppie wrote:
Please make
.
Cheers,
Yuppie
BTW: I'm not at all happy with the fact that Zope 2.8 ships with
CMFBTreeFolder. That circular dependency is a pain to maintain. Maybe we
should move CMFBTreeFolder to a CMF product.
___
Zope-CMF maillist - Zope-CMF
Hi Christian!
Christian Heimes wrote:
yuppie wrote:
First of all CMF 1.5.2 has to be backwards compatible to CMF 1.5.0 and
1.5.1, so reverting that change is no option.
That is understandable from your point of view but I don't agree with
the desicion.
This is not a decision, I'm
I
believe 'context' is redundant and this should also work:
def _getOAI(self, object):
return getOAI(self, object)
def _getExprContext(self, object):
return getExprContext(self, object)
Would you mind if I change it that way?
Cheers,
Yuppie
Hi Christian!
Christian Heimes wrote:
yuppie wrote:
That's not fair. You are free to ignore CMF development for years, but
you can't make other people pay for that. Upgrading from 1.5.x to the
latest 1.5 version has to work without *any* trouble.
I'm sorry but I'm a little bit nervous. I
and wasn't fixed when method aliases
were introduced.
Like other folders a skinned folder should never be used as method, so
__call__ should never be invoked. That code exists just for backwards
compatibility and is completely removed on HEAD.
Cheers,
Yuppie
ActionInfo objects. A
fix for the copy method is on the CMF-1_5-branch. Hope that fixes your
issue as well.
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF
.) If you set the '(Default)' alias to index_html, index_html is
called. If you don't set it or set it to '(Default)',
__browser_default__, index_html or __call__ is called depending on the
class.
HTH,
Yuppie
___
Zope-CMF maillist - Zope
Encolpe Degoute wrote:
yuppie a écrit :
| I think it's worth the effort to migrate DCWorkflow Actions to the
| CMFCore Actions machinery for CMF 1.6. And in that context your
| proposal is a move in the wrong direction.
Now that actions machinery has been refactored in CMF 1.5, I would use
Hi Tres!
Tres Seaver wrote:
yuppie wrote:
1.) catalog migration is broken
http://www.zope.org/Collectors/CMF/357
http://www.zope.org/Collectors/Zope/1823
A copy 'n' paste of the latest manage_convertIndexes code to CatalogTool
should fix this.
Fine.
Looks like there are still
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Encolpe Degoute wrote:
That's seems a good idea, but I dont where worklists will be import
in few weeks.
That sounds like you're working on a big worklists refactoring. If
that's the case, sending a small proposal to the list would be nice.
Cheers, Yuppie
Hi!
Anahide Tchertchian wrote:
yuppie wrote:
- turn import methods in CMFSetup/workflow.py into configurator class
methods so that they're easier to override when subclassing
(_extract*Nodes and _initDCWorkflow* methods)
Sounds fine if you don't want to do the big refactoring.
Yes I'd
by that.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
sense in a new repository. I guess they
should be removed from CMF trunk. (The real products are in CMF_Extras)
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org
on an external product, but maybe CMFTestCase could become part
of CMF?
Just my 2 cents.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports
feature (import from tarballs) to GenericSetup; if
the CMF community can't see a way to use GenericSetup, I will look at
porting that feature back to CMFSetup (it shouldn't be too hard).
Great. How ever the dependencies are resolved - this should become part
of the CMF.
Cheers, Yuppie
idea.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Dieter Maurer wrote:
yuppie wrote at 2005-9-5 14:06 +0200:
...
PortalTestCase is in the wrong layer. It makes assumptions about the way
CMF works. Changes to the CMF might break PortalTestCase and create a
dependency on a new Zope release. (We saw that problem already
.
- PluginIndexes, ZCTextIndex and ZCatalog have some new interfaces that
are useful to write portal_catalog setup adapters.
- The recently added i18n MessageIDs are ignored in Zope 2.8.0.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF
. I can't reproduce any problems with
test_z3interfaces.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Jens Vagelpohl wrote:
On 8 Sep 2005, at 11:08, yuppie wrote:
PS Those of you who raised concerns about ZopeTestCase causing test
problems in Zope 2.7 might want to take a look at why
test_z3interfaces is
broken when you run the tests with zopectl test.
1.) Why those of you who raised
. I'll change those tests.
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Hi Geoff!
Geoff Davis wrote:
On Thu, 08 Sep 2005 19:24:51 +0200, yuppie wrote:
Knock! Knock! Anybody there?
I told you twice that I'm concerned about using PortalTestCase:
http://mail.zope.org/pipermail/zope-cmf/2005-September/022891.html
Would be nice to get some feedback. Obviously you
on the oldstyle FTI data.
3.) It might be easier to discuss this in the context of Tres' CMFSetup
and roadmap proposals.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See
'getToolByName' hookable so that it
can return a different 'portal_catalog' based on whatever constraints
you need to distinguish which catalog to use, and then ensure
'getToolByName' is used all around where a catalog is needed.
+1
Yuppie
___
Zope-CMF
be the right layer
to implement this?
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Lennart Regebro wrote:
On 9/13/05, yuppie [EMAIL PROTECTED] wrote:
Is this in any way CMF-specific? Wouldn't a feature like that be useful
in pure Zope as well? Why do you think the CMF would be the right layer
to implement this?
Welll, what is gonna implement it? There is no standard
/022877.html
proposes to use im- and export adapters for content objects. Can't we do
the same for config objects, registering the SetupHandlers as adapters?
And get rid of the special SetupHandler registries completely?
Cheers,
Yuppie
are anyway utf-8 encoded, so there would not be any need to
convert strings from one encoding to an other.
(At the moment a hardcoded ascii encoding is passed around everywhere.)
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF
examples the handlers should be able to get the
encoding information from their context if they want to support special
encodings. So there is at least no need to support encodings in the
framework. Right?
Cheers,
Yuppie
___
Zope-CMF
Hi Tres!
Tres Seaver wrote:
yuppie wrote:
At the first glance that makes export_steps.xml and import_steps.xml
obsolete. But there is the MetaProfile that has to be shipped with a
BaselineProfile and that is maintained in the tool. Why do we still need
MetaProfiles? Can't we just walk
dependency
on CMFDefault's SkinnedFolder.
Not sure how to resolve this.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports
code from the 1.5 branch, but need passing tests first.
Are you using the latest Zope-2_8-branch revision? I recently made a
change that depends on Zope changes.
Hope svn up resolves the issue.
Sorry for not giving a heads up.
Cheers, Yuppie
sense to me: What is your goal? Why do
you need to 'hook up' POST if your edit view works already?
When should your POST method be called and what does that POST method?
Are you working on something special or just on a normal edit view?
Cheers,
Yuppie
on top of the CMF have to ship
with a GenericSetup profile for CMF 2.0.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature
Hi Jens!
Jens Vagelpohl wrote:
On 16 Oct 2005, at 16:21, yuppie wrote:
Jens Vagelpohl wrote:
Doing some more work on Five views for CMF right now. I have the edit
view hooked up and working find for my sample content type. The view
class given to me by Tres defines a POST method, but I
to 'exportimport'.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Hi Lennart!
Lennart Regebro wrote:
On 10/17/05, yuppie y.2005--E2EsyBC0hj3+aS/[EMAIL PROTECTED] wrote:
I know that pattern, but I don't like it. [...]
The code on the goldegg-folder_contents branch processes the input in
the __call__ method of the view class. The template is only invoked
Hi Tres!
Tres Seaver wrote:
Lennart Regebro wrote:
On 10/17/05, yuppie y.2005--E2EsyBC0hj3+aS/[EMAIL PROTECTED] wrote:
I know that pattern, but I don't like it. [...]
The code on the goldegg-folder_contents branch processes the input in
the __call__ method of the view class. The template
,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
on
PortalGenerator because the new setup machinery is completely different.
PortalGenerator, manage_addCMFSite and oldstyle configuration data (fti
data, workflows - actions are already removed) will soon be removed
completely from the trunk.
Cheers,
Yuppie
because on
the trunk the factory was moved to CMFDefault.
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Hi all!
If there are no objections, I'll merge tomorrow the yuppie-setup_cleanup
branch into the trunk. This will break the setup code of all third-party
products that haven't yet switched to GenericSetup/CMFSetup.
1.) factory_type_information data is replaced by XML files in the types
the
deprecation warnings to STFU you have to reimplement getActionByID. If
you want to do things right, you don't need a replacement for getActionByID.
What are the plenty more apparently legit uses of getActionByID?
Cheers,
Yuppie
___
Zope-CMF
does it look like?
queryMethodID might be useful for your use case...
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature
Hi Chris!
Chris Withers wrote:
yuppie wrote:
Well. getActionByID did make sense before type actions became normal
actions in CMF 1.4. Since than getActionByID is an ugly backwards
compatibility hack that tries to guess the called method from an
expression string that defines a context
Hi Chris!
Chris Withers wrote:
yuppie wrote:
Once again:
getActionObject(action_path) is the method you are looking for.
Another problem with this:
getActionById is defined as public, getActionObject as private, so you
can't use it in any skin scripts or templates :-(
Suggestions
and Method Aliases. metadata.html has
hardcoded method names.
- metadata.py doesn't catch ResourceLockedErrors.
- The controller code is not scalable. Adding validators doesn't look
very easy and implementing something like folder_contents looks almost
impossible.
Cheers,
Yuppie
2.0
next week.
I just checked in http://svn.zope.org/?rev=39566view=rev on the
tseaver-viewification branch. That should be more suitable for comparing
the different approaches.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF
Hi Chris!
Chris Withers wrote:
yuppie wrote:
Okay, so how would you get the url for an action from inside a skin
script or template?
obj.getActionInfo('object/view')['url'] for type actions or
provider.getActionInfo('user/join')['url'] for other actions.
Just to emphasise further, I'm
Chris Withers wrote:
yuppie wrote:
This is in a completely set up Plone site? Could you please try to
debug those values while we are still in customizePortalTypes?
Okay, in there, it's just the normal Plone types, which we don't use.
And yes, their _aliases dict appears to have 'view' keys
by the 'members_manage_form' script to
render the result. 'members_manage_form' is the method that should be
called TTW. But I doubt it works with Plone.
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
of IAction objects would be
confusing because they are quite different objects.
I fixed getActionObject by making it skip newstyle Actions instead of
raising errors.
Hope that resolves the issue.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF
Hi!
Do we need CMFDefault/exportimport.zcml on the trunk? Wouldn't it be
better to replace the five:implements directives by implements()
statements in the classes?
If there are no objections I'll change that.
Cheers, Yuppie
___
Zope-CMF maillist
be an improvement and if
there are no objections I'll work on this change.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature
Florent Guillaume wrote:
yuppie wrote:
- import/export of selected tools from a bigger profile: don't think
we really need that
What do you mean by i/o of selected tools from a bigger profile ?
Right now each tool has its own import step and export step. The
'Import' and 'Export' tab
Hi Florent!
Florent Guillaume wrote:
yuppie wrote:
- import/export of selected tools from a bigger profile: don't think
we really need that
Right now each tool has its own import step and export step. The 'Import'
and 'Export' tab of the setup tool allow to select single steps and run
them
in CMF 2.0
- merge CMFSetup from trunk into the 1.6 branch and remove it from the
trunk (CMF 2.0)
If there are no objections I'll update the deprecation warnings on the
CMF 1.5 and 1.6 branches. The other tasks can wait a bit. Any help is
welcome.
Cheers,
Yuppie
, in particular w.r.t. the
timeframe I'm proposing for a 2.0 release.
'alpha' has no special meaning to me in that context, we are in 'alpha'
since 1.5 is branched. So the relevant date for getting things done is
the 'beta' in mid December - that's one month from now. Right?
Cheers,
Yuppie
logger *and* to TTW reports might be
the way to go.
Timeframe:
We need soon a stable API to encourage the authors of setup handlers to
use that API. The actual reporting and logging can be implemented later.
Cheers,
Yuppie
___
Zope-CMF
an
easy way to make sure the log handler collects only messages for a
specific request.
Or am I missing something?
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http
this thread for a related discussion:
http://mail.zope.org/pipermail/zope-cmf/2005-November/023319.html
2.) http://www.zope.org/Collectors/CMF/392 has to be resolved.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http
))
would be replaced by this code::
logger = import_context.getLogger('SGAIFA')
logger.info('no .ini file for %s/%s' % (subdir, cid))
If there are no objections I'd like to make those changes either on your
branch or after you merged your changes into the trunk.
Cheers,
Yuppie
Hi Rob!
Rob Miller wrote:
yuppie wrote:
2.) Please set svn:keywords Id on new python files.
/me reads svn docs to learn about svn:keywords.
The easiest way to make sure they are set is to modify your svn config.
You might need something like this::
[miscellany]
enable-auto-props
running processes on big
sites
If your site contains content you have to reindex manually.
Of course this could be improved.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
for multiple node adapters per interface.
For the 'actual' answer see Tres' reply. He is more familiar with the
content handlers than I.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope
. 'GenericSetup.content.CSAFA'
Or would be 'GenericSetup.content' enough? Currently it is
'GenericSetup.CSAFA'.
Maybe you've got an idea how to resolve this. Don't know what kind of
'component' name the reports need.
Cheers,
Yuppie
___
Zope-CMF maillist
, but I'm not sure.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
(['portal_type', 'Type']),
This was the case in my initial code, but Yuppie changed it:
http://svn.zope.org/trunk/CMFCore/TypesTool.py?rev=35903r1=35864r2=35903
I don't remember what the reason was, though I believe it was discussed
a bit at the time on the lists.
- This change was made 2 years ago
ATM, so I can't test it with zopectl. But
bin\python.exe bin\test.py -v --libdir Products/CMFDefault
doesn't raise any errors on my machine.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman
()
RequestTest.tearDown(self)
PlacelessSetup.tearDown(self)
Is this extra cleanUp() necessary? I thought
PlacelessSetup.tearDown(self) calls it already.
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope
Jens Vagelpohl wrote:
On 2 Dec 2005, at 18:58, yuppie wrote:
Tres Seaver wrote:
import Testing
-import Zope2
-Zope2.startup()
I'm seeing issues in some tests which fail when run outside the full
suite after changes like these. E.g.,
zopectl test CMFDefault
I'm trying to run those tests
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
On 2 Dec 2005, at 18:58, yuppie wrote:
Tres Seaver wrote:
import Testing
-import Zope2
-Zope2.startup()
I'm seeing issues in some tests which fail when run outside the full
suite after changes like
the
setup tool.
Any kind of questions and feedback are welcome.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature
as
well. ISetupContext is already taken, so we would have to call it
IMinimalSetupContext or whatever.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org
,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Hi Florent!
Florent Guillaume wrote:
On 13 Dec 2005, at 12:50, yuppie wrote:
I'd propose to implement an update mode for list properties and to add
an update file for each allowed container. Something like that:
object name=MyContainer
property name=allowed_content_types
element value
Hi Florent!
Florent Guillaume wrote:
On 14 Dec 2005, at 10:51, yuppie wrote:
Florent Guillaume wrote:
Can I fix the pretty xml exporter to use standard identing? (2
spaces for tags, 4 for attributes)
AFAICS nothing is broken and we don't have a policy for that. So I
would not call
Hi Chris!
Chris Withers wrote:
yuppie wrote:
1.) It would be nice to have a policy for Zope. If the Zope core
officially supports the BLATHER level (not just in the deprecated zLOG
module) I'm fine with using it in GenericSetup as well.
It doesn't, ZODB has a mapping for it but it's
,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Hi Rob! Hi Jens!
Rob Miller wrote:
Jens Vagelpohl wrote:
On 20 Dec 2005, at 19:53, yuppie wrote:
The intention was to make things consistent. CMF 1.5 and CMF 2.0
have different ways to register custom type info classes. Before
that change both machineries were broken on the 1.6 branch
1 - 100 of 410 matches
Mail list logo