"efl_ui_text" have two main parts.
And here is difference between the both parts.
- "elm.text" swallow - main text => Have hard coded default font, font size, color. It can't changed by theme. But, it can be managed by text interface without efl_part() function calls.
- "elm.guide" textblock - guide text. => All text properties are managed by Edje. It can be(or will be?) managed by text interface with efl_part() function calls.
- "elm.text" Text properties can't be managed by theme.
- Even if we create a way to change text properties on "elm.text", it is confusing to use. Because of different way to change text properties of the both parts. But, if solution can be simple and pretty for "elm.text", it does not matter.
(NEW) 3. In legacy theme, font / text color could be changed according to state changes. (By listening event signals: focused, unfocused, diabled ...)
All these stuff could be applied in EDC with some programs and descriptions of states.
For, efl_ui_text, do we need to change font properties from each smart event callbacks?