Game Development Community

Committee Meeting Notes: 03/5/2013

by Michael Perry · in Torque 2D Professional · 03/07/2013 (8:28 am) · 3 replies

Old Business:
  • The Steering Committee Charter
New Business:
  • Review of docs
  • Processes:
  • - For submitting code/docs
  • - For merging
  • - For versioning
  • Competitive Advantages of T2D (and potential ones)
  • Editor shell investigation progress
  • Potential Change to Mich's schedule
  • Setting goals, task assignments
Actionable Items
Mich
  • Create placeholder docs for processes
  • Arrange followups based on this meeting to clarify work
  • Get a blog up about latest updates
  • Scripting Tutorial
  • Do a tip of the day
Melv
  • Finish tech investigation of editor shell options
  • Arrange a meeting this week with Mich to plan the next step for the editor shell
  • Potential point force controller improvement or suggestion (based on Erik G's request)
  • Do a tip of the day
Simon
  • Getting started tutorial
  • Do a tip of the day
Charlie
  • Start a doc on T2D features and comparisons
  • Continue to review code
  • Do a tip of the day
NextNext Thread
PrevPrevious Thread
More from Torque 2D Professional


Associate Matt Fairfax
PopCap
#1
03/07/2013 (1:41 pm)
I've mentioned it directly to Mich before but I thought I would throw it out here:

I highly recommend looking at Adobe Flex for the editor framework. We use it internally and I have been very impressed at how powerful and flexible it is. It reminds me a lot WPF but with full cross platform support. It also has the advantage of being editable with the very reasonably priced IntelliJ ($99 for most people) for people who want to extend the editor (warning...using IntelliJ will make you want to switch to AppCode for iOS coding =P). Using Flex also opens up some interesting possibilities with importing/exporting assets and animations from Flash.

Torque Owner Richard Ranft
Roostertail Games
#2
03/07/2013 (1:56 pm)
I hardly did any work on Mac at all and I was all for moving to AppCode...

Associate Mike Lilligreen
Retired T2Der
#3
03/08/2013 (4:27 am)
Thanks for the write up, really nice to see the to-do list that the steering committee members are working on.

I know that time constraints can prevent a more detailed protocol, but if time allows a bit more detail on the new business topics would be helpful and perhaps that could generate a bit more discussion within the community.

For example, the point on versioning. Are there proposals on what to call this week's push to the master branch (or those in the future) besides "the latest version of the master branch"? How often are updates planned - at a biweekly, monthly, quarterly rate? Or only after a certain number of commits have been reached in the dev branch?