MWEdit

[DeVaultSetter]

From the Sourceforge page:

An alternate editor for the Elder Scrolls: Morrowind computer game. Similar in appearance to the official construction set editor but with the edition of many features to make mod editing easier.

Snip from the SW thread:

Do wonder how difficult it’d be to swap DeviL out for something more supported like GraphicsMagick (assuming I understand the usage of the image library in this instance; if not, there are others to choose from).

Due to its age, the code may need some additional updates to be compatible both with modern compilers and the APIs of modern systems. Quite a few things have changed in the standard in the last twenty years. Running a compiler in dry run mode would help track all of that down along with Cppcheck which we’ve used before.

It’d be nice to get working cross-platform as well since OpenMW works across several platforms. That’d require something like GTK or Qt.

Another thing missing is the code license and the headers don’t give much clue either. Should still be possible to contact Dave over at UESP, though.

I know CMake has a VS plugin that integrates it with Visual Studio. Not sure about Meson about I’ll definitely take a look.

It is the most excited I’ve been about a project in years. May be worth looking into more 🙂

Found the solution if you want to see what happens. I’d be a little surprised if it builds out of the box, though.

As I recall, if it’s under GPL then all future changes need to be under the GPL unless permission is granted from all parties who contributed code to change the license. Other licenses aren’t as strict about it. Not too familiar with the MIT license, even though I’ve seen it around a lot. Just never really got around to reading up on it 😛

Will look at sending him a note. 🙂

Will get it going on the other machine soon!
One of the first issues is to convert to vcxproj and another is to ditch the vcclcompilertool, then, after a few moves, ultimately get to the bugs. 🙂

[Spastic Hamburger]

Here’s what I’m thinking of in terms of priorities:

1. Get it to build
2. General code updates, such as swapping out the integer headers for the library headers (they weren’t merged into the standard until around 2010 or so). This will fix some bugs and may expose others
3. Look at the bug list and decide if it’s time to tackle them with Raid
4. Larger code overhaul to modernize it
5. Possibly features and other wishlist items

How does that look? I’ll grab the repository just as soon as we get permission to start editing but that doesn’t mean we can’t try building it and start making notes. Just that we can’t modify the code 🙂

[Spastic Hamburger]

Will have more to post later but we’re going to want to use this repository: https://github.com/uesp/mwedit

That seems to be the latest official one. At least, I think so. Will need to review things more when I’m not so tired but wanted to pass it along before you got going too much 🙂

Edit:

Waiting to confirm the license. He thought it was under the Apache License but it looks like the newer repo’s license file has it set to the MIT License. No problem with either, we just want to make sure we know what we’re working with is all

• This reply was modified 5 days ago by Spastic Hamburger.
• This reply was modified 4 days, 8 hours ago by Spastic Hamburger.

[Spastic Hamburger]

Got confirmation that the code is actually under the MIT license. He didn’t have any comments regarding the code so we’ll probably just need to figure it out as we go. Just cloned the repository so I’ll start going through it 🙂

Definitely want to look at doing some rearranging of the directory structure. I’m just not a big fan of having a lot of code files all in one folder. Makes it hard for me to find what I’m looking for but we’ll get there

As a note: it looks like it uses the one-class-per-file structure.

I’m pretty rusty so bear with me!

Edit:

A cursory glance shows that there may be some headers missing from the includes. That may take some time to update. We’ll have a better handle on things once you’re able to try building it, though 🙂

Edit 2:

We’ve got a mixture of C-style types as macros and C++-style types, such as BOOL and bool respectively, that should be made consistent. There are also some code blocks that are generated by the VS class wizard that should probably be copied (if we’re allowed to, not sure how that’s handled by licensing) into the main code to allow it to be more portable. Additionally, some stuff needs the proper namespaces assigned.

• This reply was modified 3 days, 8 hours ago by Spastic Hamburger.
• This reply was modified 3 days, 8 hours ago by Spastic Hamburger.
• This reply was modified 3 days, 4 hours ago by Spastic Hamburger.
• This reply was modified 2 days, 8 hours ago by Spastic Hamburger.
• This reply was modified 2 days, 8 hours ago by Spastic Hamburger.
• This reply was modified 2 days, 8 hours ago by Spastic Hamburger.
• This reply was modified 2 days, 8 hours ago by Spastic Hamburger.
• This reply was modified 2 days, 8 hours ago by Spastic Hamburger.
• This reply was modified 2 days, 8 hours ago by Spastic Hamburger.

[Spastic Hamburger]

Took a closer look at all three code repos just now. There are definitely some missing files. Should I ask Dave about them? That would explain why I haven’t been able to follow the newest repo, such as the IO operations. The newest one appears to be mostly the GUI implementation and not the backend stuff.

[DeVaultSetter]

I’d leave Dave’s for the moment, Nimrod actually has the solution, however conversion of the vcproj to vcxproj is the first port of call. All the included files will be in there – have you got to that stage yet?
Re-arranging the dir structure is critical, as you know.

[Spastic Hamburger]

That repository looks better but there isn’t a license associated with the code. Any way we can contact them to see about getting permission to use their fork?

Yeah, we can use the project files to extract the includes and add them into the C++ source. That’s what I did with the BOSS code. 🙂

Still need to finish setting up my Geany workspace. Some that is done on a per-project basis, though, so part of it will need to wait until we finalize which repo we’re going to use. Geany is pretty manual oriented 😛

Dave also has a few other projects that could be worth exploring down the road: https://github.com/uesp/obedit and https://github.com/uesp/tes4lib along with https://github.com/uesp/skyedit and https://github.com/uesp/tes5lib

The former looks like a GUI shell but it may use the latter. Not sure, haven’t looked at the code yet. Definitely something to look into later, though.

Edit:

Looks like Nimrod has done a lot of the updating I had in mind. Excellent. That definitely would help if we can use their fork.

Edit 2:

It may only be worth doing the bare minimum on the VS project files since they’ll be generated during configuration by CMake or Meson when we get to that step. 🙂

• This reply was modified 2 days, 5 hours ago by Spastic Hamburger.
• This reply was modified 2 days, 5 hours ago by Spastic Hamburger.
• This reply was modified 2 days, 5 hours ago by Spastic Hamburger.
• This reply was modified 2 days, 5 hours ago by Spastic Hamburger.

[Author]

Posts