RE: [TCLUG:17130] Dreamweaver (was: <OT:anti-M$> *scary* stuff... )

["Schlough, Mark" <Mark.Schlough@mortgage.wellsFargo.COM>]

> -----Original Message-----
> From:	Nick.T.Reinking@supervalu.com [SMTP:Nick.T.Reinking@supervalu.com]
> Sent:	Wednesday, May 03, 2000 9:42 AM
> To:	tclug-list@mn-linux.org
> Subject:	RE: [TCLUG:17130] Dreamweaver (was: <OT:anti-M$> *scary*
> stuff...	)
> 
> Yeah - I tend to use Dreamweaver as more of a rapid
> prototyping tool than anything else.  I generate the (usually
> very clean) Dreamweaver HTML, and then go through
> it and dynamify it.  :P  Dreamweaver is a *great* prototyping
> 
	Yup, prototyping and authoring are different.  My boss *now*
understands this (^_^)

> tool, and can do extremely complex page layouts with
> tables and stuff.  It's "behaviors" features are usually quite
> helpful, also, as I'm not much of a JavaScript fiend. 
> 
	After taking a JavaScript class, I can appriciate the power of
JavaScript.  However, there are people (including the author of the textbook
we used) that say that JavaScript can solve all your problems, give you
shiny white teeth, make you a supermodel and get the chickweed out of your
lawn.  Fortunately, the instructor pointed this out in class. (^_^)  

	Her advice on web applications in general was this:

	Do it in HTML, if that doesn't cut it
	Do it with JavaScript, if that doesn't work
	Do it with an Applet, if that doesn't work
	You need to write an Application.

	It seemed like sound advice.

	Mark