X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f996b,47779b5253487c72
X-Google-Attributes: gidf996b,public
X-Google-Thread: fbb9d,47779b5253487c72
X-Google-Attributes: gidfbb9d,public
X-Google-Thread: 110f55,47779b5253487c72
X-Google-Attributes: gid110f55,public
X-Google-ArrivalTime: 1994-10-19 01:19:39 PST
Path: bga.com!news.sprintlink.net!sashimi.wwa.com!not-for-mail
From: chai@ta12.cs.uiuc.edu (Ian Chai)
Newsgroups: rec.arts.ascii,alt.ascii-art,alt.binaries.pictures.ascii
Subject: Talk: What the next version of Figlet should be like
Date: 16 Oct 1994 20:41:22 -0500
Organization: University of Illinois at Urbana
Lines: 68
Sender: boba@wwa.com
Approved: boba@wwa.com
Message-ID: <37sko2$4lt@gagme.wwa.com>
References: <37db4u$p00@charnel.ecst.CSUChico.EDU> <37hk7j$di6@gagme.wwa.com>
 <37k7eh$a3b@sashimi.wwa.com> <37p3d8$8r9@sashimi.wwa.com>
 <37ppgt$hr1@gagme.wwa.com>
Reply-To: spectre@uiuc.edu
NNTP-Posting-Host: gagme.wwa.com
Xref: bga.com rec.arts.ascii:2187 alt.ascii-art:13144
 alt.binaries.pictures.ascii:1375


boba@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.)

>   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...

>   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.

>   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.

>   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.

>   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.

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

God bless,
	Ian