Zope 3.3 I want to add a viewlet to the rotterdam skin. I don't want to create my own skin. is there an accepted way of doing this? I'm surprised that the left sidebar in rotterdam doesn't appear to have a viewlet manager. I have been unable to find any declarations in zcml (grepped for viewletManager through the entire zope source, didn't see anything relevant). It looks like rotterdam makes do with macros, instead of using viewlets. Is there a reason for this? Seems like the left sidebar is perfect for a manager, with a viewlet for navigation and another for the add menu. I am writing a syndication (web feeds: Atom, RSS, etc) package for zope and want to plug my viewlet for accessing feed links directly into rotterdam. Perhaps this isn't the way to do it, but it seems to me that a package like mine that provides general functionality shouldn't define its own skin, but should be usable in other skins. Am I wrong? Thanks, Derek
On 3/23/07, Derek Richardson <derek.richardson@gatech.edu> wrote:
It looks like rotterdam makes do with macros, instead of using viewlets. Is there a reason for this? Seems like the left sidebar is perfect for a manager, with a viewlet for navigation and another for the add menu.
The Rotterdam skin predates viewlets. -- Martijn Pieters
Derek Richardson-2 wrote:
Zope 3.3
I want to add a viewlet to the rotterdam skin. I don't want to create my own skin. is there an accepted way of doing this? I'm surprised that the left sidebar in rotterdam doesn't appear to have a viewlet manager. I have been unable to find any declarations in zcml (grepped for viewletManager through the entire zope source, didn't see anything relevant).
It looks like rotterdam makes do with macros, instead of using viewlets. Is there a reason for this? Seems like the left sidebar is perfect for a manager, with a viewlet for navigation and another for the add menu.
I am writing a syndication (web feeds: Atom, RSS, etc) package for zope and want to plug my viewlet for accessing feed links directly into rotterdam. Perhaps this isn't the way to do it, but it seems to me that a package like mine that provides general functionality shouldn't define its own skin, but should be usable in other skins. Am I wrong?
From what I understand, Rotterdam is pretty old, and people generally create their own skins from scratch.
I don't think a generic component that provides a service (syndication) should be trying to blanket impose a UI. If you want a demo UI, then have a separate package for this, which shows an example UI. The generic component could still have a viewlet, just not wire it up. Martin -- View this message in context: http://www.nabble.com/V-iewlet-in-rotterdam--tf3455247.html#a9639973 Sent from the Zope - General mailing list archive at Nabble.com.
Derek Richardson wrote:
Zope 3.3
I want to add a viewlet to the rotterdam skin. I don't want to create my own skin. is there an accepted way of doing this? I'm surprised that the left sidebar in rotterdam doesn't appear to have a viewlet manager. I have been unable to find any declarations in zcml (grepped for viewletManager through the entire zope source, didn't see anything relevant).
It looks like rotterdam makes do with macros, instead of using viewlets. Is there a reason for this? Seems like the left sidebar is perfect for a manager, with a viewlet for navigation and another for the add menu.
I am writing a syndication (web feeds: Atom, RSS, etc) package for zope and want to plug my viewlet for accessing feed links directly into rotterdam. Perhaps this isn't the way to do it, but it seems to me that a package like mine that provides general functionality shouldn't define its own skin, but should be usable in other skins. Am I wrong?
Quite frankly yes :). Like others mentioned, Rotterdam predates viewlets. But even then... who the @#$()&%*^ cares about Rotterdam. It's ugly, barely functional and quite confusing. If you're writing a syndication package for Zope, the best thing this package can do is provide a nice and clear API to the syndication data. Then people can make use of this API in their own views, viewlets or whatever. -- http://worldcookery.com -- Professional Zope documentation and training
participants (4)
-
Derek Richardson -
Martijn Pieters -
Martin Aspeli -
Philipp von Weitershausen