Talk: What the next version of Figlet should be like

Ian Chai <spe...@uiuc.edu> wrote:
>
>bob...@wwa.com (Bob Allison) writes:
>>   The next version of Figlet should:
>
>Note: I don't usually read this group in detail so you probably wanna
>do this discussion on FIGLET-L. (I am not sure if Glenn reads this
>group in detail or not.)

   Considering the pontential of this discussion, I would assume that the 
Figlet folks would scan for this subject line.  Perhaps I'm wrong.  And 
just having this talk on the Figlet list leaves out those who are not 
current subscribers.  I will try to gate this thread between the ASCII 
art groups and the Figlet list.

>>   o  Use standard Figlet .flf fonts (to be backward compatible)
>
>>   o  Use standard Figlet .flf.Z and .flf.gz fonts in compressed format.
>
>Since Glenn isn't about to re-implement compress and gzip, probably
>what will happen is that the UNIX version will use the uncompress and
>gunzip available already using a call. I dunno what that'll do to non-
>UNIX versions, however...

   Calling an outside compression program can make sense if you want to 
actually compress a file.  But to just expand compressed files shouldn't 
be that involved.  The ability to expand both .Z and .gz should maybe add 
15 or 20 K to Figlet.

   This is just a flakey guess on my part.  HyperCard is about as far as 
I've gotten in programming.  But I think that expanding files is little 
more than grabbing a look-up takle and subbing strings for tokens.  No?

>>   o  Use a new system of fonts that are made up of three parts:
>>      -  Files containing letter shapes.
>>      -  Files containing fill patterns.
>>      -  Files containing backgrounds.
>
>>   o  Have many functions and variables controllable by the user, such as 
>>      replacing the characters in a fill or background file.
>
>>   o  Be able to change the variables from letter to letter.
>
>I'm not sure what you mean by this one.

   I mean that it would be nice to have control on a letter by letter basis.

>>   o  Be able to save, open, and manipulate work files.  These files 
>>      would contain text, info on which Figlet font or font creation 
>>      files were used for a particular job, user controlled variables, etc.
>
>>   o  Should be able to control everything by commands in a file that can 
>>      be fed to Figlet.
>
>>   o  Keeps its files in compressed format (to save disk space).
>
>>   o  Keep all uncompressed data in memory, no writing to disk.
>
>This would be tricky, and I'm not sure it's worth it -- after all, one
>uncompressed file at a time isn't too much space.

   True.  I guess I'm being anal, but it dislike small temp files.  I 
understand when a big graphics program has to keep a big vm file.  But a 
small app like Figlet should be able to keep it all in ram.

>>   o  Have a version for the Mac.
>
>Heheh... I use a Mac at home and so does Glenn, but our reaction is
>"why?" After all, Macs come with super fonts already... and if you're
>using it for email, you'll have access to a unix box. But then I
>thought of all those Eudora users... well, if someone wants to
>implement it for the Mac, I have no objections. If someone wants me to
>compile it for the Mac, I could do it, but it would look horrible as
>it'll have no GUI support.

   The reason that I ask for a Mac version is that a person doesn't 
always have access to their host computer.  So if they have a DOS machine 
at home, they can run Figlet at home and work on ASCII art without being 
online.  But if they have a Mac, they cannot.  I would go without a fancy 
Mac-like interface.  After all, I go without it now, using Figlet on my host.

>>   I could think of more, but then I'm not the person who has to write 
>>all this.  It would be a great to have, but I know how much work that 
>>is.  Hey, maybe the Figlet folks could get added help from volunteer 
>>programmers.  What do you say, Figlet folks and programmers?
>
>You'll have to ask Glenn that. I'm the only non-Glenn person who's ever
>written any Figlet code, and that was way back in version 0.9. The
>current version 2.1.1 doesn't have a scrap of my code left in it.

   So, how 'bout Glenn, old buddy, old Building & Loan pal.

>I suppose if some kind of decent version-control is worked out, it
>might work.

   Ian can volunteer to work out the version-control.  Right?

>God bless,
>	Ian

--
 ::::::  :::::  ::::::  :::::::  ::::::  ::::: :::::::   ::::::  :::  :::  :::
------- ------ -------- -------- ------ ------ -------- -------- ---  ---  ---
===     ===    ===  === ===  === ===    ===    ===  === ===  === ===  ===  ===
######  ###    ######## #######  #####  ###    #######  ###  ### ###  ###  ###
 ###### ###    ######## ######   #####  ###    ######   ###  ### ###  ###  ###
    === ===    ===  === === ===  ===    ===    === ===  ===  === ===  ===  ===
------- ------ ---  --- ---  --- ------ ------ ---  --- -------- -------------
::::::   ::::: :::  ::: :::  ::: ::::::  ::::: :::  :::  ::::::   :::::::::::

Related ASCII art in the Gallery

Explore these categories from our collection of 11,000+ artworks:

   _
 _(_)_
(_)@(_)
  (_)\
     |
    \|/
  \\\|//jgs
^^^^^^^^^^^

    \\__  o
|\/    o\  o
>       < o
|/\   __/
    //

 |\__/,|   (`\
 |_ _  |.--.) )
 ( T   )     /
(((^_(((/(((_/

  , _ ,
 ( o o )
/'` ' `'\
|'''''''|
|\\'''//|
   """

 ,~~--~~-.
+      | |\
|| |~ |`,/-\
*\_) \_) `-'

 __
 \  \     _ _
  \**\ ___\/ \
X*#####*+^^\_\
  o/\  \
     \__\

Make your own ASCII art

Turn images, text or 3D into ASCII, or draw your own – right in your browser.