Good. You know what a "campaign" is? It's a prolonged military action against an enemy. Advertisers call it a campaign because you are the peasants being mass-surveilled by their soldiers for their profit.
On iPhone and Mac I currently use Better, and on Mac ublock for eliminating single annoying elements.
"Oh no how will papers make money if they can't surveil us?!" Patronage or subscriptions. Maybe schwag, like "Democracy Dies in Darkness" tshirts, sold exclusively on Amazon.
I've seen other people not get the joke/reference Apple's making with the iPhone 8 to X jump.
There might be a last-generation "iPhone 9" next year, or maybe not.
- Live video doesn't work in Safari beta. Had to watch on iPad.
- Steve Jobs tribute. Makes me a little uncomfortable. I don't think Steve would've liked being deified like this. Not sentimental, he wanted the work to speak for itself.
- Apple Park. Very pretty as a modern cathedral, but still that open plan is going to be Hell for developers.
- Apple "Town Squares". This is a very 20th Century kind of thing, a real-world gathering place, where you're supposed to learn from others. But now everyone just lives by their computer and talks online, watches online video. There's a lot of "we're restoring historic buildings" in this; the Medicis funding arts while politicking to get their Popes elected.
- The stream isn't doing the usual dual-camera picture-in-picture of presentation and zoomed-in view of presenter, so often I only see a tiny bit of a presentation screen, then it flips out for context. Very jarring.
- Apple Watch, exercise ad, lot of heart health study. Almost every watch app is getting redesigned again, because they can't figure out what it's for, beyond being a watch. "Now you can take a phone call, while you're surfing!" Streaming audio is their solution to killing the iPod… But how much is that going to impact your data cap?
- AppleTV. A presentation screen on streaming video can't show HD vs. 4k HDR video, so they desaturated the "HD" image to make the images look different.
- Aside: I've never much liked Spider-Man, but the new movie looks stupid, the costume looks like a plastic CGI figure (which it is, I guess), and the fight scene was so over-choreographed it looked like ballet, not a kid in a brawl with thugs.
- Aside 2: I love thatgamecompany's games, Flower and Journey are amazing. Sky looks just as good. But I'm dubious to the extreme about social gaming in it; that's the weakest part in Journey, which has almost no interaction.
- "For the first time, you were actually touching the button!" And then iOS 7 destroyed that UI by removing buttons and making everything a bland white void. Thanks IVE-1138.
- Ha ha everyone who had "iPhone X" on their bingo card, it's "iPhone 8". There's a regular fat model, and a super-fat + model.
- The camera is much better. I dislike the term "portrait mode", which doesn't mean portrait-vs-landscape, but bokeh.
- Using AR (Augmented Reality) Kit to put virtual objects on the real world is still silly, you're still staring at your phone. It replaces a convenient on-screen camera control with having to spin around like a doofus, you can't just sit in your chair and play comfortably.
- There are sane uses of AR to overlay physical things, like landmarks, or provide auto-translation. If Glassholes and naked Robert Scoble hadn't ruined Google Glass, it might be have a useful interface. But holding up your phone to do it is still silly.
- Wireless charging is a nice thing. In a car is a strange use for it, since it'd just bounce around without something holding it in place, like a cable.
- One More Thing: A separate model of iPhone X, with all the crazy rumor stuff. No home button, edge-to-edge screen.
- FaceID: From now on, you need to wear a mask at all times or anyone can use your "true face" to unlock your phone. The pigs can just hold your phone up in front of you to dig thru it. Good thing there's animoji, so you can send a completely virtual face (panda, poop, robot, or alien) to replace that pesky human interaction.
- Aside: I am wearing a Star Trek Mirror, Mirror tshirt. I'm the one with the goatee.
- iPhone X (pronounced "Ten"), and Qi chargers (pronounced "Chi") provide all new ways for Apple devotees to "well, actually" everyone else.
- Skate to where the oh not this quote again.
Probably makes sense for me to wait a couple months for the iPhone X and get the bleeding-edge device rather than a better what-I-already-have.
OK, get back to work.
Trying to load a PNG image and display it on the canvas has been… not fun. Delphi only knew about BMP stored in some horrible Microsoft resource format, and so everything FreePascal adds on top is a pile of hacks or undocumented features. The WWW was not especially helpful.
Mostly I'm posting this so someone else might find it in a search.
uses Classes, SysUtils, Controls, Graphics, LCLType, types, contnrs;
TSprite = class
filename: array of utf8string;
subrect: array of TRect;
constructor Create(c: integer; f: utf8string; r: TRect);
function getImage(filename: utf8string): TPortableNetworkGraphic;
img := imageCache.Items[filename] as TPortableNetworkGraphic;
if img = nil then begin
img := TPortableNetworkGraphic.Create();
imageCache.Items[filename] := img;
except on e: Exception do begin
LogError(Format('Image %s: %s', [filename, e.message]));
end; // try
Result := img;
procedure drawSprite(canvas: TCanvas; spr: TSprite; srect: TRect; tick: integer);
frame, nframes: integer;
if spr.color <> dawnUndefined then begin
canvas.Brush.color := spr.color;
nframes := length(spr.filename);
if nframes > 0 then begin
frame := tick mod nframes;
img := getImage(spr.filename[frame]);
canvas.CopyRect(srect, img.canvas, spr.subrect[frame]);
What I've learned so far:
- I spent a while trying graphics libraries (or failing to even compile them) before deciding I don't understand the UI model enough yet, so I'll prototype with some high-level drawing and circle back around to OpenGL or SDL.
- Build a do-nothing app in Lazarus, make a single form with a default FormCreate method, then quit out and write code starting from there in BBEdit.
- Part of that is that I'm not going to use a ton of GUI components, and code building is the evil opposite of Interface Builder. In IB, you edit UI and connect it to method names scanned out of the source code, it doesn't touch your code.
- The Lazarus editor is nightmarishly wrong and keeps inserting stuff in my code which makes me crazy. Maybe there's non-crazy-making settings, and probably it seems fine to masochistic Windows and Linux users, but I make enough problems in my life.
- Naming conflicts are a giant problem, so my current naming scheme is: For class "foo", it goes in file
unit FooUnit and
type TFoo = class…. I'm naming instance fields _bar and accessors bar() and setBar() as I do in most languages. I've mostly got the compiler to stop screaming at me every build. Not letting you name a unit, class, and field the same thing is infuriating.
- Build with
lazbuild -B --bm=Release whatever.lpi; I wrote a script to choose Debug or Release builds and launch the app if nothing went wrong, which is close enough to hitting Cmd-R.
- Bookmark the docs for:
- RunTime Library
- Free Component Library - in particular unit 'contnrs' wants to buy some vowels but has dictionaries, lists, etc.
- Lazarus Class Library
- There's very little explanation, so often I have to go digging in source like
/Developer/lazarus/lcl. I lost about 30 minutes today because they didn't document that TCanvas.FillRect uses Brush settings, TCanvas.Rectangle uses Pen settings, and I figured it out by reading the Carbon implementation. 😡 ☕️ 🔪
- Almost always if there's a non-domain-specific type I need it already exists. Batteries are included but mostly they're named badly, or upside down, or hidden in sofa cushions, or the dog buried them and I need a metal detector, or my psycho ex stole them and is holding them hostage for a pity fuck.
- The actual implementation code isn't much different from any other procedural language. For a guy who codes in Pascal for one year every 10 years, it's rolling along pretty fast. The near-equivalency of records and classes, and of functions, properties, and methods is convenient. Defining vars before using them, like in old-timey K&R C, is not convenient. Inline variable definition would be a gigantic quality of life improvement, which I doubt they'll do.
Every morning I get up, plug in my phone & iPad, make coffee in a French press, and say to my watch, "Hey Siri set a timer for 4 minutes". At least 2, sometimes 3 other devices (finally on Sierra just in time for High-as-in-grass Sierra to come out) beep and try to catch that. Usually they all fail except the watch. If they do succeed, I now get timers going off in multiple places, because despite Continuity nothin communicates this state.
And Apple wants an Apple TV and Apple Home to join that mob of Siris.