[pmwiki-devel] Cluster & skin integration
design5 at softflow.co.uk
Sun Mar 18 09:23:36 CDT 2007
Sunday, March 18, 2007, 12:03:06 PM, The wrote:
> Just implemented this capability in Hg--and released the upgrade.
> Works beautifully Hans. Thanks again--you are on a roll!
It would be nice if Hg and Cluster would use the same function and
function name. Then a skin can have the PVs for cluster subpages
defined just once without worrying which clustering recipe is used.
Hg and Cluster are alternative scripts, only one would be used, so
they can use the same function names.
How about ClusteringSubpageName($group, $name) for this function which
generates the group ancestor pagename?
I am trying to achieve a better integration, which will make it
unnecessary to do extensive skin hacks. If it can support both
clustering recipes even better. I am not out to wish to set
preferences for one or the other.
What I would love to see though is a statement in the recipe that it
is released under the GNU open software license. That way I would
feel more comfortable to offer support.
> However I did not want the breadcrumbs to look like the directory
> structure--I want it to look more intuitive to what the viewer is
> thinking. So I used a Site.Breadcrumb page with a bunch of
> conditioals to really rework the breadcrumb in various ways to get the
> effect I need. But with a hierarchical $BreadCrumb variable like this
> new upgrade allows, it takes all the fun out of it. It's now a piece
> of cake!
I think a group ancestor linktrail PV, i.e. breadcrumbs, can be very useful
on a page, perhaps as part of the title section.
I still have an issue in the way you use the term hierarchical in
connection to this link trail, and in connection to the group name
structure employed in Hg and Cluster. You are still calling Hg a
hierarchical groups recipe, even though you try later to explain it is
quasi-hierarchical. It is about sharing and inheriting subpages, group
attributes and group css files from a group whose name acts like an
"ancestor" and is part of the current group name, defined with
separator symbols. And only sharing this when it is missing in the
current group. This to my mind is not hierarchical in any sense, not
even a quasi sense. But it is difficult to describe, as I just found
out typing this.
More information about the pmwiki-devel