The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#21
|
|||
|
|||
Quote:
btw, my hat's off to those like NTLDR that provide solid, genuine support and quality hacks for people.. for free.. i know there are many others, but i have occupied a lot of NTLDRs time and he has always been more than gracious in his responses and patience.. |
#22
|
||||
|
||||
Yes, NTLDR is one-of-a-kind. If more members here would take after him, I think we could get on the road to recovery here at vb.org. I try, but I'm not anywhere close to being proficient at coding yet. (Just look at my hacks to prove my point. )
|
#23
|
||||
|
||||
Quote:
|
#24
|
||||
|
||||
Quote:
You're not so bad, Boofo! I've not seen any of your current works, but you're pretty good imho. *echos sentiments about NTLDR and his excellant support* |
#25
|
||||
|
||||
Quote:
I STILL have a lot to learn. My hacks are simple hacks that almost anyone could do. And where have you been, young lady? |
#26
|
||||
|
||||
*doesn't veer off topic but mentions work has been keeping me rather busy* love the sig, btw.
Also, I agree with your post above, Boofo, about banding together. It's frustrating for members upgrading to vb3 but would like to keep some of the custom features from vb2 hacks. I realize some of the more proficient coders have too many hacks to rewrite, but if there's no intention of upgrading the hack then why not allow someone else to use it? Everyone says "don't use the same code and it's okay" but ... code is code and I imagine in many cases (not all) some of the same code will have to be used as that's the way it goes. ... Oh well. I don't write hacks, so I probably shouldn't comment too much. /me cheers the hack writers and all their efforts and contributions |
#27
|
||||
|
||||
The great thing about vB3 though is that quite a few of the hacks we had to install for vB2 are now included in vB3. That makes it a lot easier on deciding what hacks to convert. And with the conditonals, now a lot of the old hacks can be done right in the templates.
|
#28
|
|||
|
|||
If some one is going to take a vb2 hack, make it work for vb3, and doesn't mention they used part of the vb2 hack, then that is wrong. But if the converter mentions you, as the orginal creator of the hack.. what's the big deal? It's not like they are taking credit for it all, just saying they convereted it over to vb3.
Am I missing something? |
#29
|
|||
|
|||
don't use any part of the code itself.. in other words, you create the entire coding for the vB3 version.. no copy paste.. although there are so many changes with vB3, copying and pasting wouldn't be recommended anyway..
|
#30
|
|||
|
|||
Quote:
Hackers vs Hackers: Does anyone here copyright php code? Does anyone fork out ?300-400 to copyright an open source hack? "Ownership" of hacks should be changed - aslong as credit is given where credit is due - anyone should be allowed to modify code and release it, I'm not saying take hack x call it hack y and release it, I mean; if the way the hack runs is significantly improved or changed why cant it be shared on vb.org? What's the problem? If as a hack creator you dont like this simply take your code down to the copyright offices and get it copyrighted. Recent example: I created a shoutbox addon for vbindex (it adds a shoutbox to the forum home display and also adds top 10 shouters and number of shouts a member has made) Some of the queries where the same as those via the original vbindex code, have you not heard the expression: Don't reinvent the wheel. The addon did use a large amount of code from vbindex but it was an addon and credit was given, still NTLDR removed the addon. I released this because, I wanted it so I figured someone else may want it. That should be the reason hacks are released. (Unless someone wants a hacker to make a hack) My addon added atleast 4 major things: shoutcounter, forum home display, forum home shout adding, top ten shouters. It is absurd to remove an addon which adds something just because someone else made it using some of your code. Hackers Attitude: This leads on to overall hackers attitude to eachother and to non hackers:
support I enjoy supporting my hack(s), however frustrating, it gives ideas for improvement, bugfixes and improves the community feel of vb.org. Some hackers don't like to support their modifications, and that's fair. Hacks are released under no obligation or warranty, I don't think anyone has the right to complain or demand anything from anyone on this forum. Basicly I agree with the first post: - hacks should not have strict ownership aslong as credit is given. Hackers are working together not in competition. Ok it's a male dominated community but why compete over something so pointless. - vb.org needs to address this issue, the forum does need opening so that there is a clear catagory to talk about making mods and hack in progress areas and other such stuff... |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|