CruxFramework / crux-widgets

6 stars 4 forks source link

[Widgets] Add attribute 'addStyleName' or refactor 'styleName' attribute #377

Open admtriggo opened 9 years ago

admtriggo commented 9 years ago

From claudio....@cruxframework.org on May 27, 2014 11:44:41

Today the default behavior of 'styleName' attribute on widgets is overwrite styles used by Crux, which contain the default styles for the component. This means that on more complex components almost (if not) all its visual functionality is lost.

This isn't a so good approach, the declarative form of styleNames should not overwrite Crux styles. If the user want to get rid of our default styles he should do it by removing Crux resources from the project, or, by removing from a component at its specific controller.

A good approach would be append the declared styleNames on the component. This way the user can give it custom styles directly in the views and the component still get the visual behavior from framework's default styles.

Original issue: http://code.google.com/p/crux-framework/issues/detail?id=377

admtriggo commented 9 years ago

From alexan...@triggolabs.com on July 03, 2014 04:37:13

Owner: juli...@cruxframework.org

admtriggo commented 9 years ago

From alexan...@triggolabs.com on July 03, 2014 04:39:04

Labels: Milestone-5.2

admtriggo commented 9 years ago

From juli...@cruxframework.org on July 30, 2014 10:38:12

Labels: -Milestone-5.2

admtriggo commented 9 years ago

From juli...@cruxframework.org on August 26, 2014 12:23:25

Labels: Milestone-M14-C4

admtriggo commented 9 years ago

From juli...@cruxframework.org on February 19, 2015 11:06:58

Labels: -Milestone-M14-C4