Commit Graph

22 Commits

Author SHA1 Message Date
Michael Jennings 8e26d97824 Sun Jan 11 17:09:07 2004 Michael Jennings (mej)
It's too bad you can't just say, "Copyright 1997-2999."


SVN revision: 8349
2004-01-11 22:10:29 +00:00
Michael Jennings 15ad73f445 Wed Feb 19 16:17:00 2003 Michael Jennings (mej)
Updated copyright statements for 2003.


SVN revision: 6698
2003-02-19 21:18:10 +00:00
Michael Jennings 1aa62bc29c Wed May 22 16:52:37 2002 Michael Jennings (mej)
Cleanups of Escreen stuff.  Always use MALLOC/FREE, not malloc/free.


SVN revision: 6272
2002-05-22 20:55:06 +00:00
Michael Jennings 9ce5b286eb Wed May 22 11:37:19 2002 Michael Jennings (mej)
Latest Escreen work from Azundris <scream@azundris.com>.


SVN revision: 6270
2002-05-22 15:38:35 +00:00
Michael Jennings 0bdd7edc63 Mon May 13 18:46:06 2002 Michael Jennings (mej)
Latest Escreen patch from Azundris <hacks@azundris.com>.


SVN revision: 6251
2002-05-13 22:47:08 +00:00
Michael Jennings 1ece1388ff Sun Feb 3 15:51:38 2002 Michael Jennings (mej)
Apparently I forgot to commit these copyright date changes. :(


SVN revision: 5895
2002-02-03 20:53:07 +00:00
Michael Jennings 3a471bb33e Wed Jun 13 21:13:51 PDT 2001 Michael Jennings <mej@eterm.org>
There is now a new mechanism for dealing with the background image
	collection, including a new update script.  Please read the newly-
	rewritten bg/README.backgrounds for details.

	Also, I'm trying to flesh out the Contributors list in that file, but
	my memory isn't cooperating.  So if you contributed one of the
	backgrounds, or know someone who did, please let me know.


SVN revision: 4810
2001-06-14 05:31:09 +00:00
Michael Jennings a286152df9 Wed May 9 17:18:11 PDT 2001 Michael Jennings <mej@eterm.org>
Fixed several bugs in the saving of settings and the support of
	scripts in menus.  Also fixed the definition of term_name in the theme
	files as pointed out by Laurence J. Lane <ljlane@debian.org>.


SVN revision: 4750
2001-05-10 00:20:15 +00:00
Michael Jennings c567ebcf33 Fri Sep 1 21:03:53 PDT 2000 Michael Jennings <mej@eterm.org>
I'm working on some deallocators now.  The idea is that when Eterm
	exits and memory debugging is on, several routines get called to free
	the in-use memory (menus, font cache, etc.) that we still know about.
	Anything left after that would be either unavoidable leaks (like
	environment variables...read the putenv() man page sometime...sigh)
	or genuine memory leaks that need fixing.  I'm down to about 4.5K of
	leftover malloc'd memory now.  Making progress....


SVN revision: 3295
2000-09-02 04:12:16 +00:00
Michael Jennings e64307644d Fri May 26 20:43:03 PDT 2000 Michael Jennings <mej@eterm.org>
Okay, there are a few changes here.  First off, I made multi-byte font
	support the default now, as long as you have ISO 10646 fonts.  In
	order to do this, I made the default encoding type "Latin1" so as not
	to interfere with 8-bit ISO 8859-1 characters.  This means that if you
	relied on the default multi-byte encoding method to be SJIS, you'll
	need to update your theme files.

	I also set it up so that Eterm will ignore SIGHUP, at least until I do
	something with it (like reloading the theme or something).

	I fixed the proportional font size algorithm.  If there is more than
	a 3-pixel variance between the minimum and maximum sizes for glyphs in
	a proportional font, Eterm will set the size to 2 standard deviations
	above the average width.  This is so that they won't look so spread
	out and ugly, but it still doesn't look perfect.  Not much I can do on
	that front...terminals must have fixed-width columns.

	And then there's the biggie.  I put in the ability to configure the
	now-infamous font effects.  I left a black drop shadow in as the
	default, but you can now customize it via the --font-fx option or in
	the config file using "font effects <stuff>" in the attributes
	context.  You can even use "fx" instead of "effects" for short.

	So what goes in the <stuff> part?  Well, you have several options.
	To use a single-color outline, say "outline <color>".  Likewise, a
	single-color drop shadow is "shadow [corner] <color>"; "bottom_right"
	is the default corner if you don't specify one.  For a 3-D embossed
	look, "emboss <dark_color> <light_color>".  The opposite, a carved-
	out look, can be had with "carved <dark_color> <light_color>".  (Of
	course, with those last two, the 3-D look will only work if you
	choose the colors wisely.)

	Those are all the shortcuts.  The long way is to specify a series of
	corner/color pairs, like "tl blue" for top-left blue, or
	"bottom_right green".  You can abbreviate using "tl," "tr," "bl," or
	"br," or you can spell out "top_left," "top_right," "bottom_left," or
	"bottom_right."  If you omit a corner name, the first one defaults to
	top-left, the second to top-right, and so on as listed above.


SVN revision: 2714
2000-05-27 03:41:22 +00:00
Michael Jennings dfc718de71 Wed Apr 12 21:18:19 PDT 2000 Michael Jennings <mej@eterm.org>
This is the initial commit with Imlib2 support.  READ THIS CAREFULLY.
	There is important information in this commit message that will keep
	you from getting screwed.

	First off, support for Imlib 1.x is GONE.  It is no longer supported
	as of now.  If you want to continue using it, do NOT install this
	version.  I tried to support both for awhile, but the code ended up
	being way too ugly and hackish.  Imlib2 is the future.  And trust me,
	when you see what we do with this future, you'll be happy for the
	switch.

	The good news is that most of the basics work.  Transparency still
	works, and the basic image stuff works.  Most users won't notice any
	major problems, so long as your Imlib2 is 100% up-to-date.

	However, a few things still don't work:

	1.  Auto mode is a bit broken.  You'll get X errors in XFree86 4.0.
	Don't use it if you're running XFree 4.

	2.  Color modifiers for images don't work.  At all.

	3.  Transparency shading/tinting will not work in 8bpp or lower.  Life
	blows sometimes.  Sorry.  Time for a real video card. :-)

	4.  The built-in icon is broken.

	5.  You WILL need to update your theme.cfg files.  The borders on the
	horizontal and vertical bar images were incorrect when combined with
	the new anti-aliased scaling.  The horizontal bars should have a right
	border of 3.  Vertical bars should have a bottom border of 3.  The
	menu images should have both right *and* bottom borders of 3.  You can
	either make those changes by hand, or use the --with-theme-update
	option to autogen.sh.  Your call.

	I think that covers everything I've run into.  I will point out that
	I don't really take advantage of a lot of the Imlib2 features just
	yet.  My first priority is to make all the stuff that worked before
	work again (or at least the important stuff).  Then I'll work on
	new features.

	So there it is.  If you're not ready for it, don't use it.  But if you
	are, I hope you like it.


