4 ms·

Actually, something very like this has been done for a long time (the XPM): https://en.wikipedia.org/wiki/X_PixMap https://en.wikipedia.org/wiki/X_PixMap All t

Actually, something very like this has been done for a long time (the XPM): https://en.wikipedia.org/wiki/X_PixMap https://en.wikipedia.org/wiki/X_PixMap All the best,

daeken 12y ago
XPM is only for resolution-specific rasters. His technique allows for bezier paths, arbitrary fills, etc and is resolution-independent. It's pretty clever, IMO.
- halosghost 12y ago
  I didn't say what the author did was bad, uncool or not clever. But it certainly isn't a revolutionary thing that's never been done before. Additionally, XPM sucks (I'm aware), and I've been wishing for a significant update to it for a long while :P
skrebbel 12y ago
Did you read the article at all? It's hardly even comparable.
- halosghost 12y ago
  I'm confused; how is this not comparable? It's creating a pixmap directly from strings. I'm not saying this project is bad or uncool, I'm just saying this isn't a completely new idea.
  - matiaspiipari 12y ago
    The ASCIImage rendering code described in the post we're discussing is actually resolution independent vector graphics. You can draw neatly pixel aligned stuff with it, as is shown in the screenshots, but it's vector graphics.
    - halosghost 12y ago
      I'm not saying the author didn't make something far more advanced or cool; but the beginning of the article makes it seem like ey thinks ey is the first to ever come up with such an idea, which is false. I was never trying to say that the project is a knock-off.
      - grkvlt 12y ago
        Exactly. The core concept here is defining images for icons in the code itself, rather than loading them from external resources. XPM was one early way of doing that, allowing you to define bitmapped images in a static array of characters representing the pixel colours, and was a very neat hack. Now this extends and improves the idea, allowing you to define images for icons in your code, using an array of characters to represent the lines in an image, and define a vector graphic. It's definitely in the same conceptual space, although there doesn't seem to have been any direct inspiration from the earlier format. Both are very cool ideas...
      - charles_parnot 12y ago
        Fair enough. I certainly did not mean to pretend anything like this.
halosghost 12y ago
I'll never understand all the down-votes; this wasn't a criticism of the project, it was just mentioning that the beginning of the article suggests nothing like it had ever been done before.

Actually, something very like this has been done for a long time (the XPM): https://en.wikipedia.org/wiki/X_PixMap https://en.wikipedia.org/wiki/X_PixMap All the best,

daeken 12y ago

XPM is only for resolution-specific rasters. His technique allows for bezier paths, arbitrary fills, etc and is resolution-independent. It's pretty clever, IMO.

halosghost 12y ago
I didn't say what the author did was bad, uncool or not clever. But it certainly isn't a revolutionary thing that's never been done before. Additionally, XPM sucks (I'm aware), and I've been wishing for a significant update to it for a long while :P

skrebbel 12y ago

Did you read the article at all? It's hardly even comparable.

halosghost 12y ago
I'm confused; how is this not comparable? It's creating a pixmap directly from strings. I'm not saying this project is bad or uncool, I'm just saying this isn't a completely new idea.
- matiaspiipari 12y ago
  The ASCIImage rendering code described in the post we're discussing is actually resolution independent vector graphics. You can draw neatly pixel aligned stuff with it, as is shown in the screenshots, but it's vector graphics.
  - halosghost 12y ago
    I'm not saying the author didn't make something far more advanced or cool; but the beginning of the article makes it seem like ey thinks ey is the first to ever come up with such an idea, which is false. I was never trying to say that the project is a knock-off.
    - grkvlt 12y ago
      Exactly. The core concept here is defining images for icons in the code itself, rather than loading them from external resources. XPM was one early way of doing that, allowing you to define bitmapped images in a static array of characters representing the pixel colours, and was a very neat hack. Now this extends and improves the idea, allowing you to define images for icons in your code, using an array of characters to represent the lines in an image, and define a vector graphic. It's definitely in the same conceptual space, although there doesn't seem to have been any direct inspiration from the earlier format. Both are very cool ideas...
    - charles_parnot 12y ago
      Fair enough. I certainly did not mean to pretend anything like this.

halosghost 12y ago

I'll never understand all the down-votes; this wasn't a criticism of the project, it was just mentioning that the beginning of the article suggests nothing like it had ever been done before.