SirDamnALot wrote:I was playing around with the tech tree file and wrote a little knick knack to make an actual tree out of the lists.
Written in Delphi, because I don't know squat about Lua
http://www.fastshare.org/download/SiS_TechTree_Visu_01..7z

sven wrote:

SirDamnALot wrote:I was playing around with the tech tree file and wrote a little knick knack to make an actual tree out of the lists.
Written in Delphi, because I don't know squat about Lua
http://www.fastshare.org/download/SiS_TechTree_Visu_01..7z

Very cool! My version of 7zip is having trouble with that archive, so I can't actually test out the program. But, as I developer, having players who are excited enough about the game to build these kinds of mods and addons suggests that we are indeed on the right track

From the screenshot, it looks like your Delphi script may be having some trouble parsing the @TECHNOLOGY.lua file (there is no tech in the game called 'haduir' ). I could write a little hack to output the core tech tree directed acyclic graph (DAG) to some kind of easily digestible format. I actually already have one such hack written up -- as I was exporting to graphviz's DOT format of the core DAG for some of the easly alpha-version tech tree visualizations. We could use something other than DOT though. Is delphi happy parsing JSON?

tech "Ancient Control Systems" | race_specific {'haduir'}  {

SirDamnALot wrote:The parser is very very simple, I scan line-wise for key words like typelist or tech and go from there with the single quotes for the name.
So the haduir are a false positive.

There should be a JSON unit for Delphi, but I never used it so far.

SirDamnALot wrote:It is not very easy to read (many cross dependencies between science fields) but I had fun writing the thing

sven wrote:

SirDamnALot wrote:The parser is very very simple, I scan line-wise for key words like typelist or tech and go from there with the single quotes for the name.
So the haduir are a false positive.

There should be a JSON unit for Delphi, but I never used it so far.

Ok, I'll think a little more about this. The fastest and easiest output format for me would probably be very simple pretty-printed Lua tables -- something where rolling a quick parser in whatever language would be easy. At a minimum, any export format would need arrays and associative tables though -- so maybe JSON is the most universally compatible option. I've written Lua\JSON table conversions before. That wouldn't be a big deal. Um, check back tomorrow. I may write up something quick before I go to bed, provided I can get all my more urgent TODOs dealt with

sven wrote:

SirDamnALot wrote:It is not very easy to read (many cross dependencies between science fields) but I had fun writing the thing

Oh, and also, just because I didn't say so loudly before -- very nice work with the graph formatting. Fully automated graph visualization is hard to do well, and the outputs you're getting look way nicer than the graph-viz images I was generating back in the day. So kudos

SirDamnALot wrote:

sven wrote:Ok, I'll think a little more about this. The fastest and easiest output format for me would probably be very simple pretty-printed Lua tables -- something where rolling a quick parser in whatever language would be easy. At a minimum, any export format would need arrays and associative tables though -- so maybe JSON is the most universally compatible option. I've written Lua\JSON table conversions before. That wouldn't be a big deal. Um, check back tomorrow. I may write up something quick before I go to bed, provided I can get all my more urgent TODOs dealt with

Oh thats cool I hope I am not distracting you too much, I can update the parsing part from my side too.
(e.g. reading parts & hulls and other tech upgrades from the tech tree file)

sven wrote:Ok, here's a super-simple pretty-printed version of the internal TECHNOLOGY table. It takes out all the shorthand and functional programming tricks in ~TECHNOLOGY.lua, and just gives you the raw data. (This takes about 10 seconds for me to export.)

  {
      "Hadron Cohesion",
      "Plasma Focusing",
      "Zero-Point Energy",
      type = "all_of"
  }

  {
   "1": "Hadron Cohesion",
   "2": "Plasma Focusing",
   "3": "Zero-Point Energy",
   "type": "all_of"
  }

sven wrote:Ok, here's a super-simple pretty-printed version of the internal TECHNOLOGY table. It takes out all the shorthand and functional programming tricks in ~TECHNOLOGY.lua, and just gives you the raw data. (This takes about 10 seconds for me to export.)

Let me know how Delphi feels about parsing that. If I can get 20 minutes to mess around, I can output a JSON version of the same table. Also, if there are other internal tables you'd like access to, I could write a little hack that would tell sis.exe to dump arbitrary internal data table to JSON/Lua, if given certain command line-options, potentially opening up a whole world of unix-style utility hacks, for those of you inclined to write such things

Captainspire wrote:Would it be alright if I tried to make it all pretty and graphical?