Welcome to Geeklog, Anonymous Wednesday, April 15 2026 @ 06:46 am EDT

Comments for Geeklog and Categories

Geeklog and Categories | 3 comments | Create New Account

The following comments are owned by whomever posted them. This site is not responsible for what they say.

sections?

Authored by: Anonymous (Anonymous User) on Wednesday, January 16 2002 @ 01:26 am EST

Hmmm. Honestly, I can\'t fully follow the database logic and I\'d like to pull back to pseudocode or flowcharting. :-) But I think maybe you are complicating things by trying to be too elegantly OOP, so that you can bolt the same structure onto every \'thing.\' I\'m not sure that\'s necessary. Why can\'t the structures be different for different types of things? It\'s not as if the display is the same; categorized links should look very different than categorized weblog entries, no? Or am I just being dense?

I also wonder if you need a full hierarchical system with infinite levels. For many users, couldn\'t you accomplish the same sort of thing by creating sections, i.e., only a one-deep hierarchy? I\'d be quite satisfied with that. Example:
Section: Politics
Weblog entries w/comments
Links
Calendar of political events
Other stuff
Section: Weblog nattering
Entries w/comments
Links
Calendar of GL development deadlines
Other stuff
Section: Computer dating
Weblog entries w/comments
...and so forth.

This would also enable you to empower moderators who are in charge of their sections of entries, links, etc., etc. It would be nice if this could maybe go down another level or two (subsections and subsubsections) but not essential.

In my own case, academia (I teach journalism), sections would allow Geeklog to be used much more easily. It would be scalable for a single course, a department, a college, on up to being a full university system.

As it stands right now, if I want to use one installation of Geeklog as the web home for several different classes --which it should be able to do -- I\'m going to have to do a lot of fudging, e.g., using GL topics as a way to cordon off the different courses.

And then there\'s the issue of user privileges being horizontal. . . .

It\'s late and I\'m not sure this has made any sense. Should I try it again in the morning, or do you catch the drift?

-ES

sections?

Authored by: Tony on Wednesday, January 16 2002 @ 07:04 am EST

Am I being complicated? I don\'t think so. Nothing I mentioned here even relates to OOP so I\'m not following your comment there.

Even for a single nested section you need to know who the parent is, right. So regardless you\'ll need a field that represents who the parent is. To me this isn\'t complicated...just more abstract. I suppose some people could see abstraction as a complicated thing but it really isn\'t.

Also, this is much more flexible than creating new structures for everything that needs to be categorized. Why create 2,3 even 4 tables that all represent pretty much the same thing?

If you can, be more specific about why you think this is complicated because I just don\'t see it that way.

-----
The reason people blame things on previous generations is that there\'s only one other choice.

---
The reason people blame things on previous generations is that there's only one other choice.

Search

Resources

About

Getting started

Support

Development

Topics

User Functions

What's New

Articles last 4 weeks

Comments last 4 weeks

Pages last 4 weeks

Links last 4 weeks

Downloads last 4 weeks