Rocky Burt wrote:
[..]
ps. Raphael, it would be phenomenal if your MySite tutorial could be
extended to cover something like this.
I hear you ;-)
Sure that's something I've been thinking about myself for
a while now but as long as the API evolves and as long as
there isn't a best practice y
Rocky Burt wrote:
I forgot to mention that I'm trying to get started with CMFSetup in CMF
1.5 as my current deployment platform happens to be Plone 2.1.1.
Hopefully most of CMFSetup's (from CMF 1.5) functionality is migratable
into CMF 2.0.
the CMF 1.5 CMFSetup spellings will work on CMF 2.
I forgot to mention that I'm trying to get started with CMFSetup in CMF
1.5 as my current deployment platform happens to be Plone 2.1.1.
Hopefully most of CMFSetup's (from CMF 1.5) functionality is migratable
into CMF 2.0.
- Rocky
Rocky Burt wrote:
Hi CMF'ers,
With all the recent talks o
Hi Florent!
Florent Guillaume wrote:
How does CMFSetup/GenericSetup deal with tools that "cache" data?
For instance, when a ZCatalog config is loaded, and some indexes are
added, they are empty.
Is there a specific phase where the index can be updateed? Where the
catalog itself can be repopu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
>
> On 24 Oct 2005, at 18:29, Tres Seaver wrote:
>
- External methods gain support by extending the saved information to
collect module/function values for external methods instead of trying
to read the body. Th
On 24 Oct 2005, at 18:29, Tres Seaver wrote:
- External methods gain support by extending the saved
information to
collect module/function values for external methods instead of
trying
to read the body. This *will* make an import blow up if the
filesystem code the external method relies on i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
> Jens Vagelpohl wrote:
>
>> There's an outstanding issue in the collector about workflow scripts
>> that are external methods. Currently, creating a snapshot of a site
>> with external methods on the Scripts tab of a DCWork
Jens Vagelpohl wrote:
[..]
- External methods gain support by extending the saved information to
collect module/function values for external methods instead of trying
to read the body. This *will* make an import blow up if the filesystem
code the external method relies on is not in the exp
Jens Vagelpohl wrote:
There's an outstanding issue in the collector about workflow scripts
that are external methods. Currently, creating a snapshot of a site
with external methods on the Scripts tab of a DCWorkflow will just blow
up. The real question here is: Do we want to support that at
On 23 Sep 2005, at 01:29, Tres Seaver wrote:
We could '_setId' on the tool with the 'tool_id' attribute after
creating it, if the tool does not derive from
CMFCore.utils.ImmutableId.
That's what I ended up doing. Fixes and a test checked in.
jens
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
> Just noticed another debilitating problem with the new cookie crumbler
> setup driven by CMFSetup in both SVN trunk and the 1.5 branch.
>
> Symptom: In a new CMFSetup-created site, no one can log in at all. Ever.
>
> Problem:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
pete wrote:
> I've written the tests now, so hopefully mailhost and cookieauth can be
> scratched off the list.
>
> http://www.zope.org/Collectors/CMF/387
>
> Is the collector the best place to put this? If not, let me know and I
> can post it else
Hi
I've written the tests now, so hopefully mailhost and cookieauth can be
scratched off the list.
http://www.zope.org/Collectors/CMF/387
Is the collector the best place to put this? If not, let me know and I
can post it elsewhere.
pete
pete wrote:
Hi,
In case it's useful, here's the
Hi Florent!
Florent Guillaume wrote:
Are you doing further work on the portal_catalog handlers you currently
have? I'd be interested in continuing that work, as I want full-CMFSetup
configuration to work as soon as possible.
Yes. But my code depends on Zope 2.8.1 and I'm currently waiting fo
yuppie wrote:
I was looking at CMFSetup, and was thinking of writing a handler for
one of the tools that isn't covered at the moment, to familiarise
myself with how it all works in a useful way.
Great! But please be aware of the fact that CMFSetup is still fast
changing code. Some things m
Hi Jens!
Jens Vagelpohl wrote:
On 11 Sep 2005, at 17:22, yuppie wrote:
The Actions thing is another issue that I noticed today. On the trunk,
we seem to have "old style" actions on some tools (I specifically
looked at the Membership and Memberdata tools because I'm re-doing
CMFLDAP) tha
On 11 Sep 2005, at 17:22, yuppie wrote:
Here's some food for thought about a possible code simplification:
I was looking at the (annoying) duplication of configuration data
between CMFSetup type information XML files and
factory_type_information structures stored inside python modules.
I
Hi Jens!
Jens Vagelpohl wrote:
Here's some food for thought about a possible code simplification:
I was looking at the (annoying) duplication of configuration data
between CMFSetup type information XML files and
factory_type_information structures stored inside python modules. It
would b
Hi!
computing project wrote:
I've written handlers for the cookie crumbler and for the mailhost - not
exactly rocket science but actually very informative as they are pretty
simple (well, the simplest!) tools. I started off looking at all the
code, and found that I didn't need to look at mos
Hi,
Thanks for the feedback - I hadn't looked where you suggested, and I'd been
thinking about starting with the catalog, so I managed to avoid two
potential pitfalls before starting (very pleasing!).
I've written handlers for the cookie crumbler and for the mailhost - not
exactly rocket sci
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
> What the status of people's various projects dealing with I/O of content
> using CMFSetup? That's something I'll be working on for CPS in the next
> few weeks, and also maybe at the Castle Sprint if there's interest.
I have
Hi Pete!
computing project wrote:
I was looking at CMFSetup, and was thinking of writing a handler for one
of the tools that isn't covered at the moment, to familiarise myself
with how it all works in a useful way.
Great! But please be aware of the fact that CMFSetup is still fast
changing
On 1 Sep 2005, at 14:18, Florent Guillaume wrote:
Please followup here about your progress, we (Nuxeo) should be
working on CMFSetup a lot this month too.
It might be useful for all those items that are not connected to a
collector issue (where you can "accept" it and signal that you are
computing project wrote:
I was looking at CMFSetup, and was thinking of writing a handler for one
of the tools that isn't covered at the moment, to familiarise myself
with how it all works in a useful way. Is anyone working on the
import/exports that aren't marked as done?
Not that I know of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
> Anahide Tchertchian wrote:
>
>> yuppie wrote:
- get rid of DCWorkflow specifics, and use the workflow factory and
API methods to import a workflow (no need to import
DCWorkflowDefinition, State, Transition classes an
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 lik
Hi,
yuppie wrote:
Please note that all other tool handlers use utils.*ConfiguratorBase. I
didn't convert workflow.py because it is the biggest handler and it
works for me as it is. But it uses deprecated patterns, so if you plan
to improve it it might be worth to refactor it using *Configurato
yuppie <[EMAIL PROTECTED]> wrote:
> Anahide Tchertchian wrote:
> > I'd like to make 3 main changes to the way CMFSetup handles workflow
> > export/import:
>
> Please note that all other tool handlers use utils.*ConfiguratorBase. I
> didn't convert workflow.py because it is the biggest handler an
Encolpe Degoute wrote:
That's seems a good idea, but I don"t 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!
Anahide Tchertchian wrote:
I'd like to make 3 main changes to the way CMFSetup handles workflow
export/import:
Please note that all other tool handlers use utils.*ConfiguratorBase. I
didn't convert workflow.py because it is the biggest handler and it
works for me as it is. But i
Hi Florent!
Florent Guillaume wrote:
In many places, CMFSetup exports and imports things like titles and
descriptions. For instance, for the workflow states and transitions.
These fields can often, outside the USA, contain non-ascii strings. How
do we export and reimport them ?
It would be
Hi Florent!
Florent Guillaume wrote:
By the way will you (or others) be at EuroPython ? It would be nice to
discuss plans for CMFSetup face to face.
I'll not make it to Göteborg and I'm not sure who the 'others'
interested in CMFSetup development are.
But I have many plans for CMFSetup and
By the way will you (or others) be at EuroPython ? It would be nice to
discuss plans for CMFSetup face to face.
Florent
yuppie <[EMAIL PROTECTED]> wrote:
> Florent Guillaume wrote:
> > In the Properties tab of CMFSetup, you can choose an active site
> > configuration, among the snapshots and
Hi Florent!
Florent Guillaume wrote:
In the Properties tab of CMFSetup, you can choose an active site
configuration, among the snapshots and the registered profiles.
This sets the current context_id for the tool, and loads the import
steps, export steps and toolset for that configuration.
Florent Guillaume wrote:
On 10 Jun 2005, at 17:02, yuppie wrote:
utils.ConfiguratorBase has some methods for generic property support.
The typeinfo handlers could use that code in a similar way as the
site properties handlers or the handlers for the newstyle Actions on
HEAD.
The propert
Hi Yuppie,
On 10 Jun 2005, at 17:02, yuppie wrote:
I have to modify CMFSetup's type information import/export
(typeinfo.py).
Currently, to discriminate on ti types on export, it does:
if isinstance( ti, FactoryTypeInformation ):
...
elif isinstance( ti, ScriptableT
Hi Florent!
Florent Guillaume wrote:
I have to modify CMFSetup's type information import/export (typeinfo.py).
Currently, to discriminate on ti types on export, it does:
if isinstance( ti, FactoryTypeInformation ):
...
elif isinstance( ti, ScriptableTypeInformatio
Hi Florent!
Florent Guillaume wrote:
I'd like to discuss possible improvements to have profile extensions
check some dependencies. This will require a way to express
dependencies, which in the general case can be extremely complex -- but
we probably don't need that.
[...]
Just some general thoug
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},
C
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
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
Hi Florent!
Florent Guillaume wrote:
On 3 Apr 2005, at 17:27, yuppie wrote:
Florent Guillaume wrote:
- all in all it's quite nice,
Well. It works for some use cases, but there is yet a lot to be done.
Though its maturity is still alpha, it already contains a lot of cruft.
Yes, I think I'll be do
On 3 Apr 2005, at 17:27, yuppie wrote:
Hi Florent!
Florent Guillaume wrote:
- all in all it's quite nice,
Well. It works for some use cases, but there is yet a lot to be done.
Though its maturity is still alpha, it already contains a lot of
cruft.
Yes, I think I'll be doing some cleanups in it if
Hi Florent!
Florent Guillaume wrote:
- all in all it's quite nice,
Well. It works for some use cases, but there is yet a lot to be done.
Though its maturity is still alpha, it already contains a lot of cruft.
- writing the code for the import handler is really painful, I wish we
could use an API
44 matches
Mail list logo
