The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
Modification to vb.org....
While working on my new vbWar 3.0 for vb 3.0.0 I noticed that each of us that writes hacks will need to enter info into the phrase, phrasetype, language, setting and settinggroup tables and possibly a few others.
My point is can the dev team for vb.org add something into the newpost.php file an area that provides the info used by certain hacks so that we all don't have to research who used what for their hacks this way there is no conflict when an end user installs them? I hope this makes sense... Thoughts/suggestions? |
#2
|
||||
|
||||
Quote:
wait for the Hack Tracking Log. It keeps track of all phrases, phrasetypes, settings, templates, db changes, file changes, etc.etc. etc., for each hack you install (providing it's a hack installed using the Hack Tracking Log, of course). Works like a charm, no need at all for vB.org to do anything at all, as the HTL also has an option to prepare a Hack Release post for you that already lists all major data (new/changed db tables, columns, files, templates, settings, etc.). |
#3
|
|||
|
|||
I would agree only to a certain point...it would require you to install every hack that was released to come up with the info needed so although I love your HTL idea the point is moot...we need a better system here on vb.org to help out us hackers and eventually the end user and an endless frustration level to both....
|
#4
|
||||
|
||||
Quote:
I think that's a much better solution than to have vb.org even more hacked up to pieces for no real reason... That'll only mean that every time they have to upgrade, it'll take ever so much longer again. |
#5
|
|||
|
|||
Quote:
Isn't this asking alot of us hackers as this would require us to check every hack out there? Quote:
|
#6
|
||||
|
||||
Quote:
|
#7
|
|||
|
|||
Quote:
Apparently I thought my idea was good but you seem to be pushing HTL which isn't here yet and IMO will make more work for hackers...I don't need a pissing contest so let's forget I even mentioned it.....case closed.... |
#8
|
||||
|
||||
Quote:
And I can assure you, the HTL might seem like it's more work but it really isn't, in practice. It's saved me an average of one hour per day for working on my vB. And it's saved an endless amount of file edits, too. I now have 8 file / template edits for 4 hacks. Without the HTL that would've cost me about 12. Once I add 4 more hacks to my HTL, I might still remain at 8 file edits, but without the HTL I would've been on 20 by now. And that difference grows exponentially. By the time I have 20 file edits for 10 hacks using the HTL, I would have about 40-50 file edits for 10 hacks without the HTL. Additionally, everything would not be nicely organized if I'd not use the HTL. Also, upgrading my board would be a lot of work, which is not the case when using the HTL. So while it might seem like "a lot more work" to make a hack, it generally saves you ten times as much work (and time) if you use the HTL for each hack you make. But ahwell, I'm not forcing anyone to use it. It's the same with picking money off the street. You don't have to do it, but it does make sense to do it. |
#9
|
|||
|
|||
Quote:
|
#10
|
||||
|
||||
Quote:
However, in a week or two I'll have a Release Candidate that a few people can test. If you want you can get a copy of that, just keep an eye out on the General hack discussion forum for a thread about "Who wants to test out the Hack Tracking Log" over the coming 2 weeks or so. oh, and the thread in my sig already gives a pretty thorough overview of everything the HTL does. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|