Hi,

Defaults

Regarding default font, size and color, I have been meaning to do something similar to the following:
https://git.enlightenment.org/core/efl.git/tree/data/elementary/themes/edc/elm/code.edc

It uses

data {
   item: "font.name" "Mono";
   item: "font.size" "10";
}

When the theme is applied, this data can be read and applied on the Ui.Text object. The same can be done for another "guide text" swallow part.

For overriding the text during runtime, the overrides need to be stored and reapplied in the cases that the theme is reapplied during runtime (e.g. if it changes) - so need a bit extra storage for the defaults.

efl_part

In order to support the guide text, Ui.Text needs to override efl_part calls to the "text" and "guide text" objects, and implement the required Efl.Text.* API redirecting calls.

We will require:

• EFL_PART_OVERRIDE definition for ui_text
• An efl_ui_text_part.eo class that will override the Efl.Text.* APIs The implementation will resolve the respective object (main text or guide text)

@id213sin, does this sound ok to you?

@herdsman

data {

item: "font.name" "Mono";
item: "font.size" "10";

}

When the theme is applied, this data can be read and applied on the Ui.Text object. The same can be done for another "guide text" swallow part.

Can we apply it without (NEW) #3 problem? In Tizen, we have different colors for focused, unfocused (default), disabled on both text parts.

In order to support the guide text, Ui.Text needs to override efl_part calls to the "text" and "guide text" objects, and implement the required Efl.Text.* API redirecting calls.

Actually, I hoped a common way to use/modify text/font properties across of whole widgets which have text parts. (ex: entry, check, radio, popup, list item and etc ...)
For example, calling efl_text_* interfaces on a widget, it changes main text part which is already implemented in EDC as a Textblock part.
And other text parts can be changed by calling efl_text_* with efl_part.
For now, it seems like that efl_ui_text have been managed in unique way. Or are you planning to change all text parts with same way of efl_ui_text?

Sorry for expanding topic to whole widgets. :(

In T6649#110040, @id213sin wrote:

@herdsman

data {

item: "font.name" "Mono";
item: "font.size" "10";

}

When the theme is applied, this data can be read and applied on the Ui.Text object. The same can be done for another "guide text" swallow part.

Can we apply it without (NEW) #3 problem? In Tizen, we have different colors for focused, unfocused (default), disabled on both text parts.

data {
   item: "font.name_focused" "Mono";
   item: "font.size_focused" "10";
   item: "font.color_focused" "#fff";

   item: "font.name_unfocused" "Mono";
   item: "font.size_unfocused" "10";
   item: "font.color_unfocused" "#252525ff";

   item: "font.name_unfocused" "Mono";
   item: "font.size_unfocused" "10";
   item: "font.color_disabled" "#181818ff";

   item: "font.name_guide_focused" "Mono";
   item: "font.size_guide_focused" "10";
   item: "font.color_guide_focused" "#fff";

...
}

The widget will update the color according to its state (keep track via callbacks).

In order to support the guide text, Ui.Text needs to override efl_part calls to the "text" and "guide text" objects, and implement the required Efl.Text.* API redirecting calls.

Actually, I hoped a common way to use/modify text/font properties across of whole widgets which have text parts. (ex: entry, check, radio, popup, list item and etc ...)
For example, calling efl_text_* interfaces on a widget, it changes main text part which is already implemented in EDC as a Textblock part.
And other text parts can be changed by calling efl_text_* with efl_part.
For now, it seems like that efl_ui_text have been managed in unique way. Or are you planning to change all text parts with same way of efl_ui_text?

Sorry for expanding topic to whole widgets. :(

In T6649#110040, @id213sin wrote:

Actually, I hoped a common way to use/modify text/font properties across of whole widgets which have text parts. (ex: entry, check, radio, popup, list item and etc ...)
For example, calling efl_text_* interfaces on a widget, it changes main text part which is already implemented in EDC as a Textblock part.
And other text parts can be changed by calling efl_text_* with efl_part.
For now, it seems like that efl_ui_text have been managed in unique way. Or are you planning to change all text parts with same way of efl_ui_text?

Ui Text is missing this feature but will support it. Whether there is an underlying TEXTBLOCK edje part or something else shouldn't affect the way the user manipulates the widget. The part logic will route the calls to the appropriate places.

Though, I feel I may have not understand your question..