Heads up,
Please review this proposal. I'll implement it
shortly if nobody has objections. We need it for
our work here at the Foliage sprint.
If you have objections, please tell me what
you think is not well done and tell me your
ideas to solve the problem in another way.
http://wiki.zope.org/
Roger Ineichen wrote:
Heads up,
Please review this proposal. I'll implement it
shortly if nobody has objections. We need it for
our work here at the Foliage sprint.
If you have objections, please tell me what
you think is not well done and tell me your
ideas to solve the problem in another wa
On 9/23/07, Roger Ineichen <[EMAIL PROTECTED]> wrote:
> Heads up,
>
> Please review this proposal.
OK. I have to admit that I don't fully understand it.
> This proposal describes a way to make the usage of such built in views
> optional.
"Such built in views" means what? "Optional" how? And why
Hi Lennart
> Cc: Adam Groszer; zope3-dev@zope.org; [EMAIL PROTECTED]
> Betreff: Re: [Zope3-dev] Proposal, free views
>
> On 9/23/07, Roger Ineichen <[EMAIL PROTECTED]> wrote:
> > Heads up,
> >
> > Please review this proposal.
>
> OK. I have to admit that I don't fully understand it.
>
> > This
Hi Martin
> Betreff: [Zope3-dev] Re: Proposal, free views
>
> Roger Ineichen wrote:
> > Heads up,
> >
> > Please review this proposal. I'll implement it shortly if
> nobody has
> > objections. We need it for our work here at the Foliage sprint.
> >
> > If you have objections, please tell me
Hi Roger,
Big +1,
That would separate the browser part from the component part.
Who knows what UI I want for a reused component, might even be that none!
On 9/23/07, Roger Ineichen <[EMAIL PROTECTED]> wrote:
> Heads up,
>
> Please review this proposal. I'll implement it
> shortly if nobody has o
Roger Ineichen wrote:
Please review this proposal. I'll implement it
shortly if nobody has objections. We need it for
our work here at the Foliage sprint.
If you have objections, please tell me what
you think is not well done and tell me your
ideas to solve the problem in another way.
http://w
Roger Ineichen wrote:
This proposal describes a way to make the usage of such
built in views optional.
"Such built in views" means what? "Optional" how? And why?
I mean with built in views just views which comes within a
package. Such view component are located in the browser folder
and bui
Hi Philip
> Betreff: Re: Proposal, free views
>
> Roger Ineichen wrote:
> > Please review this proposal. I'll implement it shortly if
> nobody has
> > objections. We need it for our work here at the Foliage sprint.
> >
> > If you have objections, please tell me what you think is
> not well do
Roger Ineichen wrote:
* Simply *ignore* that they exist. Zope actually has
facilities for doing this on a technical basis. Simply don't
inherit your skin from IDefaultBrowserLayer, and voila, you
won't get any pre-configured views at all.
I can't have unused code in our codebase. We have swi
Hi Philipp
> Betreff: Re: AW: Proposal, free views
>
> Roger Ineichen wrote:
> >>> This proposal describes a way to make the usage of such
> >> built in views optional.
> >>
> >> "Such built in views" means what? "Optional" how? And why?
> >
> > I mean with built in views just views which comes
Hi Martin
> Betreff: [Zope3-dev] Re: AW: Proposal, free views
>
> Roger Ineichen wrote:
>
> >> * Simply *ignore* that they exist. Zope actually has
> facilities for
> >> doing this on a technical basis. Simply don't inherit your
> skin from
> >> IDefaultBrowserLayer, and voila, you won't get
Hi,
Am Sonntag, den 23.09.2007, 23:52 +0200 schrieb Philipp von
Weitershausen:
> I understand the motivation. But I don't agree with the solution. I've
> you're not ok with the existing views, then you currently have two options
>
> * Simply *ignore* that they exist. Zope actually has facilities
On 9/23/07, Roger Ineichen <[EMAIL PROTECTED]> wrote:
> > "Such built in views" means what? "Optional" how? And why?
>
> I mean with built in views just views which comes within a
> package. Such view component are located in the browser folder
> and built on the BrowserPage classes. I guess the te
14 matches
Mail list logo
