aboutsummaryrefslogtreecommitdiffstats
path: root/src/lib/elementary/efl_ui_progressbar_part.eo
diff options
context:
space:
mode:
authorJean-Philippe Andre <jp.andre@samsung.com>2017-09-20 11:16:17 +0900
committerJean-Philippe Andre <jp.andre@samsung.com>2017-09-21 12:27:34 +0900
commit112edeeea807a5dc499d003729c4a8cad829c5a6 (patch)
tree1d37de5673d3ba7d7670036b02101dd41eb112e0 /src/lib/elementary/efl_ui_progressbar_part.eo
parentelm: Split off text and content for efl_part (diff)
downloadefl-112edeeea807a5dc499d003729c4a8cad829c5a6.tar.gz
elm: Remove range "span_size" API in EO
Reasons: - This API has been confused with the min size of the widget, resulting in badly laid out applications. - The EO API was not very nice (Range is about numbers, the Gfx size hint in a part is really ugly). While I understand the value of this API and how it can be used in scalable applications, it is in fact not absolutely necessary. Alternatively to that span size, the widget min size can already be defined from the application side, or the widget can simply be expanded to fill in its parent. This can obviously be reinstated later if the need arises for EO. For now, keep this feature as legacy-only.
Diffstat (limited to 'src/lib/elementary/efl_ui_progressbar_part.eo')
-rw-r--r--src/lib/elementary/efl_ui_progressbar_part.eo3
1 files changed, 1 insertions, 2 deletions
diff --git a/src/lib/elementary/efl_ui_progressbar_part.eo b/src/lib/elementary/efl_ui_progressbar_part.eo
index 0eb21412ea..a57bfa7cdc 100644
--- a/src/lib/elementary/efl_ui_progressbar_part.eo
+++ b/src/lib/elementary/efl_ui_progressbar_part.eo
@@ -1,9 +1,8 @@
-class Efl.Ui.Progressbar.Part (Efl.Ui.Layout.Part_Content, Efl.Ui.Range)
+class Efl.Ui.Progressbar.Part (Efl.Ui.Layout.Part, Efl.Ui.Range)
{
[[Elementary progressbar internal part class]]
data: null;
implements {
- Efl.Container.content { set; }
Efl.Ui.Range.range_value { set; get; }
}
}