Page MenuHomePhabricator

tooltip: eo based APIs required for tooltip
Open, NormalPublic

Description

  • make tooltip an EO widget.
  • replace indicators (used in slider and other widgets) with tooltip? If tooltip APIs are eo apis then we could remove indicators uses in slider and have common interface for this.

The elm_tooltip API has no EO equivalent yet. It provides convenience functions to assign automatic tooltips with a content or text label.

We need the convenience in EO API as well, but we may want more features, and we need to redesign to match EO's limitations.

  1. Transform API into an EO API on Elm.Widget. The callbacks will probably require a delegate/factory or a direct override.
  2. The tooltip API could be part based, although right now it isn't (if so, we can't use a direct override, only a delegate/factory).
  3. We may want to create a base tooltip widget, that could be created and managed by apps, as well as used for things like slider indicator and other common use cases.
cedric raised the priority of this task from TODO to Normal.Jul 10 2017, 3:45 PM
In T5641#89973, @jpeg wrote:

The elm_tooltip API has no EO equivalent yet. It provides convenience functions to assign automatic tooltips with a content or text label.

We need the convenience in EO API as well, but we may want more features, and we need to redesign to match EO's limitations.

  1. Transform API into an EO API on Elm.Widget. The callbacks will probably require a delegate/factory or a direct override.
  2. The tooltip API could be part based, although right now it isn't (if so, we can't use a direct override, only a delegate/factory).
  3. We may want to create a base tooltip widget, that could be created and managed by apps, as well as used for things like slider indicator and other common use cases.

@jpeg
If we will go with #3 way, it looks much like ctxpopup. (If tooltip will be developed more with new features)
And, I am not sure this tooltip support is really helpful to the developer side ? (If it does not have any way to customize its look easily)

jpeg added a comment.Jul 10 2017, 11:21 PM

I agree that #3 can be done later. But I think a common interface would be good for API (not necessarily a complete tooltip widget class).

jpeg added a comment.Dec 11 2017, 7:11 PM

I think we should use a part API to expose at least the text variant of tooltips. This would go directly in Efl.Ui.Widget class' parts.
I also think the content variant could be done using efl_content_set rather than a callback. The callback could in fact be implemented later with T6265.

zmike edited projects, added Restricted Project; removed efl.Jun 11 2018, 6:57 AM
zmike edited projects, added efl: widgets; removed Restricted Project.Jun 11 2018, 8:15 AM