switch to vbulliten forum engine

Econinja

chuckdaboss wrote:
Why should we switch to vbulliten forum engine?
Polls // Only useful in Suggestions, -1
You can see whether you posted on a thread before // Already here, -1
Hot threads // People will then boast “Hey, I'm so popular because I've got a hot thread!”, -1
Subforums // Already here, -1
Quotes have a link to the original post // Isn't it simple to just scroll up and find it? -1
Exact number of posts // So more boasting about posts! -1
Reason for editing // Could see as useful, +1 Read some arguments, -1
[video] tag // Yes I got the secret message and -1, I think Scratch's YouTube player is enough
more diverse emoji // MORE SPAM! -1
more bbcode tags // What about them? 0
^^^ this is why
Support please
Reason for editing: added more reasons

Comments above. Rating: -9/10. No support.
Reason of editing: Editing! :P

Last edited by Econinja (July 10, 2015 01:07:12)

VoltageGames

CatsUnited wrote:
TheHockeyist wrote:
chuckdaboss wrote:
TheHockeyist wrote:
No support. This would bring a lot of confusion and rage.
how?
-snip-
Hot Threads are threads that are considerably popular, getting a bunch of posts in a short amount of time and they have a special icon, which varies from forums to forums.
By subforums, he means we split the suggestion forum into “website suggestions” and “editor suggestions” (just an example).

gdpr533f604550b2f20900645890

TheHockeyist wrote:
chuckdaboss wrote:
TheHockeyist wrote:
No support. This would bring a lot of confusion and rage.
how?
Everyone's used to this system. If we were to change, there would be a lot of users complaining and wanting to go back to the old system. It would be very hard to get used to.

Wasn't the transition from 1.4 to 2.0 a big transition? Yet it happened. Change is not necessarily bad.

I wasn't there for 1.4, but I've seen enough screenshots and read enough about it to know it was a big change.

TheHockeyist

Chibi-Matoran wrote:
TheHockeyist wrote:
chuckdaboss wrote:
TheHockeyist wrote:
No support. This would bring a lot of confusion and rage.
how?
Everyone's used to this system. If we were to change, there would be a lot of users complaining and wanting to go back to the old system. It would be very hard to get used to.
Wasn't the transition from 1.4 to 2.0 a big transition? Yet it happened. Change is not necessarily bad.

I wasn't there for 1.4, but I've seen enough screenshots and read enough about it to know it was a big change.

Not necessarily, but if it was a surprise, how many users would object? I suspect at least 95%.

gdpr533f604550b2f20900645890

TheHockeyist wrote:
Chibi-Matoran wrote:
TheHockeyist wrote:
chuckdaboss wrote:
TheHockeyist wrote:
No support. This would bring a lot of confusion and rage.
how?
Everyone's used to this system. If we were to change, there would be a lot of users complaining and wanting to go back to the old system. It would be very hard to get used to.
Wasn't the transition from 1.4 to 2.0 a big transition? Yet it happened. Change is not necessarily bad.

I wasn't there for 1.4, but I've seen enough screenshots and read enough about it to know it was a big change.

Not necessarily, but if it was a surprise, how many users would object? I suspect at least 95%.

Then the Scratch Team should announce the change ahead of time.

The_Scratch_Squad

1. What exactly are “hot threads?”

2. No polls. You should always post your opinion.

3. What subforums?
Details please.

4. No support. There is no reason to do it automatically. Just include the link from the source…

5. Exact number of posts can create competition… That is not the point of Scratch.

6. Put it beneath your original post…

7. Just put a link…

8. More Scratchicons? Eh… No support. Its already spammed at times, and I can't think of a reason to add them…

9. Why? I think the codes we have are all right.

10. There needs to be a gradual change. Think about it. If 4/5 fish were used to be in an environment with very clan water, with pH of 5, they would be fine. 2 years later,move them to a tank with 8 pH, they would probably panic for a while…
Same with scratch.

Last edited by The_Scratch_Squad (July 10, 2015 00:58:26)

jvvg

I would like to point out that switching to vBulletin would not be technically feasible for two reasons:
1. They use different database systems, and converting between them would be extremely difficult to impossible
2. This website uses the Django/Python environment. vBulletin was programmed in PHP. This server would likely not support a PHP script, and even if it did, it would be difficult to integrate it with the Scratch website since they are mutually incompatible.

gdpr533f604550b2f20900645890

jvvg wrote:
I would like to point out that switching to vBulletin would not be technically feasible for two reasons:
1. They use different database systems, and converting between them would be extremely difficult to impossible
2. This website uses the Django/Python environment. vBulletin was programmed in PHP. This server would likely not support a PHP script, and even if it did, it would be difficult to integrate it with the Scratch website since they are mutually incompatible.

No support as per this, then.

thecontestmagic

Chibi-Matoran wrote:
jvvg wrote:
I would like to point out that switching to vBulletin would not be technically feasible for two reasons:
1. They use different database systems, and converting between them would be extremely difficult to impossible
2. This website uses the Django/Python environment. vBulletin was programmed in PHP. This server would likely not support a PHP script, and even if it did, it would be difficult to integrate it with the Scratch website since they are mutually incompatible.
No support as per this, then.

