Is this allowed?

[Paul M]

If it's vb2 hack then won't it have needed an extensive re-write to work with 3.5 anyway ? - so not really be using much of the original code ?

[Milad]

Originally Posted by Xenon

well, yes he can post the modification into the supportthread for that hack

does this mean that I can post my port in the original thread?

[Bubble #5]

Originally Posted by Milad

does this mean that I can post my port in the original thread?

Isn't there a section in every hack thread dedicated to hack mods and add-ons? Why couldn't people just simply post their updated versions there, that way it's still in the original thread, everything is above board, and the original coder gets the proper acknowledgment.

I sure do like this bunny :bunny:

Originally Posted by Bubble #5

Isn't there a section in every hack thread dedicated to hack mods and add-ons? Why couldn't people just simply post their updated versions there, that way it's still in the original thread, everything is above board, and the original coder gets the proper acknowledgment.

I sure do like this bunny :bunny:

Yes, but that section is for actual add-ons of major hacks. For instance vbadvance CMPS: there are alot of add-ons that act as modules to vBa CMPS. Also, only the author has permission to add hacks to that field.

Like Xenon said, you may post fixes/ports in the original hack thread, that way you aren't taking any credit of the actual hack.

[Bubble #5]

Thanks for the clarification Danny

Originally Posted by Danny.VBT

you may post fixes/ports in the original hack thread

Serves the same purpose really. As long as a link is provided in the original thread somewhere (for example; a post) that's fine. I suppose this way would be easier for everyone though. However it would be nice to have one central master thread posted somewhere in vB.org that people could subscribe to, where updates of this nature could be listed for those who wish to learn about them. Surely no one here expects every single member to read every old 2.0 hack thread each and everyday, just to see if someone has posted a new update for it. Having a 'update' thread somewhere in vB.org so that coders could post a link to the thread would make good sense :bunny:

[Milad]

Originally Posted by Xenon

well, yes he can post the modification into the supportthread for that hack

Originally Posted by Danny.VBT

Like Xenon said, you may post fixes/ports in the original hack thread, that way you aren't taking any credit of the actual hack.

I have posted my port

Originally Posted by Bubble #5

Thanks for the clarification Danny


Serves the same purpose really. As long as a link is provided in the original thread somewhere (for example; a post) that's fine. I suppose this way would be easier for everyone though. However it would be nice to have one central master thread posted somewhere in vB.org that people could subscribe to, where updates of this nature could be listed for those who wish to learn about them. Surely no one here expects every single member to read every old 2.0 hack thread each and everyday, just to see if someone has posted a new update for it. Having a 'update' thread somewhere in vB.org so that coders could post a link to the thread would make good sense :bunny:

Yes, some centrialized section where updates could be posted seems like a good idea. The only issues is that who would have control over it? We can't have regular users be able to edit update sections, because that will allow abuse of the system. And also, giving the ability to the Authors won't help much because in situations like these...they are not around.

[Bubble #5]

Originally Posted by Danny.VBT

Yes, some centrialized section where updates could be posted seems like a good idea.

Thank you

The only issues is that who would have control over it?

It's just a thread, like any other thread. You wouldn't need a seperate forum category for something like this.

We can't have regular users be able to edit update sections, because that will allow abuse of the system.

See above It's just a thread that members could subscribe to for reference to future updates. For example; Milad could post in the thread I'm refering to with a post something like this:

"Anyone who wants an updated version of the old 2.0 hack called "blah-blah-blah" can find one by clicking this link to original thread. (insert link here)..."


Now anyone who has subscribed to this 'updated hack thread' would receive an e-mail with Milads post in it. If they wanted an update to that 2.0 hack then they could proceed further. If they don't, then they don't worry about it. It's just a thread that will notify members that an old unsupported 2.0 hack has a update available.

[Paul M]

What's wrong with just creating a new thread as an add-on to the original - with links to the original saying this add-on is to convert xxxx to work on vb3.5. Then it's available in the 3.5 area where people can find it, and links back to the original, giving due credit to it.

[Bubble #5]

Originally Posted by Paul M

What's wrong with just creating a new thread as an add-on to the original

Because no one would ever know that it was even there (see #4)

1.) That would create a situation where there'd be a lot of random sorted threads (instead of one central master thread) each containing only one post and...

2.) No one would be subscribed to these 'seperate threads' (unless they were psychic) like they would be with a master thread. A lot of people don't visit here everyday, nor do they read the entire site each time they visit.

3.) Having a lot of separate threads would prevent a key feature of having a central master thread, that being to e-mail members when a new update is listed somewhere else in the forum. A single master thread would send out a new e-mail each time a new update was listed in the master thread.

4.) Every single member is not going to monitor or read every single old 2.0 -3.0 hack thread each and everyday, just to see if someone else has posted a new update for it. However, listing these updates in a master thread would announce these updates easily via e-mail for members who subscribed to the master list.

5.) Having one central master list would make it much easier for people to track down other updates for other hacks, they wouldn't even need to use the search engine, they would simply read the thread to learn about all listed updates.

:bunny: