I set up a couple types of object
	But left a few issues for later!

Tour of loading objects
	Vertex and texture coordinates, and different indices
	Kind of a circus...
	I borrowed the solution from vulkan-tutorial.com

Object orientation:
	.obj files may be laid out differently
	We'd enforce consistency on them if making an actual engine
	We're more likely to have a collection of stuff we found
	So we might need to transform coordinates on loading
	We'll set up a callback function for this
		Could use a matrix operation, but I think the callback is more flexible

Couple Organization Changes:
	load_level function
	We'll put together a list of game objects
		It's ready

Project 1:  Create a replacement for load_level that loads a level from a file
	How do you want to do this?
	We will add a text name for each object
	Do you want a full MVP instead of just location?  
		If so, we should work out how to rotate objects individually

Lab today:  Start project 1
	You'll replace the load_level function with something better
	I'll post a project description, but basically:
		Due:  Monday, October 19
		Requirements:  Load several types of object, one in more than one spot
		How hard:  Depends how far you want to take it, could be pretty easy
		File Format:  You decide.  Could be XML, plain text, etc.
		Level Editor:  Totally not required
		Long walls:  Feel free to make a range possible, but not required