Michael Howitz wrote:
Am Mittwoch, den 05.04.2006, 09:36 -0500 schrieb Jeff Rush:
I know that Zope3 dropped 'implicit' acquisition, but is there any support for
*explicit* acquisition that walks the __parent__ containment hierarchy.
Something that follows the same rules as traverse() to look u
On Wednesday 05 April 2006 10:32, Jeff Rush wrote:
> Now I'm a bit confused -- there seem to be 'publication namespaces' e,g.
> '++resource++', and 'TALES namespaces' e.g. 'zope:', and the
> publication namespaces leak into the TALES namespaces i.e. are accessible
> as shown by your examples, but I
On Friday 31 March 2006 08:49, Jeff Rush wrote:
> whereas I'm trying to get:
>
> X.__getattr__('Y') # X.Y
You can use: X/++attribute++Y. A list of all those traversal namespaces are in
zope.app.traversing/configure.zcml.
Regards,
Stephan
--
Stephan Richter
CBU Physics & Chemistry (B.S.)
Hi all.
As promised I set up a repository with my SQLAlchemy integration work.
Actually it works under my test cases.
The main part is the integration of the transaction process into zope so that it
is transparent to the user.
Someone with more SQLAlchemy experience should have a look at the
just wanted to say thanks to Jurgen for getting this set up... :)
> Hi all.
>
> As promised I set up a repository with my SQLAlchemy integration work.
>
> Actually it works under my test cases.
>
> The main part is the integration of the transaction process into zope so
> that it is transparent
hi all... i've recently tried to start moving away from
zope.app.form.browser.editview's EditView, and to zope.formlib.form's
Form and EditForm, but have run into something that confuses me.
i'm setting up the zcml for both of them basically the same way, using
browser:page and assigning a templa
Thanks, I will follow up on this.
I did find that the following worked as an interim fix. In my "select"
statement, instead of "select price", we use "select format(price,2) price":
it breaks the i18n stuff but it works otherwise. IDecimal sounds like a much
better approach.
> -Original
Hi Jurgen! This is excellent news. Thank you for this work! I will also
look at the code to see what I can do to contribute. I think it would
be great for you to post an announcement to the SQLAlchemy list. There
are folks there in tune with core SQLAlchemy code that may also be able
to offer
Let's first see if it works as expected.
I really have no idea if it is usefull for full blown applications.
I only tested my use cases, we'll see what happens if someone else uses it.
Since the repository is online I did a lot of changes and impovements
and I'm constantly working on.
I'm now st
On Thu, 06 Apr 2006 18:48:12 +0100, jürgen Kartnaller
<[EMAIL PROTECTED]> wrote:
Let's first see if it works as expected.
I really have no idea if it is usefull for full blown applications.
I only tested my use cases, we'll see what happens if someone else uses
it.
Since the repository is
Hi Pete,
I assign templates in view classes when using formlib:
from zope.app.pagetemplate.viewpagetemplatefile import
ViewPageTemplateFile
class ConsumerRegistrarForm(form.Form):
.
.
template = ViewPageTemplateFile('registrar.zpt')
.
.
I would also be interested to find out
On Apr 6, 2006, at 7:27 PM, Alen Stanisic wrote:
Hi Pete,
I assign templates in view classes when using formlib:
from zope.app.pagetemplate.viewpagetemplatefile import
ViewPageTemplateFile
class ConsumerRegistrarForm(form.Form):
.
.
template = ViewPageTemplateFile('registrar.zpt')
ah, hah! that would be why no matter what i do to the template, it
doesn't change anything. I guess, since "viewlet" takes a template
argument in zcml, i assumed it was using it. thanks, as always, Gary.
On 4/6/06, Gary Poster <[EMAIL PROTECTED]> wrote:
>
> On Apr 6, 2006, at 7:27 PM, Alen Stan
On 4/6/06, Martin Aspeli <[EMAIL PROTECTED]> wrote:
> I, for one, am really excited by this [sqlalchemy / zalchemy]. I really hope
> that Zope 3 will have a somewhat consistent story for RDBMS access that (a)
> uses
> technology not invented in Zope alone (b) is scalable and robust and (c) is
> do
Jeff Shell wrote:
On 4/6/06, Martin Aspeli <[EMAIL PROTECTED]> wrote:
I, for one, am really excited by this [sqlalchemy / zalchemy]. I really hope
that Zope 3 will have a somewhat consistent story for RDBMS access that (a) uses
technology not invented in Zope alone (b) is scalable and robust and
15 matches
Mail list logo
