This means I'm only able to spend evenings and weekends working on Quest, so the pace of development from my side may be slower than it has been lately.
I've also been sponsored to add some features to Quest 5.3 - features which I think are pretty cool. Most notably, a graphical map, and the ability to switch the "POV" character. I've been implementing these in a separate fork - now that Quest 5.2 is out I'll be merging this into the code on CodePlex. I'll also write some blog posts explaining these features soon.
My priority is to continue working on the sponsored features, and then I'll turn my attention to the other stuff for the Quest 5.3 release (well, before that, I also need to update the wiki docs to reflect 5.2 - could use some help here too!) I've already gone through and pruned the Issue Tracker a bit - currently 35 open items assigned to v5.3 (other items pushed back to 5.4 or 5.5 - not much distinction between the two and priorities will surely change yet again).
So, there's plenty of scope for people who are interested to make contributions! I would of course love it for anybody to pick up any of the items assigned to v5.3, but that's not the be-all and end-all, I'm happy for other features to be implemented too. It may be worth dropping me an email, or posting here, before doing loads of work though.
I think it would be good for the focus of v5.3 to be on features that enhance the look and feel of playing games in Quest. So I would particularly like to focus on these items:
- #857 Tabs and Accordions http://quest.codeplex.com/workitem/857
- #868 Partial window clearing (maybe an option to have "errors" like "I can't see that" fade out nicely after the player takes another turn - think Vorple does this?) http://quest.codeplex.com/workitem/868
- #985 Web Fonts http://quest.codeplex.com/workitem/985
- #1036 User-defined pane http://quest.codeplex.com/workitem/1036
Out of these I'm most keen on #985. Having really nice typography available to games will make a big difference I think.
It's probably time to revisit how the panes work, actually. Ideally the desktop version should render panes (inventory, places/objects, compass and potential new "user-defined pane") purely in HTML, just like the web version. And the command bar at the bottom of the screen, and location bar at the top should be HTML too - this will bring the two UIs closer together, reduce duplication of code, and make full interface customisation much easier.
Also, it would be nice to make it very easy to add images and sounds in the Editor, by integrating various APIs e.g. Freesound (http://quest.codeplex.com/workitem/955), Flickr (http://quest.codeplex.com/workitem/965) and YouTube (http://quest.codeplex.com/workitem/1044). I'm not sure how feasible it would be to add these to the desktop Editor - maybe these could be for the web version only.