[01:29] nice [01:30] But I am serious - someone working with me can get these all up. [01:58] Seeing if I can add artwork for the handheld [01:59] https://archive.org/details/hh_gnw_dkong2 [01:59] got it! [02:03] aspect ratio is wrong [02:06] if you want it 640 wide it should be 852 tall [02:24] Well, remember I hacked this [02:24] Hence I need a folk [02:24] Someone in here who has wanted to help [02:24] To generate the JSONs [02:47] *** azakai has joined #jsmess [05:52] Night Night [19:41] Back, a little [19:41] So unwell! [19:49] OK, I'm gonna try and grind out some progress today/tonight. [19:54] Lovely! [19:59] What's your preferred naming convention for feature branches? [19:59] On Emularity, specifically. [19:59] db48x currently controls that [19:59] If you let me have that you willlll regret it [20:13] control? [20:13] You mean the naming convention? :-) [20:13] yes [20:13] you imply that I've thought about a naming convention [20:13] Well, I imply that you might not want me to be the one who decides on the naming convention [20:14] that's possible :) [20:14] Sound fork: EmuBlarity [20:14] OK, so if I just pick feature/thing-I'm-doing it'll be cool? [20:14] yep [20:14] Cool. [20:14] heh [20:14] Graphics fork: EmuStarity [20:14] Horse fork: EmuMarity [20:15] HD graphics fork: EmuClarity [20:15] License: EmuSharity [20:15] lol [20:15] If ever there were a reason to fork a license... [20:16] OK, feature/swap-that-floppy it is, then. [20:17] OK, so... let's see. Because I'm too lazy to look it up myself, do we have interfaces for swapping floppies with other emulators? I know I saw hints about it for SAE. [20:18] not really [20:18] OK. [20:18] in principle we could build something for PCE; it has a very basic mechanism for swapping between a list of disk images [20:18] I'll try to think ahead a little, then, to make sure everything can be consistent. [20:19] The fun thing for PCE is that the Mac wants to have ULTIMATE CONTROL over disk insertion and removal, so. [20:20] yea [20:20] But I'll tackle MAME first and make sure I'm not painting us into a corner. [20:22] Stick with MAME [20:22] MAME is the big one. Don't get big, the scope creep with lose you [20:23] Yeah, definitely, just want to plan ahead instead of stapling something on that's gonna have to be completely refactored for the other emulators. [20:23] Avoiding scope creep is one thing, making sure I'm not hemming us in is another. :-) [20:23] There is a very good chance it WILL have to refactored for other emulators. [20:23] Premature optimization being the root of all evil, etc. [20:24] We have ... 4 emulators now? 3? [20:24] MAME, PCE, SAE, DOSBOX [20:24] MAME, PCE, DOSBox, SAE [20:24] Yeah. [20:24] All with different mechanisms. [20:24] I think the only thing I see that wouldn't be generally common with all of them, interface-wise, is that some machines (I think just the Mac?) don't want you manually switching floppies. [20:24] I chatted with NaTMeg about SAE. His response is "Yeah, that's not likely to get hugely better anytime soon, and the hero who will make it go into WebAssembly won't be me." etc [20:25] PCE is PCE [20:25] Right. [20:25] DOSBOX will eventually potentially be overtaken by MAME [20:25] As will PCE [20:25] Maybe even SAE [20:25] That's why it's worth going into MAME [20:25] Understood. [20:26] I'm just thinking about the separation between the web interface vs. the mechanism underneath for actually switching the floppy interfaces. [20:26] Now that I've dinged the surface of that, I'm just gonna make it work first. [20:26] Yeah [20:27] Right now, that is the NUMBER ONE thing that people ask about [20:27] I mean, that and why is it crackly sound on their not-new machines [20:27] Meanwhile. Is there a great quick IA example that already has multiple floppies loaded up? Otherwise, I should probably learn to stitch them together with existing examples (e.g. Wasteland). [20:28] I can make one [20:28] there are a number of them, but they're hard to find [20:28] Oh, many [20:28] Let me give you one. [20:29] https://archive.org/download/BorrowedTime4amCrack/Borrowed%20Time%20(4am%20crack).zip [20:29] Hell, Dark Castle still crackles on my reasonably new MacBook. [20:30] OK, cool, I'll bang on that for a bit. [20:30] https://archive.org/download/TimeZone4amCrack/Time%20Zone%20%284am%20and%20san%20inc%20crack%29.zip [20:31] There it is [20:31] Your Ragnarok [20:31] A 6-floppy, 12-sided adventure [20:31] * oscar grabs a hammer [20:31] That is the max case [20:31] The absolute max [20:32] Famous last words... [20:33] Actually, Wasteland wants you to make "play" copies of all 4 floppies, which is arguably worse because it means we need to incorporate loading fresh, blank disks. [20:33] Or at least, that's how the C64 version works, I'm assuming the Apple II version is the same. [20:48] Well, the key here is just to bring to bear a bunch of disks. [20:49] Another thing you could do is have a blank floppy in the item, and then do like Bank Street Writer and we see about swapping floppies to save something typed [20:49] That should get you started. [21:05] heh [21:05] Right. [21:05] I thought I had introduced a bug, but it turns out that I had misspelled a filename in the testcase I was using [21:08] ok, pushed [21:35] Ah, looks like Time Zone *also* wants to create data disks, with some fun caveats per the text file. [21:41] Oh god, this text file. This game is a nightmare. [21:41] Though fortunately, none of that affects what I need to do. [21:50] I love reading those things [21:52] Hm, so. This game has one .dsk file and the rest are in the zip file, but the MAME file loader seems to skip right over the zip files... [21:59] Oh, yes. [21:59] Oh, YES [21:59] That's because the loader will want the files in the directory. [21:59] Unpack 2. put them there to read from [21:59] We only put one in so the system doesn't explode [21:59] hence the 00_playable.dsk bullshit [22:00] That will all end when this is fixed with your thing [22:00] we should make a test item without those hacks [22:01] Right [22:01] We will definitely have to get that soonish [22:01] But I figured first see if oscar shoots himself [22:12] So, I take it nobody here wants to take on the "match the emulated handhelds to items on archive and in the code" stuff, and I should shake my discord for someone? [22:17] (I expect people doing code stuff, like db48x and DFJustin and bai and azakai and so on not to have time for it. But anyone else?) [22:38] Haha, no suicide here, just need to figure out what I need to do from a metadata standpoint to specify that. But right now, I'm cooking dinner... should be back this evening, but I'm turning it over mentally meanwhile. [22:39] Because we should be able to specify a zip archive to hold (at least some of) the disks in the metadata, right? Well. I haven't looked at the schema. [22:41] mostly the items just specify an extension, and the Emularity tries to use all files with that extension [22:44] Yeah, I noticed that. [22:45] So it's a question of organization... I would think you'd want to specify at least *something* in the metadata instead of just ordering the filenames to come out right? [22:45] Anyway, I'll monkey around a bit more after we finish dinner and bathtime, etc. for the kids. [22:51] yea, it will also look for properties named like 'mame_peripheral_flop1' (and similar for any mame device you might want to use) [22:52] it would be nice to explicitly list every disk image available in the item, along with human-readable descriptions for each of them [22:53] but for now filename order is good enough [23:33] DFJustin: https://archive.org/details/hh_gnw_dkong2 - better resolution? [23:33] Filename order is the best. [23:52] So, I did a thing [23:53] https://archive.org/details/hh_taltbeast [23:53] *** balrog has quit IRC (Quit: Bye) [23:58] *** balrog has joined #jsmess