Split the project specification and the project state

The project specification and the project state should be stored separately (maybe sublime-project and sublime-workspace?). As it is now, it will be difficult to edit the project files (because there is so much state information stored there) and sharing projects doesn't make much sense. The simplicity of the old project files was great but I really like the features of the new projects. Can't we have the best of both worlds? sublime-project (build_system, folders, save_all_on_build, plus any include/exclude instructions). sublime-workspace (buffers, file_history, find_in_files, find_state, groups, layout, select_file, show_minimap, side_bar_visible, side_bar_width, status_bar_visible)

"It may be worth doing this, but I'm concerned about confusing people: people may not know what a 'workspace' is, so they use the project functionality when they'd be better served by using workspaces." http://www.sublimetext.com/forum/viewtopic.php?f=2&t=1444&p=6606#p6623

Sublime Text "internally" manages the state information for other aspects of the editor ("Auto Save Session", "Session"), so why not store the project definitions "externally" and the current state (workspace) "internally"?

By storing these separately, people could more easily share projects and could still have their own local workspaces.

The biggest issue I can see is the possibility of the project and the workspace getting out of sync (if one of the files is moved to a different location).