Differences between DB editors

A few times the question "How do the DB editors differ from one another?" was raised.

So, lets have a look starting with Codeimp's Doombuilder2.

Not much happens between editing modes, except for indicating which mode is in focus on the top toolbar. On the right sidebar is the plugin for Undo/Redo.

Next, let's look at DoombuilderX which is a rewrite of DB2 by anotak

Depending on which mode is in focus some capabilities appear or disappear on the top toolbar, which now also incorporates the default plugins. Again, there is the right sidebar for Undo/Redo.

Continuing on, here is GZDoom Builder, a rewrite of DB2 by MaxED, to incorporate some GZDoom features.

Again, depending on the editing mode used some capabilities appear and disappear. The most pronounced feature is the separation of the mode features on top toolbar and the editing features and plugins on the left sidebar. Plus, there is the right sidebar showing more plugins.

And lastly, GZDoom Builder - Bugfix by ZZYZK, which is the continuation of GZDB.

While ZZYZK is no longer involved with the maintenance of the editor, it is boris who stepped up to the plate.

Revisions are from version r1 to r3086 (current as of Oct. 13, 2019)

Interesting.

What's the minimum window size?  For example, if you were stuck on a 1024x768 monitor would DB2 (etc) still be usable?

On 10/30/2019 at 2:48 AM, andrewj said:

Interesting.

 

What's the minimum window size?  For example, if you were stuck on a 1024x768 monitor would DB2 (etc) still be usable?

For the main editor window there's no size limitation. The limiting factor are the sector/linedef/thing editing dialogs. They fit just fine on 1024x768. The linedef editing dialog for UDMF barely fits in GZDB(-BF), since it's much bigger to accommodate all the options. If Windows is set to use DPI scaling of >100% it will not fit.

You forgot to add Doom Builder, the granddaddy of them all!

Man it's so hard to use now, not quite as bad as going back to the truly ancient editors, but it doesn't do anything automatically for you. You can't separate one sector into two by simply drawing a line between them, oh no. You have to trace the whole thing out. It's so awful and I find it hilarious that even despite how bad it is, it's still better than everything there was before it, at least as far as what I've attempted to use.

I still see that some people are using it from time to time. Up til late 2016, I was one of those people. For the 10 of you out there still using DB1, please switch. It'll be the best choice you make as a mapper.

A couple of nitpicks

On mardi 29 octobre 2019 at 11:49 PM, Kappes Buur said:

rewrite of DB2

They're forks, not rewrite. DB2 is a rewrite of DB1, it has basically nothing in common except the name. All the code was rewritten, notably since it's in C# while DB1 was in Visual Basic.

DBX and GZDB may have rewritten some parts, but the bulk of the original DB2 code is still there. They've focused on adding their own features, fixing some bugs, etc.

On mardi 29 octobre 2019 at 11:49 PM, Kappes Buur said:

ZZYZK

ZZYZX

6 hours ago, Gez said:

DB1 was in Visual Basic

The GUI was in VB, but lots (most? all?) of other stuff was in C++.