4 ms·
> The engraving was created using imagemagick, which took the user’s text and returned an “engraved” image to be overlaid on the rear of the iPod. Couldn't thi
by Kwpolska 20d ago
> The engraving was created using imagemagick, which took the user’s text and returned an “engraved” image to be overlaid on the rear of the iPod.
Couldn't this be handled client-side, just overlaying plain text in gray 'Helvetica, Arial, sans-serif' on top of the image? At this scale, the specific font doesn't matter.
Although interestingly, Apple still renders the text server-side (and offers engraving only for iPads, apparently): https://www.apple.com/shop/preview/engrave/PH304LL/A?th=hello%20world&s=2&f=mixed https://www.apple.com/shop/preview/engrave/PH304LL/A?th=hell...
- bbx 20d agoI was wondering the same thing. Maybe it had to be done server side for accuracy. I can imagine customers returning their iPod because the shipped result didn't match what the webpage was showing. At that time, text rendering in the browser was still fairly pixelated.
- c0_0p_ 20d agoMaybe browser font tech wasn't quite there yet. It's not shown in the video but if you want the text to show mid animation then you need to do a skew effect on the text.
- dunstanorchard 19d agoI would I have tried that. Presumably it either didn't look as good, or there was something about the bad-word checker that required me to run it server-side. Maybe we didn't want a list of rude words sitting around in a .js file for anyone to look at. I don't recall, but whatever the reasons the imagemagick solution worked best for us.