Skip to:
Content
Pages
Categories
Search
Top
Bottom

Re: Parent / Childrelationship in forum loop


kevinjohngallagher
Member

@kevinjohngallagher

Well, there’s no good way of putting this without making it look like i’m flogging my own dead horse, but here goes:

Can someone tell me why we’re working out vital data in regards to each forum on as CSS links?

Why on Earth don’t we work out each attribute at the start of the loop, and then feed off an object, giving our template developers and therefore users far more options?

As it stands, we call bb_forum_class(); inside the TR, which then creates the $bb_forums_loop object; which calls classes();, and that works out all the attributes of the forum, but rather than sending them back as a usable object the whole thing returns a string of CSS code.

Why not allow template developers access to:

$bb_forums_loop->first_child

$bb_forums_loop->last_child

$bb_forums_loop->bb_root

etc?

I mean, the code itself if great, and the job you’ve done is really good, but it fixes one singular issue (getting the right CSS output), rather than fixing the bigger problem of not knowing all attributes of the forum. Not only does it lead to very messy templates (if someone can be bothered to deal with it – and i’ve not seen a template that has yet), but it does indeed duplicate alot of the work.

Skip to toolbar