Home discussions products about writing Projects

Open Source for Collaborative Knowledge Development and Learning

Note: This site's content is accessible to all versions of every browser. However, this browser may not support basic Web standards, preventing the display of our site's design details. We support the mission of the Web Standards Project in the campaign encouraging users to upgrade their browsers.


Blog Entry [details and replies]

KNotations :: Documentation and development plans from the KnowNet development team Weblog 84 entries 23-June-2006 1 authors
show or hide details for this item Cool future feature: sidebar_slots Blog Entry 0 replies 27-November-2004 Mike Malloch
Kind:
Blog Entry
Created:
27-November-2004 11:49:40
Last Updated:
18-January-2005 22:23:07
Author:
Mike Malloch
Status:
visible
I was just thinking about how to get some customisable context into knotes blogs, eg for group tasks which associate a blog, some discussion items and a resource area...

We need in the next few days to have at least a mock-up of using blogs in 'team-tasks' for demonstrating in a couple of our project sites ( team-tasks are knownet's first stab at a goal-directed discussion and resource-development component, not yet productised ). One feature of our current ad-hoc implementations of team-tasks - which do not use weblogs - is a special tool which appears everywhere in the task's content and interfaces, for switching between the discussions, resources, and seed-content. I'd like to have a simple way to get that kind of context-sensitive tool into weblogs.

A natural solution would be to do as the Plone folks did with 'left_slots' etc... a machinery to marshall all the content specified in a ZMI-editable property, fetching content from macros in context. This would be a great way to add sidebar elements to weblogs. In fact it would be a great way to handle the customisation of the sidebar in general. We could have an omnibus macro to call which assembles all the default sidebar elements, which could optionally be replaced as a ZMI property by a series of finer-grained macros for individual elements. This would make it a lot easier for site-admininstrators to customise ( I had envisaged this happening by their customising the sidebar_macros template). The only things I do not like about this are

  • the way that the entire slots property would be what acquisition noticed, rather than individual elements - though this could be overcome by combining slots customisation with template customisation within content
  • the oddities of trying to combine this with user-configurable slots - I suspect that we could make sense of this by having a hierarchy of macro calls, with some common sidebar elements combined in one macro, to effect a mix of fine-grained customisation and sensible acquisition of sitewide defaults or higher-level content-area customisations.

The only other problem is that I never did figure out how the magic of slot marshalling happens, but I suspect it can be done with a wee bit of python :O)

Comments please

If you are already registered here, please click the "Login" button to send your username/password with the comment. Click the "Anonymous" button to leave a comment without logging in.

Please tell us who you are

E-Mail Address (Required)
We need a valid email address in order for you to post a comment. You will recieve an email containing a special validation link. The comment will not be published until validated
Name
Please leave your name
Title
Lead-in
Body Text ( HTML tags are allowed )
Validation
Please enter the text from the image above
Preview your comment