Re: tiles/blocks
Dylan Jay <djay-n0pU0XVUApFWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
On 25 Apr 2014, at 7:11 pm, Guido Stevens <[email protected]> wrote: > On 04/24/2014 01:22 AM, Dylan Jay wrote: >> >> Maybe it's clear to others but I'm still confused by who you want to create the layouts and who you want to insert the tiles and what the skill level of each kind of user is? >> Know who we want to do what really helps understand what we build. >> >> What is it you are thinking of? >> >> --------------- >> theming space | >> --------------- >> sitesetup | >> --------------- >> content space | >> --------------- > > You're missing the key of my use case, which is: application space. I by "space" I mean a place where a certain kind of user can do things. - a themer will on a diazo theme in the theme control panel. They might also work with portal_skins or portal_customerize etc. They might also use an editor and create browser view overrides. - an admin makes decisions about maintaining users, content rules, workflow etc so generally their space sitesetup, and perhaps top level sharing tabs. - an editor/contributor makes decisions about adding new pages, editing etc so their space is the plone content UI. add-new menu, /edit etc. ie, What I'm trying to get out of you is who is creating the rules that a machine will obey? Or which combination of user roles will make these decisions? > want *the system* to make render-time decisions on both which > blocks/tiles to render and in which layout to do so. > > | As a developer > | I want to dynamically combine multiple information streams > | in order to render a context-sensitive personalized user interface. I think I might know what you are getting at, but it would certainly help if you gave concrete examples. For example: An admin fred wants to have some a home page whereby users that don't have permission to access certain tiles won't see them. And when they won't see them the page still looks good? So somehow the themer has to create a layout flexible enough to work with arbitrarily appearing and disappearing elements? I'm guessing you want more than this, but is this the kind of thing you are thinking of? We did have a need for layout like this once and we used PloneContentPanels with alias plugin so the panels would disappear when you didn't have permission. The usecase hasn't really come up since. It's something I thought collective.cover can handle and is something I'd expect only comes up when you have logged in users like in an intranet. > > :*CU# > -- > Guido Stevens | +31.43.3618933 | http://cosent.nl > > s o c i a l k n o w l e d g e t e c h n o l o g y > ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs