Further I'd like to know, what happens to ZPT at runtime. Are they compiled into
Python modules?
Thanks
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Shane Hathaway wrote:
[snip]
But the ZCML I've
written gives me a sick feeling, because I don't know how to refactor
ZCML. The sick feeling doesn't go away, so I get scared of Zope 3. Then
I come here, hoping to find comfort.
I share these sentiments. Not that I have a particularly sick
Jeff Shell wrote:
On 3/15/06, Martijn Faassen [EMAIL PROTECTED] wrote:
Jim Fulton wrote:
- We don't have a good way for installing collections of local
components that work together. For our projects, we've used the
generation machinery to automate this, but that only works if you
want to
Philipp von Weitershausen wrote:
Martijn Faassen wrote:
I stand by my conclusions on this approach sounding simple in theory,
but still being a bit harder than it should be in practice. :)
I think this is pretty simple:
def makeAnnotationAdapter(for_, factory, key):
Martijn Faassen wrote:
Philipp von Weitershausen wrote:
Martijn Faassen wrote:
I stand by my conclusions on this approach sounding simple in theory,
but still being a bit harder than it should be in practice. :)
I think this is pretty simple:
def makeAnnotationAdapter(for_, factory,
Jean-Marc Orliaguet wrote:
[snip]
excuse me, but can someone explain what problem the pattern / workaround
is supposed to fix, does it create and return a default annotation value
in case an annotation key does not exist? shouldn't the annotation
machinery be fixed instead to provide
Martijn Faassen wrote:
Jean-Marc Orliaguet wrote:
[snip]
excuse me, but can someone explain what problem the pattern /
workaround is supposed to fix, does it create and return a default
annotation value in case an annotation key does not exist? shouldn't
the annotation machinery be fixed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhold Strobl wrote:
Further I'd like to know, what happens to ZPT at runtime. Are they compiled
into
Python modules?
No, they are compiled into bytecodes exceuted by the TAL interpreter,
which is invoked when the template is rendered.
Tres.
Jean-Marc Orliaguet wrote:
[snip]
OK, basically you mean that the 'annotations' given in your original
post should implement a 'setdefault' method?
I don't see how that would help - you'd still end up writing a factory
that uses the setdefault, right?
I don't want to keep repeating factory
On 3/16/06, Martijn Faassen [EMAIL PROTECTED] wrote:
Jeff Shell wrote:
I don't think there's anything wrong with custom Python code to set
this up. It's programmatic, isn't it? A lot of it may be repetitive,
and if that's the case, functions/methods can help. Are we all just so
used to
Martijn Faassen wrote:
Jean-Marc Orliaguet wrote:
[snip]
OK, basically you mean that the 'annotations' given in your original
post should implement a 'setdefault' method?
I don't see how that would help - you'd still end up writing a factory
that uses the setdefault, right?
I don't want
Hey Jeff,
Jeff Shell wrote:
On 3/16/06, Martijn Faassen [EMAIL PROTECTED] wrote:
[snip]
I'd like there to be common patterns so there's at least a
reasonable chance that you can plug my TTW UI for user management
into your application without having to rewrite large parts of
either. I'd also
Hi there,
Let's come up with a plan for widgets. We have a very nice widget system
in Zope 3, but it's not perfect. There are a bunch of things that could
be improved:
* the widgets are hanging out in dusty zope.app.form.browser. Perhaps
it's time to move them into zope.widget? Not even in
On 3/16/06, Martijn Faassen [EMAIL PROTECTED] wrote:
* Jim tells me Don't look at SimpleInputWidget, it's too complicated.
This sounds wrong and zope2-like; something called Simple that's too
complicated. We need to figure out how to make that story less complicated.
Basically, it tries to be
Lennart Regebro wrote:
On 3/16/06, Martijn Faassen [EMAIL PROTECTED] wrote:
[snip]
Are people interested in developing a plan to tackle these issues? If
some of us chip in we may get somewhere.
Are widgets tied to schema fields now? I have the feeling they are,
but maybe not. If they are,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
snip
* sources and terms are nice, but we should at least provide some basic
sources and register some basic terms for them; that bit is completely
missing in Zope 3 right now. People should be able to at make a simple
On 3/16/06, Martijn Faassen [EMAIL PROTECTED] wrote:
Just to interfaces of schema fields as views. The schema fields are in a
hierarchy. I'm not sure how you would mean to decouple this.
Anyway, my aim with this discussion is not to fundamentally overhaul the
way widgets work, just to see
On 3/16/06, Martijn Faassen [EMAIL PROTECTED] wrote:
Shane Hathaway wrote:
[snip]
But the ZCML I've
written gives me a sick feeling, because I don't know how to refactor
ZCML. The sick feeling doesn't go away, so I get scared of Zope 3. Then
I come here, hoping to find comfort.
I
Hey Roger,
Great to have you onboard on this!
Roger Ineichen wrote:
[snip]
btw,
didn't Gary Poster start a widget refactoring?
Good question. I have no idea what the status of all that stuff is;
whether anything got merged or not..
Regards,
Martijn
On Thu, Mar 16, 2006 at 11:38:02AM -0500, Tres Seaver wrote:
zcml:ktupema_necro_halogo
eh?
http://www.google.com/search?hl=enlr=q=ktupema+necro+halogobtnG=Search
Your search - ktupema necro halogo - did not match any documents.
--
Paul Winkler
http://www.slinkp.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Winkler wrote:
On Thu, Mar 16, 2006 at 11:38:02AM -0500, Tres Seaver wrote:
zcml:ktupema_necro_halogo
eh?
http://www.google.com/search?hl=enlr=q=ktupema+necro+halogobtnG=Search
Your search - ktupema necro halogo - did not match any
On Thursday 16 March 2006 11:06, Martijn Faassen wrote:
Are people interested in developing a plan to tackle these issues? If
some of us chip in we may get somewhere.
Gary has already begun the work of a widget replacement. Talk to him, he has
some good ideas.
Regards,
Stephan
--
Stephan
Stephan Richter wrote:
On Thursday 16 March 2006 11:06, Martijn Faassen wrote:
Are people interested in developing a plan to tackle these issues? If
some of us chip in we may get somewhere.
Gary has already begun the work of a widget replacement. Talk to him, he has
some good ideas.
On Mar 16, 2006, at 11:42 AM, Martijn Faassen wrote:
Hey Roger,
Great to have you onboard on this!
Roger Ineichen wrote:
[snip]
btw,
didn't Gary Poster start a widget refactoring?
Good question. I have no idea what the status of all that stuff is;
whether anything got merged or not..
Jeff Shell wrote at 2006-3-15 14:26 -0700:
...
Anyways, I don't mind if someone wants 'browser:addform' as an add-on.
But I don't think those things belong in the core. If someone wants to
make a package that lets them build a web site using nothing but ZCML
to glue a bunch of crap together! then
Hi all,
my work on http://dev.zope.org/Zope3/ReducingTheAmountOfZCMLDirectives
has been nearly completed on the philikon-reduce-zcml branch and is
ready for review.
What I didn't cover:
* rdb:provideConnection wasn't removed. On a second thought, this
directive also contains deployment
Lets step back and look at why we created ZCML. A primary goal of the
component architecture was to make it easier to reuse packages. A
major problem with Zope 2 products is that they are hard to
customize. The CMF made this a bit better with skins. You could
override selected scripts or
On 3/16/06, Tres Seaver [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
snip
* sources and terms are nice, but we should at least provide some basic
sources and register some basic terms for them; that bit is completely
missing in Zope 3
On Thu, Mar 16, 2006 at 08:06:11PM -0700, Jeff Shell wrote:
| By the way, isn't it pretty easy to provide straight up values anyways
| for those quick drop-down situations?
|
| trip_type = zope.schema.Choice(
| title=_(uTrip Type),
| description=_(uTrip Type),
|
29 matches
Mail list logo
