Hi, in my opinion anything useful to reduce duplicate styles customization inside bxml/wtkx files is good (and less error-prone). So I agree with your proposal on Container level, without introducing too much complex things, at least as a starting point.
More in detail, I've not a clear idea if it will be better to implement/use it as a container attribute, or if a sub-element, but to me is a detail, no preference at the moment. A question: using the URL-based styles setter (in the attribute style), will it be possible to set multiple styles in the same external json file ? If this is right for me can be enough (at least at the moment, and see later for a generalization). Or ... an old thing come to my mind: do you remember a ticket ( https://issues.apache.org/jira/browse/PIVOT-245 ) related to add some more parametrization of Terra theme in the json file (and pass it at application startup) ? Having default (overridden) styles there maybe could be another similar way to have overridden styles in application-specific json files, in a transparent way ... comments ? Bye, Sandro -- View this message in context: http://apache-pivot-developers.417237.n3.nabble.com/Named-styles-tp933133p933727.html Sent from the Apache Pivot - Developers mailing list archive at Nabble.com.
