#bitfighter IRC Log

IRC Log for 2012-07-19

Timestamps are in GMT/BST.

00:21:12 BFLogBot - Commit 37df79c4d9f3 | Author: watusim...@bitfighter.org | Log: SetTeam lua method now working, at least for some objects, try to "normalize" the handling of certain attributes in pack/unpack updates
00:21:14 BFLogBot - Commit 2bc6d0e79bfc | Author: watusim...@bitfighter.org | Log: Rename gameObject.cpp/h to BfObject.cpp/h
00:21:15 BFLogBot - Commit d3fddd5412a1 | Author: watusim...@bitfighter.org | Log: More cleanup of pack/unpack
00:21:17 BFLogBot - Commit 586b2cc0e0e3 | Author: watusim...@bitfighter.org | Log: Add Lua methods to NexusZone, not fully functional yet
00:21:18 BFLogBot - Commit c1e3b0a5fe30 | Author: watusim...@bitfighter.org | Log: Add Lua methods to NexusZone, not fully functional yet
02:33:08 raptor has joined
02:33:09 ChanServ sets mode +o raptor
02:33:46 raptor Watusimoto: are you really awake?
04:07:51 raptor Quit ()
07:33:45 Watusimoto Quit (Ping timeout: 260 seconds)
07:43:39 sam686 has left
07:53:40 watusimoto has joined
07:53:41 ChanServ sets mode +o watusimoto
10:56:01 kodaws has joined
11:00:47 LordDVG has joined
11:22:04 kodaws Quit (Ping timeout: 248 seconds)
12:08:56 raptor has joined
12:08:56 ChanServ sets mode +o raptor
12:10:30 LordDVG Quit (Remote host closed the connection)
12:47:08 kodaws has joined
15:27:56 raptor Quit ()
15:51:26 raptor has joined
15:51:26 ChanServ sets mode +o raptor
16:18:58 raptor good day!
16:45:53 watusimoto Quit (Read error: Operation timed out)
17:12:56 kodaws Quit (Read error: Connection reset by peer)
17:40:48 Watusimoto has joined
18:43:11 Watusimoto no
18:43:25 Watusimoto well, yes, actually
18:43:30 Watusimoto but not at the time
18:43:44 raptor doesn't know what you are talking about
18:44:28 Watusimoto watusimoto was answering the question you posed at 4:33AM this morning
18:44:38 Watusimoto "are you really awake?"
18:46:02 raptor oh yeah
19:14:05 raptor i sadly have had little time to work on bitfighter of late - too much school and life stuff going on  :(
19:17:51 Watusimoto that's probably good news :-)
19:17:58 Watusimoto quick design question:
19:18:32 Watusimoto I added 4 new methods to nexusZone (renamed from NexusObject)
19:18:44 Watusimoto isOpen, setOpen, setOpenTime, setCloseTime
19:18:55 Watusimoto so Lua could control the nexys
19:18:58 raptor ok
19:19:25 Watusimoto though they operate on the nexus object itself, they are really passthroughs to the NexusgameType which is where all that stuff happens
19:19:36 Watusimoto these are not nexys-by-nexus methods
19:19:45 raptor ah
19:19:46 Watusimoto so here's the problem
19:20:01 Watusimoto 1) It seems very natural to query a nexus object about its status
19:20:14 Watusimoto and also to set its status
19:20:22 Watusimoto and so on
19:20:32 Watusimoto but if you do this:
19:20:45 Watusimoto n = NexusZone.new(); n.setOpen(true)
19:21:18 Watusimoto you get an error (or rather you did before I fixed it) because nexus isn't yet in a game, and so it has no game and thus no gametype to pass the setOpen cmd to
19:21:24 Watusimoto so nothing happens
19:21:27 Watusimoto this, however, works:
19:21:45 Watusimoto n=nexusZone.new(); n:addToGame(); n:setOpen(true)
19:22:13 Watusimoto I do plan on adding similar methods to NexusGameType (if I can figure out how to make that work)
19:22:23 raptor and that is because it is routed through the gametype
19:22:23 Watusimoto but the question is should I remove them from NexusZone?
19:22:29 Watusimoto yes
19:22:35 raptor hmmm
19:23:00 raptor so maybe the question is, should a game object contain methods to manipulate itself, or just attributes?
19:23:35 Watusimoto but it's not manipulating itself
19:23:40 Watusimoto that'st he probelm
19:23:47 Watusimoto it's manipulating the gameType
19:23:59 raptor ohhhh
19:24:03 Watusimoto but from the user's standpoint, it's the nexus that they're changing
19:24:29 Watusimoto if you want to open the nexus, you want to write code like: n = findNexus(); n:open()
19:24:32 Watusimoto or something
19:24:49 Watusimoto you don't want to do g = getGameType(); g.openNexus()
19:25:03 Watusimoto even though the second is really the proper thing
19:25:14 raptor hmmm
19:25:27 Watusimoto unless, of course, we made each nexus open and close on its own schedule
19:25:43 Watusimoto but this would mess up the timer display, and be kind of a pain
19:26:13 raptor ^^ that would allow for multiple nexii with different timers each
19:26:19 raptor but display would be hard
19:27:46 Watusimoto yes -- we'd probably need to get rid of the nexus timer display, or display the time of the nearest one or something
19:28:08 Watusimoto though it would be cool to have different nexus schedules and different scores
19:28:26 raptor i think it makes more sense to have each nexus control it's own time
19:28:26 Watusimoto but I think the timer display is kind of important
19:28:51 Watusimoto maybe
19:29:29 raptor maybe we could display the top 2 or 3 nexus timers, add a number to them and number the overlay arrows
19:30:29 Watusimoto that would be difficult for players to figure out, I think
19:30:37 Watusimoto maybe a timer on the arrow itself?
19:30:55 Watusimoto and revert to current timer if all nexii have the same schedule?
19:31:18 raptor i like that
19:31:20 Watusimoto though multiple timers would get jumbled
19:31:30 Watusimoto imagine 3 nexii off to the right
19:31:35 Watusimoto all kind of in line
19:31:53 Watusimoto we'd have to space the timers out a bit
19:31:59 Watusimoto and thus the arrows
19:32:28 raptor or detect the timer dimensions on the display and make sure they don't overlap
19:33:40 raptor rats - i have to go home and study now.  sorry
19:34:44 masterkaen has joined
19:34:45 kaen Quit (Read error: Connection reset by peer)
19:38:44 raptor Quit ()
19:46:19 masterkaen Quit (Quit: Leaving)
19:46:38 kaen has joined
21:38:43 sam686 has joined
21:38:48 ChanServ sets mode +v sam686

