I also considered just driving the whole way, but that would be a 31 hour drive and I'm not doing that.
Did some travel searches for an event I'd like to get to later this year. The event web page gives an airport and shuttle information, but it's one of those little airports nobody flies to going that route I'd have long layovers and it would be very expensive. Alternately, I can fly direct to a major airport much cheaper, rent a car, and have a 2 hour drive between that airport and the event location. I'd get there faster and about the only way that doesn't end up cheaper is if I rented a Tesla.
@gnomon For a toy, it's probably faster to just do it yourself, though if you're not careful you could end up making a tool.
Last week's focus on reports got a lot of progress and a nice list of remaining tasks that for the most part are easy things to pick up later. This week I'm going to focus on the configuration related stuff. That's what I'm going to try: focusing on a different functional area each week, see what I can get done on that which I can just start using, leave future me some guidance on what's left to do there.
So we know that the Enterprise-D cleans itself (good for the bloody ship, it'd have to given just how huge it is for the size of the crew else everybody would be too busy on janitorial duty to be at their stations), but the supposedly more technologically advanced Voyager has at least one crew member with a messy room. Did Voyager lose its self-cleaning function or can crew members just opt out for their quarters? Do Federation starships steal socks when people aren't looking?
On the plus side, this does let me get HTML export on reports basically for free, so I might add that in. Same approach will also work for CSV export, which I think would be useful.
The approach here is to add a toHtml() to my report elements and when you print the report the report can go down the list of its elements to generate a web page, send it off to a web view with a convenience print() method, and I just use that. My main objection is that bringing in Chromium just for printing seems wasteful, but it does save me writing a lot of code that I'd rather not write today.
Got printing support added to for reports in Typica 2. I hate the way I did it and will probably replace that eventually, but the way I did it gets me something that works for very little effort and honestly I'd rather work on stuff that makes printing less needed in the first place so further work on that is unlikely to be highly prioritized.
Reports in Typica 2 are now far enough along that I've started actually using those for production planning instead of going to another computer with Typica 1 for that. There's still a little more work to do with this, but for the most part all that's left there is bringing over the reports I want to keep. Some operations no longer require a database round trip and are thus much faster and this also represents a significant reduction in code size.
Pluto TV's Star Trek Voyager channel has changed to being a DS9 channel in case anybody wants to watch that as it was originally intended: with advertisements trying to convince you that if you look like a normal person instead of someone with a professional makeup artist and a photoshop expert you should ask your doctor about deadly toxins and here are the 8 ways that'll really mess you up (but ask your doctor anyway).
Author of Typica software for coffee roasters.