I'm sorry for the asciigram of my class hierarchy being all messed up in my previous post.

(Looked fine in Mozilla Thunderbird but I must have used some tabs between spaces. Everything is scrambled and unreadable.)


Also I may have stated more clearly the goal (which must be obvious anyway) :
'Music' is the page with the "must login" requirement in this mini-site, which triggers the redirect to Login for basic authentication.

There it is again, using "extends" instead of arrows.

Controlers
========

SitePage extends Webkit.Page, MiscUtils.Configurable

   Main extends SitePage

   ... other public pages

   SecurePage extends SitePage

       Login extends SecurePage

       Music extends SecurePage

       ... other "must login" pages

Views
=====

SitePageView

   LoginView extends SitePageView

   MusicView extends SitePageView

   ... other views




And I forgot to give an exemple of Cheetah being sometimes unfriendly with Webware (which might have seemed rather gratuitous). That's not a big point but it annoyed me enough:

Cheetah uses a settings() methods (from SettingsManager) for its own settings.

Webware has the Configurable mixin.

When you mix both in a single hierarchy like in the "standard" inheritance approach, whatever settings you had in the logic part of the servlet is shadowed by template own settings.

That's what I mean when I say that we lack integration : one by one components look good but when we put everything together there are (minor) glitches.


OFS.


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to