| 00:37.10 | *** join/#wowprogramming Treeston (~stolenleg@chello213047049072.5.graz.surfer.at) |
| 03:10.48 | *** join/#wowprogramming Iriel (~Iriel@173-8-135-209-SFBA.hfc.comcastbusiness.net) |
| 03:45.11 | *** join/#wowprogramming Adys (~adys@unaffiliated/adys) |
| 07:42.18 | AcidWeb | BTW jnwhiteh what is your policy about MoP update of wowprogramming.com. I can start updating it right after addons will be enabled in beta or wait for official release? |
| 07:43.12 | jnwhiteh | I have to run an API scan |
| 07:43.17 | jnwhiteh | let me see if I have th ebeta installed anywhere. |
| 07:43.37 | jnwhiteh | I'll patch up |
| 07:43.40 | jnwhiteh | and look at how bad it is |
| 07:43.49 | *** part/#wowprogramming Iriel (~Iriel@173-8-135-209-SFBA.hfc.comcastbusiness.net) |
| 07:43.59 | jnwhiteh | the problem is that updating the API master file would cause any functions that are going away to disappear from listsings. |
| 07:44.15 | jnwhiteh | in the meantime, you could add any NEW ones you want |
| 07:44.21 | jnwhiteh | that would be easy |
| 07:44.35 | jnwhiteh | just use the flag mop |
| 07:44.41 | jnwhiteh | so I can find them and batch process them if necessary |
| 07:44.42 | jnwhiteh | hell |
| 07:44.48 | jnwhiteh | anything you touch for mop just use that flag |
| 07:44.57 | jnwhiteh | and i'll be able to figure it out |
| 07:45.02 | jnwhiteh | heading to work, bbl |
| 07:46.10 | AcidWeb | I'm not talking about the technical aspects but about content changes that might confuse users of your page. aka Newbies that will read about things that are not yet in retail client. |
| 09:03.03 | *** join/#wowprogramming tardmrr (~tardmrr@74.80.58.143) |
| 09:03.47 | *** join/#wowprogramming tardmrr (~tardmrr@WoWUIDev/WoWI/Dongle/Tem) |
| 09:03.47 | *** mode/#wowprogramming [+v tardmrr] by ChanServ |
| 11:01.23 | *** join/#wowprogramming tem (~tardmrr@WoWUIDev/WoWI/Dongle/Tem) |
| 11:01.24 | *** mode/#wowprogramming [+v tem] by ChanServ |
| 11:07.45 | *** join/#wowprogramming stolenlegacy (~stolenleg@unaffiliated/stolenlegacy) |
| 15:30.39 | *** join/#wowprogramming stolenlegacy (stolenlega@unaffiliated/stolenlegacy) |
| 16:51.17 | *** join/#wowprogramming Torhal|work (~torhal_wo@67.58.77.206) |
| 19:04.00 | jnwhiteh | AcidWeb: I'm not sure I quite understand.. what on wowprogramming concerns content changes? |
| 20:08.47 | *** join/#wowprogramming Torhal|work (~torhal_wo@67.58.77.206) |
| 20:59.34 | AcidWeb | jnwhiteh: Let me provide hypothetical scenario. MoP client have enabled addons and we start adding MoP changes to wowprogramming. A wild newbie appear. He still writting Cata addons - he might make errors trying using methods that dont work in Cata yet. |
| 21:00.11 | jnwhiteh | yes, this is exactly what I was talking about |
| 21:00.17 | jnwhiteh | its a matter of whether or not I update the master listing. |
| 21:00.33 | AcidWeb | OK. Then i missunderstand you. Sorry. |
| 21:00.36 | jnwhiteh | the individual pages can be added easily |
| 21:00.44 | jnwhiteh | nothing stopping it from beign done now. |
| 21:00.50 | jnwhiteh | they won't be in the listing until the master is updated |
| 21:01.03 | jnwhiteh | the only *problems* are when something that already exists gets updated and changed for mop |
| 21:01.10 | jnwhiteh | those, i'll do what I can to fix manually with notes, etc. |
| 21:04.19 | AcidWeb | k |
| 22:11.42 | *** join/#wowprogramming stolenlegacy (stolenlega@unaffiliated/stolenlegacy) |