I hope I’m not being too presumptuous here, but I thought I’d open a thread so I can make announcements regarding new releases of GSBEdit, new features being implemented, and so on. This should be easier than people having to skip to page 8, 9, and so on in the other thread to find out what’s happening.
Where can I get GSBEdit?
The official site is at http://modding.kempj.co.uk/. There is currently nothing there due to a big reorganisation I carried out. Content will return.
What is the current version?
Currently GSBEdit is heavily alpha and I’m not assigning version numbers. Different releases are differentiated by their release date. Since 110204, GSBEdit has the ability to automatically check for new releases and inform the user.
What OS is supported?
The Python source package will run on any system which provides the appropriate versions of Python and wxPython (see the Download page for more information). A Windows package is also available for those who cannot run (or do not wish to run) Python scripts. For several releases, the module editor had a bug under Ubuntu which rendered it non-functional, and this was fixed as of release 110219.
Until I have the site set back up fully, the Windows releases are not being updated and the required Python/wxPython version numbers aren’t listed. However, it should run on the version of Python supplied with any reasonably modern OS.
What changed in the current release?
- Added more module attribute descriptions.
- Added plasma weapon attributes, along with unlockcost and hidden.
- Module class name is now a bit more friendly.
- Additional information, such as DPS calculations, can now be displayed.
- DPS calculations are now displayed (using a very basic calculation for now).
! Fixed module editor not showing the name of the selected module.
! Fixed error when there is an install file but no package file.
! Fixed propogation of attribute update messages.
! Fixed silly bug with checkboxes showing wrong value.
Where can I send bug reports, suggestions, or complaints?
You can either PM me directly, or (until I set up a GSBEdit bug thread) post them to the original modding tools thread at viewtopic.php?f=23&t=5786. I would like to keep this thread clear of bug reports and tech support related messages so that people can find useful information quicker (not just information related to the current release).
How can I contribute?
The easiest way to contribute is simply to use GSBEdit and give me your feedback. Let me know what’s good, what’s bad, what small things annoy you, and what you’d like to see in the future. If you want to get more deeply involved then another way is to mock up new features - providing me with example interfaces or reference code. The final level is to work directly on the GSBEdit code. This is rather more involved and has some procedure around it, see the next section for details.
How can I work with the GSBEdit code?
GSBEdit is now hosted on Google Code (gsbedit.googlecode.com/hg/ to a local copy on your machine. Cloning from this repository ensures you start with the last release that was made available, without any of my subsequent development changes. You may also want to make a server-side clone on Google Code to make it easier for me to merge your changes back into the stable repo. This is the last time you should touch the stable repository, any merges and pushes into it are handled by me. When you are ready for me to look over your changes, push them up to your server-side clone and let me know. If it all checks out then the changes will be merged in to my development copy and from there in to the stable repo.