IRC log for #bzflag on 20130228

01:22.37*** join/#bzflag Constitution (~josh@bzflag/developer/Constitution)
02:04.07*** join/#bzflag Marzipan (~Marzipan@sign-4db6b2dd.pool.mediaWays.net)
02:13.24*** join/#bzflag Detrimental (~james@h44.239.90.75.dynamic.ip.windstream.net)
03:30.51*** join/#bzflag JeffM (~JeffM@cpe-76-167-236-199.socal.res.rr.com)
03:30.51*** join/#bzflag JeffM (~JeffM@unaffiliated/jeffm2501)
03:30.51*** mode/#bzflag [+v JeffM] by ChanServ
04:18.24*** join/#bzflag Fira (artix@unaffiliated/fira)
04:18.44*** join/#bzflag [dmp] (~dennis@users.d75.net)
04:18.44*** join/#bzflag [dmp] (~dennis@unaffiliated/dmp/x-546784)
04:54.32*** join/#bzflag jeffm (~jeffm@cpe-76-167-236-199.socal.res.rr.com)
04:54.32*** join/#bzflag jeffm (~jeffm@unaffiliated/jeffm2501)
04:54.32*** mode/#bzflag [+v jeffm] by ChanServ
07:05.09*** join/#bzflag ashvala (~ashvala@unaffiliated/ashvala)
07:16.37*** join/#bzflag Marzipan- (~Marzipan@sign-4db6bb31.pool.mediaWays.net)
07:38.49*** join/#bzflag rathis (~rathis@b01bd9ce.bb.sky.com)
08:08.30*** join/#bzflag rodgort (~rodgort@li125-242.members.linode.com)
09:50.36*** join/#bzflag ashvala (~ashvala@unaffiliated/ashvala)
11:10.25*** join/#bzflag ashvala (~ashvala@unaffiliated/ashvala)
14:55.16*** join/#bzflag ibot (~ibot@rikers.org)
14:55.16*** topic/#bzflag is http://BZFlag.org || https://www.ohloh.net/p/bzflag || http://wiki.BZFlag.org/Getting_Help || Channel Logs: http://ibot.rikers.org/%23bzflag/ || 2.4.2 is the current version
14:55.17*** mode/#bzflag [+o ibot] by ChanServ
15:47.50*** join/#bzflag ashvala (~ashvala@unaffiliated/ashvala)
15:54.30*** join/#bzflag L4m3r (~l4m3r@bzflag/developer/L4m3r)
15:54.30*** mode/#bzflag [+v L4m3r] by ChanServ
16:07.41*** join/#bzflag TimRiker (~TimRiker@bzflag/projectlead/TimRiker)
16:07.41*** mode/#bzflag [+o TimRiker] by ChanServ
16:07.55*** join/#bzflag ashvala (~ashvala@unaffiliated/ashvala)
16:13.27Notify03BZFlag:bullet_catcher * 22670 (trunk/bzflag/include/bzfsAPI.h trunk/bzflag/src/bzfs/WorldWeapons.cxx and 2 others): Remove some redundant declarations found by compiling with -Wredundant-decls.
16:16.03BulletCatcherTimRiker, what is the status of fixing the ns.mecworks.com slave DNS service?
16:17.30TimRikerwill ping mecworks again on it today. what's the status on bz.bzflag.bz ? Do we have other slave dns servers we could use?
16:18.22TimRikermy dsl line was having issues, so I changed the primary to unpublished. we could use more secondaries. I could drop mecworks if we had more listed.
16:18.36BulletCatcherbz.bzflag.bz was fixed a couple of days ago, so we only have one that isn't working right now.
16:21.06BulletCatcherThe DNS server I run at SRI-NIC.ARPA.NET is available.
16:21.55BulletCatcherOther servers that have been discussed aren't in production.
16:24.22*** join/#bzflag TimRiker (~TimRiker@bzflag/projectlead/TimRiker)
16:24.22*** mode/#bzflag [+o TimRiker] by ChanServ
16:39.27*** join/#bzflag swigg_ (~swigg@nsc69.38.101-238.newsouth.net)
16:52.13*** join/#bzflag JeffM (~JeffM@unaffiliated/jeffm2501)
16:52.14*** mode/#bzflag [+v JeffM] by ChanServ
17:24.22*** join/#bzflag swigg (~swigg@bzflag/player/Swigg)
18:18.49*** join/#bzflag BulletCatcher (~bc@bzflag/developer/BulletCatcher)
18:54.41tofu_.bz's dns is migrated to the new hardware and seems to be working, but I'll verify before throwing the switch again
19:15.38*** join/#bzflag khonkhortisan2 (~kyle@c-76-121-156-73.hsd1.wa.comcast.net)
19:15.46*** part/#bzflag khonkhortisan2 (~kyle@c-76-121-156-73.hsd1.wa.comcast.net)
19:28.28*** join/#bzflag omron (~MSkalicky@81.19.46.234)
20:23.34*** join/#bzflag TimRiker (~TimRiker@bzflag/projectlead/TimRiker)
20:23.34*** mode/#bzflag [+o TimRiker] by ChanServ
20:28.42*** join/#bzflag runde (~terje@cpe-75-80-168-176.san.res.rr.com)
21:05.08*** join/#bzflag alpha1-2 (~nb_j@201.252.143.128)
21:37.46*** join/#bzflag mas1 (~mas@81.19.46.234)
21:41.46*** part/#bzflag omron (~MSkalicky@81.19.46.234)
21:48.13allejowhat's the difference between bz_GetPlayerMottoData_V1 and bz_GetPlayerMottoData_V2?
21:48.37allejobzfs.cxx shows V2 and wiki shows V1
21:49.14swiggv2 is the deluxe version
21:49.45allejo...
21:50.18alezakosV2 offers a bz_BasePlayerRecord
21:50.57allejoohhhh perfect!
21:51.18allejouses V2
21:51.39alezakosCheck out bzfsAPI.h, line 1077
21:51.45alezakosand the wiki needs to be updated :)
21:55.09Notify03BZFlag:Allejo * 8601 /Bz_eGetPlayerMotto: added V2 info
21:55.10allejowiki updated :)
21:59.26JeffMthe wiki should document both
21:59.34JeffMas older versions won't have the V2
21:59.47JeffMthe different versions are to maintain compatability
22:00.10Constitution~allejo++
22:00.27alezakos~allejo++
22:01.14Notify03BZFlag:Allejo * 8602 /Bz_eGetPlayerMotto: v1 and v2 info
22:01.25allejo:)
22:01.38JeffMthanks
22:01.40*** join/#bzflag mas (~mas@81.19.46.234)
22:02.18JeffMmost servers run current versions, but it's probalby a good idea to document each step just in case
22:02.49JeffMand yes, kudos for taking the initiative to update yon docs
22:03.28alezakosand for helping out on the latest cheater day
22:04.23allejoJeffM, makes sense
22:04.29allejoand no worries alezakos
22:06.36JeffMhmmmm would it be possible to have a script that saw whenever there was a change in API.h and generated a ticket to review documentation?
22:07.12allejopossible yes. who's gonna write it is a different question :p
22:07.30JeffMprobably depends on what VCS we end up with
22:07.39JeffMour SF options are probably limited
22:15.13blast007BitBucket has lots of service integrations, though some of them are for paid services (like basecamp)
22:16.42blast007another option would be generating documentation *from* the source
22:16.58JeffMtrue
22:17.09JeffMI've seen that to be an ok start but it's never great
22:17.28JeffMunless you can force your developers to follow the comment conventions
22:17.44JeffMby doing it with wiki the documenters don't have to be those that can commit
22:18.04JeffMin the code you end up with every bit of documentation being a push request
22:22.03*** join/#bzflag JeffM (~JeffM@107.209.61.105)
22:22.03*** join/#bzflag JeffM (~JeffM@unaffiliated/jeffm2501)
22:22.03*** mode/#bzflag [+v JeffM] by ChanServ
22:31.17alpha1-2one question, excuseme my ignorance (I'm still new here). but isn't it that the code need allways to be documented, apart of the wiki?
22:31.45allejoin a perfect world, yes
22:31.52JeffMdepends on your definition of "need"
22:31.56JeffMand how your project is run
22:32.19alpha1-2"in a perfect world" :)
22:32.21JeffMsome agile dev houses don't bother documenting anything since if you can read the code then it is documentation
22:32.34JeffMit depends who uses the docs
22:32.45JeffMin our case the API needs to be documented for non developers
22:32.56JeffMsince the reason it exists is for them
22:33.20JeffMI'd be fine with us using a tool on the API header and making it so that changes to that header have to have the doc comments
22:33.32JeffMit'd be a good place to start and see how well we handle that kind of documentation
22:34.13alpha1-2wait... the API need to be readed mostly for non-developers than for developers?
22:34.23alpha1-2needs*
22:34.27JeffMyeah its for people to use to make plugins
22:34.33JeffMnot for use to use to modify the server
22:34.42JeffMit's used by people who are not as familiar with the core code
22:34.56JeffMwe do use it a little internaly
22:34.59alpha1-2oh, plugins
22:35.02JeffMyeah that api
22:36.12alpha1-2is API.h only for hangle plug-ins then?
22:36.19JeffMyeah
22:36.25alpha1-2uh :P
22:36.37JeffMit's all the exported functions that a plugin can use
22:36.43JeffMor should use on linux, can use on windows
22:36.44alpha1-2I will need some time for undestand this ten :)
22:37.01alpha1-2understand* then*
22:37.02JeffMon windows you have to "export" a function so it can be used by a runtime loaded module
22:37.20JeffMthe bzAPI.h is the file where we define all the functions and classes that are exported
22:37.45JeffMso it's the one header that you need to include in a plugin to give you all the functions that you can use
22:37.58JeffMit defines the plugin class and a bunch of stuff
22:38.00alpha1-2do you mean in execution time?
22:38.04JeffMyeah
22:38.08JeffMwell compile time too
22:38.10JeffMplugins are compiled
22:38.11alpha1-2uh :) interesting...
22:38.13JeffMthey are in C++ too
22:38.21JeffMthey build to a .so lib or a dll
22:39.34alpha1-2ok, ok, I'm understanding better :)
22:40.03JeffMinternaly we have all kinds of funcitons and classes but they are not exposed for a plugin to use
22:40.09JeffMon windows they can't even be used
22:40.26JeffMLinux techincaly can use them with our current compiler settings but we have talked about changing that
22:40.33JeffMjust to keep the API clean
22:40.38alpha1-2then when you refer to a documented API, this API will be used mostly for plug-ins developers than for core developers right? and then this API should be easy to read?
22:40.46JeffMyes
22:41.00JeffMand should be writen with a plugin developer in mind
22:42.54alpha1-2ok, thanks.... but in other hand, when you document core code, it should be documented normally, right? :)
22:43.03JeffMsure
22:43.25JeffMyou always should document with your target audience in mind
22:43.39alpha1-2and in the same time, I don't know, you should document it in wiki too or only plug-ins?
22:44.01JeffMwe generaly don't document the core code
22:44.07alpha1-2ok
22:44.10JeffMso it hasn't come up
22:44.15JeffMusualy we put comments in the code
22:44.22JeffMsince a core developer will be reading the code anyway
22:44.33alpha1-2yeah, I thought that :)
22:44.47JeffMit's possible to waste a lot of time doing external documentation for things that people never use.
22:46.11alpha1-2ok, I'm understanding, thanks
22:46.15JeffMsure

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.