• Track: Has not changed since “\pɔʁt.na.wak\” dev in PA.
• Track is part of “\pɔʁt.na.wak\” and is supposed to be a throw-away “quick” project. At that point it’s worth thinking whether there’s some real long term value in the project and in which case build a real standalone one.
• What I need is a more generic way to describe track segments.
• And import the ones from SCARM.
• Then use it on my own layout design.
• The 2D view lacks precise geometry tools that I’d take as a given:
• rulers x/y,
• units (inch vs mm),
• ability to move something at a specific place by x/y coords,
• rotate by entering an angle,
• ability to measure distance,
• ability to dup/offset a track to another one (or an anchor point).
• NCE Cab:
• Wrote a “design doc” / spec / desiderata doc for it.
• Need to do a prototype.
• First need to validate can use the RS485 interface on Windows/Java & Linux/Java (instead of Linux/Python). That first test could be a simple Java port of the existing python nce protocol decoder, without the ncurses part.
• 3D Blender:
• Desired goal would be to have a quick export from Tracks or for Scarm into a blender file, then play with materials there.
• “Cab Engineer” Android Mobile WiThrottle:
• I’ve started this for my own need as part of the old JMRI / JED experiment, then made a single use app with Wear integration also as an experiment.
• I had some desire last to reboot that into a formal project.
• See “Cab Engineer” below in 2017-12-18 update.
• Randall replacement for the NCE Button Board.
• Desktop app to access Wyze cams

It’s interesting to consider scopes:

• Cab Engineer: For me + public app.
• Value for me: mild.
• Existing apps: Engine Driver.
• 3D Blender: Only for me.
• Track: For me + public app.
• Value for me: medium/high.
• Existing apps: Plenty on desktop (can’t match), none on Mobile.
• Would be satisfied if I could just match desktop Scarm.
• NCE Cab: For me + public / for club.
• Value for me: medium / low. Technical challenge.
• Experimental: high value.
• Finished product: low value.
• Public / club: No adoption realistically expected at all.

So of these, based on value:

• Track / desktop is highest.
• Track / mobile is for fun and shows some interest.
• NCE Cab for the experimental phase value.
• 3D blender for some moderate value.

Based on this my order is going to be:

• NCE Cab - experimental phase aka validation prototype.
• Track / desktop.
• Revamp of experimental project, focusing on Scarm level.
• No mobile target at first but keep in mind for feasibility.
• Track / mobile. Maybe.