Hi Alex, no, I want the normal effect of a vertical layout, since finaly is get in both ways. The problem for me is :
1) people that wants to change it must subclass layout to modify, instead of override css rule 2) there's an excess of html code since in each component inside the layout the current approach with inline styles are generating the style attribute for all components, so this ends in bloated code that I don't see in any example of UI sets out there 2018-03-12 18:41 GMT+01:00 Alex Harui <aha...@adobe.com.invalid>: > > > On 3/12/18, 10:11 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" > <carlos.rov...@gmail.com on behalf of carlosrov...@apache.org> wrote: > > >> > >> I still don't get why, if your Button is a subcomponent, some framework > >> code was setting display style on it unless you were using a layout > >>class > >> in the component itself. > >> > > > >that's the side effect of inline styling, as I put the button inside a > >vertical layout, the layout imposes display: block > >while my css dictates display: inline-block. The browser shows the later > >strikes out. For me that behavior can be right > >if I can change easily from CSS overriding rule, but not if is a line of > >code inside a framework that makes me override a whole class > >to change an inline style. > > Just to be sure I understand, your goal was to use vertical layout but > make one child not layout vertically? Sort of like "includeInLayout" in > Flex? > > Handling exceptions usually requires more code. So it sounds like you are > creating layouts that allow for exceptions, which seems like a reasonable > thing to do. The existing layouts will be more simple (and essentially > stupid) but will do the job with the least code when exceptions are not > needed. > > That's how I understand it. > -Alex > > -- Carlos Rovira http://about.me/carlosrovira
