Working together for standards The Web Standards Project

The Web Standards Project Dreamweaver Task Force was created in 2001 to accomplish two tasks: to work with Macromedia (later Adobe) to improve the standards compliance and accessibility of Web pages produced with Dreamweaver and to communicate effectively within the online Dreamweaver community. Having successfully completed its initial goals, WaSP announces that the Dreamweaver Task Force will be renamed the Adobe Task Force to reflect a widened scope. The Adobe Task Force will collaborate with Adobe on all of the company’s products that output code or content to the Web, and will continue to advocate compliance with Web Standards and accessibility guidelines by those who use Adobe’s products to design and build Web sites and applications. Read the press release to learn more.

Your Replies

#1 On March 10th, 2008 1:08 pm Mark Wales replied:

It’s good that you’re spreading out to all of Adobe’s products, but Dreamweaver still needs a lot of work to make it encourage people to use web-standards. I gave up using it when I discovered standards as it just makes things more complicated.

#2 On March 11th, 2008 7:16 am David Sims replied:

I’m also glad to see that this work continues–many thanks to those who are actively involved from those of us who aren’t–however, I am very sorry to see (or not see!) HomeSite included in the list of Adobe products included in this initiative.

Dreamweaver, while very good in many ways, just doesn’t hold a candle to HomeSite in terms of code control, code cleanliness and speed of production. I have felt for quite some time that Adobe is overlooking a marvellous product that could easily rival newer comers like Eclipse, Aptana, etc.–if only Adobe cared. HomeSite doesn’t cost as much as DW, so I can see why it’s not included (from a pure profit motive point of view), but if updated with “all the latest” in frameworks, AJAX, AIR, etc. and still kept lean and mean, HomeSite could be a real addition to Adobe’s lineup…and a real addition to the world of web standards.

Best wishes for a productive endeavor…if you can include HomeSite, that would be even more exciting for those of us handcoders who still love our favorite tool.

David

#3 On March 11th, 2008 1:25 pm Ricardo replied:

Isn’t HomeSite just like Notepad++, Notepad2, SciTE, etc.?

#4 On March 11th, 2008 3:46 pm Brady J. Frey replied:

Great to hear the initiative still has movement; I agree that Dreamweaver’s code is atrocious (and I spend money training all my new hires away from it), but I’d say Photoshop’s template output might be equal in horror if not worse. You have the choice of a divitis cocktail or a table based mix… and they’re not that pretty to begin with. Regardless, I hope it works out, and always happy to help here in SF if they have questions.

#5 On March 14th, 2008 6:53 am Dominic Shiells replied:

Acrobat
The big program that Adobe need to sort out on the web is Adobe Reader or Adobe Acrobat.
The problem is that instead of putting text in HTML they put it in an PDF which is really annoying if you have to open up the program like 5 times.
Acrobat is Ok if you are accessing a document that needs to use a PDF file say a scanned in file but with CSS you can make a document look as good. It is the amount of files that do not need to use PDF files and do use them.

Flash
Flash is a program which is good but not good if you are accessing a website from a browser that does not have flash you have a problem.
The problem is if you have a small budget, the software to do any kind of Flash code considering the Program costs tremendous amounts of money.
There is also no way to turn flash programs of! If you do not want to watch flash programs they have no way to actually stop their own program.
Flash has much advantages such as you can use any shape textbox or create your own and being an artist it is a program very desirable!

#6 On March 16th, 2008 5:43 pm Spirit69 replied:

It’s good that you’re spreading out to all of Adobe’s products, but Dreamweaver still needs a lot of work to make it encourage people to use web-standards. I gave up using it when I discovered standards as it just makes things more complicated.

#7 On March 18th, 2008 12:23 pm MattG replied:

This should be a really good move for Adobe. As others have commented there are some issues that need to be addressed, but for the most part I am happy with all of Adobe’s current programs. I am not a professional designer/coder by any means but I use Dreamweaver to build up sites for my home business. While I do have to go through and clean up code here and there, I am happy with its features. Hopefully the new Adobe Task Force will be able to take care of some of these issues and create an all around better software.

#8 On March 30th, 2008 7:03 am jboy replied:

Nice to see it’s still rolling on, but let’s get a few things clear..

Homesite 5 (not the + version) needs to be brought back…i use it in Vista x64 it craps out a few times in a day. VS2005 or 2008 don’t cut the formatting for classic ASP.

Please please please make this an agenda….hope Jeff is still on the team…

Long live Homesite i guess i could use DW and only code view…but it’s a bit clunky.

Many thanks

jboy

#9 On April 7th, 2008 9:27 pm paul replied:

is there any non-obvious reason why my previous comment bemoaning the
lack of flashplayer for THE quintessential internet OS’s, namely the BSD
derivatives, was removed ?
(free/net/open/dragonfly)
what use are webstandards when you can sit there with standards compliant
browser, fast and capable hardware and software that makes it work, and
still be unable to view a large proportion of the available content that’s out there,
with many sites being completely unusable ?
am I assuming too much when I assume “open” and “accessible”
when the term “web standards” is mentioned ?
this is very much on-topic for this announcement.
any insight or comments gratefully received.

#10 On April 7th, 2008 11:22 pm Richard replied:

It’s good that you’re spreading out to all of Adobe’s products, but Dreamweaver still needs a lot of work to make it encourage people to use web-standards. I gave up using it when I discovered standards as it just makes things more complicated.

#11 On April 12th, 2008 5:19 am creativeuser replied:

I gave up using it when I discovered standards as it just makes things more complicated.

#12 On April 25th, 2008 6:18 pm Rum man replied:

Best wishes for a productive endeavor…if you can include HomeSite, that would be even more exciting for those of us handcoders who still love our favorite tool.

#13 On May 11th, 2008 6:08 pm Daniel Schutzsmith replied:

This is terrific news! I agree with may others sentiments on here but I think that maybe we haven’t all been using the same DW? I’ve been teaching DW CS3 for a year now and its nothing but great for creating valid markup with very little necessity to hand code (which I have done since 1998). So I am not sure where the disconnect is. Maybe its in user training? Maybe folks just don’t know the power thats already built into DW?

#14 On May 14th, 2008 8:25 am Sven replied:

Including HomeSite is a good idea. Where can we apply for that? Hand Coding is still the cherry on the top of a good code.

#15 On May 27th, 2008 9:41 pm Dns replied:

It’s good that you’re spreading out to all of Adobe’s products, but Dreamweaver still needs a lot of work to make it encourage people to use web-standards. I gave up using it when I discovered standards as it just makes things more complicated.

#16 On May 28th, 2008 7:02 am Patrick Heimann replied:

Ok, hi @ all. I think that Adobe Reader should get some more little functions. Maybe extracted from Adobe Acrobat. I have to work everyday with this “good job” application. There are so many people who need to work everyday with this freeware tool produced by adobe, but i think that there are some missing parts which should be included in the Reader. At the very least, Adobe should create a small business solution for smaller companys. For example an adobe Acrobat light edition which is affordable for most people. Thx for reading my reply

Post a Reply

Comments are closed.