Log for #openttdcoop.devzone on 13th January 2010:
Times are UTC Toggle Colours
00:43:08  *** KenjiE20|LT has joined #openttdcoop.devzone
00:43:13  *** KenjiE20 has quit IRC
02:15:33  *** Mark has quit IRC
02:48:38  *** KenjiE20|LT has quit IRC
03:25:09  *** PeterT has quit IRC
05:35:44  *** Frankr has joined #openttdcoop.devzone
06:35:28  *** Frankr has quit IRC
06:45:46  *** DJNekkid has quit IRC
08:22:32  *** ODM has joined #openttdcoop.devzone
08:24:58  *** welshdragon has quit IRC
10:10:32  *** Mark has joined #openttdcoop.devzone
10:59:01  *** welshdragon has joined #openttdcoop.devzone
12:09:15  *** KenjiE20 has joined #openttdcoop.devzone
14:22:09  *** Frankr has joined #openttdcoop.devzone
15:09:32  <Frankr> can i ask
15:10:34  <Frankr> when using parameters can you use one parameter for more than action or is it not possible
15:11:15  <Frankr> an example would be we want to add a Cargodest parameter which will mean planes will be cheaper to purchase and run and pax will increase
15:13:18  <Hirundo> That is possible, yes
15:15:06  <Frankr> ok cool thanks hirundo
15:16:30  <Ammler> Hirundo: can I move already committed changesets to a special branch?
15:16:49  <Ammler> as you are specialist with hg branching now :-)
15:17:16  <Hirundo> I don't know whether retroactive branching is possible
15:17:27  <Hirundo> as hg histories are generally immutable
15:53:40  <Frankr> ammler the putty key did get changed didn't it from your site
15:57:18  <Ammler> Frankr: yes
15:57:36  <Ammler> new IP and fingerprint
15:57:40  <Frankr> thought so
15:57:53  <Ammler>
15:59:09  <Frankr> thanks
15:59:39  <Ammler> you should be able to just ignore the warning and next time, it does work without, afaik
16:07:38  <Frankr> ok
17:00:06  *** Frankr has quit IRC
17:02:29  *** Frankr has joined #openttdcoop.devzone
19:20:51  <Webster> Latest update from devactivity: Redmine - Revision 3150: Set a white list of issue attributes that can be mass-assigned from cont... <>
19:42:14  *** PeterT has joined #openttdcoop.devzone
19:48:39  <andythenorth> hi hi
19:51:31  <andythenorth> planetmaker in the audience?
20:03:40  <planetmaker> hi andythenorth
20:03:44  <planetmaker> I'm somewhat here, yes
20:11:19  <andythenorth> planetmaker: without wanting to impose, wondering about FIRS economy templating for industries?
20:12:02  <planetmaker> he :-)
20:12:34  <planetmaker> what do we make dependent on a template / a config setting for the economy styles?
20:12:41  <planetmaker> availability
20:12:56  <planetmaker> probability ingame / at map generation
20:13:04  <andythenorth> yes to both of those
20:13:10  <planetmaker> something else?
20:13:17  <andythenorth> accepted and produced cargos
20:13:25  <planetmaker> oh, right
20:13:25  <andythenorth> (most wont change that, a couple will)
20:14:03  <andythenorth> let me look at industry action 0 to see if anything else...
20:14:48  <planetmaker> ok... but in any case only action0 is changed, right?
20:15:34  <andythenorth> yes, production code stays the same for all economies
20:15:50  <andythenorth> tiles might need to change cargo acceptance, but maybe not
20:16:36  <planetmaker> hm... cargo acceptance... that's anyway only a cargoID local to the industry, right?
20:16:46  <andythenorth> industry map colour should be handled separately - I think it might be useful to let players change that one day
20:16:53  <andythenorth> but that can wait for now
20:17:28  <planetmaker> andythenorth, map colour must not be changed by players IMO. What do you do in a multiplayer game? Impose a map colour setting from the server to the clients?
20:17:34  <andythenorth> good point
20:17:37  <planetmaker> That's detrimental to all GUI guides...
20:17:43  <andythenorth> I guess I have to find good map colours!
20:18:26  <planetmaker> That is IMO rather a point which needs addressing in OpenTTD's source code.
20:18:42  <andythenorth> tile cargo acceptance shouldn't need to be templated
20:18:44  <planetmaker> like a colour translation table added or so
20:18:53  <planetmaker> ok... back to topic, yes :-)
20:19:16  <planetmaker> if it's only action0s which change, the thing could be quite simple, I guess.
20:20:45  <andythenorth> I hope so
20:20:57  <andythenorth> I guess it will be a lot of action 7s / action 6s
20:22:10  <planetmaker> yes :-)
20:22:36  <planetmaker> I guess action7 / action0 is easier, though
20:23:07  <planetmaker> if economy != this economy skip next sprite
20:23:17  <planetmaker> action0 for this economy
20:23:28  <planetmaker> then next action7 / action0 pair for the next economy
20:23:45  <planetmaker> these action0s only need those properties which change
20:24:06  <planetmaker> thus this action7 / action0 sequence can be put into a template on its own
20:24:13  <planetmaker> and be called from the respective industries
20:24:22  <planetmaker> defining the values prior to inclusion of this template
20:25:25  <Ammler> action9* ;-)
20:25:49  <andythenorth> planetmaker: yes action 7 should work fine
20:26:13  <andythenorth> it will involve some redundant nfo, but hey, the template engine writes that, not me :)
20:26:39  <planetmaker> well... you could include the action0 in yet another template and avoid the redundancy.
20:27:19  <planetmaker> but as long as we don't have loops in the source, there's no nice way to template it.
20:28:16  <planetmaker> python2nfo is really needed :-P
20:28:22  <andythenorth> well yes
20:28:24  <planetmaker> or is it python4nfo ? ;-)
20:28:26  <andythenorth> but meanwhile...
20:28:49  <planetmaker> well, the duplication will be the action0s which are similar.
20:29:02  <andythenorth> I employ three developers who each claim they could write a python-nfo compiler in a weekend, but the problem is I don't pay them to work weekends :|
20:29:22  <andythenorth> I don't mind the duplication.  bandwidth is cheap
20:29:38  <planetmaker> I'd define in the industry things like THIS_MINING_INGAMEPROB
20:29:41  <planetmaker> etc
20:29:45  <andythenorth> yup
20:29:54  <planetmaker> and then in the template just re-use that for every economy.
20:30:02  <planetmaker> sounds like... two hours work ;-)
20:30:16  <planetmaker> excluding actually templating the industries themselves
20:30:27  *** PeterT has quit IRC
20:30:32  <andythenorth> well I am not working on the FIRS code right now...I do have some FIRS website stuff to do though :)
20:30:39  <planetmaker> :-)
20:30:42  <andythenorth> meaning if you wanted to template it...
20:30:48  <andythenorth> ...feel free
20:31:11  <planetmaker> he... :-) I better don't promise that atm. Pretty dense RL schedules.
20:32:02  <andythenorth> that's fine ;)
20:32:41  <planetmaker> but I realised that FooBar has returned at least to the forums :-)
20:37:33  <andythenorth> he might be free in a couple of months
20:38:05  <andythenorth> my plan is to get economies implemented and production callback code
20:38:25  <andythenorth> then we're having a baby, so who knows how much OpenTTD there'll be
20:51:28  <planetmaker> hu? "how much OpenTTD there'll be"? How do you mean?
20:54:13  * Ammler isn't sure, if andy means FIRS like a baby or if he become father
20:56:42  <andythenorth> Ammler: real baby...
20:59:29  <planetmaker> oh :-)
20:59:45  <planetmaker> yes, that might eat a lot of time - and will cause you sleep-less nights ;-)
21:00:14  <andythenorth> or it will give me lots of time to stare at code and listen to a screaming child
21:00:21  <andythenorth> oops, bad parenting skills :|
21:01:50  <planetmaker> :-P
21:03:20  <Rubidium> first language the baby speaks: NFO :)
21:05:43  <Ammler> first word is fish
21:06:03  <andythenorth> first word should be 'bulldozer' hopefully
21:06:09  <andythenorth> not very likely though
21:07:42  *** PeterT has joined #openttdcoop.devzone
22:15:23  *** ODM has quit IRC

Powered by YARRSTE version: svn-trunk