C:  2 AWARDS, 1 CONTINUING after 2nd demo
D:  2 AWARDS, 1 CONTINUING after 2nd demo

	C comments:  all proposals need to be more specific about:
		. shell and environment variables, cwd and .hist history
		. special characters that might be jumbled by apache
		. killing runaway processes
		. support for fg and bg, if any
		. for those who would have us rotate thru a command
			history, you should know that development often
			rotates through two or three commands, so
			perhaps you could make them hot buttons, or at
			least make the text of the past command clickable.

	D comments:  all proposals need to be more specific about:
		. what to do about images requested through javascript & css
		. tell me whether you are planning to use lynx on the
			server side, and if so, how much you are adding
			beyond what lynx can do.
		. i need to know if you plan to host this or plan to use
			k9.

	GENERAL COMMENT:
		. proposals that are appropriately resource-sharing 
			& cost-sharing with another group will be preferred
			(for C and D awards), especially 70-30 splits of
			the project
		. timelines should be horizontal even if they take
			more work to create.
		. don't put my pre-proposal dates in your timelines!
		. try to be specific about what i will see in each demo --
			this is very hard, but very important.
			you don't even have to stick to it -- just give
			some idea of how we can milestone and checkpoint
			the construction of the software.

VERY COMPETITIVE (in no particular order)

C:Barber	COMMAND-PANEL IN JAVA			68800/1.6
	comments:  i like the part about check-boxing frequent commands
		and options.  i want to see a more detailed list.  will it
		be a special work item to build such a list?  would it be
		dynamic based on the situation -- customized?  or
		learned?  is the execute button too slow for people who
		prefer to keep hands on keyboard?  why not have the button
		OR ENTER?  You definitely need to submit a plan for
		collaboration, hiring, or subcontracting -- group is too
		small.

C:Halley        EDITOR/EXPLORER/SHELL IN CSS/JS/AJAX	60000/1.2
	comments:  i like the emacs idea of having an editor window
		open at the same time the browser is presenting a shell.
		your challenge is to remain competitive while involving
		another team!  10p specs could show more mock up
		screens and exactly what should be an active link
		in the browser.

C:Chen		HOTKEY/BATCH IN AJAX			54400/1.6
	comments:  more discussion of limitations than proposed function!  
		text in screen examples unhelpful.  i like the hot key
		idea best -- this proposal could be much better written
		making clear the vision.  10p spec should be very clear
		about the hot key ideas with screen shot examples.

D:Buchman	KID SAFE PHP/JS				84500/1.3
	comments:  great idea, should show example of image blurring --
		will it really work at all resolutions?  would like to
		see partnership with another group.  put your name on
		your proposal front page please!  10p spec should show
		language in which censorship rules are to be written.

D:Feldman	THIN CLIENT IN JAVA			87500/1.4
	comments:  mostly i like the text zoom idea.  should partner
		with someone who has a similar idea.  i would like to
		see some screen grab examples in 10p spec, in situations
		when it would be truly useful.

COMPETITIVE (in no particular order)

D:Chen		ASCII IMAGES IN PHP/JS			112000/1.6
	comments:  seems too easy with existing tools, although i would 
		like to see the ascii images actually work.  very good
		example of ascii image.  10p spec should include analysis
		of performance gain with various assumptions about
		image size, cpu time, and bandwidth.

SLIGHTLY COMPETITIVE (in no particular order)

C:Buchman	SKINS AND SESSIONS			58500/1.3
	comments:  good vision, definitely worth pursuing.  several
		screen grabs of different skins would really drive
		home the point.  don't give up on this idea, but do
		write it up better.  name on the front page is a good
		place to start.

D:Halley	TABBED BROWSER IN CSS/JS		108000/1.2
	comments:  good vision but not well explained -- fortunately
		someone else proposed mozilla-style tabs ...  a good
		reason to partner, perhaps...

NOT COMPETITIVE (in no particular order)

C:Feldman	AUTOCOMPLETING SHELL IN PYTHON		59500/1.4
	comments:  proposal is written backwards -- start with vision.
		there is not much functionality proposed here.

C:Greiner	FRIENDLY? SHELL IN AJAX/PHP		50000/?
	comments:  link is dead -- no other info in the proposal
		for those of us who can't get to link?  oh link is now
		alive!  this is a good first step, but oddly, not
		as good a demo or proposal of concept as just a
		bunch of static screen grabs that promise to deliver
		something better.  as you know, i know how to build
		this in one line of php too...  kudos for jumping
		ahead, but a demo of search would have made this
		proposal competitive.  also, the rm restriction is
		a bit questionable.

D:Barber	JAVA GUI SHELL				84000/1.6
	comments:  nothing wrong with the final screen grab, but the
		proposal is written backwards -- should put vision 
		first, then talk turkey.  GUI, while nice, doesn't
		seem to add anything except a reorganization of the
		browser screen.