Skip to content
This repository has been archived by the owner on Mar 9, 2019. It is now read-only.

Migrate Snap saves to a Snap 'Project' #9

Open
jhenkens opened this issue May 7, 2014 · 1 comment
Open

Migrate Snap saves to a Snap 'Project' #9

jhenkens opened this issue May 7, 2014 · 1 comment
Assignees

Comments

@jhenkens
Copy link
Contributor

jhenkens commented May 7, 2014

Add metadata to Snap 'Project'

  • Was the project extended from a base file?
  • Is the project a base file itself?
  • How many versions does it have/what is the latest version?
  • Notes
  • Name
@jhenkens jhenkens self-assigned this May 7, 2014
@jhenkens
Copy link
Contributor Author

I messed around with this as a way to have versioning, but have, for now, stashed off the changes and put them elsewhere.

I'll look at it again when we start working more on the versioning system, or potentially the media-extraction system (to store each media object separately in a database accessible by a global id). For the time being, we simply use a snap_file, which doesn't include any native versioning, but does separate the 'project' xml (smaller) from the 'media' xml (larger, contains all the sprite models and sounds).

The project_name, thumbnail, and notes are all extracted from the XML on update and stored in the database as a separate entity for the snap_files#index action.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant