[WIP] Mod Builder

[Bigguy]

I'll do this now so I don't forget.

[margarett]

Yoshi, thank you very much for this. I have been using it in my (short list of) MODs.

In the previous version (1.3) I could never "Convert a Package to a Project". In this version I finally could.

But there was something wrong with it. In this specific case, I am doing a series of operations in Load.php:

Code Select Expand

    <file name="$sourcedir/Load.php">
        <operation>
...
        </operation>
        <operation>
...
        </operation>
        <operation>
...
        </operation>
        <operation>
...
        </operation>
        <operation>
...
        </operation>
    </file>

(not pasting the code as it is an unapproved MOD yet)

After import, I only get 1 operation in Load.php (the first one).

You can get the affected MOD from modsite directly

[NanoSector]

Hmm that's weird.

I'll have to admit, the conversion process isn't the best piece of code. It's quite possible that it just grabs the <file> tag and only grabs the first operation within.

ETA: Confirmed this
https://github.com/Yoshi2889/ModManager/blob/master/OrganizingProjectC/Forms/convertProject.cs
Around okButton_click. Notice how there is no foreach with the file tag [note to self]

[Bigguy]

I was going to report this when it happened and I will try to reproduce this but I could not use it. It was erroring out every time I tried to do something. I am using ver. 1.4 Running W7 on x64 I'll get back to you when I know what I did to break it, lol.

[NanoSector]

The error itself would help, too

[Atomic Blaze]

* Atomic Blaze feels left out

No XP support

[NanoSector]

Upgrade yer software

I'd love to support XP but Vista+ make it much easier to do certain things.

[Arantor]

And in less than 3 months, XP will be unsupported anyway.

[NanoSector]

Mod Builder 1.4.3 and 1.4.4 are released

Code Select Expand

=== 1.4.4 ===
! Bugfix: Fix bug where downgrading MB does not store the actual version in the settings.
! Bugfix: Converting a package now takes all instructions into account.
! Bugfix: Really fix bug with versions.

=== 1.4.3 ===
+ Feature: New Update dialog.
+ Feature: Changelog diplay upon update.
! UI fix: Resized Mod type and Mod ID controls for better UX.
! Bugfix: Wrong icon displayed on PHP code check success.
! Bugfix: PHP code checking now does not display a CMD dialog.
! Bugfix: When adding/editing a source code edit, now displays the correct titles.

This should fix margarett's bug and add Colin's suggestion. Thanks guys!

[Biology Forums]

Thanks for this

[birdenemeklazim]

great application

thanks

[NanoSector]

2.0 is coming along nicely, I've been working on it in my spare time.

So far it features a completely different internal structure, which is much easier to maintain and should be much more stable. It no longer depends on reading package info files, and no longer requires a database to come along with it. Projects now run entirely from memory, so no more annoying "you first need to save your project" messages. Furthermore it no longer crashes if you move, rename or delete your project files (if the file is deleted the project can be gracefully moved to memory).

Projects are saved in xml format, but with extension .mbproj. You can edit them with your favorite text editor if you like. Internally, the program serializes the Project class to make this possible. Proper error handling is implemented. I've got rid of my custom field validation and used built in .NET components. Everything has moved to one form control and I'm trying to move the entire project view to one nice tree structure.

Right now the codebase is a bit of a mess with a lot of unfinished items and a main form with too much code But at least the basic project system is functional. I have a sketch in my head for translation support, and the whole structure is also pretty much planned.

If there's anything you'd love to see in 2.0, let me know! Every small feature can make a big difference. 

[ZerK]

looking forward to this i ve never been good packaging my mods

[Adonix]

Waiting for version 2.0 

[C. Davis]

It would be cool if you could edit a smf installation and it would detect what had been added and you could checkmark what you DID add.

[C. Davis]

Also, if it had the option to UPGRADE packages instead of making you uninstall old mod versions and install the new one.

[Kindred]

I don't think you understand what this script is or what it does...

[C. Davis]

I don't think you understand what this script is or what it does...

You're really ******ting on me today aren't you?

I have the current version already. This program creates the package to upload to the server to install a mod.

In it's current state, you have to uninstall the old version of a package before installing the new version. There is no option to create an update script.

[Kindred]

As do 99% of the mods on the mod site...

[C. Davis]

As do 99% of the mods on the mod site...

Don't you think it would be nice have a feature like that?

Plus, he did say

If there's anything you'd love to see in 2.0, let me know! Every small feature can make a big difference.