| 01:05.20 | *** join/#bzflag DTRemenak (~DTRemenak@cpe-172-112-10-183.socal.res.rr.com) |
| 01:05.20 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 01:05.20 | *** mode/#bzflag [+v DTRemenak] by ChanServ |
| 02:32.33 | *** join/#bzflag bertman (~bert@unaffiliated/bertman) |
| 05:32.11 | *** join/#bzflag dngor (abuse@p3m/dngor) |
| 05:43.19 | *** join/#bzflag DipoleHourglass (uid134094@gateway/web/irccloud.com/x-tybspiqfimgowkjx) |
| 06:05.40 | *** join/#bzflag Cobra_Fast (~coprah@wtwrp.de) |
| 06:05.49 | *** join/#bzflag EvilJStoker (jstoker@unaffiliated/jstoker) |
| 06:06.20 | *** join/#bzflag aFreshMelon (sid25548@gateway/web/irccloud.com/x-wtsmhicecjroirrm) |
| 06:10.56 | *** join/#bzflag tw1sted (~tw1sted@104.236.87.240) |
| 06:10.56 | *** join/#bzflag [dmp] (~dennis@unaffiliated/dmp/x-546784) |
| 06:10.56 | *** join/#bzflag bboles_ (~quassel@2607:fcd0:100:8300:1c::a3ed) |
| 07:42.50 | *** join/#bzflag L4m3r (~l4m3r@bzflag/developer/L4m3r) |
| 07:42.50 | *** mode/#bzflag [+v L4m3r] by ChanServ |
| 11:27.01 | *** join/#bzflag Delusional (~Delusiona@pool-74-98-250-92.pitbpa.fios.verizon.net) |
| 11:27.43 | *** join/#bzflag Delusional (~Delusiona@unaffiliated/delusional) |
| 11:48.45 | *** join/#bzflag joevano (~joevano@bzflag/developer/JoeVano) |
| 11:48.45 | *** mode/#bzflag [+v joevano] by ChanServ |
| 17:34.02 | blast007 | For 2.6, I think it would be nice to replace our various flat file storage formats (server: bans, reports, maybe groups; client: server list cache, HTTP resource index, maybe the client config) with something that has a bit more of a formal structure. So some options would be a different structured text format like YAML, or an embedded database like SQLite3. YAML was already something being pondered |
| 17:34.08 | blast007 | for plugin configuration files (instead ... |
| 17:34.11 | blast007 | ... of the existing .ini format) in issue #7 of the bzflag repo. |
| 17:34.36 | blast007 | (I should also figure out why this irssi plugin to split long lines break like that sometimes) :P |
| 17:35.13 | allejo | i'd be in favor of YAML |
| 17:35.14 | the_map | speaking out of complete ignorance, JSON seems to be a pretty good format, and possibly has parsing libraries |
| 17:35.39 | blast007 | JSON is okay for data, less good for configurations. it lacks support for comments. |
| 17:35.42 | allejo | I just don't like JSON's lack of readability when maintaining manually |
| 17:36.26 | blast007 | yeah, JSON isn't really desiged for human manipulation |
| 17:40.58 | JeffM | I've used sqlite for configs before |
| 17:41.19 | JeffM | several DB tools make it easy to edit/debug the data manual |
| 17:43.10 | blast007 | with things like bans and groups (but probably not reports), these tend to get shared |
| 17:43.32 | JeffM | and it makes doing reports/searches way easier |
| 17:43.46 | JeffM | an actual queriable data file |
| 17:44.16 | blast007 | with sqlite, we'd still have to wrangle some of the data in our code into a format the game can work with, at least for bans |
| 17:44.33 | JeffM | sure, but that's just code |
| 17:44.37 | blast007 | I've been playing with SQLite3's API for this |
| 17:44.54 | JeffM | there is a nice .net layer for it I've used quite a bit |
| 20:36.08 | *** join/#bzflag qayshp (~Adium@bellevue.maana.io) |
| 21:18.46 | qayshp | @L4m3r one of my coworkers just said they play bzflag :) had to drop in |
| 21:20.32 | the_map | hello |