SVN revision: 2478
2000-04-13 04:19:05 +00:00
Michael Jennings 42fde9c99d Thu Feb 10 15:10:01 PST 2000 Michael Jennings <mej@eterm.org>
This is the first public availability of the work thus far on Eterm
	0.9.1.  There's quite a bit of new stuff here.

	* Added scrollbar thumb support.

	* Completely redid the terminfo/termcap stuff.  The terminfo file is
	now compiled (by tic) and installed by default (unless you specify
	--without-terminfo).  The config files still say xterm, though,
	because some programs (like SLang and GNU mc) use the silly algorithm
	of "Is $TERM set to xterm?" to detect mouse reporting support in a
	terminal. =P  But if you don't ever use xterm, you can use Eterm's
	termcap and just name it "xterm" instead.  Thanks to Marius Gedminas
	<mgedmin@takas.lt> for his patch that started this whole revamp.

	* Added the kEsetroot script for KDE users from Dax Games
	<dgames@isoc.net>.

	* You can now configure the Home and End emulation via --with-home=
	and --with-end= options to configure.  The --with-terminfo option is
	also new, and --enable-xim is now the default.

	* Added a new image state, disabled, for when Eterm loses focus.  This
	is supported by all widgets (well, all those that could possibly be
	on screen when Eterm lost focus), even the background image.  So you
	could actually have all your images darken on focus out and restore
	to normal on focus in.

	* Widget colors formerly dealt with as colors (menu text color,
	scrollbar color, etc.) are now handled by the imageclasses.  Each
	image state can have a foreground and background color defined.  The
	current exception is the background image; I hope to add that later.
	The foreground is the text color and the background is the object
	color (for solid color mode).  So menu text color is set by the menu
	imageclass.  And again, for unfocused colors, use the disabled state
	of the imageclass.

	* Proportionally-spaced fonts are now handled much better.  They are
	still forced into evenly-spaced columns (it's a terminal for crying
	out loud!) but at least you don't end up with Eterm's wider than your
	screen. :-)

	* Home on refresh is gone, as is home on echo.  It's now much simpler.
	There are two options:  home on output, and home on input, the former
	being a combination of echo and refresh.  Also, keypresses that don't
	necessarily have corresonding output can trigger a home on input,
	like Ctrl-End or whatever...ones that don't have special meaning.
	Credit to Darren Stuart Embry <dse@louisville.edu> for pointing out
	this issue and the one with "m-" in font names.

	* I finally got around to re-merging the new parser stuff from my
	work on the Not Game.  Closed up some old potential behavior quirks
	with theme parsing.

	* Added a new escape sequence to fork-and-exec a program.  Also added
	a scrollback search capability to highlight all occurances of a string
	in your scrollback buffer.  Use the new "Etsearch" utility to access
	it.  "Etsearch string" to search for a string, then "Etsearch" by
	itself to reset the highlighting.

	* And of course, the biggie.  Eterm now supports a completely-
	customizeable buttonbar.  Not a menubar, a buttonbar.  It can have an
	arbitrary number of buttons, and each button can perform an action,
	just like a menuitem.  So a button could bring up a menu (like a
	menubar) or launch a program (like a launchbar) or perform an
	operation (like a toolbar).  Each button can have an icon, text, or
	both.  And you can have buttons left- or right-justified in the
	buttonbar.  You will eventually be able to have an arbitrary number
	of buttonbars, but I'm still working on that.

	As with any change this big, things could very easily be broken.  So
	beware. :-)  I have tested this myself, and everything seems to work,
	but I can't test every possibility.  Let me know if you find anything
	that's broken, and enjoy!


