Replying Code Library and Tutors Corner

[wyrd]

I can understand the reason for not allowing anyone to create new threads within these forums, but why is replying disabled? Someone could have a question or comment about the code or tutorial. I personally like comments on things that I program. There's also the fact that if someone has their code or tutorial moved to these forums, they have no way to update it (in which case a mod would have to take their time out to do it).

 

I just think if people were allowed to reply it'd boost interest and perhaps be followed by more submissions.

[Volte]

Questions/comments about the submissions should be directed to PM. Cluttering up the article thread with all kinds of question/comment posts is really not needed and would just serve to make it harder to find other updates and such posted in the same thread.

 

However, I do think that the original poster should be able to reply to his or her own threads to post updates and corrections.

[Derek Stone]

You also have to remember that a bulletin board system isn't exactly the best place for a code repository. We're simply working with what we've got.

[Robby]

Wyrd you make a valid point but Simon has a better point that cluttering up the thread with comments would make it harder to find the updates and such.

 

Honestly, I don't care either way

[Nerseus]

You can, as an alternative, "clutter" up the General forum and reference the tutorial or code library page. If it looks good, an Admin can move it to the right thread. A PM would work, too, but I think some users may not know that feature exists.

 

Granted, it's not as easy as replying directly to the thread, which a moderator could tweak if the topic got out of hand. My biggest fear (relatively small as it is) is that people would post updated versions of the code that might be offtopic or go outside the scope of the original sample. I like the idea of having it kept "clean" since it's sole purpose is to provide easy access to good tips and samples.

 

-Nerseus

[Volte]

Well, it is possible to make vBulletin moderate posts and attachments which are sent to a forum. This is the way the forum was originally set up when I joined EXVBF a couple of years back. Anyone could post or reply to anything in Tutors Corner (Code Library didn't exist at the time), but the posts were sent to a moderation queue which moderators could review and either accept or deny.

 

It would be more work for the moderators (perhaps a system could be worked out so forum leaders could moderate the Code Library and Tutors Corner queue or something) but would allow people to post updates (et al) and still allow the moderators to keep the two forums relatively clean.

[Robby]

Nerseus, that's an idea that's very plausible...

You can, as an alternative, "clutter" up the General forum and reference the tutorial or code library page...

When we create a new thread in CL or TC we can provide a link to the General section whee they can post comments or suggestions.

 

What about this http://www.xtremedotnettalk.com/showthread.php?s=&threadid=78476

[Derek Stone]

As an alternative to posting in the General forum I think it might be wiser to create two subforums entitled "Code Library Discussion" and "Tutors Corner Discussion". This is the model that is used on the vBulletin site, and it works quite well from my viewpoint. It would keep posts out of General and keep the Knowledge Base forums uncluttered. Threads could be created by whomever posts the tutorial/code snippet in the Knowledge Base, or it could be left up to the users to create threads. For the most part I'd prefer the former however.

[wyrd]

Hmm.. well in defense to the original reply, this is after all a discussions forum. I think that it'd be only fitting that we are allowed to publicly discuss code samples and tutorials in an organized fasion, rather then simply creating threads in the general forums (which is quite detached from the actual sample/tutorial, and doesn't invite any comments).

 

However, a person trying to update their old code would indeed have a problem (assuming the reply options was enabled). But, since the threads in these forums can only be created by moderators anyway (which shouldn't be changed), they'd have to contact a mod via PM and ask them to update the original post (like they have to do currently).

[Nerseus]

I like Derek's idea of having a "Code Library Discussion" forum (or subforum, or whatever the powers that be like) for each of those forums.

 

-Ner

[Robby]

Yeah I like that idea too.

[Volte]

I'll throw my "approval" into the ring as well. :) However, we should make it so that only badged members can start threads there too - whenever a code sample or tutorial is posted (or moved by a moderator), whoever did the posting/moving will also create a discussion thread in the appropriate forum. No need to let every user create a thread whenever he/she wants to say one little thing.

[wyrd]

EDIT:

 

You know what, forget this last post (and the one above). I think Derek's idea is the best one out of the bunch. *thumbs up*

 

Removed post

Edited October 23, 2003 by wyrd