3 ms·
Interesting the article didn't mention the one thing I remember vividly about RIP graphics, which is the rendering process. I always assumed it was vector based
by dwater 6y ago
Interesting the article didn't mention the one thing I remember vividly about RIP graphics, which is the rendering process. I always assumed it was vector based because of the way the image would get rendered segment by segment as it was downloaded. It looked like you were watching a video of the artist painting the image. Shapes and lines would get created and filled in and overlayed. On a 2400 modem it was interesting to watch, which was important when you were waiting for data to trickle in. Here's an example:
https://youtu.be/XtWmPO-cLR8 https://youtu.be/XtWmPO-cLR8
- bluedino 6y agoBasically the same effect happened with a lot of DOS shareware drawing programs in the day. The file formats were often instructions like: Line (20,500) (45, 520) (15) Line (200,523) (65, 520) (15) Circle (300, 300) (100) (30) Fill (50,30) (16) and so on If you had a slower computer, or the software wasn't optimized that well, you'd be able to sit and watch your drawing re-draw every time you loaded the file or made certain edits.
- int_19h 6y agoNot just DOS, Windows as well. The WMF (Windows Metafile), EMF (Enhanced Metafile) and EMF+ formats are exactly that, except that primitives correspond to GDI or GDI+ calls. And they're still fully supported. Even MSPaint in Win10 can still open them, although it's not listed among supported extensions when you do File -> Open.
- acheron 6y agoThis was also how graphics worked in Prodigy, IIRC.
- deleted 6y ago[deleted]