SVN revision: 2048
2000-02-11 00:25:07 +00:00
Michael Jennings 67e4e8d959 Tue Jan 11 23:47:36 PST 2000 Michael Jennings <mej@eterm.org>
More fixes with menus and transparency.  After you build this version,
	check out the brand new "glass" theme at http://www.eterm.org/.  It
	looks sweet. :-)


SVN revision: 1905
2000-01-12 07:49:02 +00:00
Michael Jennings 0c66bab547 Wed Jan 5 21:23:56 PST 2000 Michael Jennings <mej@eterm.org>
Copyright date updates.


SVN revision: 1860
2000-01-05 17:34:32 +00:00
Michael Jennings b1d55e271d Wed Dec 29 12:32:19 PST 1999 Michael Jennings <mej@eterm.org>
I think I've finally got the menu behavior working right.  Menus now
	move themselves if needed, and exposes are now handled properly.


SVN revision: 1782
1999-12-29 10:36:38 +00:00
Michael Jennings c58c7d411b Thu Nov 18 21:47:02 PST 1999 Michael Jennings <mej@eterm.org>
I've rewritten almost the entire scrollbar.  It mostly works, but it
	still has issues.  I've put an #error directive in so that it won't
	compile; take it out if you *really* wanna try it.  It's much more
	efficient than before.


