| |interface Efl.Text_Format @beta | |├ (P) ellipsis | |├ (P) wrap | |├ (P) multiline | |├ (P) text_horizontal_align_auto_type | |├ (P) text_horizontal_align | |├ (P) text_vertical_align | |├ (P) linegap | |├ (P) linerelgap | |├ (P) tabstops | |├ (P) password | |├ (P) replacement_char
Description
Description
Details
Details
- Differential Revisions
- D10963: efl_text_format: rename tabstops,lingap,linerelgap
- Commits
- D11264 / rEFL7f57e8e6019a: move stabelized items out of @beta
Status | Assigned | Task | ||
---|---|---|---|---|
Open | None | T7510 evaluate stabilization potential of efl.ui classes and dependencies | ||
Open | None | T7849 efl.ui.text | ||
Open | None | T7853 efl.text_interactive | ||
Resolved | ali.alzyod | T7856 efl.text_format | ||
Resolved | ali.alzyod | T7939 enum Efl.Text_Format_Horizontal_Alignment_Auto_Type | ||
Resolved | None | T7940 enum Efl.Text_Format_Wrap |
Comment Actions
The proposed rework:
interface Efl2.Text.Wrap.Properties ├ (P) ellipsis ├ (P) wrap
Previous API has been moved to other classes.
Comment Actions
I am unsure what are the plans for Efl.Text.Format, but having Format and Style interfaces is very confusing. We should find names that indicate what kind of properties each of these interfaces hold.
Comment Actions
Hmmmmm... I think Line already acts as a sort of prefix. Looks clear enough to me as it is.
Except that I would add an underscore to line_gap, line_rel_gap and tab_stops, like the other properties, of course :)