Leave a comment

Comments 7

katachi_kun January 30 2010, 21:47:24 UTC
A good carpenter never blames his tools. Dreamweaver 1-3 weren't bad if you were just doing basic html pages with minimal tables. I say a lot of the problems with shitty pages built with Dreamweaver were user error. If you change your mind 7 or 8 times on the placement of a cell or image by dropping and dragging, and don't properly undo the changes made or double check in the html viewer, yeah it's going to leave a lot of extra unnecessary code. If you don't understand cells or tables or frames, your'e gonna make a mess, but that's not Dreamweaver's fault. All the poorly coded and ghetto-rigged company databases don't mean that "C++ Is shitty for programming! Look at all the terribly coded software it's produced!" There was a "Clean Up Code" feature that supposedly went through your html and got rid of all the loose tags, but I was never messy enough with my code or hell bent on having frames in tables in frames with java and flash that it got too confusing to just start at line 1 and read through to check for errors manually ( ... )

Reply

katachi_kun January 30 2010, 21:49:45 UTC
also I can honestly say I've never used 90% of the features in Dreamweaver. Just simple "make some css and page templates with basic tables, make the pages, add text and pics" for me!

Reply

orochiyamazaki January 31 2010, 14:54:03 UTC
I'll generally lean towards any kind of ubiquitous freeware app, or a web app, to avoid such hangups since I work on no less than a dozen computers. Most of the bigger suites' added "value" are often what turn me off. With some of the big web editing apps, proprietary features seems to piss all over W3C/IETF standards, entice boneheads to pile on the crap, and it's murder on backwards/forwards/cross-compatibility ( ... )

Reply

katachi_kun January 31 2010, 18:01:59 UTC
I never had multiple computer issues like that, but I do know that in 1999, browsers displayed html differently, even if the page was written entirely in notepad. We used the first Dreamweaver and Illustrator 6 to do our web design, and learned to work with the differences in how browsers displayed the html. The more you learn to keep the stuff simple, the more likely you were to have it display the same in every browser. But I was majoring in design, not software engineering, so 90% of our time doing websites was drawing page layouts one page at a time in Illustrator and printing them out, with website design having more of an emphasis on "will this website be viewable to colorblind users? Does the color pallette work well with the navagation?" than "is this scrolling text java app awesome? How much Flash can I put in before it crashes? How much bandwidth is being used per page? (I had a roommate who was an SE in 2005 who got paid to streamline bandwidth usage in existing websites ( ... )

Reply


Wait, wut? anonymous April 27 2011, 12:04:29 UTC
I don't get it. You're smart enough to use Dublin Core, but still code in HTML 3.2?

& there's nothing wrong w/ using DW; syntax colouring alone makes it superiour to good ole notepad. Then again, why buy DW when you can get most of the same features in Komodo Edit?

Reply

Re: Wait, wut? orochiyamazaki April 29 2011, 00:25:42 UTC
In this case, as well as all the other pages of this particular client, the challenge was working around the issue of having to make it broadly compatible with some really REALLY old hardware.

I gotta agree with the nod to Komodo Edit, it's a great app that's totally customizable as the need arises. Aptana Studio is also really feature-rich, and I think a little more beginner-friendly. I don't really do any web design at the moment, but for the occasional update and edit, I'm glad that there are so many good open source / freeware / value-priced editors out there. Ditto with graphics and office suites... With some part-time projects, I just can't afford to keep getting licenses for stuff like Adobe CS, QuarkXPress or MS Office.

Reply


Leave a comment

Up