The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
|
#11
03-10-2005, 05:32 PM
|
||||
|
||||
I generally only release code that I am going to use myself in some way. I figure, the work is done anyway, why not share? I am not microsoft and am not being paid for the code. So, my target audience is NOT non-coders. My target audience is coders who also release their work.
This way, I get a benefit because my code gets tested harder and sometimes useful feature additions are suggested. And, my fellow coders get the benefit of having something that they can use in some fashion or another. I will agree that most people should release their hacks to the beta forum first and let the kinks in installation instructions get worked out. I also think the current sorting system brings some of the worst hacks up to the top instead of letting them sink. Unsupported code often has the most cries for help, which means it stays at the top of the heap and gets more attention, more installs by people who don't READ before they try to install and then more replies, which keep it at the top. If you want to avoid bad code, it's your job to read and see if users are having problems. If you can't code yourself, don't install very new modifications. Give them time to either have the kinks worked out or to prove that they are stable. 
|
|
#12
03-10-2005, 05:35 PM
|
||||
|
||||
|
i always look over the hacks before installing them, and will test them out first. and i don't find a lot of them to be buggy, they work for the system that the creator made them for, for the most part.
|
|
#13
03-10-2005, 07:13 PM
|
||||
|
||||
|
Quote:
Not saying this is always the case and I know that some hacks really are full of bugs, but alot of times the so called "bugs" are due to the user trying to install the hack on a vb version which it wasn't designed for, a conflict with another hack or the user not following the instructions carefully. You can't hold the coder responsible for any of those things. As for support, most of us work full time jobs (50-60 hours per week for me) and can't dedicate all of our spare time to supporting free hacks. I do the best I can but its just not possible to answer every single question. Sometimes you have to rely on the hack users to help eachother.
|
|
#14
03-10-2005, 08:03 PM
|
|||
|
|||
|
Quote:
|
|
#15
03-11-2005, 02:09 AM
|
|||
|
|||
|
Quote:
 We can't simply delete hacks because they have bugs or problems. It is up to the hack author to update his code and up to the user to research and test this code before hacking their board. If anything these bits of 'crap' code as you call it can always be used by other coders. I can't tell you how many times I have taken someone else hack and made it my own for my own needs. Coders don't spend every waking hour here supporting their hacks. Most of us code something for ourselves and release it. We may never improve that code again because it dose what we need it to, while everyone that installed it crys for improvments. At this point your coding the new version for others needs, and that always gets pushed back to make room for your own needs. This is why updates tend to come slower or never at all. Quote:
|
|
#16
03-12-2005, 02:36 AM
|
|||
|
|||
|
It might be useful if another row of options could be added to accompany:
Supported DB Changes Installer included Which might include: Support Withdrawn Add-ons Permitted And another which would indicate that the hack is "closed" or will not be developed further by the original hacker (not sure how best this could be worded). If all these options were available to the hacker, could they possibly prove useful to everyone?
|
|
#17
03-12-2005, 04:43 AM
|
||||
|
||||
|
Quote:
Addon's are always permitted, I can't think of a reason they wouldn't be. Its not like you are re-releasing the whole bit of code.
|
|
#18
03-12-2005, 06:32 AM
|
|||
|
|||
|
Quote:
Take, for example, a hack with 300 support posts. In the first 200 posts, the hacker offers support. Along about post 201, the hacker stops. This always results in a lot of exasperation for everyone and a "support withdrawn" box would be bit of clarification. Quote:
|
|
#19
03-12-2005, 09:31 AM
|
||||
|
||||
|
Let me make my position absolutely clear.
I believe that the administration of this board has an obligation and a responsibility to all users to ensure that the code that they use is functional. That it works. That its fit for the purpose for which it was intended. i respect the time and effort involved by all coders..I DO NOT make any attack upon the individual!....NO! Please do not misunderstand me here. Its just that I feel that the crew should be more aware of the image that is projected. After all, we are all professional and that is the way it should be. The coding should reflect professionalism as well. For one, I am grateful for any snippets that come my way but they must be accurate and have good code protocol and syntax and reflect a good degree of know-how and professionalism as opposed to spaghetti code. I trust that the above makes sense.
|
|
#20
03-12-2005, 09:58 AM
|
|||
|
|||
|
Quote:
Quote:
Quote:
|
 |
«
Previous Thread
|
Next Thread
»
Linear Mode
|
|
All times are GMT. The time now is 01:01 PM.