Apr 21

PlasmaShop news update

Category: Development, Uru

Ok, I know it’s been a LONG time since I’ve posted anything here, but I figured I should give a little background as to the current status of PlasmaShop, libPlasma, and all those other related things ;)

Due to several issues, including lack of real cross-platform-ness and some limitations and annoyances with Delphi, I’ve now started re-writing PlasmaShop in its entirety in C++ using the wxWidgets toolkit, for a 3.0 release. This will allow it to run natively on Windows, Linux and even OSX (assuming I can find a Mac to compile it on…). Also, it should take care of several of the UI issues people have mentioned to me in the past, including the many features that are more hidden than I realized, causing people to either not know they exist, or have trouble figuring out how to use them. Who knows, I might even get crazy enough to write real documentation this time ;). Included with the suite will be at least all the functionality of PlasmaShop, including a graphical PRP editor to replace (or at least complement ;) ) the old (and horrendously outdated) PRPTool and PRPExplorer tools.

Even more of interest to some, though, will be that the PlasmaShop 3.0 suite, including libPlasma, will be completely open source under the GPL, so others can actually make use of the work, or provide their own updates. I haven’t decided between the old GPL v2 that libPlasma has been (technically) under since I started the project, and the more-recently-released GPL v3, but it will be one of those two, most likely. If someone is an expert on licensing or knows the GPL really well and has a suggestion, I’m definitely open to hearing it :)

As of right now, libPlasma supports an insanely large amount of Plasma’s formats (almost all of the PRP classes, all the encryption formats, and a few other things), but PlasmaShop is still relatively early in its development. Therefore, I can’t predict any sort of time frame for its release, or even when it’ll be ready for beta testing. However, once I get the licensing stuff more final, I’ll be releasing the SVN repository details on here for those interested parties to peruse.

Finally, regarding MOUL support: PlasmaShop 2.x and PRPTool 0.2 have, for quite some time, supported MOUL files, although only in a private build. I did this because I wasn’t sure about the necessary legal stuff regarding it, but it seems that anymore it doesn’t matter anyway (especially with Dustin’s nifty “Drizzle” project out there now), so I’m now merging the two versions into the public release, which you can download from here: [PlasmaShop 2.2.3] ♦ [PRPTool 0.2]. With that in mind, libPlasma also supports MOUL, as well as the other Plasma 2.x and 3.x engines, and therefore PlasmaShop 3.0 will follow suit.

Peace
~Z

EDIT: Robert found a bug that appeared in 2.2.3 that caused some incorrect data to be written to PAK files, which caused both PlasmaShop and Uru to fail on attempting to read them; This bug has been fixed now, and the updated version is at the same download location above.  Also, the links actually point to the right files now :).  Thanks Robert!

3 Comments so far

  1. Robert The Rebuilder May 1st, 2008 5:16 am

    Exciting news, Zrax! I’ve downloaded the latest version and am trying it out now.

    Just a note: your links for PlasmaShop and PRPTool are switched around.

  2. Robert The Rebuilder May 1st, 2008 6:39 am

    I just tried PlasmaShop 2.2.3. When I attempt to add a Python file to an existing PAK file, an error dialog appears saying “Access violation at address XXXXXXX in module ‘PlasmaShop.exe’: Read of address 00000000′

    When I create a new PAK file and add a Python file to it, no errors appear, but the file is not listed in the PAK contents dialog. When I add a second file, I get the error dialog above.

    I had this problem in 2.2.1, but it was fixed in 2.2.2. Was the fix somehow lost in 2.2.3?

  3. Zrax May 2nd, 2008 9:35 pm

    Re: the links: Haha, so they are; I’ll fix that, thanks!

    Re: the PAK bug: Hmm, I’m not sure what’s going on there… I’ll take a look at it and let you know

    EDIT: Ok, I’m not sure what I was thinking/smoking/whatever when I wrote the code that was causing the bug, but in any case, it’s fixed now :). Thanks!

Leave a comment