v0.1.5

Release v0.1.5

This release is to fix issues when launching the application. It features a bootstrapping process that ensures required files, directories, and dependencies are in place. Also fixed an issue where compiling a newly-created project would fail.

v0.1.3

This release brings improvements to the build system to work out issues that were popping up on the user's end. We expect missing file errors to be reduced, and these changes will make developing and testing easier. One noteworthy change brings certain files into your Documents/icesickle path, allowing you to quickly modify plugins and languages without having to dig through strange system directories. The API also saw some minor changes.

Highlights

Installation re-structure

There were significant discrepancies between the development and production (user-end) environments which were causing headaches. By re-structuring how the build system works, and modifying some folders on the user's end, the problem is dealt with. There are some rough edges to smooth out, still.

Build changes - The build is improved to include more of the files that are needed on the user's end, making the app much less likely to complain about missing files.

Directory changes - While the app is still installed as usual, we've made it more friendly to modify the editor via plugins and scripting languages. Plugins, languages, and your settings are all stored under your machine's Documents folder. E.g. on Windows that may look like: C:\Users\[Your Name]\Documents\icesickle

API

✅ Added

Requests

• log - creates a message in the log (either info, warn, or error)
• getLog - requests the entire log
• clearLog - deletes all entries from the log

Events

• logAdded - occurs when an entry is inserted in the log, broadcasted with the new entry
• logCleared - occurs when the log is cleared/emptied
• responseLog - response to the getLog request, returns the entire log

Issues resolved

• #40 - Implement logging events
• #43 - Create alias for Plugin logging called Plugin.log()
• #44 - Improve differences between dev/prod environments and their negative impacts
• #49 - Resolved settings issue with missing keys

v0.1.2

This release provides enhancements and modifications to the plugin system, simplifying plugin requires and providing more utility with the main application. Events and requests have been updated semantically and documentation on the wiki will be gradual.

Plugin improvements

Plugins are re-factored to take a Plugin context, which provides access to enums, windows, settings, event, etc. Developers now longer need to require the class to use it. Plugins can now have a menu item listed under the Extensions menu by providing a onMenuClick handler.

Events and Requests

Organized and re-structured events and requests to be more logically-named and discoverable. The wiki has been updated to gradually document these features. Breaking changes had to be made to support this effort.

API

🔷 Modified

Requests

• newProject, renamed from createNewProject
• saveProject, renamed from requestSaveProject
• compileProject, renamed from requestCompileProject
• newObject, renamed from newCustomObject
• editObject, renamed from patchProjectObject
• editTrigger, renamed from updateTrigger
• openWindow, renamed from requestOpenWindow
• newImport, renamed from importFile
• editImport, renamed from updateImport

❌ Removed

Requests

• requestOpenProject - ask the app to prompt the user to open a project
• requestOpenProjectMap - old way to open a project

Issues resolved

• #13 Application is quit when the root window closes
• #14 Exit button added to File menu
• #33 Plugin class is now passed to each loaded plugin
• #34 Enumerations are now available to plugins via Plugin.enums
• #29 Add functionality to plugins
• #36 Application path is changed to a more resilient location

v0.1.1

This is a small patch release.

Bug fixes

• Fixed #32 - application would not start if settings.json file was missing

Tweaks

• About window under Help will now show useful developer information, including app path and plugin path

0.1.0

We've been chugging along to fill in core features of Ice Sickle. This release focuses on scripting language support and map compilation, among smaller edits. These two features will still receive major development time in the next release as things like a stronger code/trigger editor, syntax highlighting, script validation, and UI are rolled out.

Highlights

Scripting language support

With 0.1 comes the ability to support arbitrary scripting languages. These act as plugins, in a sense, where a developer can invent their own syntax and offer a translator to convert to JASS during map compilation. The framework has also been laid (but not implemented) for other handy features like pretty printing, syntax highlighting, and validation. Ice Sickle comes with JASS pre-installed.

Partial map compilation

The Map > Compile feature is now underway, and will be for some time. This takes your project and generates the files necessary to construct a .w3x MPQ. It uses the WC3MapTranslator module to convert JSON data to war3map.* files. Units, items, destructables, and triggers are already supported! (Screenshot #1)

API

✅ Added

• request-scripting-languages and response-scripting-languages

Bug fixes

A few, but missed tracking them due to rapid development.

User input and bug fixes

v0.0.6

Update version

Auto updater and map creation improvements

Remove old code for root view creating a new project

This logic is handled in the app now

Fix autoUpdater bug

Fix Listview text overflow

Closes #18

Auto updater improvements

Created a window to notify users of events related to auto updater. The user is shown that the application is checking for updates on startup. When a new update is available, downloading begins, so the progress is shown there. When downloading is complete, the application is restarted.

Test autoUpdater system

Uploading a new version (all that's changed is the version number of the app) to see if the autoUpdater is functioning correctly.