Version: , by Zachery
Developer Last Online: May 2017
Version: Unknown
Rating:
Released: 11-22-2005
Last Update: Never
Installs: 0
No support by the author.
Basicly, were are nearing the final stages of handing over the project to a group of coders so they will be able to continue the work. We would like to keep area51 open but matthew wants to use his license else where, since hies no longer directly involved. (That means we are sans one vB license for area51).
The uShop code is just about ready for a BETA test, it just needs to be packaged, documented, etc. Which will be the responsability of the new coders.
I will be announcing them over the next few days as we finalize some things.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
Look's to me like there was alot more gratitude then complaints as of late. :ermm:
Nono, I ment that I shouldn't complain. I'm really sorry if I made it sound like YOU people were complaining, that's NOT what I ment.
Quote:
Originally Posted by Xplorer4x4
I am just curious why you need a public test board? I offered to test and you said there were pleanty of testers.
Because the way I see it, coding a vB hack has (should have) 4 phases:
1. Localhost testing. You test it on your computer and weed out the obvious errors such as parse errors and blank pages.
2. Privately owned public board. You let some users try out the hack on a public board, but one owned and managed by you so that if something goes terribly wrong or serious bugs appear, it's not the end of the world (or the end of someones forum).
3. Public beta. You release the hack with the Beta tag slapped on it, and make it clear to users that they are installing a hack that MIGHT have bugs, but SHOULDNT have any serious ones.
4. Release. By then you have probably weeded out all but the most obscure bugs, which will either surface come time or remain hidden forever due to noone accessing them.
That way I believe you minimise the risk you are exposing your hacks users for, and in the end create a better product
Nono, I ment that I shouldn't complain. I'm really sorry if I made it sound like YOU people were complaining, that's NOT what I ment.
Now your clear on that.
Quote:
3. Public beta. You release the hack with the Beta tag slapped on it, and make it clear to users that they are installing a hack that MIGHT have bugs, but SHOULDNT have any serious ones.
1. Localhost testing. You test it on your computer and weed out the obvious errors such as parse errors and blank pages.
2. Privately owned public board. You let some users try out the hack on a public board, but one owned and managed by you so that if something goes terribly wrong or serious bugs appear, it's not the end of the world (or the end of someones forum).
3. Public beta. You release the hack with the Beta tag slapped on it, and make it clear to users that they are installing a hack that MIGHT have bugs, but SHOULDNT have any serious ones.
4. Release. By then you have probably weeded out all but the most obscure bugs, which will either surface come time or remain hidden forever due to noone accessing them.
How long does it really take? I mean... I'm not trying to be an ass here... but other people create their very complicating hacks overnight. Hell, I write different scripts in a matter of a few hours. I just find it so hard to believe that it takes this long to release this hack. Maybe I'm being a little ignorant as I am not exactly sure what you're all putting into it, but it's a matter of adding and subtracting points while adding and subtracting options at the same time.
Maybe I have no idea what I'm talking about... but it seems like this has taken far longer than it should have. Either way, I'm still really anxious to see this hack finished. I just hope it happens soon.
If there is anything I can do to help out, please let me know. Even if it means paying for the test board license. =P
An update on whats going on Details »»
About Developer
No support by the author.
12-22-2005, 11:01 AM
LMAO!
