[00:49] *** tech234a has quit IRC (Read error: Connection timed out) [00:57] *** tech234a has joined #jsmess [01:23] *** tech234a has quit IRC (Ping timeout: 1230 seconds) [01:30] *** tech234a has joined #jsmess [02:24] *** Vito`_ has quit IRC (Ping timeout: 1230 seconds) [02:24] *** mattl_ has quit IRC (Ping timeout: 1230 seconds) [02:24] *** Vito`_ has joined #jsmess [02:24] *** mattl_ has joined #jsmess [02:43] *** Ctrl-S___ has quit IRC (Ping timeout: 1230 seconds) [02:44] *** Ctrl-S___ has joined #jsmess [04:44] *** Ctrl-S___ has quit IRC (Ping timeout: 1230 seconds) [04:44] *** mattl_ has quit IRC (Ping timeout: 1230 seconds) [04:44] *** mattl_ has joined #jsmess [04:45] *** Ctrl-S___ has joined #jsmess [05:55] *** tech234a has quit IRC (Ping timeout: 1230 seconds) [05:55] *** tech234a has joined #jsmess [07:19] *** Vito`_ has quit IRC (Ping timeout: 1230 seconds) [07:19] *** Vito`_ has joined #jsmess [07:43] *** Ctrl-S___ has quit IRC (Ping timeout: 1230 seconds) [07:44] *** Ctrl-S___ has joined #jsmess [08:00] *** Sgeo has quit IRC (Read error: Connection reset by peer) [08:52] *** tech234a has quit IRC (Ping timeout: 1230 seconds) [08:53] *** tech234a has joined #jsmess [08:59] *** balrog has quit IRC (hub.efnet.us irc.colosolutions.net) [09:01] *** balrog_ has joined #jsmess [09:14] *** balrog_ is now known as balrog [09:33] *** Ctrl-S___ has quit IRC (Ping timeout: 1230 seconds) [09:34] *** Ctrl-S___ has joined #jsmess [10:21] *** tech234a has quit IRC (Ping timeout: 1230 seconds) [10:21] *** tech234a has joined #jsmess [10:39] *** mattl_ has quit IRC (Ping timeout: 1230 seconds) [10:40] *** mattl_ has joined #jsmess [11:14] *** Ctrl-S___ has quit IRC (Ping timeout: 1230 seconds) [11:22] *** Ctrl-S___ has joined #jsmess [11:35] *** Vito`_ has quit IRC (Ping timeout: 1230 seconds) [11:35] *** Vito`_ has joined #jsmess [12:17] *** tech234a has quit IRC (Ping timeout: 1230 seconds) [12:18] *** tech234a has joined #jsmess [12:36] *** mattl_ has quit IRC (Ping timeout: 1230 seconds) [12:36] *** mattl_ has joined #jsmess [13:11] *** Ctrl-S___ has quit IRC (Ping timeout: 1230 seconds) [13:12] *** Ctrl-S___ has joined #jsmess [14:41] *** Sgeo has joined #jsmess [15:28] *** Vito`_ has quit IRC (Ping timeout: 1230 seconds) [15:28] *** Vito`_ has joined #jsmess [15:56] *** tech234a has quit IRC (Ping timeout: 1230 seconds) [16:03] *** tech234a has joined #jsmess [17:05] *** Ctrl-S___ has quit IRC (Ping timeout: 1230 seconds) [17:06] *** Ctrl-S___ has joined #jsmess [17:48] *** mattl_ has quit IRC (Ping timeout: 1230 seconds) [17:48] *** mattl_ has joined #jsmess [18:06] *** Lord_Nigh has quit IRC (Read error: Operation timed out) [18:20] *** Lord_Nigh has joined #jsmess [18:38] *** Lord_Nigh has quit IRC (Read error: Connection reset by peer) [18:55] *** Lord_Nigh has joined #jsmess [21:13] So, here's my next question. We're getting on well into a year or two since I added new emulator types into the system. The question is if there's an even slightly easy way to know what emulators we currently don't support that are ready to be supported. [21:13] Do we in any way have a listing, somewhere, that says "This is now working. This can be added." [21:13] And then I can go ahead and add them to the driver list, start getting them in, etc.