[geeklog-devel] Geeklog Document structure

[Web Site Master]

This definitely should take over all tree structures in GL like Topics,
Links, etc.  It's something that has been missing for a while. 

I would also suggest a sort order would also be needed for each category
since alphabetically isn't always wanted (user defined).

How do you get around linking to objects without hard coding for them?  A
few more API plugin functions are needed in general that allow for
returning, what linkable objects a plugin has and a link to a object if an
ID is given.

-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello
Sent: September-26-07 1:58 PM
To: Geeklog Development
Subject: Re: [geeklog-devel] Geeklog Document structure

At 06:27 AM 9/26/2007, Oliver Spiesshofer wrote:
>So a centralized hierarchical topic-plugin might do the trick. A 
>central function that provides a tree-structure and a menu in a 
>block, and a good admin-interface that allows to add static pages, 
>links, events and static pages to it - basically a subtopic feature 
>where what belongs to a topic is managed by the plugin instead of 
>the story/links/elements added, and display those in short lists 
>instead of spreading them all over the page so things can be found 
>by clicking through the tree.

I'd love to see this. In fact, I'll do it as part of the calendar 
bounty if you like.

As a full categories plugin, it requirements are a bit more extensive 
than just provide categories like the links plugin or topics:

* Manage multiple independent hierarchical categories.
* Objects can be in multiple categories in the same hierarchy.
* Objects can be categorized in multiple hierarchies.
* A category contains a unique (within a branch) name, an optional 
long description and full GL permissions. Support for extended data 
should be provided. Topic icons should be supported but not required.
* Support "uncategorized" conditions (in conjunction with the next item)
* Concepts like "default" and "archive" could be managed by the 
category manager, on a per object basis.
* Support topic titles in multiple languages as well as categories 
restricted by language. (Language is one of the reasons an object can 
be in multiple hierarchies.)
* Full extension API with callbacks for
    * Attaching an object type to a hierarchy
    * Notice when categories in linked hierarchies are added, 
deleted, moved or changed
    * Ability to create, modify, destroy hierarchies/categories and 
category/object relationships from code
* Managed block menus for each hierarchy either as a whole or per 
object (the phpblock parameter checkin earlier this year will make this
easier)
* "Directory" pages where the category plugin manages lists/trees of objects
* Updated advanced search options. (Probably a secondary project 
taken on when/if topics are replaced by this plugin)
* SQL-based "flat hierarchies" for system generated categories: like 
users in group X, or stories alphabetically by title (A version 2 
requirement, no doubt)

I have the handling of ad hoc objects somehwat well object-ized in my 
almost released Tags plugin. So porting it to a category plugin would 
be easy. I already need to write a category object for the calendar 
bounty. If it could help all of GL, so much the better.

----
Joe Mucchiello
Throwing Dice Games
http://www.throwingdice.com 

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://eight.pairlist.net/mailman/listinfo/geeklog-devel

__________ NOD32 2550 (20070925) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com