My new toy Project :)

-
My new toy Project :)

https://github.com/tothpaul/Delphi/tree/master/AsciiShape
https://github.com/tothpaul/Delphi/tree/master/AsciiShape

Comments

  1. CaduTech (Carlos Eduardo Olivieri)February 12, 2017 at 8:35 AM

    Paul TOTH, Following you on Git.

    ReplyDelete
  2. Alexander BenikowskiFebruary 12, 2017 at 9:17 AM

    Remember doing the other implementation back then(the one you linked ;) ). Fun little thing.

    ReplyDelete
  3. Jeroen Wiert PluimersFebruary 12, 2017 at 9:45 AM

    Berline. I love that name and the carriage type.

    ReplyDelete
  4. Brett WiltonFebruary 12, 2017 at 11:26 AM

    Is there a site that has a list of ASCII Shapes definitions someone has generated ?

    ReplyDelete
  5. Alexander BenikowskiFebruary 13, 2017 at 1:42 AM

    Paul TOTH Maybe i am a bit nitpicking here, but my repo is not another but THE (reference) implementation for Delphi ;)

    ReplyDelete
  6. Paul TOTHFebruary 13, 2017 at 1:58 AM

    Alexander Benikowski :D well I think that my Parser is better...it merge the ellipsis points at parse time cause only 2 points are required ;) and you didn't implement antialiasing...but mine is VCL only and is not a TGraphic component, so both are welcome I think ;)

    The main reason I've made my own version is to remove the OnDraw event and define colors inside the text. the syntax is simple, and explained in the code
    https://github.com/tothpaul/Delphi/blob/master/AsciiShape/Main.pas#L103

    ReplyDelete
  7. Alexander BenikowskiFebruary 13, 2017 at 2:02 AM

    Paul TOTH i did implement antialiasing, and its VCL+FMX ;)
    memnarch.bplaced.net - AsciiImage for Delphi: GDI-Downsampling, FireMonkey and more! | Sparetime-Development

    The Problem with the in syntax definition(while handy) is, that we never endet up with a final solution. So this is left out in mine.

    ReplyDelete
  8. Paul TOTHFebruary 13, 2017 at 2:16 AM

    Alexander Benikowski ok, didn't see the update :)

    ReplyDelete
  9. Alexander BenikowskiFebruary 13, 2017 at 2:30 AM

    Paul TOTH while it helps to have multiple implementations, could you document your changes (like inline definition) which diverge from the original by CParnot? As you can see here: http://asciimage.org/
    The implementation is already available for a lot of other languages. Just in case someone is confused why it works in yours but(if using the inline style) not for others. For compatibility reasons ;)

    ReplyDelete
  10. Paul TOTHFebruary 13, 2017 at 2:54 AM

    Alexander Benikowski yep, on the JS implementation there's a Lower/Upper case distinction...it's not standard I think, but nice also :)
    xqt2.com - Ascii to Icon Based on a post "Replacing Photoshop With NSString ...

    ReplyDelete
  11. Alexander BenikowskiFebruary 13, 2017 at 3:18 AM

    The lower/upper case distinction is part of it, that's why the lowercase letters are listed after the Uppercase ones to denote a lower priority

    ReplyDelete
  12. Paul TOTHFebruary 13, 2017 at 3:47 AM

    Alexander Benikowski yes but the JS implementation do not fill the polygons in lowercase.

    ReplyDelete
  13. Alexander BenikowskiFebruary 13, 2017 at 3:55 AM

    That's just for the WebEditor to give the user predefined styles to tinker with.

    EDIT: Ok haver to correct myself. His implementation seems to enforce it. But on the other side it is just for sake of presentation  there and he documented his changes. And his changes do not conflict with the standard itself. He just doesn't allow to alter settings per shape, which might be for simplicity reasons for a Webform.

    ReplyDelete

Post a Comment