Live data from Hacker News

Adobe & HTML

html.adobe.com

21–30 of 71 posts

Re: Adobe & HTML

#21
post #7
post #5

Earlier quoted context omitted.

They're working fine for me in Chrome 18 and Webkit nightly, though not in Safari 5.1.5.

Yes, but are you using the experimental --enable-css-regions switch?

If it's experimental, I don't think either Adobe or Google can be blamed for the fact they don't work. Naturally the css doesn't degrade – the browser is advertising support for a feature that's currently broken in the browser and thus disabled by default.

Re: Adobe & HTML

#22
post #16

If you're not a designer, it might be hard to see, but the importance of this work is impossible to overstate. In 10 years, we'll look back on today and think about how barbaric and stupid it was that we didn't have re-flowable text in multi-box CSS layouts or absolute control of typefaces on the web. I have come upon the edge of what CSS is capable of multiple times, especially when building http://dustincurtis.com…

I am with Dustin on this one, but from a different angle. By creating flowable text, Adobe will ridiculously enhance the usefulness of their current publishing tools. A few years back I dabbled into newspaper publishing, and you can't imagine just how frustrating it is to have a beautiful layout in InDesign, which isn't really portable to the web. Having these tools will allow 'normal' people who don't do web to easily create stunning experience; that is a big undertaking!

Re: Adobe & HTML

#23
post #16

If you're not a designer, it might be hard to see, but the importance of this work is impossible to overstate. In 10 years, we'll look back on today and think about how barbaric and stupid it was that we didn't have re-flowable text in multi-box CSS layouts or absolute control of typefaces on the web. I have come upon the edge of what CSS is capable of multiple times, especially when building http://dustincurtis.com…

> the only sane way to build the layouts was to absolutely/manually position every paragraph

To me, this looks like the most INsane way to build a layout. What is wrong with a "let browsers and users choose their font size, their text widht, etc."?

For instance, both my wife and I are Kindle users, we have different font size, the text reflows almost always correctly, and who prefers bigger font has bigger font. My father is also a Kindle user and use an even bigger font because of his age. Soon he will have to read book on this device, because all fixed-font books will be too small for him.

Re: Adobe & HTML

#24
post #7

Earlier quoted context omitted.

Yes, but are you using the experimental --enable-css-regions switch?

If it's experimental, I don't think either Adobe or Google can be blamed for the fact they don't work. Naturally the css doesn't degrade – the browser is advertising support for a feature that's currently broken in the browser and thus disabled by default .

I was asking if the parent was using the experimental feature and wondering if it worked for him because of it. I am not using the experimental feature.

Of course samples are only samples, but they would be better if they showed a real life scenario where you have to make it work for the current generation of browsers and the upcoming generation. You don't have to degrade it with CSS, just make it work somehow.

Re: Adobe & HTML

#25
post #16

If you're not a designer, it might be hard to see, but the importance of this work is impossible to overstate. In 10 years, we'll look back on today and think about how barbaric and stupid it was that we didn't have re-flowable text in multi-box CSS layouts or absolute control of typefaces on the web. I have come upon the edge of what CSS is capable of multiple times, especially when building http://dustincurtis.com…

I am with Dustin on this one, but from a different angle. By creating flowable text, Adobe will ridiculously enhance the usefulness of their current publishing tools. A few years back I dabbled into newspaper publishing, and you can't imagine just how frustrating it is to have a beautiful layout in InDesign, which isn't really portable to the web. Having these tools will allow 'normal' people who don't do web to easi…

> to easily create stunning experience

I know that I've lost this battle and that I'm in a minority, but to me "stunning experience" comes from the content, and not the presentation.

Re: Adobe & HTML

#26
post #25

Earlier quoted context omitted.

I am with Dustin on this one, but from a different angle. By creating flowable text, Adobe will ridiculously enhance the usefulness of their current publishing tools. A few years back I dabbled into newspaper publishing, and you can't imagine just how frustrating it is to have a beautiful layout in InDesign, which isn't really portable to the web. Having these tools will allow 'normal' people who don't do web to easi…

> to easily create stunning experience I know that I've lost this battle and that I'm in a minority, but to me "stunning experience" comes from the content, and not the presentation.

Presentation without content isn't much, but content without presentation isn't either. When you are competing for users' attention, having an option to present the content in a memorable and outspoken way is quite important.

It's much like code, no one cares what your backend looks like, if users can't work with your apps.

Re: Adobe & HTML

#27
post #23
post #16

If you're not a designer, it might be hard to see, but the importance of this work is impossible to overstate. In 10 years, we'll look back on today and think about how barbaric and stupid it was that we didn't have re-flowable text in multi-box CSS layouts or absolute control of typefaces on the web. I have come upon the edge of what CSS is capable of multiple times, especially when building http://dustincurtis.com…

> the only sane way to build the layouts was to absolutely/manually position every paragraph To me, this looks like the most INsane way to build a layout. What is wrong with a "let browsers and users choose their font size, their text widht, etc."? For instance, both my wife and I are Kindle users, we have different font size, the text reflows almost always correctly, and who prefers bigger font has bigger font. My f…

There are two big "design movements" on the web, and dustin represents one end of the spectrum. His side argues that great design makes things better, and that we all should put more time into design.

The other side says "design is not needed", and that each user can manage their design settings themselves. These are the people that pushed for RSS and Responsive design, and that see design as more of an optional addon.

None of the sides are always correct.

Re: Adobe & HTML

#28

Earlier quoted context omitted.

But what's wrong with Dreamweaver? /s

Joking aside, Dreamweaver got me into HTML and CSS six years ago when I was 13 and now I have a pretty awesome job developing. Like pdenya states, it's definitely not for power users. But it has its place.

I do agree with you and was definitely was in the same boat. Dreamweaver actually functions pretty well for a starter/basic FTP and code editor, but beyond that it's very, very outdated and needs a massive overhaul.

Re: Adobe & HTML

#29
post #16

If you're not a designer, it might be hard to see, but the importance of this work is impossible to overstate. In 10 years, we'll look back on today and think about how barbaric and stupid it was that we didn't have re-flowable text in multi-box CSS layouts or absolute control of typefaces on the web. I have come upon the edge of what CSS is capable of multiple times, especially when building http://dustincurtis.com…

> after a while, I noticed that I had started to subconsciously alter my designs to fit within the limitations of the display technology.

Isn't that what always happens? That's one of the reasons designs from different eras look different: not just that fashions change, but that the output technology changes and allows a different set of design choices. No matter how much somebody in the 1940s might have wished to set some type a smidgeon wider or narrower, that just wasn't possible until the advent of phototypesetting in the 60s, and 1940s designers would have subconsciously altered their designs to fit within the limitations of their technology.

Re: Adobe & HTML

#30
post #16

If you're not a designer, it might be hard to see, but the importance of this work is impossible to overstate. In 10 years, we'll look back on today and think about how barbaric and stupid it was that we didn't have re-flowable text in multi-box CSS layouts or absolute control of typefaces on the web. I have come upon the edge of what CSS is capable of multiple times, especially when building http://dustincurtis.com…

> after a while, I noticed that I had started to subconsciously alter my designs to fit within the limitations of the display technology. Isn't that what always happens? That's one of the reasons designs from different eras look different: not just that fashions change, but that the output technology changes and allows a different set of design choices. No matter how much somebody in the 1940s might have wished to se…

At the fringes of every fashion era, there have been things that've peeked out into the future and tried to push things forward.

As a designer, if you aren't constantly trying to build stuff that's better than what other people think is currently possible, then you may have just become a cog in a machine.

Post reply on HN