On Sunday 13 August 2006 08:35, Philipp von Weitershausen wrote:
Yeah, I'm not convinced. At least not by the current Boston skin. I find
its code over-structured (subpackages just for the sake of subpackages,
it seems). Also, it isn't as flexible as one would think it is. It
claims it uses
On Monday 14 August 2006 04:30, Michael Haubenwallner wrote:
Stephan Richter wrote:
Lovely Systems, Roger and I have all been in agreement to publish generic
components as we go; if you are subscribed to all check-in messages, you
probably saw already a bunch of packages landing in the z3c
On Monday 14 August 2006 05:27, Philipp von Weitershausen wrote:
[EMAIL PROTECTED] gets messages to *all* checkins, no matter which
package. THe problem is that you guys aren't subscribed to
[EMAIL PROTECTED] so your postings don't show up.
Yes, I am. I switched on the day the list was
On Monday 14 August 2006 05:56, Stephan Richter wrote:
On Monday 14 August 2006 05:27, Philipp von Weitershausen wrote:
[EMAIL PROTECTED] gets messages to *all* checkins, no matter which
package. THe problem is that you guys aren't subscribed to
[EMAIL PROTECTED] so your postings don't show
Jeff Shell wrote:
2. There's an 'add to cart' form that is in this page's main template
(or other)
code, and the user has added something to the cart. The 'update' action of
the form adds the item on a post-back. But because it comes *after* the
'cartContents' content provider, the
On 8/14/06, Stephan Richter [EMAIL PROTECTED] wrote:
Right, so you fixed the problem with the provider TALES expression,
which has to do update()/render() at the same time. My question
is: How do you know which content providers are used by a view? Do you
manually list them?
A Page class (or
