To Do

Next Release: 0.7

• StaticObjectMarkers kill cli/main.rb in RstReal
• Derived data should not eliminate real/fluid data...
• @trn = :deleted for a deleted field
• Finalize THost v3.current prediction,
• Handle exploding minefields (theoretically possible :)
• THost alliances!
• finish merge host-sim and read-rst: reenable RGA and Pillage detection, riot detection, super spy, then clean io/mdata.rb for real; clean MData stuff at the end of shipmission.rb minefield.rb tvcr2.rb starbaseplus.rb
• Gui/wx (zoom exponential, not linear; object may disappear when switching view; Delete button for user_can_delete?() objects, edit ability, show text of markers)
• ...

Further To Do

Underlying data:

• Winplan auto??.dat is bogus, but nauto??.dat should work (patched version of winplan, according to stefan's filefmt)
• Fix none/more than one race-id or hull-id from THost messages; though the derivation is correct, the ensuing crashes are annoying, to say the least; Also when missing race.nm or running SimHost when missing *spec*, thanks Hans-Hermann for reporting,
• Wondering if some kind of wrapper for dangerous input (i.e. from User) could maintain speed, yet protect the user. Maybe that could be the "smart" layer also? -> derived
• Event system from deep core,
• Locking system (or very good event thread from wise that can do everything?)
• Setup partial hostruns (just for one location; also find out when it's applicable and when not),
• Let Verify take unpredictable info from actual hostrun to cancel out a series of markers (low priority),
• Introduce ShipModel a la JVC (saves fields in similar ships, i.e. memory, as well as makes multi-turn ship-building doable), should also cover current build_order (which is an inappropriate array)
• auto-read old universe and auto-predict to show useful info; do this all in the background so user can already look at current data,
• Complete THost host-run (Lady Royale, cargo transfer to other players, ship building; and then some),
• Match with PHost host-run (getting there...),
• Apply TRN also to current turn and then copy it to history subdir,
• Don't keep all universes in memory (halfway),
• Read additional PHost files (like hullfunc.txt),
• Many more message types,
• Hook messages to markers about them,
• Many more utilXX.dat records, what to hook to resulting markers? No double marker when both message and util record,
• derive additional info from VCR's (mainly about enemy planets),
• WinPlan leftovers (race.nm from RST in early phase),
• PHost v4,
• add predicted.txt (one step towards 'future commands', oh, Yeah :),
• Plug-in system; provide hooks before and after game/universe is read/created, but also for reading messages, UFO's(?) and a few utilXX.dat records (which carry add-on info; other info is accessible anyway, no need for a hook),
• "smart" step one: non-scanned minefields that should be removed, especially when scooping the minefield, this is verifiable; armament of enemy ships when sweeping your minefields; but also bases for unowned planets don't exist,
• Add "smart" step, linking related info to ships that are uniquely identifiable, but may not have been so (or may not even have been available) when the info was read; example: minehit gives you damage and ship ID, but you don't necessarily know where the ships is (it may even have colonized -- who knows :), Take active sensor sweeps and mark planets as "no activity"; in the same way, recognize that minefields may have decreased in size if they're no longer scanned at expected distance, also minefields layed with THost tell about the max number of torpedoes in the ship that laid them,

Prediction:

• Build ships,
• Beam up missions for cargo prediction (and movement/fuel),
• Take max cargo of ships into account for beam-up and transfer,
• Take alliances into account for 'lfm' prediction,
• minefield scooping prediction,
• Mass check (trimming) prediction (how?),
• colonise ships (pl.owner and pl.col_clans still need to be set, how does Colonise behave on an enemy planet?)
• RGA?

User Interface (wx, mostly):

• working keys on linux/gtk would be nice...
• zoom should use a factor, not a fixed addition
• Show ship hulls on he map
• use WinPlan's gamestat.dat
• Command-line tool,
• show 'status' of ships, minefields etc in the one_liner functions "S168 u LARGE" for unseen, "S168 D LARGE" for user-deleted etc,
• get the editable popups to a decent level,
• Ship traces (history, maybe even future, positions of selected ship),
• (slowly) grey out history stuff,
• Filter(s) for Marker types (will use on filtering in the core-engine),
• Better visibility of Markers,
• printing stuff like m+f+d vs activity should be done based on age (may be print both? activity is probably more recent, but m+f+d can be more accurate),
• Better distinction between ships and planets/bases? (not color, but probably shape can help here),
• Show stacks of torps, fighters (or defense strength (how?)?),
• Other ways to move (scroll) and zoom the map (rectangle, fixed zoom factors, remember user-set Views, quick-key to "switching" zoom factor),
• Keybindings for the buttons and toggle,
• Plug-in system, to show additional fields, or data from add-ons, (can provide hooks on update-screen; allow GUI elements to be added), SB+ is a nice example, has its own config and predictable data,
• Fleet management (and other automization jobs; goto, randmax, vpcheck; markers can help a lot here; this is client stuff, not viewer?),
• Make a version for colorblind ppl? need assistance for this, I think...

Big Improvements (minor release)

• (0.7?) Predicting all future data (or the doable part), merge simulation with real RST data (reading).
• (0.8?) Revamp the UI,
• (0.9) going beta (declaring stable, closing in on v1.0),

v0.8, 0.9, 1.0 Blocks

• Get PHost v3 on par with THost prediction,
• Getting the plug-in systems in place,
• Get partial hostrun to work,
• Perform certain tasks in the background,
• Key bindings,
• reading all(?) message and util-record types,

Huge Improvements (major release)

• (1.0) Reading and showing all VGAP data, allowing convenient editing of non-current data and processing that info smoothly for immediate display,
• (2.0) Make RVV a client (but it may be closer to 1.0 than an entire major release),

Specially Requested Features

• Edit of waypoints, so don't have to 'guess' in JVPC (Kero),
• get a list of objects from a rectangle on the map (RuN),
• clients would be so much better if they were capable of making reasonably-intelligent estimates based on info they know and info from the user... many different estimates to present to the user, that would be using the power of a computer properly in a vgap client (NicM)
  (that's w.r.t. ships armament, thus also minefield sweeping)
  (is this the "smart" item in the "underlying data" list?),
• Setting to show only data of at most X turns old (Kuperus),
• Allow for other layouts (in particular, no popup), this is partially a Wise request, too (Hopman),

Like this site? EC Karma++