[geeklog-devel] Geeklog Topics and Blocks

[Vincent Furia]

I had done some thinking on this several years ago. The most flexible design
I came up with is using "tag" style backend. Instead of having tid's
associated with stories, there would be topic_assignments (or some better
named...) table allowing a many-to-many relationship between stories (or
blocks, or plugins, etc) and topics.

I went so far as to also consider how to handle sub-topics. Easy way: you
could define topic relationships by having a topic separator (e.g. "-" or
"/") in the topic name. Hard way: create a hierarchal data structure in the
database (parent child relationship, or tree representation similar to how
comments are not handled). The latter design would allow more flexibility,
though the former would be significantly less work to implement.

Any change that modified the database would require quite a bit of work (as
my suggestion in the first paragraph would). If you end up going with any of
these ideas, I had thought out quite a bit more detail if you want it.

-Vinny

On Sun, Aug 21, 2011 at 14:31, Tom <websitemaster at cogeco.net> wrote:

> I have started to do a bit of research/work on my feature request about
> allowing topics to be associated with other objects like staticpages, etc.
>
> http://project.geeklog.net/tracking/view.php?id=1155
>
> I was also thinking about (I haven't decided to tackle it yet):
>
> - Allowing blocks to be assigned to one or more topics and not just one or
> all.
> - Allowing stories (and other objects)  to be assigned to one or more
> topics.
>
> Does anyone have any thoughts or opinions...
>
> Tom
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20110821/fff277d1/attachment.html>