[Zope3-dev] RE: issue 216
Roger Ineichen
dev at projekt01.ch
Mon Mar 21 21:10:23 EST 2005
Hi Roman
> -----Original Message-----
> From: zope3-dev-bounces+dev=projekt01.ch at zope.org
> [mailto:zope3-dev-bounces+dev=projekt01.ch at zope.org] On
> Behalf Of Roman Roelofsen
> Sent: Monday, March 21, 2005 11:26 PM
> To: zope3-dev at zope.org
> Subject: Re: [Zope3-dev] RE: issue 216
>
>
> Hi developers,
>
> I followed this "issue 216" thread with much interest. I´m
> new to Zope 3 (Zope
> at all :-) ) and always asked myself how to provide a UI for
> site visitors
> and admins and what the Zope3-intended way is. Now I know
> that there is no
> "Zope3-way" :-).
>
> While learning Zope3 I´m developing a small sample app for
> myself. I´m now at
> a stage where I must divide my UI for the SV and admins.
>
> My plan is to provide a custom page template for the SV
> pages. This template
> will use the standard_macros/page template and override all
> of the ZMI
> elements, and, of cource, reuse some of them like the banner. In this
> template I implement the user_views and user_actions slots.
> Now my SV pages
> don´t have any ZMI elements but they are still affected by
> the global skin
> which IMHO is importent if I want to use my compontent in
> other sites.
>
> ~ So, what do you think about my approach?
> ~ Is there a better, more "zopeish" way?
Yes, add a own skin, there you can provide whatever you like.
Hm, that's not right. If you inherit your skin from the rotterdam layer
you will inherit all views and pages.
Right now we don't have a clean empty minimal skin layer where you
can inherit without inherit to much views etc.
Perhaps we add this for the 3.2 release. I think Garrett has also
a use for this.
> While trying to find a solution for my problem, I always
> wondered why the
> Zope-skins don´t provide a "userpage" macro like they do
> provide the page,
> views, dialog, etc. macros.
>
> ~ Wouldn´t this solve this problem?
Don't messup the macros with skins. Somtime it's better
to add a new skin then everything catch with permissions
or conditions in TAL.
> Best regards,
>
> Roman
>
Sorry I don't have this much time for explain.
Do you need it right now? I plan to implement
a new skin in about two weeks. There will also
be a presentation skin which shows the use of
site visitor skins.
Otherwise take a look at the skins in the trunk.
This are:
zope.app.rotterdam
zope.app.zopetop
zope.app.boston
Regards
Roger Ineichen
> > Hi Jim
> >
> > > -----Original Message-----
> > > From: Jim Fulton [mailto:jim at zope.com]
> > > Sent: Monday, March 21, 2005 4:18 PM
> > > To: Tres Seaver
> > > Cc: dev at projekt01.ch; zope3-dev at zope.org
> > > Subject: Re: issue 216
> > >
> > > Tres Seaver wrote:
> > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > Hash: SHA1
> > > >
> > > > Roger Ineichen wrote:
> > > > | Can we close the issue 216 which was reported by you?
> > > > |
> > > > | The preview concept works in any situation.
> > > > |
> > > > | That's only a problem of what the index.html
> > > > | page presents.
> > > > |
> > > > | For a project without a own presentation skin
> (index.html pages)
> > > > | is the index.html page used which uses the same menu
> items like
> > > > | the ZMI.
> > > > | That's correct. This is the index.html where you see also
> > > > | if you point the browser directly to index.html.
> > > > |
> > > > | I don't think there is no need for another concept like Jim
> > > > | proposed in the issue.
> > > > |
> > > > | We really have to se what's presented in the index.html view.
> > > > | If this index.html page is uesing the same menu like the ZMI,
> > > > | we have to see this.
> > > >
> > > > Roger,
> > > >
> > > > I do not believe that he original issue has been resolved:
> > > >
> > > > ~ - If the 'index.html' view is intended for use by the :content
> > > > ~ manager", then it needs to use the same macro as the
> > >
> > > other CMF views,
> > >
> > > > ~ in order to preserve the navigation.
> > > >
> > > > ~ - If, on the other hand, the 'index.html' view is
> > >
> > > intended for the
> > >
> > > > ~ "site visitor", it should *not* appear (directly) as a
> > >
> > > tab for the
> > >
> > > > ~ CM; the CM should have a "preview" tab which renders the
> > > > ~ 'index.html' view inside an <iframe>.
> > > >
> > > > ~ Likewise, the SV-centric template should strip out all
> > >
> > > the other ZMI
> > >
> > > > ~ elemetns (the left-hand nav, the Zope3 logo, etc),
> > >
> > > which should *not*
> > >
> > > > ~ be exposed by default to the site visitor.
> > >
> > > I suggest that index.html is for site visitors. I agree that
> > > it should
> > > not be a tab (I didn't think it was). It should also not
> use any ZMI
> > > elements.
> > >
> > > Jim
> >
> > Ok, I know what you mean. You use the ZMI for a project, right?
> > And you need a presentation skin? That's not what we have now.
> >
> > Yes, we don't have a tab in the ZMI for the index.html.
> > But the index.html is not implemented as a pure presentation view
> > for endusers.
> > It's a presentation page but not a hole presentation layer/skin.
> >
> > The index.html views are not useable as a enduser skin.
> > There are loosly views for present a object. E.g the
> > index.html view for the conent type images calls image presentation
> > without any html. Just a xy.gif presentation. You need more
> > then this index.html for make it useable as a presentation UI for
> > endusers.
> >
> > I still think we need a presentation skin for endusers
> > and not only index.html pages/views.
> >
> > Like I proposed before, I can add a new presentation skin.
> > Something like we have in Plone. If we do this, we should use
> > different views and actions like:
> > "user_actions" and "user_views" where we can offer a new namspace
> > for actions and views for endusers if the ZMI doesn't fit.
> >
> > If you can wait, I work on it after the release 3.1. Otherwise
> > I can add a small presentation skin which will fit for what you
> > need.
> >
> > Regards
> > Roger Ineichen
> >
> > > --
> > > Jim Fulton mailto:jim at zope.com Python Powered!
> > > CTO (540) 361-1714
> http://www.python.org
> > > Zope Corporation http://www.zope.com http://www.zope.org
> >
> > _______________________________________________
> > Zope3-dev mailing list
> > Zope3-dev at zope.org
> > Unsub:
> >
> http://mail.zope.org/mailman/options/zope3-dev/r.roelofsen%40tuxed.de
> _______________________________________________
> Zope3-dev mailing list
> Zope3-dev at zope.org
> Unsub:
> http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch
>
>
More information about the Zope3-dev
mailing list