IRC log for #wowprogramming on 20110101

15:35.24*** join/#wowprogramming infobot (~infobot@rikers.org)
15:35.24*** topic/#wowprogramming is World of Warcraft Programming: A Guide and Reference for Creating WoW Addons ~ http://wowprogramming.com
16:25.30*** join/#wowprogramming stolenlegacy (~stolenleg@chello213047049244.5.sc-graz.chello.at)
18:12.44*** join/#wowprogramming Zasurus (~Zasurus@78-105-174-15.zone3.bethere.co.uk)
18:45.55lua_botNew edit on node 'docs/api/BNIsSelf' by Adys (No summary) - http://wowprogramming.com/docs/api/BNIsSelf
18:59.38*** join/#wowprogramming Iriel (~Iriel@adsl-71-158-244-138.dsl.pltn13.sbcglobal.net)
19:36.11lua_botNew edit on node 'docs/events/PLAYER_AVG_ITEM_LEVEL_READY' by Adys (No summary) - http://wowprogramming.com/docs/events/PLAYER_AVG_ITEM_LEVEL_READY
19:37.41lua_botNew edit on node 'docs/events/AUCTION_HOUSE_DISABLED' by Adys (No summary) - http://wowprogramming.com/docs/events/AUCTION_HOUSE_DISABLED
19:39.38Adysjnwhiteh: two things top off my mind
19:39.47jnwhitehok
19:39.48Adysjnwhiteh: first of all, all the CHAT_MSG_* events need to be cleaned up
19:40.04Adysi wanted to do that but ive never worked with them and so on
19:40.11jnwhitehwe stopped doing events
19:40.17jnwhitehi believe its the right thing to do.
19:40.23jnwhitehwith very few exceptions
19:40.25Adyswhatchoo mean?
19:40.26jnwhitehlike GUILD_ROSTER_UPDATE
19:40.28jnwhitehwell
19:40.29jnwhitehthey change
19:40.31jnwhitehtoo frequently
19:40.34jnwhitehand they're too repetitive
19:40.40jnwhitehand /eventtrace gives the BEST information you can find
19:41.29Adysmmh, fair nuf
19:41.36Adysare you planning to remove the documentation on them entirely?
19:41.49Adysi mean, even if they change, its still nice to have descriptions for them
19:41.49jnwhitehno
19:41.51jnwhitehbut I could
19:42.03jnwhitehwhat I did was drop all but descriptions from the book
19:42.12jnwhitehI could change the node prototype to drop arguments/returns from the event node
19:42.18jnwhitehprobably makes more sense
19:42.23Adyssounds good
19:42.28Adyssecond thing, still on events
19:42.28jnwhitehand have a static note on each page showing how they can get information about the arguments.
19:42.33jnwhitehi dont know when i'll remember to do that
19:42.36jnwhitehmy life is rough atm
19:43.13Adysdropping the nodes isnt really urgent, i can take care of documenting whatever's left and not care about the args
19:43.26Adysso yeah; second thing, is it okay to categorize them?
19:43.50jnwhitehi think its a lost cause
19:44.13Adyshow so?
19:44.21jnwhitehwell, there's so much of the API that needs to be documented
19:44.27jnwhitehthats much more important
19:44.46jnwhitehevents almost ALWAYS have code that we can look at in the FrameXML
19:44.52jnwhiteh_AND_ we have /eventtrace and a way to reproduce them
19:44.58jnwhitehso I consider them much less important
19:45.04Adysthe thing about categorizing is
19:45.04jnwhitehteach a man to fish, and all that :P
19:45.29Adysi often get people saying "what event should i watch for if i want <this> or <that> feature ready"
19:45.42Adysshirik was asking again about it yesterday
19:45.54Adyswanted to check when guildname was ready, i just looked at guild-related events
19:46.59Adysjnwhiteh: anyway, this is more of an "is it okay if i spam the channel with event categorizing" question; wont take me long
19:47.18jnwhitehwell there's no categorization page
19:47.29Adysthat can be added later no?
19:47.29jnwhitehand a search for GUILD_ or _GUILD should get you most of the responses :P
19:47.43jnwhitehthat's my general feeling
19:47.50Adysfair nuf ill leave it alone for now
19:51.44lua_botNew edit on node 'docs/events/CONFIRM_DISENCHANT_ROLL' by Adys (No summary) - http://wowprogramming.com/docs/events/CONFIRM_DISENCHANT_ROLL
19:51.45lua_botNew edit on node 'docs/events/COMPANION_UNLEARNED' by Adys (No summary) - http://wowprogramming.com/docs/events/COMPANION_UNLEARNED
19:54.04lua_botNew edit on node 'docs/events/TALENTS_INVOLUNTARILY_RESET' by Adys (No summary) - http://wowprogramming.com/docs/events/TALENTS_INVOLUNTARILY_RESET
19:55.21lua_botNew edit on node 'docs/events/UNIT_TARGETABLE_CHANGED' by Adys (No summary) - http://wowprogramming.com/docs/events/UNIT_TARGETABLE_CHANGED
19:55.22lua_botNew edit on node 'docs/events/UNIT_PHASE' by Adys (No summary) - http://wowprogramming.com/docs/events/UNIT_PHASE
19:55.23lua_botNew edit on node 'docs/events/UI_SCALE_CHANGED' by Adys (No summary) - http://wowprogramming.com/docs/events/UI_SCALE_CHANGED
19:55.23lua_botNew edit on node 'docs/events/UNIT_CONNECTION' by Adys (No summary) - http://wowprogramming.com/docs/events/UNIT_CONNECTION
19:56.22lua_botNew edit on node 'docs/events/VOTE_KICK_REASON_NEEDED' by Adys (No summary) - http://wowprogramming.com/docs/events/VOTE_KICK_REASON_NEEDED
19:57.35lua_botNew edit on node 'docs/events/STREAMING_ICON' by Adys (No summary) - http://wowprogramming.com/docs/events/STREAMING_ICON
19:59.54lua_botNew edit on node 'docs/events/BATTLEFIELD_QUEUE_TIMEOUT' by Adys (No summary) - http://wowprogramming.com/docs/events/BATTLEFIELD_QUEUE_TIMEOUT
19:59.55lua_botNew edit on node 'docs/events/BN_CONNECTED' by Adys (No summary) - http://wowprogramming.com/docs/events/BN_CONNECTED
19:59.56lua_botNew edit on node 'docs/events/BN_DISCONNECTED' by Adys (No summary) - http://wowprogramming.com/docs/events/BN_DISCONNECTED
19:59.57lua_botNew edit on node 'docs/events/FORGE_MASTER_SET_ITEM' by Adys (No summary) - http://wowprogramming.com/docs/events/FORGE_MASTER_SET_ITEM
19:59.58lua_botNew edit on node 'docs/events/FORGE_MASTER_OPENED' by Adys (No summary) - http://wowprogramming.com/docs/events/FORGE_MASTER_OPENED
20:00.04lua_botNew edit on node 'docs/events/FORGE_MASTER_ITEM_CHANGED' by Adys (No summary) - http://wowprogramming.com/docs/events/FORGE_MASTER_ITEM_CHANGED
20:00.05lua_botNew edit on node 'docs/events/FORGE_MASTER_CLOSED' by Adys (No summary) - http://wowprogramming.com/docs/events/FORGE_MASTER_CLOSED
20:01.20lua_botNew edit on node 'docs/events/AUCTION_MULTISELL_FAILURE' by Adys (No summary) - http://wowprogramming.com/docs/events/AUCTION_MULTISELL_FAILURE
20:01.21lua_botNew edit on node 'docs/events/ARTIFACT_DIG_SITE_UPDATED' by Adys (No summary) - http://wowprogramming.com/docs/events/ARTIFACT_DIG_SITE_UPDATED
20:02.27lua_botNew edit on node 'docs/events/GUILD_PERK_UPDATE' by Adys (No summary) - http://wowprogramming.com/docs/events/GUILD_PERK_UPDATE
20:04.33lua_botNew edit on node 'docs/events/INSPECT_READY' by Adys (No summary) - http://wowprogramming.com/docs/events/INSPECT_READY
20:04.34lua_botNew edit on node 'docs/events/INSTANCE_ENCOUNTER_ENGAGE_UNIT' by Adys (No summary) - http://wowprogramming.com/docs/events/INSTANCE_ENCOUNTER_ENGAGE_UNIT
20:05.02Adysjnwhiteh: thats all the ones I can do off the top of my head
20:06.06lua_botNew edit on node 'docs/events/UNIT_MAXPOWER' by Adys (No summary) - http://wowprogramming.com/docs/events/UNIT_MAXPOWER
20:07.19jnwhitehk
20:08.37Adysjnwhiteh: how do you get the event listings btw?
20:08.38lua_botNew edit on node 'docs/events/GM_PLAYER_INFO' by Adys (No summary) - http://wowprogramming.com/docs/events/GM_PLAYER_INFO
20:08.49jnwhitehwhat do you mean?
20:09.03Adysthe list of all events, how do you get it? since you dont scan the exe
20:09.09jnwhitehyes I do
20:09.17Adysoh, i thought you didnt
20:09.18jnwhiteh:P
20:09.21jnwhitehI do
20:09.25jnwhitehbut everything is 100% verified
20:09.30jnwhitehI just get 'candidates'
20:09.33jnwhitehand then see which ones are real
20:09.39jnwhitehthat's why wowprogramming is always right :P
20:09.52Adysis it possible to reg all events on a frame
20:09.57Adysand look at what the frame registered?
20:10.31jnwhitehyes, but I don't do that
20:10.35jnwhitehI register an event
20:10.44jnwhitehcheck to see if its registered
21:56.52*** join/#wowprogramming Zasurus (~Zasurus@78-105-174-15.zone3.bethere.co.uk)
22:23.46*** join/#wowprogramming stolenlegacy (~stolenleg@chello213047049244.5.sc-graz.chello.at)

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