*Ssssssh*. Let them live in the pipe dream that these extensions were rushed together after mighty Steve wrote his open letter. Adobe never heard of HTML5 before Steve told them a few weeks ago, didn't you know?![]()
Best post of the day!
*Ssssssh*. Let them live in the pipe dream that these extensions were rushed together after mighty Steve wrote his open letter. Adobe never heard of HTML5 before Steve told them a few weeks ago, didn't you know?![]()
*Ssssssh*. Let them live in the pipe dream that these extensions were rushed together after mighty Steve wrote his open letter. Adobe never heard of HTML5 before Steve told them a few weeks ago, didn't you know?![]()
Perhaps Adobe should focus more on creating great HTML5 tools for the future, and less on criticizing Apple for leaving the past behind.
In the enterprise world where you sometimes have custom written software you paid several million for and you have it installed across thousands of computers in many different countries, upgrading software is often a no-go. I've work on creating bigass video tutorials for DOS-based software for a major car manufacturer. Green DOS text on black, The Matrix style. They used this software globally. This was in 2003, the software was probably from the early 90's... And I'm sure they'll be using it in 2023 as well. The video tutorial wasn't cheap, but pretty much anything is cheaper than upgrading or replacing the software.I think there's some more merit to trying to maintain support for older HARDWARE. Physical peripherals like scanners, printers or contoller cards generally have no reason they CAN'T work with whatever the latest software is. New drivers simply have to be written to communicate with them. When that doesn't happen, it usually comes down to planned obsolescence or laziness on the part of the manufacturer and driver developers.
But on the software/OS side? If you want things to progress forward efficiently and quickly, you have to draw a line and cut off support of the former "standards".
Probably true, since it wasn't included in the just-released CS5. But Adobe wasn't going to sit on their asses anyway... they pretty much own the market for this type of software and they aren't going to let anyone sneak past them when it comes to supporting the latest standards.While it may well and true that Adobe was planning this long before the iPad, I can bet that weren't in any rush to implement HTML5 options into their suite until Apple put them on Front Street.![]()
Who needs DreamWeaver? I like to code in raw HTML & CSS! I'd do it in raw binary if I could.
Who needs DreamWeaver? I like to code in raw HTML & CSS! I'd do it in raw binary if I could.
While it may well and true that Adobe was planning this long before the iPad, I can bet that weren't in any rush to implement HTML5 options into their suite until Apple put them on Front Street.![]()
When you get caught up in trying to preserve the "status quo" while you're simultaneously trying to "think of the future" -- you wind up with mediocre results. This is probably the #1 reason Microsoft's Windows product is considered inferior to Apple's OS X. Apple is willing to cut loose old tech. They draw a line and say "Tough luck... but anything we make after THIS point no longer has "legacy" code in it to support the previous technology." Microsoft, by contrast, tries to be everything to everybody. They're worried about their customers who STILL want to run some 16-bit application written for Windows '95, so they load up Windows 7 with a bunch of code that allows you to configure it to run the old stuff.
At some point, you're left supporting what amounts to two complete operating systems, rolled into one, just to maintain it all ... and it's a huge mess!
I think there's some more merit to trying to maintain support for older HARDWARE. Physical peripherals like scanners, printers or contoller cards generally have no reason they CAN'T work with whatever the latest software is. New drivers simply have to be written to communicate with them. When that doesn't happen, it usually comes down to planned obsolescence or laziness on the part of the manufacturer and driver developers.
But on the software/OS side? If you want things to progress forward efficiently and quickly, you have to draw a line and cut off support of the former "standards".
Not that it's Adobe's fault (it's Macromedia's), but isn't Dreamweaver just about the corniest and most pretentious name a web coding+layout application could possibly have? "background: #ffffff; color: #000000; oooooh I'm totally weaving dreams now."is that a joke? do you even know what Dreamweaver is?
Not that it's Adobe's fault (it's Macromedia's), but isn't Dreamweaver just about the corniest and most pretentious name a web coding+layout application could possibly have? "background: #ffffff; color: #000000; oooooh I'm totally weaving dreams now."
I like it though. I remember when it was first released, and the only other viable alternative we had was MS FrontPage. Ugh.
While it may well and true that Adobe was planning this long before the iPad, I can bet that weren't in any rush to implement HTML5 options into their suite until Apple put them on Front Street.![]()
Probably true, since it wasn't included in the just-released CS5.
Its not surprising that HTML5 support wasnt included at launch, HTML5 is not even finalized yet, how do you build a tool for a work in progress? A work in progress that is not expected to be finished until 2012?
Thanks a lot, now I'll hear a theme song and think of mullets whenever I launch DW.when i see the splash page, i always get this song in my head. it never fails.
So I keep hearing, but where are these export options in CS5? Is it an ActionScript thing, or...? I see the same old swf / gif / png sequence / mov stuff in the export dialog...But it was, just not this part and not in Dreamweaver.
not like HTML5 is a standard yet. it's like wifi N.
I'm sure MR people and Apple fans in general don't mind, but I think this whole "well, iPhone sold well without Flash and iPad is just a big iPod Touch so it should be fine on that one as well" is oversimplifying the matter a bit.Well, Apple and other network companies certainly see it to be bigger than just Wifi N otherwise they (Apple) wouldn't be bold enough to drop Flash in favor of HTML5. The iPad has been a huge success even for many of the MR people that "know" Flash doesn't run on it.
So I keep hearing, but where are these export options in CS5? Is it an ActionScript thing, or...? I see the same old swf / gif / png sequence / mov stuff in the export dialog...
the question is why was this not in the shipping version?
Maybe because Adobe was ignoring the open standard to promote its own proprietary closed standard. Abusing its monopoly over image editing to force Flash on every one. Does anyone think they would have sold half as many copies of Flash if they hadn't shoved it in almost every CS bundle.