UI Redux
Hello there world wide web! Today we decided to give an update on our Maze Editor app for macOS and what we’ve been working on.
Code Sample – Sound Manager
In this post we decided to share the code that we use (with a few small edits) to manage our sounds in the iOS app (with little modification, it may even work on macOS!). And without further ado…
Is thing still on?
YES! Yes, it is. We’ve been hard at working on the Editor and the iOS game that it makes levels for, please be patient and we will be posting more about the dev process and our progress.
That’s all for now!
Introducing Maze Editor – Video Demo
Well, we finally got our macOS app to the point that it’s usable and we can save/load data files.
Check out the video on youtube:
Saving/Loading Files
It’s been a few weeks since our last post so without further ado…
Deciding your document format sometimes can be difficult. Other times very easy, especially when you’re just creating simple documents of data that has a format that’s already defined (images for image editors, text documents for text editors etc). But when coming up with a format to represent your custom data it can almost be just as hard as coming up with a name for something…
Solving a nagging problem
Did you ever have a problem that no matter how much you tried, you couldn’t figure it out? Well today we solved one (of course we have many, but that’s for another time) of ours!
UI – Issues Tracker
After working on the room properties UI the next thing we wanted to do was add a way to track different issues with a given level. Some of the things we wanted to track were:
UI – Room Properties
The next thing we started working on was the UI for editing room properties. From the get go we knew we wanted to use a Popover as it just made since, otherwise we would have had to figure out a way to select a room in the editor UI and then click properties or something… would have been a nightmare.
Deciding the UI – Editing Data
Setting level data
Next we had to decide on how we wanted to present UI for actually adding data to the currently selected level, we looked into a few different UI presentations but we didn’t like the early ones, the one we finally settled on…
Deciding the UI
The Editor
The next thing we had to decide on was: what UI are we going to present to the user when she is editing a level?