inexorabletash / travellermap Goto Github PK

The script is appended for analytics.

Could be fixed by not having an explicit body tag pair, but the CSS currently requires it to set the body classes.

Adding the following MapLabel to the labels in Render.cs will add a label to show the "Hiver Young Worlds" on the new maps

        new MapLabel("Vargr Enclaves", 95, -135),            
        new MapLabel("Hiver Young Worlds", 90, 135)

"Object reference not set to an instance of an object."

e.g.

https://travellermap.com/api/jumpworlds?sector=Solomani%20Rim&hex=1824&jump=0&milieu=IW

Two cases:

• custom markers w/ urls - if not loaded, schedule a load/invalidate. Otherwise draw, similar to the overlay path.
• standard "you are here" markers w/o URLs. The image is controlled by CSS so there are different styles to handle.

CSS for atlas specifies a monochrome overlay color, but the canvas code hardcodes the color.

Fix this somehow, ideally with declarative logic.

Seem to be seeing context lossage on OSX in Chrome 49.

Verify, and handle "webglcontextlost" and regenerate canvas (same as resize does)

Need to make the canvas aspect ratio depend on screen aspect ratio

There appears to be a race where the double-click triggers an "immediate" update, but a preceding update from the position/scale triggers a "delayed" update which then results in the credits hiding?

Instead of vast swaths of empty space, consider fallback data approaches:

• Allow defined fallbacks, e.g. for M1000 it's okay to just use 1105
• Otherwise, use placeholders (i.e. dotmaps) based on 1105

Add server logic to 301 Redirect all http requests to https

Now that ES6+URL+Fetch polyfill are assumed, use the newfangled capabilities.

"default" allegiance calculation and/or default colors for borders, routes, etc. has changed

Trying with cloudinternetexplorer.com

Dragging is fine.

via email: "The Points of Interest button on the Beta version opens a selection menu in the same manner as the share button, legend button, change map appearance button, and the help, feedback, and more button. A second click on the four mentioned buttons closes the menu, however to close the Points of Interest menu one must click on the Search button. Wouldn't a second click on the Points of Interest button to close the menu be in keeping with the function of the four other The Points of Interest button on the Beta version opens a selection menu in the same manner as the share button, legend button, change map appearance button, and the help, feedback, and more button. A second click on the four mentioned buttons closes the menu, however to close the Points of Interest menu one must click on the Search button. Wouldn't a second click on the Points of Interest button to close the menu be in keeping with the function of the four other buttons?"

The Universe API will give back sectors for multiple eras, but the makers don't know how to request a specific era's data

• .xlsx to .tab files
• add new T5SS 4-char allegiance codes to global table
• add 4-char to 2-char allegiance table
• render 4-char or 2-char allegiances depending on scale
• handle T5SS base codes - switch based on sector source
• rebase images
• T5SS output should use T5SS base codes (uncollapsed)
• Booklet should show T5SS base codes (uncollapsed)
• update doc/secondsurvey (base codes, allegiances)
• update metadata references (e.g. Border, Route allegiances)

Verify, for both legacy and T5SS sectors:

• sector data:
  • SEC
  • T5Tab
  • T5Col
• metadata:
  • MSEC
  • XML
  • JSON
• world data sheet
• sector booklet
• map rendering at 8/16/32/64/128 px/pc
• map legends

The T5 calculation of importance doesn't count Hiver and K'kree based - I assume others as well, this means the Federation world's LOOK less important than some nearby world's outside of Federation.

Examples:

https://travellermap.com/go/spin/1910?marker=res/markers/beowulf.png

https://travellermap.com/go/spin/1910?yah - (you are here)

The maximum tile dimensions are 2048, and the x/y coordinates for api/tile are multiples of the width. So when 2560 gets clamped to 2048 everything goes wacky.

Up the limits (and watch out for hitting memory limits, e.g. by clamping # of pixels not dimensions independently) and/or correct the x/y parameters when w/h get clamped.

e.g. using a bad color name in a - it tells you the line number of the error but nothing further.

Bounds are fine; it's rendering using the exact scale, which may not match the scale of the tiles in view.

Profiling indicates that Routes are responsible for significant memory use. There are about 10k routes in the database, and each is fairly heavyweight:

• Start and End hexes (ints - could be shorts instead)
• Start/End offsets (each is a Point of two ints, could be just 4 sbytes total)
• Style (nullable LineStyle enum, probably int)
• Width (nullable float)
• Color (nullable Color)
• Allegiance (string)
• Type (string)

One option would be a RouteGroup with the metadata and lighter weight route objects inside. This would also reduce the size of the XML.

Another would be to allow routes to contain multiple points.

https://github.com/empira/PDFsharp

PDFium renders them just fine, as does Apple's preview, but Acrobat reports an error on open.

The canvas isn't resized correctly

Also, Centrax has some sort of major glitch in its invisible borders.

At least, per tracing. There seem to be double rAF registrations.

To facilitate searches by readers of Agent of the Imperium

e.g. /api/universe?tag=Official

Maybe allow | operator to specify multiple matches?

Appears iOS doesn't support this, leading to blurry tiles appearing above crisp ones.

Events are processed as window-relative, not element relative (due to a past simplification)

E.g. it should notice if "Allegiance" isn't there by some known abbreviation

• base abbrev codes - e.g. base A NS indicates A decodes to Naval and Scout base
• base code sym color name - sym is a Zapf Dingbats character
• region - like border but only filled, not stroked
• label options high, low, left, right
• Render types for labels subsec, quadrant, sector, custom

E.g. something CSS-like, using "media-queries" to handle scale-sensitive values and allowing scale factors

There are several data errors in the Hiver trade routes, mainly J-5+ routes.