Taylor

	Count
Releases	0
Commits	6
Contributors	2
Pull requests merged	2
Issues closed	1

At a Glance

• My Mental Health Life is currently difficult
• Windows Issues Fixing the console issue on Windows
• Path Issues Working on fixing the current working directory feature
• Taylor v0.5.0 Progress Where the new release is at

My Mental Health

If you follow my personal blog you will have seen that things have been pretty hard for me. This has meant pulling back on the amount of serious work I can do, including working on Taylor.

The plan was to have v0.5.0 released already but I haven’t been able to commit many hours to the last couple of tough challenges I want to get done before releasing.

I’m not sure how much longer the current stressors are going to be affecting me but I am prioritising myself and getting through this situation. I will still try to fit in some Taylor development as I really want v0.5.0 released but I will not sacrifice my health to do so.

This means I will put no deadlines or promises for a release date.

I appreciate your understanding on this.

Windows Issues

Pull request

While I was preparing for Taylor’s v0.5.0 release I started building up a proper checklist to make sure things weren’t broken or there were no regressions. This has already payed off as it discovered that Taylor’s development experience was broken on Windows and has been since v0.4.0.

This came about due to unknown changes but it was related to how I wanted to package Taylor as both a CLI tool and GUI which it seems Windows has issues with.

A new config option was added for toggling the behaviour of showing a console on Windows. This is set to true for Taylor CLI but should probably be set to false (the default value) when you export your games. You shouldn’t have to change anything about your config to get this fix, just upgrade to v0.5.0 when it releases.

Path Issues

I discovered this issue when testing on Windows but it seems it applies to all systems. This is some functionality I added during the v0.4.0 development but I now think is an anti-feature.

When running your game internally we would Dir.chdir to the location of the executable. I thought this was helpful because it means you don’t need to think about the current working directory when loading in your assets but has caused issues when you want to do something like ../taylor to launch your project or game. This causes it to not respect your actual current working directory and makes it unable to find game.rb.

On Linux and OSX I didn’t notice this because I always just put taylor somewhere in my $PATH and it resolves correctly. On Windows though it was changing the directory to where the actual executable was still, even though on Linux and OSX it stayed in the current directory.

This is still a work in progress.

Taylor v0.5.0 Progress

I think this is reasonably close. The last issue I’m aware of is the path issue described above.

There may be more issues that come out of the release checklist and I’m trying to delay this release to include as many positive changes as possible. I want to make v0.5.0 a release that brings Taylor up to the standards I expect. I feel there has been some slips in quality since v0.4.0 but that was somewhat expected with how massive that release was.

If you’re interested if following the release, see the pull request.