flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jude <flexcapaci...@gmail.com>
Subject Re: [FLEXJS] TextLayout (was Re: Debugging (was [DISCUSS] Release Apache FlexJS 0.5.0))
Date Thu, 19 Nov 2015 02:46:12 GMT
BTW one benefit of SVG is that it has a shadow dom. That means it is
shielded from tampering unwanted CSS styling. This is one of the problems
web devs face using web components. So if you have a web component,
"MyButton" and it has it's using the regular DOM using div, img and spans
to make the button, all that markup is affected by CSS selectors and
inheriting styles. When a shadow dom is enabled it tells the browser to not
apply any CSS to it's content. The HTML5 video player uses shadow dom. If
you add it to a page none of your CSS changes the look or feel of the
buttons, slider, and so on. Browser manufacturers have agreed to expose
this feature to web developers which is great but it will be years before
it can be used solely. SVG has had shadow dom for almost ten years. Anyway,
food for thought.

On Sat, Nov 7, 2015 at 12:27 PM, Harbs <harbs.lists@gmail.com> wrote:

> BTW, another data point is that FOP implemented the KP algorithm. I don’t
> know how practical it would be to adapt that code, but it’s an Apache
> project, so licensing should be a non-issue.
> On Nov 7, 2015, at 10:00 PM, Harbs <harbs.lists@gmail.com> wrote:
> >
> > On Nov 6, 2015, at 8:55 PM, Alex Harui <aharui@adobe.com> wrote:
> >
> >> That was an awesome list!  Thanks.  Just curious, can text layout end up
> >> affecting more than two lines back?
> >
> > Yes. Assuming we’re dealing with paragraph composition, text anywhere in
> the paragraph can effect the entire line breaking sequence. The line breaks
> are determined by different penalties and glue. A single line can cause all
> the other lines to break differently.
> > There’s lots of good links on the algorithm on the wikipedia page I
> linked to earlier. Bram Stein did an implementation of the algorithm in
> Javascript as well.[1] What’s interesting on his page is that he has a
> comparison between default browser rendering and using the algorithm.
> >
> >> I still think it boils down to rectangles on a path but the path may
> not be a straight horizontal line or always going left-to-right, and you
> sometimes have to go back a bit.
> >
> > Yes. That’s true. It’s rectangles on a path, but I would not call it
> simple… ;-)
> >
> > [1]https://github.com/bramstein/typeset/

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message