Well being Open Source, she probably got her own 'variables'. So no wonder she leave you alone. ;)



* MarcoH64 just got inspired by this thread and goes out to look for some nice new 'variables' for himself. :D Lol being an experienced vB user, i might even test some beta's

Great Idea!!! NOT

I don't harrass any of the coders here, but yet because I'm not a coder you think that I shouldn't have access to them, along with the thousands of other users? LOL - Well for your information I'm sure most of the hack creators here don't create them for people like you, they create them for people who are in need of the hack regardless of if they can code. In fact, I see a vbulletin modification site being more useful to users who can't code rather than who can code. I imagine you think Jelsoft designed vbulletin only for experienced users like you. (I don't think so)

If there are too many people asking "dumb" questions, the coder has the option of not wasting his time responding to each of them in case you didn't know. Why don't you blame the author for making you wait longer, they're the ones who release it. If you're such an excellent coder why don't you make your own needed hacks instead of blaming non coders like myself for making you wait longer.

If you want a solution that works instead of making it against regulations for non technical users to use these hacks, why not make it common knowledge that questions will be answered on a limited basis, or not at all, during the beta phase?

I just put up 7 paid hack requests, I guess I should be flagged and have my viewing rights revoked because I must not be too experienced. I think you're asking for too much control. :disappointed:

yayvb - I think he was just making a point that sometimes coders get bogged down answering questions that are either answered in posted or readme material or they start feature requesting the author to death.

Beta projects (unless otherwise mentioned) are not generally designed for a wide audience. They are usually designed for experienced users who can 'open up the hood' and fix something by themselves in a rut. They are put up so that other users can contribute with their feedback or even to help fix problems. Though non technical users are great with feature suggestions or reporting when something doesn't work (which are both valuable contributions) beta stages are tough to support to people who don't know vb, php and/or sql.

As far as a coder not responding to posts - of course that is their choice - but its akin to committing reputation suicide with a dull spoon on a site like this (in other words: not advisable).

I think a very obvious disclaimer should be placed in all beta threads. Such like the one I put on all my BETA modifications:

"This hack is in it's early BETA stages, and it should be used for DEBUGGING purposes only. "

I think it will be too difficult to determine who is "eligible" to use beta hacks.

^ ^
quiz :p

yayvb: Stop using the products of your website and pay attention. Look at the thread I posted in the beginning of this thread.

Geek: Open Source or 'malware' isnt that what marriage is about?? :)

-Jason

Perhaps some kinda Support FAQreation mod? ...

Select a post (that is to be the FAQ Answer)

- Make FAQ? Y/N

- Enter Title / Description

- Submit > FAQ is entered into (HAQ FAQ) page, which is linked from top post in thread.

- FAQ Management - ability to change sort order of FAQs

Just tossing around some ideas, and would also hope that folks with no coding experience, but who have suggestions that could improve a Beta, and have a vested interest that the hack works in practice and not just principle be not excluded from Betas.

~ Mark

That isn't a bad idea, but it's alot to code ;)

Chris

most of the time, i noticed if an author has to repeatedly explain what the hack is for (beta or not).... it a hint that maybe the first post explanation should be more detailed. plain and simple.

that's just what I noticed. it goes down significantly with very detailed and screenshot rich first posts.

and if there are repeat questions...the authors just referrs them back to the first post. (or other thread goers).

getting lost in a thread finding answers to questiosn already asked is a big issue... as such, I think MJM's post is great idea. for thread readers, authors, n00bs and experienced coders/mod users alike.

When a hack is released in beta form you are going to confuse newcomers. They haven't been doing this long enough to grasp the basics yet. But they haven't been burned real bad either - yet - so they're going to venture in and try to install complex hacks and beta hacks. They really should hold off until they've been through some simple ones... but they really don't know that.

There's really only a couple of things the hack author can do to make this more clear -- warn inexperienced coders it's not a final release ... use good screenshots (as mentioned above) ... and keep updating the first and second post in the thread with the LATEST information and easy-to-find answers to those repeat questions they keep getting in the thread.

It's not just beginners who get lost in this. The rest of us get busy or we're too lazy. Alot of people just read the first 5 pages and the last 5 pages ONLY before scampering off to install it.