Whoah, it's so slick!
The biggest hassle for me has always been
- finding the latest version of a table through the clunky forum interface, which it seems your UI already takes care of; maybe different releases of the same real-world table could be grouped under the same heading somehow?
- downloading the table, unzipping it, moving it to its proper directory, then hunting for the ROM, likewise moving it where it needs to go. I guess cab users have an even worse time with this. I don't know if the ROM file can be included for legal reasons, but even if it can, it seems there would need to be different packages for desktop users, cab users, then you have different backglass versions... What if, and I'm only dreaming here, there would be a simple client-side application which gets a special download link from your site and then does all this stuff automatically? You'd have to set it up once with the proper paths, and then it takes care to unzip the table, makes sure you have the ROM and downloads it otherwise, gets any B2S file it is told to... Not that easy to do obviously, but that would be the most convenient thing ever.
1. If you look at the GitHub page there's more detailed info about it, but in a nutshell it's exactly as you describe: All table releases are linked to the real-world table, you wouldn't actually be able to upload a table release without finding (or creating) its parent.
2. I feel your pain. The good news is that I've created exactly that about a year ago, it's called Pind and basically indexes VPF, offers a nice UI and allows downloading and unzipping everything to the right place in one click. I'm using it on my cab and it works, but installation is kind of cumbersome on Windows (Node.js needs a few native modules that need compiling), that's why I've never officially announced it here (only over at Hyperspin-fe).
Looking good
I think that any release should come default with RELEASE DATE+VP VERSION+TABLE VERSION for an easiest way to search any thing by title,date, ect ect.... A more power full search to ensure any new update is not missing and of corse a flag "NEW" if the file is newer then last visit
All but VP version is already there, and that's actually a good point. Adding to TODO.
Looking really good! I hope this goes forward!
One question:
If user selects AFM for example -> will this view show all releases of this table? Or only the original versions and then you would get the MODs for that table under the mod section of that release?
Because I think this is the way it should work and also looks like from UI point of view. However the AFM example you have used is a MOD already so I'm not sure how the table/mod relation is planned now.
I think this kind of parent - child relation between a released table and MOD's based on that would be really good. This would eliminate the confusion about the author(s) of the original release and always show that one first (as it should... because without it there would be no MOD ).
Yes, for now it would list one release after another, latest first. However, now I think about it, it would be indeed nice to somehow "attach" the mod to its parent. Putting all into the accordion tab probably won't do it, but I'll figure something out!
Also there are so many backglasses available on other forums, will you integrate them?
By "integrate" you mean if they're going to be available once there's actual data? Not sure, I would think that authors would upload their creations themselves, so you'd need to ask them
I'm going to spend some time on a homepage / dashboard in order to show you what kind of information we could pull out of a structured data set.