Timeline for How to design an AssetManager?
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 29, 2010 at 15:30 | comment | added | Skizz | @Joe: I only gave SQL as an example and then only in a development environment, you could equally use a VCS. I only suggested SQL database since you can then add extra information to the stored objects and use the SQL functions to query information from the database (more a management gain than anything else). As for opaque IDs as premature optimisation - some might see it that way I guess, but I think it would be easier to start off with that rather than show-horning it in at a later point in the development. I don't think it would affect development much if you used ID or strings. | |
| Jul 29, 2010 at 14:23 | comment | added | user744 | I voted you down because you suggested shoehorning everything into a SQL table with primary keys rather than using a real VCS. Also I consider using opaque IDs rather than string names premature optimization. I used strings on two large projects for all assets other than translation keys, of which we had hundreds of thousands of very long string keys (and then only to port to consoles). They were usually normalized so we could use pointer compares rather than string compares, but string compares are often dominated by the cost of the memory fetch and not the actual compare anyway. | |
| Jul 29, 2010 at 9:35 | history | edited | Skizz | CC BY-SA 2.5 |
Expanded idea.
|
| Jul 28, 2010 at 10:30 | history | answered | Skizz | CC BY-SA 2.5 |