Modification to vb.org....

[Dark_Wizard]

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?

[KuraFire]

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?
I got a thought:

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.).

[Dark_Wizard]

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....

[KuraFire]

[...] it would require you to install every hack that was released to come up with the info needed [...]
Not true. First of all, a lot of the data can already be presented if the Hack author generates the vb.org post using the HTL, and second of all, you don't have to install anything to get full access using the HTL. You can do test runs of the install so that you can see exactly all the various things the Hack requires/adds/modifies/whatever, or you can choose to import-only the Hack, meaning you don't install anything but you do import all the Hack data so that you can see what all changes without your board being touched.

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.

[Dark_Wizard]

I think that's a much better solution than to have vb.org even more hacked up to pieces for no real reason...

Not true...to have a central location for all this info on vb.org IMO is better and leave it seperate from the vb files so an upgrade won't effect it. Also how much longer do we have to wait on HTL? The longer we wait to do as you said the more out of control this gets to be...

Isn't this asking alot of us hackers as this would require us to check every hack out there?
You can do test runs of the install so that you can see exactly all the various things the Hack requires/adds/modifies/whatever, or you can choose to import-only the Hack, meaning you don't install anything but you do import all the Hack data so that you can see what all changes without your board being touched.

[KuraFire]

Not true...to have a central location for all this info on vb.org IMO is better and leave it seperate from the vb files so an upgrade won't effect it. See, that's not really possible. You can't keep track of all this additional data without making some major changes to the vB files and database.

[Dark_Wizard]

See, that's not really possible. You can't keep track of all this additional data without making some major changes to the vB files and database.

Huh? One small file, a seperate table from vb and a few template edits is what I come up with...

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.... :rolleyes:

[KuraFire]

Huh? One small file, a seperate table from vb and a few template edits is what I come up with...

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.... :rolleyes:
How exactly would you like to add 10 new data fields to a thread using only one small file and some template edits? That's very impressive if you ask me.

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. :)

[Dark_Wizard]

How exactly would you like to add 10 new data fields to a thread using only one small file and some template edits? That's very impressive if you ask me.

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. :)

You have a beta copy I can test then? I would love to see what this really does.

[KuraFire]

You have a beta copy I can test then? I would love to see what this really does. I don't have a beta copy that's ready to test right now. In a way I do, but it lacks a working component (install routine can't actually do the installation of settings, right now).

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. :)