You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a property images now (on both programs and ROMs), which we use to store filenames of images that presumably show the gameplay. The issue, as I see it, is that we don't store those images in this database yet. So the filenames don't really reference anything that people can use.
Two solutions:
Remove the properties
Add the images
I'm in favour of the second. I propose we add a directory images to the project's root. In it we add all images using a SHA1 hash over their contents as the filename (but with the original extension of course). Then we reference those new filenames in the images properties.
Unless we wish to preserve the original image filenames for some reason..? I can't really think of one.
The text was updated successfully, but these errors were encountered:
Another solution could be to make the images property reference URLs of images, referring to places elsewhere on the internet. This would probably work fine for the CHIP-8 Archive and some other long lived sites, but we'd have to keep track of broken links and remove those. That doesn't feel very self-contained or future proof...
We have a property
images
now (on both programs and ROMs), which we use to store filenames of images that presumably show the gameplay. The issue, as I see it, is that we don't store those images in this database yet. So the filenames don't really reference anything that people can use.Two solutions:
I'm in favour of the second. I propose we add a directory
images
to the project's root. In it we add all images using a SHA1 hash over their contents as the filename (but with the original extension of course). Then we reference those new filenames in theimages
properties.Unless we wish to preserve the original image filenames for some reason..? I can't really think of one.
The text was updated successfully, but these errors were encountered: