Re: I'm Still Using Text Editor

I think it really depends on what kind of work you are doing.

I have 3 or 4 LARGE projects that i look after. All the content is taken
into template pages from Data stores using scripts.

For me it is best to use a GOOD text editor. I use editpad (it's free from
www.jgsoft.com) which has very sophisticated search and replace functions.

However if i was going to produce several different 'one-off' pages then i
would probably use a WYSIWYG editor.

OTH one of my colleages uses Homesite, and swears by it, but he tweaks all
his code in a text editor!

for what it is worth , if you go to 'drill-down' sessions at various
meetings, i think you will find most of the gurus use some kind of text
editor for their coding!

Frank
----- Original Message -----
From: H. G. Quinn <hgquinn(at)attglobal.net>
To: <wmacleod(at)innotrac.com>
Cc: <hwg-techniques(at)hwg.org>
Sent: Tuesday, May 02, 2000 2:05 PM
Subject: Re: I'm Still Using Text Editor


> The technique to use with DW is (and you have to know HTML to do it) work
in the
> design window, and keep your eye on the HTML palette which you _always_
keep
> open -- cleaning up and tweaking as you go, so things never get out of
hand.
>
> This way you get to focus on design, but you get clean code, too -- no
cascading
> messes that, once you clean them up, undo your layout.
>
> Productivity increase?  For me, and for eveyone woth whom I've discussed
this
> issue, work gets done in about 1/3 the time it would otherwise take,
assuming
> the pages are complex.
>
> DW is great with templates.
>
> "William E. MacLeod" wrote:
>
> > >-----Original Message-----
> > >From: H. G. Quinn [mailto:hgquinn(at)attglobal.net]
> > >Sent: Tuesday, May 02, 2000 1:16 PM
> >
> > >I agree that knowing how to code raw HTML is critical.
> > >However, once you know
> > >how to do that, the productivity increase you can get out of
> > >using Homesite,
> > >Arachnophilia, or (WYSIWYG) Dreamweaver will blow you away.
> >
> > The productivity increase may be beneficial, however, when one attempts
to
> > validate the code, insure that the site is accessible for visually
impared
> > users, one will tend to spend more time correcting the code that was
> > generated by Dreamweaver or another WYSIWYG program that your
productivity
> > will actually slow down.  I guess it all depends on what your standards
are.
> >
> > If the goal is not in complete validation and accessibility standards,
this
> > is fine, but when you are developing major corporate web sites,
> > accessibility and validation are mandatory issues....especially in
> > E-Commerce.
> >
> > The best thing to do, in my humble opinion, is explain to the client
that a
> > quality web site will take time.  At my shop we tell the client at least
90
> > days for a finished product ready for publication.  This gives us plenty
of
> > time for design and implementation from front end to back end.  The way
I
> > prefer to handle it is to create a set of templates that validate in the
> > first place, then use those for the development of the site.  It makes
life
> > much easier and keeps the ulcers at bay.
> >
> > William E. MacLeod
> > Innotrac Corporation
> > Web Services
>
> --
> Heather Quinn
> hgquinn(at)attglobal.net
> http://pws.prserv.net/windyhill
>
>

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA