]
To: Daniel Nouri [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
On Wednesday 18 July 2007 07:35, Daniel Nouri wrote:
You make it sound like the more objects you adapt, the more flexible you
are. Which is true to a certain extent, but at the same time, the more
Hi Stephan!
Stephan Richter wrote:
On Tuesday 17 July 2007 14:28, Daniel Nouri wrote:
plone.portlets introduces some two dozen (!) interfaces/concepts on top of
viewlets in order to implement the flexibility that it needs. E.g. it
introduces an 'available' method/property that controls
Hi!
Roger Ineichen wrote:
I do not recommend using views for content that is only
used inside a
template. Because context/@@viewname
is also traversable as a real view and will probably show up in
google.
How would it show up in Google? Google bots don't try
arbitrary URLs, they
Hi!
Stephan Richter wrote:
On Monday 16 July 2007 19:32, Daniel Nouri wrote:
I do not recommend using views for content that is only
used inside a template. Because context/@@viewname
is also traversable as a real view and will probably show
up in google.
How would it show up in Google
Hermann Himmelbauer wrote:
Am Dienstag, 17. Juli 2007 14:08 schrieb Stephan Richter:
On Monday 16 July 2007 19:32, Daniel Nouri wrote:
I do not recommend using views for content that is only
used inside a template. Because context/@@viewname
is also traversable as a real view
Hi Roger!
Roger Ineichen wrote:
If you like a explicit pattern, then calling views in ZPT is
fine. On the other hand, if you use a viewlet manager,
the manager can implement conditions and show based on
rules e.g. session state or login status more or less
viewlets.
I think best reason to
Stephan Richter wrote:
On Wednesday 20 June 2007 13:55, Daniel Nouri wrote:
Isn't it reasonable to expect an action to
execute although it's not visible when the form is rendered again?
Nope. For me the condition is a condition of availability and not visibility.
That's exactly where I
Currently, when you have a condition on an action, and it is satisfied on
render time, you'll get a button. However, if you click that button and the
condition happens to be false in the subsequent request, the action will not
be executed, with no error message or notice.
Is this intended?
Achim Domma wrote:
Hi,
I try to understand how to customize the look feel of my page using
the new skin/layer implementation of version 3.3. I followed the example
on
http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/SimplifySkinning
but still don't understand on how to
not behaving as it
should?
--
Daniel Nouri [EMAIL PROTECTED]
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users
10 matches
Mail list logo