Index Search ←Prev date Next date→

These logs were automatically created by BFLogBot on irc.freenode.net.

00:21:12		BFLogBot - Commit 37df79c4d9f3 \| Author: watusim...@bitfighter.org \| Log: SetTeam lua method now working, at least for some objects, try to "normalize" the handling of certain attributes in pack/unpack updates
00:21:14		BFLogBot - Commit 2bc6d0e79bfc \| Author: watusim...@bitfighter.org \| Log: Rename gameObject.cpp/h to BfObject.cpp/h
00:21:15		BFLogBot - Commit d3fddd5412a1 \| Author: watusim...@bitfighter.org \| Log: More cleanup of pack/unpack
00:21:17		BFLogBot - Commit 586b2cc0e0e3 \| Author: watusim...@bitfighter.org \| Log: Add Lua methods to NexusZone, not fully functional yet
00:21:18		BFLogBot - Commit c1e3b0a5fe30 \| Author: watusim...@bitfighter.org \| Log: Add Lua methods to NexusZone, not fully functional yet
02:33:08		raptor has joined
02:33:09		ChanServ sets mode +o raptor
02:33:46	raptor	Watusimoto: are you really awake?
04:07:51		raptor Quit ()
07:33:45		Watusimoto Quit (Ping timeout: 260 seconds)
07:43:39		sam686 has left
07:53:40		watusimoto has joined
07:53:41		ChanServ sets mode +o watusimoto
10:56:01		kodaws has joined
11:00:47		LordDVG has joined
11:22:04		kodaws Quit (Ping timeout: 248 seconds)
12:08:56		raptor has joined
12:08:56		ChanServ sets mode +o raptor
12:10:30		LordDVG Quit (Remote host closed the connection)
12:47:08		kodaws has joined
15:27:56		raptor Quit ()
15:51:26		raptor has joined
15:51:26		ChanServ sets mode +o raptor
16:18:58	raptor	good day!
16:45:53		watusimoto Quit (Read error: Operation timed out)
17:12:56		kodaws Quit (Read error: Connection reset by peer)
17:40:48		Watusimoto has joined
18:43:11	Watusimoto	no
18:43:25	Watusimoto	well, yes, actually
18:43:30	Watusimoto	but not at the time
18:43:44		raptor doesn't know what you are talking about
18:44:28	Watusimoto	watusimoto was answering the question you posed at 4:33AM this morning
18:44:38	Watusimoto	"are you really awake?"
18:46:02	raptor	oh yeah
19:14:05	raptor	i sadly have had little time to work on bitfighter of late - too much school and life stuff going on :(
19:17:51	Watusimoto	that's probably good news :-)
19:17:58	Watusimoto	quick design question:
19:18:32	Watusimoto	I added 4 new methods to nexusZone (renamed from NexusObject)
19:18:44	Watusimoto	isOpen, setOpen, setOpenTime, setCloseTime
19:18:55	Watusimoto	so Lua could control the nexys
19:18:58	raptor	ok
19:19:25	Watusimoto	though they operate on the nexus object itself, they are really passthroughs to the NexusgameType which is where all that stuff happens
19:19:36	Watusimoto	these are not nexys-by-nexus methods
19:19:45	raptor	ah
19:19:46	Watusimoto	so here's the problem
19:20:01	Watusimoto	1) It seems very natural to query a nexus object about its status
19:20:14	Watusimoto	and also to set its status
19:20:22	Watusimoto	and so on
19:20:32	Watusimoto	but if you do this:
19:20:45	Watusimoto	n = NexusZone.new(); n.setOpen(true)
19:21:18	Watusimoto	you get an error (or rather you did before I fixed it) because nexus isn't yet in a game, and so it has no game and thus no gametype to pass the setOpen cmd to
19:21:24	Watusimoto	so nothing happens
19:21:27	Watusimoto	this, however, works:
19:21:45	Watusimoto	n=nexusZone.new(); n:addToGame(); n:setOpen(true)
19:22:13	Watusimoto	I do plan on adding similar methods to NexusGameType (if I can figure out how to make that work)
19:22:23	raptor	and that is because it is routed through the gametype
19:22:23	Watusimoto	but the question is should I remove them from NexusZone?
19:22:29	Watusimoto	yes
19:22:35	raptor	hmmm
19:23:00	raptor	so maybe the question is, should a game object contain methods to manipulate itself, or just attributes?
19:23:35	Watusimoto	but it's not manipulating itself
19:23:40	Watusimoto	that'st he probelm
19:23:47	Watusimoto	it's manipulating the gameType
19:23:59	raptor	ohhhh
19:24:03	Watusimoto	but from the user's standpoint, it's the nexus that they're changing
19:24:29	Watusimoto	if you want to open the nexus, you want to write code like: n = findNexus(); n:open()
19:24:32	Watusimoto	or something
19:24:49	Watusimoto	you don't want to do g = getGameType(); g.openNexus()
19:25:03	Watusimoto	even though the second is really the proper thing
19:25:14	raptor	hmmm
19:25:27	Watusimoto	unless, of course, we made each nexus open and close on its own schedule
19:25:43	Watusimoto	but this would mess up the timer display, and be kind of a pain
19:26:13	raptor	^^ that would allow for multiple nexii with different timers each
19:26:19	raptor	but display would be hard
19:27:46	Watusimoto	yes -- we'd probably need to get rid of the nexus timer display, or display the time of the nearest one or something
19:28:08	Watusimoto	though it would be cool to have different nexus schedules and different scores
19:28:26	raptor	i think it makes more sense to have each nexus control it's own time
19:28:26	Watusimoto	but I think the timer display is kind of important
19:28:51	Watusimoto	maybe
19:29:29	raptor	maybe we could display the top 2 or 3 nexus timers, add a number to them and number the overlay arrows
19:30:29	Watusimoto	that would be difficult for players to figure out, I think
19:30:37	Watusimoto	maybe a timer on the arrow itself?
19:30:55	Watusimoto	and revert to current timer if all nexii have the same schedule?
19:31:18	raptor	i like that
19:31:20	Watusimoto	though multiple timers would get jumbled
19:31:30	Watusimoto	imagine 3 nexii off to the right
19:31:35	Watusimoto	all kind of in line
19:31:53	Watusimoto	we'd have to space the timers out a bit
19:31:59	Watusimoto	and thus the arrows
19:32:28	raptor	or detect the timer dimensions on the display and make sure they don't overlap
19:33:40	raptor	rats - i have to go home and study now. sorry
19:34:44		masterkaen has joined
19:34:45		kaen Quit (Read error: Connection reset by peer)
19:38:44		raptor Quit ()
19:46:19		masterkaen Quit (Quit: Leaving)
19:46:38		kaen has joined
21:38:43		sam686 has joined
21:38:48		ChanServ sets mode +v sam686