Config
Log for #openttdcoop.devzone on 21st June 2012:
Times are UTC Toggle Colours
07:28:36  *** Zuu has joined #openttdcoop.devzone
08:06:17  *** Zuu has quit IRC
10:40:01  *** Os has joined #openttdcoop.devzone
11:26:28  *** LordAro has joined #openttdcoop.devzone
11:38:13  *** Os has quit IRC
12:01:46  *** Brot6 has joined #openttdcoop.devzone
12:01:56  <Ammler> @rss fetch devzone
12:02:03  <Ammler> @rss view devzone
12:02:07  <Ammler> @rss
12:02:07  <Webster> Ammler: (rss <url> [<number of headlines>]) -- Gets the title components of the given RSS feed. If <number of headlines> is given, return only that many headlines.
12:02:15  <Ammler> Brot6: view devzone
12:02:21  <Ammler> Brot6: show devzone
12:02:25  <Ammler> Brot6: help
12:02:25  <Brot6> Ammler: help topics: 10 core modules: auth, basics, config, filters, httputil, irclog, remote, unicode, userdata, wordlist; 84 plugins: alias, autoop, autorejoin, azgame, bans, bash, botsnack, cal, chanserv, chucknorris, debug, deepthoughts, delicious, dice, dict, digg, dns, eightball, excuse, factoids, figlet, forecast, fortune, freshmeat, geoip, googlefight, greed, greet, grouphug, hangman, hl2, host, imdb, insult, iplookup, karma,
12:02:25  <Brot6> keywords, lart, lastfm, linkbot, markov, math, modes, nickrecover, nickserv, note, poll, q, quiz, quote, reaction, realm, redmineurls, remind, remotectl, ri, roshambo, rot, roulette, rss, salut, script, search, sed, seen, shiritori, slashdot, spell, spotify, theyfightcrime, threat, topic, translator, tube, tumblr, twitter, uno, urban, url, usermodes, weather, wheeloffortune, wserver, youtube; 3 plugins ignored: use help ignored
12:02:27  <Brot6> plugins to see why (help <topic> for more info)
12:02:30  <Ammler> Brot6: rss
12:02:30  <Brot6> Ammler: incorrect usage, ask for help using 'Brot6: help rss'
12:02:35  <Ammler> Brot6: help rss
12:02:36  <Brot6> Ammler: manage RSS feeds: rss types|show|list|watched|add|change|del(ete)|rm|(force)replace|watch|unwatch|rmwatch|rewatch|who watches
12:02:47  <Ammler> Brot6: rss show
12:02:47  <Brot6> Ammler: incorrect usage, ask for help using 'Brot6: help rss'
12:02:53  <Ammler> Brot6: rss show devzone
12:02:53  <Brot6> Ammler: I don't know any feeds named devzone
12:03:00  <Ammler> Brot6: rss list
12:03:00  <Brot6> Ammler: 32bpp (devzone) (watched), a51 (devzone), administration (devzone) (watched), admintools (devzone) (watched), aidev (devzone) (watched), basesets (devzone) (watched), branches (devzone) (watched), devactivity (devzone), gamescripts (devzone) (watched), grftools (devzone) (watched), mqs (devzone) (watched), newgrfs (devzone) (watched), osqc (devzone), pixel (devzone)
12:03:12  <Ammler> Brot6: rss grftools
12:03:12  <Brot6> Ammler: incorrect usage, ask for help using 'Brot6: help rss'
12:03:18  <Ammler> Brot6: rss show grftools
12:03:18  <Brot6> Ammler: lemme fetch it...
12:03:18  <Brot6> Ammler: using old data
12:03:18  <Brot6> Ammler: Channel : GRF Tools: Activity
12:03:18  <Brot6> Makefile for NewGRFs: Common part - Bug #4030 (New): REPO_NAME not defined (foobar) @ http://dev.openttdcoop.org/issues/4030
12:03:18  <Brot6> NewGRF Meta Language - Feature Request #4029 (New): More information about white pixels (Xotic750) @ http://dev.openttdcoop.org/issues/4029
12:03:20  <Brot6> GRFCodec - Bug #4014 (Closed): Nforenum and var61 (frosch) @ http://dev.openttdcoop.org/issues/4014#change-10935
12:03:23  <Brot6> GRFCodec - Bug #4014 (Closed): Nforenum and var61 (Snail) @ http://dev.openttdcoop.org/issues/4014
12:03:26  <Brot6> NewGRF Meta Language - Feature Request #3898 (Closed): more useful error with plural problem in lang... (yexo) @ http://dev.openttdcoop.org/issues/3898#change-10934
12:03:27  <Ammler> and #3000
12:03:29  <Brot6> Ammler: #3000 is http://dev.openttdcoop.org/issues/show/3000 "Bug #3000: DevZone compile failed - Belarusian Town Names - #openttdcoop Development Zone"
12:03:38  <Ammler> ok, Brot6 seems back :-)
12:04:00  <Brot6> Hello from console
12:04:49  <Ammler> I always have troubles to remember the damn git commands
12:05:10  <Ammler> maybe I should setup a hg mirror for rbot
12:08:05  <Ammler> planetmaker: something else very important which needs attention?
12:08:17  <Ammler> (or whoever) :-)
12:08:50  <Ammler> @topic remove -1
12:08:54  <Ammler> @services op
12:08:54  *** ChanServ sets mode: +o Webster
12:08:55  <Ammler> @topic remove -1
12:08:55  *** Webster changes topic to "Talk about things hosted and developed on http://dev.openttdcoop.org | Downloads log: http://bundles.openttdcoop.org/log.csv | Sandbox passwords are the same as the usernames"
12:11:04  <Ammler> Brot6: rss show newgrfs
12:11:05  <Brot6> Ammler: lemme fetch it...
12:11:05  <Brot6> Ammler: using old data
12:11:05  <Brot6> Ammler: Channel : NewGRFs: Activity
12:11:05  <Brot6> Central European Train Set - Feature #4031 (New): Auto-refit (oberhuemer) @ http://dev.openttdcoop.org/issues/4031
12:11:05  <Brot6> Central European Train Set - Support #3791 (Closed): GPL exception for graphics from 3D models (oberhuemer) @ http://dev.openttdcoop.org/issues/3791#change-10987
12:11:07  <Brot6> Central European Train Set - Code Review #3333 (Closed): palette indices used for cargo recolouring (oberhuemer) @ http://dev.openttdcoop.org/issues/3333#change-10986
12:11:10  <Brot6> Central European Train Set - Feature #3045: Länderbahn rolling stock (oberhuemer) @ http://dev.openttdcoop.org/issues/3045#change-10985
12:11:13  <Brot6> Central European Train Set - Feature #3045: Länderbahn rolling stock (oberhuemer) @ http://dev.openttdcoop.org/issues/3045#change-10984
12:11:39  <Ammler> Brot6: rss show basesets
12:11:42  <Brot6> Ammler: lemme fetch it...
12:11:50  <Brot6> Ammler: using old data
12:11:50  <Brot6> Ammler: Channel : Base Data Sets: Activity
12:11:50  <Brot6> OpenGFX - Bug #3682: Suspended building missing contrast between wall and windows (mrmill) @ http://dev.openttdcoop.org/issues/3682#change-10929
12:11:50  <Brot6> OpenGFX - Feature #3563: Road depot variants for arctic and tropic (mrmill) @ http://dev.openttdcoop.org/issues/3563#change-10928
12:12:32  <Ammler> Brot6: rss show administration
12:12:32  <Brot6> Ammler: lemme fetch it...
12:12:32  <Brot6> Ammler: using old data
12:12:32  <Brot6> Ammler: Channel : DevZone Help Center: Activity
12:12:32  <Brot6> DevZone Help Center - Membership #4021 (New): Applying for project: CNR U-4-a Northern (knuckles88) @ http://dev.openttdcoop.org/issues/4021
12:12:32  <Brot6> DevZone Help Center - Revision 159:92e313170800: [compiler] update .default scripts (Ammler) @ http://dev.openttdcoop.org/projects/home/repository/revisions/92e313170800
12:12:34  <Brot6> DevZone Help Center - Membership #3997 (New): Applying for project: Hover Vehicles (Hazzard) @ http://dev.openttdcoop.org/issues/3997
12:12:42  <Brot6> DevZone Help Center - filetypes.NML.conf (Terkhen) @ http://dev.openttdcoop.org/attachments/download/3032/filetypes.NML.conf
12:15:24  <Ammler> planetmaker: I am not sure, what #4021 and #3997 want, shall we create a project for them?
12:15:24  <Brot6> Ammler: planetmaker: #4021 is http://dev.openttdcoop.org/issues/show/4021 "Membership #4021: Applying for project: CNR U-4-a Northern - DevZone Help Center - #openttdcoop Development Zone"
12:15:24  <Brot6> Ammler: planetmaker: #3997 is http://dev.openttdcoop.org/issues/show/3997 "Membership #3997: Applying for project: Hover Vehicles - DevZone Help Center - #openttdcoop Development Zone"
12:16:32  <Brot6> dutchtrains: update from r597 to r600 done - http://bundles.openttdcoop.org/dutchtrains/nightlies/r600
12:18:44  <planetmaker> Ammler: yes, seems we should
12:19:57  <planetmaker> I'll create them, Ammler
12:21:07  <Brot6> repository /home/hg/hover registered in Redmine with url /home/hg/hover
12:21:07  <Brot6> repository /home/hg/hover created
12:22:57  <Brot6> DevZone Help Center - Membership #4021: Applying for project: CNR U-4-a Northern (planetmaker) @ http://dev.openttdcoop.org/issues/4021#change-10988
12:24:36  <Brot6> Hover vehicles - Membership #3997: Applying for project: Hover Vehicles (planetmaker) @ http://dev.openttdcoop.org/issues/3997#change-10990
12:33:15  <Ammler> hover is too generic :-P
12:34:42  <Ammler> oh and planetmaker, you should asign the ticket, if you don't close it
12:35:02  <planetmaker> true
12:35:38  <Ammler> well, depends on the email settings, but asign would generate it more surely :-)
12:36:32  <planetmaker> redmine lacks one thing: generally I'd like only e-mail about things I'm involved in. But I want e-mails about everything in the helpcenter
12:37:06  <planetmaker> well, hover is generic, but maybe it can be made more clear. It's good enough for now, I think
12:37:31  <Ammler> hmm, there is redmine 2.0, I might upgrade it, but first I want to upgrade the hypervisor
12:37:51  <planetmaker> understandably
12:38:07  <planetmaker> but so, redmine 2.0 is better than chiliproject?
12:38:31  <Ammler> no, chiliproject is better but I am too lazy to migrate :-(
12:38:38  <planetmaker> meh
12:39:00  <planetmaker> what's the difference?
12:39:02  <Ammler> well better in the sense of "comunity friendlier"
12:39:20  <planetmaker> well... important is the difference for the users really
12:39:23  <Ammler> e.g. redmine has no IRC devs
12:39:30  <planetmaker> hm, right
12:39:38  <Ammler> no, for me, important is only the admin view
12:40:10  <planetmaker> yes.... but that should not be the primary decision maker
12:40:10  <Ammler> but as said, the migration workload is not worth it
12:41:26  <Ammler> another worth a look would be Rhodecode
12:42:11  <Ammler> that would be nice as I don't see fork possibilities in the next time from redmine/chiliproject
12:43:13  <Ammler> and afaik the dev of rhodecode also provides patches and plugins for redmine
12:44:26  <Ammler> redmine 2 uses rails 3, which might not every plugin support we use
12:46:02  <Ammler> oh; and we still need to solve the ogfx-trains issue :-P
12:50:29  <planetmaker> yes, we do. It's quite tricky
13:03:01  *** G19star has joined #openttdcoop.devzone
13:03:10  <G19star> Hi :)
13:03:42  <planetmaker> hello
13:05:50  <G19star> :) i'm new to this and i'm looking for any way to Contribute to the Project i'm finfing the 32BB project interesting trough:)
13:06:00  <G19star> finding*
13:08:31  <LordAro> howdy
13:09:15  <planetmaker> aye. Well, there's different ways how to contribue. You could create (blender) models, you could get involved into the NewGRF programming as 32bpp is just a sprite and works like NewGRFs did for years (now)
13:09:56  <planetmaker> the idea is to create a full set of graphics for OpenGFX by initially providing the OpenGFX+ NewGRFs with the required models and sprites rendered from that
13:10:41  <LordAro> that said, i should really get around to doing the road vehicles for terkhen :L
13:11:00  <planetmaker> :-)
13:12:47  <G19star> Did the OLD sprites already got converted to a grf?
13:15:52  <G19star> Well for now, i like to help with testing things, as i need to work on my experience first, i'm installing a linux machine now to work with:)
13:19:28  <G19star> Well i gtg for now see you guys later:)
13:19:28  *** G19star has quit IRC
13:55:06  <Terkhen> LordAro: no need to hurry :)
14:59:22  <Xotic750> planetmaker: A couple of question for you, why do we set a different track_type in redefine_engines.pnml compared to the track_type in the engine_*.pnml files? Why do some engine_*.pnml files contain the vehicle ID while others do not, as we are redefining the standard vehicles?
15:02:07  *** ODM has joined #openttdcoop.devzone
15:36:18  *** frosch123 has joined #openttdcoop.devzone
15:38:56  <planetmaker> Xotic750: in redefine_engines does what the name suggests. It associates with each default engine ID a name. Thus no-where except there we need to worry about the vehicle IDs
15:39:29  <planetmaker> Each engine, whether it has a separate file or not, should iirc have an entry in that file
15:39:37  <Xotic750> ok, so the engines_*.,pnml files should not have the ID included
15:39:52  <planetmaker> as that file redefines the things which are global. Like tracks. Like refittability, like climate availability
15:39:59  <planetmaker> indeed, they should not
15:40:08  <planetmaker> it's sufficient to associate ID and name once
15:40:10  <Xotic750> ok, then I will make sure to remove them
15:40:25  <planetmaker> (but it should be done exactly once)
15:40:44  <Xotic750> and what about the track_type
15:41:05  <Xotic750> the redefine seems to use various ones from the rail track table
15:41:30  <Xotic750> but the individual files all use normal_rail or maglev or monorail
15:41:44  <Xotic750> but the redefine uses other ones
15:45:50  <planetmaker> IMHO the track types should happen in redefine_engines. But you're right that it's inconsistent and possibly not even correct
15:46:34  <planetmaker> or maybe it could be in the individual files. But then could just use a simple template defined elsewhere (so that it makes sure that all rail engines always use the same definitions)
15:47:06  <planetmaker> hm... though... pondering... maybe there's reason to treat them slightly different. Like metro tracks or high speed tracks. Not sure though
15:47:52  <planetmaker> I guess we should allow the usual flexibility which is typical for this set. And only really distinguish erail and rail. And ofc. mono and maglev.
15:48:03  <planetmaker> with the proper fallbacks as defined in the CTT
15:48:05  <Xotic750> ok, so if we have have them defined in the redefine and remove then from the individual files, which are the correct rail_type definitions?
15:48:09  <planetmaker> s/CTT/RTT/
15:48:09  <Brot6> planetmaker meant: "with the proper fallbacks as defined in the RTT"
15:48:28  <planetmaker> :-O
15:49:10  <planetmaker> the correct ones are probably those which I added last. Similar to what found also in DutchTrains
15:49:17  <planetmaker> where I basically copied that from
15:49:37  <Xotic750> erm, lol, so that would be in the redefine I guess
15:51:42  <Xotic750> Oh, as I haven't been able to do any graphics recently, I kind of got stuck into changing the project to use the c preprocessor to generate the code rather than the macro style we were useing :) I guess you remember us talking about it
15:51:43  <Terkhen> that new Brot6 feature is nice :)
15:52:01  <Terkhen> s/nice/great/
15:52:01  <Brot6> Terkhen meant: "that new Brot6 feature is great :)"
15:52:23  <frosch123> :o
15:52:35  <frosch123> s/:o/:p/
15:52:35  <Brot6> frosch123 meant: ":p"
15:53:07  <Xotic750> I haven't finished converting and testing everything  yet though, but I am thinking of uploading it soon
15:54:13  <Xotic750> the generated nml file is much easier to read an debug doing it this way :)
15:57:07  <Terkhen> hi frosch123
15:57:19  <Terkhen> s/hi/hello/
15:57:20  <Brot6> Terkhen meant: "hello frosch123"
15:58:48  <Xotic750> and you were right it was a hell of a lot of work, but I think it's worth it
16:01:38  *** LordAro has quit IRC
16:05:26  <frosch123> s/frosch123/terkhen/
16:05:26  <Brot6> frosch123: You did something wrong... Try s/you/me/ or tell me "help sed"
16:05:54  <frosch123> s/s\/frosch123\/hello /
16:05:58  <frosch123> :)
16:06:02  <frosch123> hi terkhen
16:06:16  <frosch123> oh, i missed a / :(
16:08:14  <Terkhen> hi :P
16:32:21  <planetmaker> Xotic750: did you look at e.g. how FIRS does it?
16:33:10  <planetmaker> with the includes? That would be the way I'd prefer (as I understand it :-P )
16:33:10  <planetmaker> But probably you have it somewhat that way
16:33:10  <Xotic750> No, I went off and read the manual pages on gnu gcc about the preprocessor and it capabilities and then took it from there
16:33:35  <planetmaker> tbh, I'd like to see it before the whole code is changed. So maybe you can make a patch queue for it...?
16:33:36  <Xotic750> then basically broke iour code down into it's smallest component parts
16:34:39  <Xotic750> I don't know how to make a patch queue, but to be honest thee is so much change that it would probably be better to zip up the pnml files and give them to you
16:34:49  <Xotic750> alternatively I have it on the render server
16:35:08  <Xotic750> I don't know if you made yourself access on there yet?
16:35:41  <Xotic750> as I said, it's not fully ready yet, but it is getting close
16:36:22  <Xotic750> I've basically converted all engines and the basic wagons
16:36:44  <Xotic750> but still have to do the more complex ones, like tank and bulk and piece
16:38:32  <Xotic750> and then there is the documentation to be done :P
16:42:22  <planetmaker> well. But one big thing to change all is... hard to digest... :S
16:43:46  <planetmaker> a patch queue is doing the same thing as commiting. But commiting it to a patch
16:44:12  <planetmaker> and as you say "not yet done all", you obviously do that in steps. As such each step could constitute a single patch / commit
16:44:26  <Xotic750> basically it's kind of a rewrite, but I'll see if I can make the queue thingy
16:44:49  <planetmaker> and... you do that on the render repo?
16:45:17  <Xotic750> no, been doing it locally at my GF and then upload a copy there
16:45:51  <Xotic750> it would be a nightmare without a decent editor
16:46:25  <planetmaker> of course it would. I rather have a diff than a new bundle
16:46:36  <planetmaker> or a queue of diffs
16:46:42  <planetmaker> much easier to see what changes
16:47:31  <planetmaker> and... it often helps to discuss big changes before "they are done"
16:47:34  <planetmaker> I do expect me to have comments ;-)
16:48:26  <Xotic750> Yeah, it will have them, just going to take a little while
16:48:59  <Xotic750> and holidays start tomorrow, midsommar
16:49:03  <planetmaker> why do you need to convert all wagons to discuss the concept or idea?
16:49:18  <Xotic750> so the GF will expect a fair bit of attention ;)
16:49:32  <planetmaker> i.e. why not before you invested loads of time in a thing to be discussed?
16:50:24  <planetmaker> but yes, of course, RL is important. I just mean... discuss big things early :-)
16:50:35  <planetmaker> Not when you're 'done' only to be possibly frustrated when my view differs (not that I expect it necessarily, I simply don't know what you did)
16:50:36  <Xotic750> well, we did discuss the possibility, and then I had the time and the desire to learn
16:50:44  <planetmaker> ok :-)
16:51:11  <Xotic750> things are much more flexible now
16:51:23  <Xotic750> but of course there will be things you don't like
16:51:37  <Xotic750> and we can deal with them
16:53:03  <Xotic750> but I think you will like the overall aspect of what can be accomplished this way
16:53:42  <planetmaker> When we implemented it for FIRS we discussed the things on a per-template level before each was commited. And then applied to each industry individually in a separate commit each
16:54:32  *** LordAro has joined #openttdcoop.devzone
16:56:26  <Xotic750> it's possible that you may be able to make diffs on a per engine or wagon and apply them that way, but I don't think so, the change is kind of common to all and is best applied in one go, well so far
16:57:03  <Xotic750> as I said, there are still the more tricky wagons to go
16:57:03  <Xotic750> and they may not fit into the templates that I have so far
16:57:08  <Xotic750> yet to be seen
16:57:50  <planetmaker> don't fall for the trap to put all logic in templates. It's worse than having it in the vehicle files :-)
16:58:26  <Xotic750> well, they aren't exactly templates, but more of a set of rules
16:58:34  <planetmaker> well, yes. Rules can also be too universal :-)
16:58:53  <planetmaker> I don't say you did or do :-) I just know I fell for that kind of trap previously
17:01:16  <Xotic750> let me show you an example engine, the sh125
17:01:16  <Xotic750> http://paste.openttdcoop.org/show/1495/
17:01:36  <Xotic750> that will give you an example of how an engine can be defined
17:02:36  <Xotic750> then there are the templates/rules that are in the include files that add the appropriate nml code
17:02:36  <planetmaker> it can... but I really don't like it
17:03:25  <planetmaker> basically the existing code is replaced by many more defines and then hidden in templates
17:05:37  <Xotic750> yes, it uses the c preprocessor just like if coding c++
17:05:37  <planetmaker> I know... I once wrote NewGRFs that way, too
17:05:37  <Xotic750> and the nml snippets are reused, so there is less nml to be incorrect
17:05:41  <Xotic750> you get far more feedback from the preprocessor about anything you have done incorrect
17:05:41  <planetmaker> we can probably do with about 20% of the defines. Most are not necessary
17:05:41  <Xotic750> and get extra debug info in the form of line numbers and the files that they are in and where they were called from
17:06:38  <planetmaker> e.g. I'd not make a template "define_engine_livery_graphics.pnml"
17:06:38  <Xotic750> that's a rule set
17:06:38  <planetmaker> exactly
17:06:38  <planetmaker> a too generic one
17:06:38  <planetmaker> it needs too many defines
17:06:56  <planetmaker> #include engine_mu_mail_wagon
17:06:57  <Xotic750> it uses the same amount of defines as you had parameters
17:08:55  <Xotic750> an it is definately far more robust than the way it was working previously
17:10:20  <Xotic750> and by adding 1 define to a engine or wagon, I control adding 32bpp sprites, or 8bpp rendered sprites, or original pixel art
17:12:13  <Xotic750> and once it is all documented, creating a new vehicles becomes very easy
17:12:46  <Xotic750> there are less chances of typing mistakes in naming as it is all generated for you
17:13:13  <Xotic750> and if you type a define name incorrect then you get told about it during preprocessing
17:14:15  <Xotic750> 'but of course, I am sure there are areas that can and will be improved upon
17:19:54  <Xotic750> here is an example of the train lookup table
17:19:55  <Xotic750> http://paste.openttdcoop.org/show/1496/
17:20:36  <Xotic750> this makes sure that you don't get names etc different across different files
17:20:42  <Xotic750> like I found with the floss
17:21:04  <Xotic750> which in 1 file was called floss47 and in another it was shfloss
17:25:46  <planetmaker> Xotic750: you don't have to convince me of the advantage of templates. Yes
17:26:13  <planetmaker> But... there's IMHO still way too many unneeded defines like for the livery overrides. It could be just one for each
17:28:15  <planetmaker> and wrt http://paste.openttdcoop.org/show/1496/ I'm not really convinced it adds really much to the clarity. And why does it define the names?
17:28:37  <planetmaker> The default trains must not define a new name.
17:28:53  <Xotic750> sure, but that will require some more tables to reduce things further
17:29:06  <planetmaker> as it spoils all the translations which OpenTTD readily provides for them into all the tens of languages
17:29:23  <Xotic750> it doesn't define anything new, only what already existed in the project, just collected together in 1 place
17:30:00  <Xotic750> ah, you mean the description entry
17:30:07  <Xotic750> that was just there for my testing
17:30:27  <Xotic750> same as we have 2 entries for rail types
17:30:51  <Xotic750> because there were defined per engine file and again in the redefine engines file and both were different
17:31:00  <Xotic750> that was why I was asking questions
17:31:16  <planetmaker> yes, one is wrong. The "proper" ones are the NORMAL_RAIL30 and so on
17:31:23  <planetmaker> as it makes use of the RTT
17:31:25  <Xotic750> yep
17:31:38  <Xotic750> so that column will also disappear
17:31:58  <Xotic750> I've got to go right now, GF is here waiting
17:32:15  <planetmaker> but then... what is gained by that table, Xotic750? It just is pre-processed into what is now redefine_engines.pnml
17:32:29  <Xotic750> but hopefully I will catch up with you soon and we can discuss things some more
17:32:55  <Xotic750> take a look at the floss and see the mistakes between the files
17:33:08  <Xotic750> this is avoided by using such a table
17:33:51  <planetmaker> yes and no
17:34:06  <planetmaker> as you still can re-define the thing in the engine file just the same. Just as now
17:34:12  <Brot6> Dutch Rail Furniture - Revision 9:e1227cb7984d: Change: remove minimal game version check. OpenTTD r... (foobar) @ http://dev.openttdcoop.org/projects/dutchrailfurniture/repository/revisions/e1227cb7984d
17:34:12  <Brot6> Dutch Rail Furniture - Revision 10:641e325e7d47: Docs: wiki graphics for rail furniture (foobar) @ http://dev.openttdcoop.org/projects/dutchrailfurniture/repository/revisions/641e325e7d47
17:35:05  <planetmaker> you can't template everything.
17:35:37  <planetmaker> E.g. it does not make sense to put every speciality of the flatbed wagon into templates / includes. It's just that wagon and no need to crypt it using templates
17:35:58  <planetmaker> especially it's 2cc stuff with containers or so
17:37:42  <Xotic750> as I said, I have only done the basic stuff, the stuff that is all the same has become templated
17:38:04  <Xotic750> the more complex/diverse ones I still need to look at
17:38:25  <Xotic750> and yes, they may be done in the definition file itself
17:38:43  <Xotic750> I really have to go now
17:39:14  <planetmaker> see e.g. how I implemented callbacks in FIRS: http://dev.openttdcoop.org/projects/firs/repository/entry/sprites/nml/templates/check_secondary_closure.pnml as called by http://dev.openttdcoop.org/projects/firs/repository/entry/sprites/nml/industries/cement_plant.pnml#L388
17:39:21  <planetmaker> that's how I like it nowadays
17:39:57  <planetmaker> http://dev.openttdcoop.org/projects/firs/repository/entry/sprites/nml/industries/cement_plant.pnml#L359 is the start of the industry
17:40:28  <planetmaker> and a very useful line and way to expand things is http://dev.openttdcoop.org/projects/firs/repository/entry/sprites/nml/industries/cement_plant.pnml#L11
17:41:28  <planetmaker> anyway, also I have to go now :-) Talk to you later
17:51:34  *** Zuu has joined #openttdcoop.devzone
18:34:37  *** G19star has joined #openttdcoop.devzone
18:36:30  <G19star> good evening:)
18:36:57  <Yexo> good evening
18:53:00  <G19star> is there still some interest in completing the 32B graphics:P ?
19:00:09  * Terkhen is quite interested
19:00:39  <Terkhen> from what I have seen in the forums, there is a lot of interest, but graphics developers are still unsure about moving from the old format to the new one
19:00:50  <G19star> oh
19:00:56  <G19star> i did already move them to new one
19:01:02  <G19star> personal ofcourse
19:01:54  <G19star> .grf is a easy install method for users compared to last methods
19:03:10  <Terkhen> yes, I would love to adapt old graphics (at least the one that have a consistent artstyle) to use them in OpenGFX
19:03:17  <Terkhen> sadly, they seem to be a mess with regard to licensing
19:03:25  <Terkhen> and that's always a complicated issue
19:03:34  <G19star> i think thats the biggest isue indeed
19:04:35  <G19star> so with the licensing, who do you mean the OpenTTD devs our who ?, sorry pretty new to this world:)
19:04:41  <Terkhen> now we are trying to get 32bpp in OpenGFX+ NewGRFs as a way to show what can be done
19:05:12  <Terkhen> NewGRF licensing it's not an OpenTTD issue, or at least not directly
19:05:26  <Terkhen> it's an issue for any future NewGRF developers that use the sprites with unclear license
19:05:56  <Terkhen> as they can't release the resulting set with a clear license
19:07:01  <G19star> thats pretty :) sad lol
19:07:07  <Terkhen> indeed
19:07:35  <Terkhen> you might want to check OpenGFX+ Trains, Xotic750 is doing some great 32bpp sprites for it :)
19:07:48  <Terkhen> anyways, time for dinner
19:07:49  <Terkhen> bbl
19:08:06  <G19star> :) bb i will check them
19:10:34  <Brot6> Dutch Trains 2 - Feature #4025: ICMs (Voyager1) @ http://dev.openttdcoop.org/issues/4025#change-10994
19:36:48  *** Os has joined #openttdcoop.devzone
19:53:51  <Brot6> DevZone Help Center - Membership #4021: Applying for project: CNR U-4-a Northern (knuckles88) @ http://dev.openttdcoop.org/issues/4021#change-10995
19:57:28  *** Os has quit IRC
20:11:24  <Brot6> DevZone Help Center - Membership #4021: Applying for project: CNR U-4-a Northern (planetmaker) @ http://dev.openttdcoop.org/issues/4021#change-10996
20:38:27  *** G19star has quit IRC
21:22:51  *** ODM has quit IRC
21:35:10  *** frosch123 has quit IRC
22:07:57  *** LordAro has quit IRC
22:54:41  *** Os has joined #openttdcoop.devzone
23:34:34  *** Os has quit IRC

Powered by YARRSTE version: svn-trunk