Tech tree viewer in the works...

Lemmy · #1 May 22nd, 2002, 12:47 PM

...by me

shamanblues asked if there is something like this made here, it looks like there wasn't , and there isn't someone already working on it.

The idea is too make a program which allows you to view the tech tree like in Civ.

Here's what i had in mind,

You got your basic window, inside there is one main view, in which the tree is shown, each tech is shown as a button, clicking on it will bring up a new window with information about the tech.
The new window will tell you all new components, facilities, and spy ops gained upon completion of this tech.

At the moment i'm not sure if one button should represent an entire tech area, or only one lvl in a tech area.

ideas/thought?
feature requests?
oh, about features, i will not make this an editor, just a viewer...at least for now.

And all of this will be written in Java.

Richard · #2 May 22nd, 2002, 04:22 PM

I like the ideas

.

DirectorTsaarx · #3 May 22nd, 2002, 04:28 PM

Quote:

Originally posted by LemmyM:
[QB<snip>
The idea is too make a program which allows you to view the tech tree like in Civ.

Here's what i had in mind,

You got your basic window, inside there is one main view, in which the tree is shown, each tech is shown as a button, clicking on it will bring up a new window with information about the tech.
The new window will tell you all new components, facilities, and spy ops gained upon completion of this tech.

At the moment i'm not sure if one button should represent an entire tech area, or only one lvl in a tech area.

<snip>
[/QB]

I vote for one button = 1 tech level.

This is going to be a vey complex tree, isn't it?

Lemmy · #4 May 22nd, 2002, 04:57 PM

Quote:

Originally posted by DirectorTsaarx:
I vote for one button = 1 tech level.

you're right, 1 button = 1 lvl is best.

Quote:

This is going to be a vey complex tree, isn't it?

a little...the algorithm to place all the buttons is probably the hardest part, but i already made it for a civ3 techviewer...and if i hadn't lost the source to that, it would be a lot easier

[ May 22, 2002, 16:12: Message edited by: LemmyM ]

Lemmy · #5 May 22nd, 2002, 05:39 PM

i was also thinking about a search function by name, there is a textfield, and you must choose to search for a component, spy op, facility, or tech area, and then the main view would center in the corresponding tech button

Gryphin · #6 May 22nd, 2002, 06:02 PM

I don't know if this helps.
I was able using Word to take the Tech Tree created by, um, was it you? and reduce it to a Tab Delimeted file.. From there I was able to port it to MicroSponge Access. A few preliminary efforts indicated I could do pretty defined searches on just a flat file.
I could send you the results or the seriess of macros I used to do the "parsing".
I realize not everyone has MicroSponge Access but ...
I'm not a programmer but if this helps, please let me know.
I will have guest for the next 6 days.. I may still be able to send it or upload it.

Lemmy · #7 May 22nd, 2002, 09:55 PM

It wasn't me who created that file.
I'm writing my own parser in Java and store the data in Java classes, figuring out how to connect with acces in Java (if possible) would take too much time.

Hank · #8 May 23rd, 2002, 09:24 PM

The JDBC/ODBC bridge connects Java to Access fairly quickly. But the better design is to do as you are planning, parse the SEIV files themselves for the data you need that way your techtree will be able to pickup patch changes and probably even mod changes easily.

Ransack · #9 May 24th, 2002, 12:18 AM

I was thinking of doing something like this too. One difference is that I am planning to use SVG as the output format. This would allow you to just point at a tech-level node and see in a floating window exactly what became available at that point.

Sound like a good idea?

Lemmy · #10 May 24th, 2002, 09:39 AM

Quote:

Originally posted by Hank:
The JDBC/ODBC bridge connects Java to Access fairly quickly. But the better design is to do as you are planning, parse the SEIV files themselves for the data you need that way your techtree will be able to pickup patch changes and probably even mod changes easily.

yep, that's right, i'm writing a seperate Loader class, so that any patch changes will be easily updated.

Quote:

Originally posted by Ransack:
I was thinking of doing something like this too. One difference is that I am planning to use SVG as the output format. This would allow you to just point at a tech-level node and see in a floating window exactly what became available at that point.

Sound like a good idea?

hmm, don't know much about SVG, other that it's based on xml?