SVN revision: 1333
1999-11-19 04:05:24 +00:00
Michael Jennings 11b7b87dad Fri Oct 8 15:31:49 PDT 1999 Michael Jennings <mej@eterm.org>
This should fix all the weird menu behavior from time to time (well,
	I hope it does anyway).


SVN revision: 719
1999-10-08 18:49:57 +00:00
Michael Jennings dd84c6abab Thu Oct 7 18:48:31 PDT 1999 Michael Jennings <mej@eterm.org>
Shaved off around 100 KB of memory usage per Eterm by moving more
	code into the shared library, removing lots of unneeded variables, and
	fixing some small leaks here and there.


SVN revision: 710
1999-10-07 22:18:14 +00:00
Michael Jennings e700e69dff Mon Sep 20 18:32:01 PDT 1999 Michael Jennings <mej@eterm.org>
Lots of changes here.  First off, this should fix the background draw
	bug with transparency that several people pointed out.  While I was
	at it, I also cleaned up a lot of other related stuff.  Three-state
	images should be a lot more robust now.

	Then again, some stuff may be broken entirely from this, so let me
	know. :-)

	For one thing, the various image modes should work as expected now.
	You can allow and disallow modes for the various widgets.  The
	fallback mode is "solid" now, rather than "image," so you can cause
	a certain widget to refuse to use an image if you want to.  If you
	specify an image without specifying a "mode" line that allows the
	"image" mode, your image will not appear. <-- READ THIS TWICE!  I
	had to go back and fix all the theme files because of this, so you
	will need to remove your current theme directory and allow Eterm's
	"make install" to put the new ones in place; otherwise, everything
	will go back to being solid colors. =]

	Anytime something changes this drastically, there are bound to be
	problems.  Let me know if you find any of them. :)


SVN revision: 348
1999-09-21 01:16:46 +00:00
Michael Jennings e4070d2075 Reverting last change for now. Something's very wrong here.
SVN revision: 347
1999-09-20 23:57:57 +00:00
Michael Jennings 933cb583be Mon Sep 20 16:08:41 PDT 1999 Michael Jennings <mej@eterm.org>
Lots of changes here.  First off, this should fix the background draw
	bug with transparency that several people pointed out.  While I was
	at it, I also cleaned up a lot of other related stuff.  Three-state
	images should be a lot more robust now.

	Then again, some stuff may be broken entirely from this, so let me
	know. :-)

	For one thing, the various image modes should work as expected now.
	You can allow and disallow modes for the various widgets.  The
	fallback mode is "solid" now, rather than "image," so you can cause
	a certain widget to refuse to use an image if you want to.  If you
	specify an image without specifying a "mode" line that allows the
	"image" mode, your image will not appear. <-- READ THIS TWICE!  I
	had to go back and fix all the theme files because of this, so you
	will need to remove your current theme directory and allow Eterm's
	"make install" to put the new ones in place; otherwise, everything
	will go back to being solid colors. =]

	Anytime something changes this drastically, there are bound to be
	problems.  Let me know if you find any of them. :)


SVN revision: 345
1999-09-20 23:08:00 +00:00
Michael Jennings 661b1b9448 Tue Aug 17 18:06:01 PDT 1999 Michael Jennings <mej@eterm.org>
Now that we have a fixed CVS server....  This includes the old 0.8.10
	code, but it's now 0.9.  It also includes a timer subsystem.


SVN revision: 52
1999-08-18 01:12:47 +00:00