Firedrake969

jvvg wrote:
I would like to point out that switching to vBulletin would not be technically feasible for two reasons:
1. They use different database systems, and converting between them would be extremely difficult to impossible
2. This website uses the Django/Python environment. vBulletin was programmed in PHP. This server would likely not support a PHP script, and even if it did, it would be difficult to integrate it with the Scratch website since they are mutually incompatible.

Even if it is compatible (which it could be - firsthand experience having Zend and Django working together), it would most likely take a large transition - Django models are extremely different from most, if not all, of PHP's database systems (although, as stated, it's possible to make them work together), which would probably require a database reset/rebuild (losing all posts). I'm not sure how much DjangoBB is integrated with the main site (if it's also in Django), but that would require an even larger reset and rebuild.

Epicness123

TheHockeyist wrote:
CodingKyle123 wrote:
TheHockeyist wrote:
chuckdaboss wrote:
TheHockeyist wrote:
No support. This would bring a lot of confusion and rage.
how?
Everyone's used to this system. If we were to change, there would be a lot of users complaining and wanting to go back to the old system. It would be very hard to get used to.
Well, they would just have to get used to it. There are a lot of pros to this new forum if they do decide to switch
*insert typical flaming here should the switch be implemented*
What would you rather see? No flaming or excessive flaming?

Heck, this thing used FluxBB before the 2.0 website. No complaining.

CatsUnited

Epicness123 wrote:
TheHockeyist wrote:
CodingKyle123 wrote:
TheHockeyist wrote:
chuckdaboss wrote:
TheHockeyist wrote:
No support. This would bring a lot of confusion and rage.
how?
Everyone's used to this system. If we were to change, there would be a lot of users complaining and wanting to go back to the old system. It would be very hard to get used to.
Well, they would just have to get used to it. There are a lot of pros to this new forum if they do decide to switch
*insert typical flaming here should the switch be implemented*
What would you rather see? No flaming or excessive flaming?
Heck, this thing used FluxBB before the 2.0 website. No complaining.

FluxBB has a similar design to Django, the main difference is that Flux uses PHP.

jvvg

CatsUnited wrote:
Epicness123 wrote:
TheHockeyist wrote:
CodingKyle123 wrote:
TheHockeyist wrote:
chuckdaboss wrote:
TheHockeyist wrote:
No support. This would bring a lot of confusion and rage.
how?
Everyone's used to this system. If we were to change, there would be a lot of users complaining and wanting to go back to the old system. It would be very hard to get used to.
Well, they would just have to get used to it. There are a lot of pros to this new forum if they do decide to switch
*insert typical flaming here should the switch be implemented*
What would you rather see? No flaming or excessive flaming?
Heck, this thing used FluxBB before the 2.0 website. No complaining.
FluxBB has a similar design to Django, the main difference is that Flux uses PHP.

I think DjangoBB is basically someone trying to create a version of FluxBB in Python. If you look, they are actually very similar in terms of features, though the inner workings are pretty different.

dude341

CodingKyle123 wrote:
chuckdaboss wrote:
dude341 wrote:
V-Bulletin would lose a lot of Scratch integration. No support.
what do you mean
Yeah, what do you mean by it would lose “a lot of Scratch intergration.”???

DjangoBB is very well integrated with Scratch. V-Bulletin is not, and I've used it (It's bad)

chuckdaboss

dude341 wrote:
CodingKyle123 wrote:
chuckdaboss wrote:
dude341 wrote:
V-Bulletin would lose a lot of Scratch integration. No support.
what do you mean
Yeah, what do you mean by it would lose “a lot of Scratch intergration.”???
DjangoBB is very well integrated with Scratch. V-Bulletin is not, and I've used it (It's bad)

Its not!

CatsUnited

chuckdaboss wrote:
dude341 wrote:
CodingKyle123 wrote:
chuckdaboss wrote:
dude341 wrote:
V-Bulletin would lose a lot of Scratch integration. No support.
what do you mean
Yeah, what do you mean by it would lose “a lot of Scratch intergration.”???
DjangoBB is very well integrated with Scratch. V-Bulletin is not, and I've used it (It's bad)
Its not!

Any evidence?

Blank1234

V-Bulletin might be good, but if we switch to that, we lose all the scratchblocks and other scratch only forum features

So basically this:

dude341 wrote:
V-Bulletin would lose a lot of Scratch integration. No support.

Last edited by Blank1234 (July 13, 2015 13:18:46)

chuckdaboss

Blank1234 wrote:
V-Bulletin might be good, but if we switch to that, we lose all the scratchblocks and other scratch only forum features

So basically this:
dude341 wrote:
V-Bulletin would lose a lot of Scratch integration. No support.

that's true, but I don't know if we would lose

scratchblocks :: motion

DaSpudLord

No support due to pretty much everything said above.

chuckdaboss

Closed because it was a bad idea in the first place.

Discuss Scratch