Roger Ineichen wrote:
class LanguagesVocabulary(SimpleVocabulary):
... languages from a translation domain.
implements(ILanguagesVocabulary)
def __init__(self, context, domain='zope'):
terms = []
# collect languages from translation domain
Philipp von Weitershausen schrieb:
Roger Ineichen wrote:
class LanguagesVocabulary(SimpleVocabulary):
... languages from a translation domain.
implements(ILanguagesVocabulary)
def __init__(self, context, domain='zope'):
terms = []
# collect languages from
Roger Ineichen wrote:
Philipp von Weitershausen schrieb:
Roger Ineichen wrote:
class LanguagesVocabulary(SimpleVocabulary):
... languages from a translation domain.
implements(ILanguagesVocabulary)
def __init__(self, context, domain='zope'):
terms = []
#
On Mar 25, 2006, at 5:41 AM, Philipp von Weitershausen wrote:
You can, of course, leave this as it is and implement the 'tiks'
vocabulary as:
def tiksLanguagesVocabulary(context):
return LanguagesVocabulary(context, 'tiks')
and then register that as a regular IVocabularyFactory utility,
Jean-Marc Orliaguet wrote:
Is there any reason for not being able to unregister global utilities?
Usually there are registered at startup in ZCML, but they can also be
registered programatically with provideUtility().
let's say that the startup process is done and my application wants to
Jean-Marc Orliaguet wrote:
Is there any reason for not being able to unregister global utilities?
Usually there are registered at startup in ZCML, but they can also be
registered programatically with provideUtility().
let's say that the startup process is done and my application wants to
What do you think about the following:
We have three concept in Zope 3 which are the real base for
Zope 3 as application server.
This are:
- python
- Zope components
- ZMCL
Each of them are well separated. Python is well documented,
Zope 3 is also good documented for a devleoper in it's
Philipp von Weitershausen schrieb:
Roger Ineichen wrote:
You implemented a concept which requires to write additional
python code for registration!
Wrong. I require addition python code for *creation*. *Registration* is
still done in ZCML. Please understand this difference.
Before the
Roger Ineichen wrote:
Philipp von Weitershausen schrieb:
Roger Ineichen wrote:
You implemented a concept which requires to write additional
python code for registration!
Wrong. I require addition python code for *creation*. *Registration* is
still done in ZCML. Please understand this
Philipp von Weitershausen schrieb:
[...]
Jim's statement says that #1 should rather be done in Python, whereas #2
remains in ZCML. That's exactly the point of my proposal.
Yes, I absolutly understand your point. I'm only not sure if ZCML sould
be a own abstract layer in our development
10 matches
Mail list logo