Page MenuHomePhabricator
Feed Advanced Search

Oct 17 2019

zmike archived efl (efl-1.23).
Oct 17 2019, 7:05 AM

Oct 16 2019

YOhoho added a comment to T8380: efl.ui.relative_layout.
@property relation_left {
         keys {
            child: Efl.Object; 
         }
         values {
            target: Efl.Object; 
            relative: double;
         }
      }

You can set base line of each side based on target.
relative decides relative position on horizontal(left, right)/vertical(top, bottom) axis of the target.

Oct 16 2019, 10:25 PM · efl (efl-1.24), efl: api, efl: language bindings
YOhoho triaged T8380: efl.ui.relative_layout as TODO priority.
Oct 16 2019, 10:24 PM · efl (efl-1.24), efl: api, efl: language bindings

Oct 15 2019

ali.alzyod added a comment to T8297: Efl2.Text.Content*.
In T8297#145463, @tasn wrote:

Because the Button widget uses the basic text object which doesn't support markup.

Oct 15 2019, 9:13 AM · efl (efl-1.24), efl: api
tasn added a comment to T8297: Efl2.Text.Content*.

Because the Button widget uses the basic text object which doesn't support markup.

Oct 15 2019, 9:02 AM · efl (efl-1.24), efl: api
ali.alzyod added a comment to T8297: Efl2.Text.Content*.

Are there any reason for button or other widgets to not implement Efl.Text.Content.Markup instead of Efl.Text.Content.Plain
I think it is great feature and already implemented, so why not to use it

Oct 15 2019, 8:48 AM · efl (efl-1.24), efl: api
zmike added a comment to T8297: Efl2.Text.Content*.

I think it's fine to continue having them be separate; the point of interfaces is to break them into manageable chunks of API which can be incrementally applied as needed rather than force nonfunctional API across all possible objects.

Oct 15 2019, 5:38 AM · efl (efl-1.24), efl: api

Oct 14 2019

tasn added a comment to T8297: Efl2.Text.Content*.

I think the separation is cleaner (as not everything supports markup, e.g. the text of a button), but I'm open to whatever you think is right.

Oct 14 2019, 11:22 PM · efl (efl-1.24), efl: api
ali.alzyod added a comment to T8297: Efl2.Text.Content*.

Do we really need two interfaces? we can combine them into one interface, since no one really uses interface Efl2.Text.Content.Plain but instead will use interface Efl2.Text.Content.Markup
So I think combining them into one make sense.

interface Efl2.Text.Content
|├ (P) markup
|├ (P) text
|├ (P) bidi_delimiters
Oct 14 2019, 6:33 AM · efl (efl-1.24), efl: api
zmike moved T8289: efl text widgets from Backlog to Evaluating on the efl: api board.
Oct 14 2019, 5:56 AM · efl (efl-1.24), efl: api
zmike moved T8296: efl2.canvas.text from Backlog to Evaluating on the efl: api board.
Oct 14 2019, 5:56 AM · efl (efl-1.24), efl: api
zmike moved T8297: Efl2.Text.Content* from Backlog to Evaluating on the efl: api board.
Oct 14 2019, 5:56 AM · efl (efl-1.24), efl: api
zmike moved T8298: Efl2.Input.Text from Backlog to Evaluating on the efl: api board.
Oct 14 2019, 5:56 AM · efl (efl-1.24), efl: api
zmike moved T8299: Efl.Text_Cursor from Backlog to Evaluating on the efl: api board.
Oct 14 2019, 5:56 AM · efl (efl-1.24), efl: api
zmike moved T8300: Efl2.Text.Markup from Backlog to Evaluating on the efl: api board.
Oct 14 2019, 5:56 AM · efl (efl-1.24), efl: api
zmike moved T8301: Efl2.Text.Item.Factory from Backlog to Evaluating on the efl: api board.
Oct 14 2019, 5:56 AM · efl (efl-1.24), efl: api

Oct 12 2019

tasn assigned T8298: Efl2.Input.Text to woohyun.
Oct 12 2019, 7:34 AM · efl (efl-1.24), efl: api

Oct 10 2019

cedric added a comment to T5567: Simple factories (with or without model).

I think we should go with this the way we did go with List/Grid and List_View/Grid_View. Menu start simple with a pack API where you pack menu items. Later on we could have a MVVM version.

Oct 10 2019, 4:28 PM · efl (efl-1.24), efl: mvvm, efl: widgets
cedric closed T7580: efl.ui.factory, a subtask of T7845: Unstructured stabilization items, as Resolved.
Oct 10 2019, 4:24 PM · efl (efl-1.24), efl: api, efl: language bindings
cedric closed T7580: efl.ui.factory as Resolved.

This is done.

Oct 10 2019, 4:24 PM · efl (efl-1.23), efl: api
cedric closed T7381: [MVVM] Efl.Ui.View_List Performance Improvement, a subtask of T5354: Provide infrastructure for MVVM, as Resolved.
Oct 10 2019, 4:20 PM · efl (efl-1.24), efl: mvvm, efl: data types
cedric closed T7658: [MVVM] create Efl.Ui.Item_View and infrastructures for common item based view widgets., a subtask of T5354: Provide infrastructure for MVVM, as Resolved.
Oct 10 2019, 4:16 PM · efl (efl-1.24), efl: mvvm, efl: data types
cedric closed T7376: [MVVM] Model Selection Support, a subtask of T5354: Provide infrastructure for MVVM, as Resolved.
Oct 10 2019, 4:14 PM · efl (efl-1.24), efl: mvvm, efl: data types
cedric closed T7376: [MVVM] Model Selection Support as Resolved.
Oct 10 2019, 4:14 PM · efl (efl-1.23), efl: mvvm
cedric closed T5333: Cleanup View interface aka finish MVVM as Resolved.
Oct 10 2019, 4:13 PM · efl (efl-1.23), efl: mvvm, efl: data types
cedric closed T5333: Cleanup View interface aka finish MVVM, a subtask of T5354: Provide infrastructure for MVVM, as Resolved.
Oct 10 2019, 4:13 PM · efl (efl-1.24), efl: mvvm, efl: data types
tasn added a parent task for T8298: Efl2.Input.Text: T8151: RFC: Text interfaces design proposal.
Oct 10 2019, 8:10 AM · efl (efl-1.24), efl: api
stefan_schmidt added a comment to T8119: Evas segfaults on recent builds of x86.

Correct, the feature was enabled again in master now and we need to make sure it gets fixed before the next release.

Oct 10 2019, 1:28 AM · efl (efl-1.24)

Oct 9 2019

Thanatermesis added a comment to T8119: Evas segfaults on recent builds of x86.

Sorry to not have answered before, I was not receiving notifications until now :)

Oct 9 2019, 5:14 PM · efl (efl-1.24)

Oct 7 2019

segfaultxavi added a comment to T7573: efl.ui.l10n.

The EO file is weird:

@property l10n_text {
   set {
   }
   get {
      values {
         domain: string @optional;
      }
      return: string;
   }
   values {
      label: string;
      domain: string @optional;
   }

This means the setter has two parameters (label and domain) but the getter only has one (domain). So what is the getter retrieving? Is this thing in use?

Oct 7 2019, 2:25 AM · efl (efl-1.24), efl: api

Oct 4 2019

zmike added a commit to T8280: eolian_cxx not freeing iterators (thus leaking memory): rEFLe0341cd8f6f3: eolian-cxx: Release iterators.
Oct 4 2019, 7:40 AM · efl (efl-1.24)
zmike added a commit to T8214: EDI Cursor issues: rEFLa20aea042832: elm_code_widget: when the position is updated, set new geom to cursor.
Oct 4 2019, 7:40 AM · efl (efl-1.23), regression, Restricted Project
bu5hm4n removed subtasks for T5354: Provide infrastructure for MVVM: T7382: [MVVM] Efl.Ui.View_List Homogenous Support, T5365: Use efl.part for efl.ui.property_bind.
Oct 4 2019, 3:16 AM · efl (efl-1.24), efl: mvvm, efl: data types
bu5hm4n removed a parent task for T5365: Use efl.part for efl.ui.property_bind: T5354: Provide infrastructure for MVVM.
Oct 4 2019, 3:16 AM · efl (efl-1.23), efl: mvvm, efl: widgets
bu5hm4n removed subtasks for T5354: Provide infrastructure for MVVM: T7659: Fix efl_part issues in C#, T7485: [MVVM] Add a Factory class that help implementing cached item factory.
Oct 4 2019, 3:15 AM · efl (efl-1.24), efl: mvvm, efl: data types
bu5hm4n removed subtasks for T5354: Provide infrastructure for MVVM: T8153: Efl.Ui.Factory_Bind work on string, T7670: Remove Efl.Model_Container_Item, T7668: Autogenerate property_bind View , T7528: Improve lifecycle of Child model, T7458: Composite Model renaming, T7405: [MVVM] Multistyle Factory, T7404: [MVVM] Factory text property handles, T7380: [MVVM] Efl.Ui.Viewlist renaming., T5355: Replacement of genlist for MVVM.
Oct 4 2019, 3:14 AM · efl (efl-1.24), efl: mvvm, efl: data types
bu5hm4n removed a parent task for T5355: Replacement of genlist for MVVM: T5354: Provide infrastructure for MVVM.
Oct 4 2019, 3:14 AM · efl (efl-1.23), efl: mvvm, efl: widgets
bu5hm4n removed a parent task for T8153: Efl.Ui.Factory_Bind work on string: T5354: Provide infrastructure for MVVM.
Oct 4 2019, 3:14 AM · efl (efl-1.23), efl: mvvm, efl: data types
bu5hm4n removed subtasks for T5333: Cleanup View interface aka finish MVVM: T7832: Provide helper logic for text binded property, T7473: Add a create event on Efl.Ui.Factory, T7472: Asynchronous create function in Efl.Ui.Factory, T7471: Add an efl.model.property_ready_get and efl.model.properties_ready_get., T7470: [MVVM] Create a ViewModel helper class, T7469: Find a better name for Efl.Factory.model_connect.
Oct 4 2019, 3:13 AM · efl (efl-1.23), efl: mvvm, efl: data types
bu5hm4n removed a parent task for T7832: Provide helper logic for text binded property: T5333: Cleanup View interface aka finish MVVM.
Oct 4 2019, 3:13 AM · efl (efl-1.23), efl: mvvm, efl: data types
bu5hm4n removed a subtask for T6360: EO: Item and Item_List API's: T5327: Refactor toolbar.
Oct 4 2019, 3:07 AM · efl (efl-1.23), efl: mvvm, efl: widgets

Oct 3 2019

tasn added a comment to T8298: Efl2.Input.Text.

@woohyun, do you fellas have any input on this? A lot of these functions need like they need some changes and you all have the expertise. I was hoping to get feedback in the other ticket, but let's just merge the discussion to here.

Oct 3 2019, 12:16 AM · efl (efl-1.24), efl: api

Oct 2 2019

segfaultxavi updated the task description for T7717: docs todo.
Oct 2 2019, 6:17 AM · efl (efl-1.24), efl: docs, efl: api
tasn added a comment to T8297: Efl2.Text.Content*.

This affects a lot of the naming then. I didn't realise you were planning on stabilising Efl.Text, I thought it was within my mandate to change, and to be honest, I thought I'd have the energy to fight the restriction/regression.

Oct 2 2019, 6:13 AM · efl (efl-1.24), efl: api
tasn added a comment to T8297: Efl2.Text.Content*.

Ah oops, already released. :(

Oct 2 2019, 6:12 AM · efl (efl-1.24), efl: api
tasn added a comment to T8297: Efl2.Text.Content*.

It shouldn't be, because this restriction shouldn't (and haven't) be there. Though it is.

Oct 2 2019, 6:11 AM · efl (efl-1.24), efl: api
zmike added a comment to T8297: Efl2.Text.Content*.

Aha, I see.

Oct 2 2019, 6:08 AM · efl (efl-1.24), efl: api
zmike added a comment to T7864: efl.gfx.arrangement.

Alright, so we've now got content_padding that has 2x uint params (thanks @YOhoho!).

Oct 2 2019, 6:06 AM · efl (efl-1.24), efl: api, efl: language bindings
tasn added a comment to T8297: Efl2.Text.Content*.

Let me explain what I meant:

Oct 2 2019, 6:04 AM · efl (efl-1.24), efl: api
zmike added a comment to T8297: Efl2.Text.Content*.

I'm not sure I understand your argument here. Just because an interface has been stabilized doesn't mean that it can't have methods/properties/events added to it. My comment about Efl.Text being stable was with regard to the name of the interface and its existing property, not its ability to receive new features.

Oct 2 2019, 5:59 AM · efl (efl-1.24), efl: api
segfaultxavi added a commit to T7864: efl.gfx.arrangement: rEFLfa908800556d: efl_gfx_arrangement: change content_padding param type and remove scalable.
Oct 2 2019, 3:11 AM · efl (efl-1.24), efl: api, efl: language bindings
tasn added a comment to T8299: Efl.Text_Cursor.
In T8299#144189, @zmike wrote:

I do like this rework a lot better, and it seems sensible to have a (temporary) object for this kind of thing just for actual usage.

class Efl2.Text.Cursor
├ (P) position

This should probably be something more like text_position just to be explicit about what kind of position it is.

Oct 2 2019, 2:56 AM · efl (efl-1.24), efl: api

Oct 1 2019

tasn added a comment to T8296: efl2.canvas.text.

Some quick comments:

├ (P) size_formatted
├ (P) size_native

What are the units of these sizes? From the example, it looks like it's characters.

Oct 1 2019, 11:35 PM · efl (efl-1.24), efl: api
tasn added a comment to T8296: efl2.canvas.text.
In T8296#144139, @zmike wrote:
class Efl2.Canvas.Text
├ (P) is_empty
├ (P) is_ellipsized
├ (P) style_insets

For these 3 (and the size_* properties) it would be nice to have a doc note about whether they perform additional operations (i.e., recalc) or just return internal values. This could likely be stated as a global doc note in the class doc instead of per-property.

Oct 1 2019, 11:32 PM · efl (efl-1.24), efl: api
tasn added a comment to T8296: efl2.canvas.text.
In T8296#144135, @zmike wrote:

To start, I think this entire API could be moved to something like Efl.Gfx.Textblock (in src/efl/interfaces) and then implemented by this object, which seems like it would be best-named Efl.Canvas.Textblock in order to reflect the purpose. Is Efl.Ui.Text intended to be a reimplementation of these methods/properties or will it just forward to this object? If it's reimplementing then the interface should probably be a mixin?

Oct 1 2019, 11:23 PM · efl (efl-1.24), efl: api
tasn added a comment to T8301: Efl2.Text.Item.Factory.

Also going to overhaul

Oct 1 2019, 1:25 PM · efl (efl-1.24), efl: api
tasn added a comment to T8300: Efl2.Text.Markup.

Will probably change, see my comment in T7855. It's also something I'm thinking of overhauling tomorrow.

Oct 1 2019, 1:25 PM · efl (efl-1.24), efl: api
tasn added a comment to T8297: Efl2.Text.Content*.

Efl.Text being stable means we can't use this namespace at all... :| This shouldn't be a problem, and it's stupid we are jumping backwards and shittifying our API instead of fixing bindings generators, but it's another argument I gave up on (and was already decided in the past but was changed without a discussion on the ML so I didn't catch it).

Oct 1 2019, 1:22 PM · efl (efl-1.24), efl: api
tasn added a comment to T7855: efl.text_font.

I suspect this might change a bit tomorrow. This, as you said, is essentially a copy of what was there, though I'm having second thoughts about it. I'm in the process of reviewing everything now that we've had some time to absorb the new interfaces and I don't think I like this.

Oct 1 2019, 1:19 PM · efl (efl-1.24), efl: api, efl: language bindings
tasn added a comment to T8298: Efl2.Input.Text.

Sorry this is still just a copy paste from what was there before. I'm still waiting for feedback on these functions in T8226. They will only be changed after that.

Oct 1 2019, 1:18 PM · efl (efl-1.24), efl: api
tasn added a comment to T8299: Efl.Text_Cursor.

Thanks a lot for your feedback! I only learned today about Eina.Position2D et al. This is exactly the kind of feedback I was looking for. Will act upon it soon!

Oct 1 2019, 1:16 PM · efl (efl-1.24), efl: api
zmike triaged T8301: Efl2.Text.Item.Factory as TODO priority.
Oct 1 2019, 10:32 AM · efl (efl-1.24), efl: api
zmike added a comment to T8300: Efl2.Text.Markup.

This feels pretty bizarre with the naming considering Efl.Text is a simple text get/set interface. Probably needs some thinking on; feels almost like it should be Markup_Interactive or somesuch.

Oct 1 2019, 10:31 AM · efl (efl-1.24), efl: api
zmike triaged T8300: Efl2.Text.Markup as TODO priority.
Oct 1 2019, 10:26 AM · efl (efl-1.24), efl: api
zmike added a comment to T8299: Efl.Text_Cursor.

I do like this rework a lot better, and it seems sensible to have a (temporary) object for this kind of thing just for actual usage.

Oct 1 2019, 10:23 AM · efl (efl-1.24), efl: api
zmike added a comment to T8299: Efl.Text_Cursor.

The proposed rework:

Oct 1 2019, 10:09 AM · efl (efl-1.24), efl: api
zmike triaged T8299: Efl.Text_Cursor as TODO priority.
Oct 1 2019, 10:08 AM · efl (efl-1.24), efl: api
zmike updated the task description for T8298: Efl2.Input.Text.
Oct 1 2019, 9:53 AM · efl (efl-1.24), efl: api
zmike added a comment to T8298: Efl2.Input.Text.

I'll preface this by saying that I'm not an expert on input panel needs (@woohyun and HQ experts on that) and am only reviewing the API based on a surface-level understanding of it and how cohesive it may be to the rest of the stabilized EFL API stack. This interface is for defining methods for allowing widgets to interact with input method modules.

interface Efl2.Input.Text
├ (P) autocapital_type

This name feels weird.

├ (P) prediction_allow

Shouldn't this just be text_prediction with the value being enable?

├ (P) input_hint

This is pretty ugly with such a huge enum, but I'm not sure how we could improve on it without making the API worse. Will require some thought.

Oct 1 2019, 9:53 AM · efl (efl-1.24), efl: api
zmike triaged T8298: Efl2.Input.Text as TODO priority.
Oct 1 2019, 9:41 AM · efl (efl-1.24), efl: api
zmike added a comment to T7856: efl.text_format.

This needs doc work, but so does everything else. Seems good.

Oct 1 2019, 9:40 AM · efl (efl-1.24), efl: api, efl: language bindings
zmike added a comment to T7856: efl.text_format.

The proposed rework:

interface Efl2.Text.Wrap.Properties
├ (P) ellipsis
├ (P) wrap
Oct 1 2019, 9:39 AM · efl (efl-1.24), efl: api, efl: language bindings
zmike added a comment to T7857: efl.text_style.
├ (P) underline2_color
├ (P) glow2_color

These seem like they should be renamed to something clearer.

Oct 1 2019, 9:27 AM · efl (efl-1.24), efl: api, efl: language bindings
zmike added a comment to T7857: efl.text_style.

The proposed rework:

interface Efl2.Text.Style.Properties
├ (P) foreground_color
├ (P) background_type
├ (P) background_color
├ (P) underline_type
├ (P) underline_color
├ (P) underline_height
├ (P) underline_dashed_color
├ (P) underline_dashed_width
├ (P) underline_dashed_gap
├ (P) underline2_color
├ (P) strikethrough_type
├ (P) strikethrough_color
├ (P) effect_type
├ (P) outline_color
├ (P) shadow_direction
├ (P) shadow_color
├ (P) glow_color
├ (P) glow2_color
├ (P) gfx_filter
├ (P) halign_auto_type
├ (P) halign
├ (P) valign
├ (P) line_spacing
├ (P) line_spacing_factor
├ (P) line_height
├ (P) line_height_factor
├ (P) tab_width
Oct 1 2019, 9:20 AM · efl (efl-1.24), efl: api, efl: language bindings
zmike added a comment to T7855: efl.text_font.

font_lang should be font_language I think since we've been consistent about not shortening words. Otherwise this is just doing font -> font_family and adding font_size. Seems reasonable, and the name Font.Properties also makes sense.

Oct 1 2019, 9:17 AM · efl (efl-1.24), efl: api, efl: language bindings
zmike updated subscribers of T7855: efl.text_font.

The proposed rework:

interface Efl2.Text.Font.Properties
├ (P) font_family
├ (P) font_size
├ (P) font_source
├ (P) font_fallbacks
├ (P) font_weight
├ (P) font_slant
├ (P) font_width
├ (P) font_lang
├ (P) font_bitmap_scalable
Oct 1 2019, 9:15 AM · efl (efl-1.24), efl: api, efl: language bindings
zmike added a comment to T8297: Efl2.Text.Content*.

Efl2.Text.Content.Markup is T7858
Efl2.Text.Content.Plain is T7854

Oct 1 2019, 9:12 AM · efl (efl-1.24), efl: api
zmike triaged T8297: Efl2.Text.Content* as TODO priority.
Oct 1 2019, 9:10 AM · efl (efl-1.24), efl: api
segfaultxavi added a comment to T8296: efl2.canvas.text.

Following @zmike's suggestion:

├ (E) layout,changed

We have been using the naming convention property_name,changed for events triggered when a property changes, but there's no property named layout.
Could this event be renamed to follow this convention? Is there any particular property change that would always emit this event?

Oct 1 2019, 8:48 AM · efl (efl-1.24), efl: api
zmike added a comment to T8296: efl2.canvas.text.

Ah, a further note: style cannot be used here as it will conflict with style from Efl.Ui.Widget. Perhaps text_style or some other name.

Oct 1 2019, 8:46 AM · efl (efl-1.24), efl: api
devilhorns closed T7089: evas_vg_batman example doesn't run under weston as Resolved.

This is working now. Fixed by commit https://git.enlightenment.org/core/efl.git/commit/?id=13ecc4898c23aa58421a847efbe5392d2b18cef8

Oct 1 2019, 8:18 AM · efl (efl-1.23), Restricted Project, efl: rendering
segfaultxavi added a comment to T8296: efl2.canvas.text.

Some quick comments:

├ (P) size_formatted
├ (P) size_native

What are the units of these sizes? From the example, it looks like it's characters.

├ (P) style
The style priority is the order of creation, styles created first                                            
are applied first with the exception of $NULL which is implicitly                                            
first.

Having the priority of a style depend on the creation timestamp of the style seems a bit complicated.
We could keep this as default behavior, but I would add API to change a style's priority.
Also, I do not know what a style string is in this context, is this explained someplace else?

Oct 1 2019, 7:31 AM · efl (efl-1.24), efl: api
zmike added a comment to T7704: verify @since tags for stabilized apis.

To clarify, this should fail only in src/lib, since we don't necessarily want to enforce this for all usages of eolian (e.g., tests/apps).

Oct 1 2019, 6:44 AM · efl (efl-1.24), efl: docs, efl: api
zmike added a comment to T8296: efl2.canvas.text.
class Efl2.Canvas.Text
├ (P) is_empty
├ (P) is_ellipsized
├ (P) style_insets

For these 3 (and the size_* properties) it would be nice to have a doc note about whether they perform additional operations (i.e., recalc) or just return internal values. This could likely be stated as a global doc note in the class doc instead of per-property.

├ (P) legacy_newline

Is this just for providing compatibility with legacy API? If so, then I think this should be an internal thing and not exposed in the eo file.

├ (P) style
├ (P) size_formatted
├ (P) size_native

These two should both be Eina.Size2D.

├ (M) visible_range_get
├ (M) cursor_handle_new
├ (M) cursor_handle_free
Oct 1 2019, 6:38 AM · efl (efl-1.24), efl: api
zmike added a comment to T8296: efl2.canvas.text.

To start, I think this entire API could be moved to something like Efl.Gfx.Textblock (in src/efl/interfaces) and then implemented by this object, which seems like it would be best-named Efl.Canvas.Textblock in order to reflect the purpose. Is Efl.Ui.Text intended to be a reimplementation of these methods/properties or will it just forward to this object? If it's reimplementing then the interface should probably be a mixin?

Oct 1 2019, 6:27 AM · efl (efl-1.24), efl: api
zmike triaged T8296: efl2.canvas.text as TODO priority.
Oct 1 2019, 6:06 AM · efl (efl-1.24), efl: api
zmike added a comment to T8289: efl text widgets.
In T8289#144119, @tasn wrote:

Thanks for your comments. The branch generates just fine here (other than the C++ bindings that don't compile, but that will be fixed once I rename things). Are you using latest Eolian or the one from my branch? Because q66 recently made some breaking changes.

As for your comments:

In T8289#144050, @zmike wrote:
class Efl2.Ui.Text
├ (P) valign

This seems like it could just be efl.gfx.arrangement::content_align.

Thanks for the tip. It does indeed, though it means I have to also implement padding I guess?

Oct 1 2019, 6:00 AM · efl (efl-1.24), efl: api
tasn added a comment to T8289: efl text widgets.

Thanks for your comments. The branch generates just fine here (other than the C++ bindings that don't compile, but that will be fixed once I rename things). Are you using latest Eolian or the one from my branch? Because q66 recently made some breaking changes.

Oct 1 2019, 1:19 AM · efl (efl-1.24), efl: api

Sep 30 2019

q66 added a commit to T7704: verify @since tags for stabilized apis: rEFL71c83d2005e0: efl: add code to enforce presence of @since tags.
Sep 30 2019, 11:13 AM · efl (efl-1.24), efl: docs, efl: api
zmike added a comment to T8289: efl text widgets.
class Efl2.Ui.Text
├ (P) valign

This seems like it could just be efl.gfx.arrangement::content_align.

├ (P) scrollable

This could probably be managed through efl.ui.widget_scrollable_content::scrollable_content for anyone who wants it?

├ (P) cnp_mode
├ (P) selection_handler_disabled

This seems a bit strange? I'd imagine this type of thing should use a selection API and not be directly part of the widget.

├ (M) cnp_copy
├ (M) cnp_cut
├ (M) cnp_paste

I'll leave these since I don't know how fully the cnp stuff is thought out at this point.

├ (P) context_menu_disabled
├ (M) context_menu_clear
├ (M) context_menu_item_add

This context menu API feels pretty ugly to continue using, just as it did in legacy. I imagine we can come up with better ideas here?

├ (E) cnp,paste
├ (E) cnp,copy
├ (E) cnp,cut

These events should all probably have event info.

Sep 30 2019, 10:06 AM · efl (efl-1.24), efl: api
zmike updated the task description for T8289: efl text widgets.
Sep 30 2019, 9:36 AM · efl (efl-1.24), efl: api
zmike edited projects for T7510: evaluate stabilization potential of efl.ui classes and dependencies, added: efl: api; removed efl: language bindings.
Sep 30 2019, 9:35 AM · efl (efl-1.24), efl: api
zmike edited projects for T8289: efl text widgets, added: efl: api; removed efl: language bindings.
Sep 30 2019, 9:35 AM · efl (efl-1.24), efl: api
zmike triaged T8289: efl text widgets as TODO priority.
Sep 30 2019, 9:34 AM · efl (efl-1.24), efl: api
q66 added a commit to T8280: eolian_cxx not freeing iterators (thus leaking memory): rEFLf3199ba04bcb: eolian-cxx: Release iterators.
Sep 30 2019, 7:08 AM · efl (efl-1.24)
q66 added a commit to T8280: eolian_cxx not freeing iterators (thus leaking memory): rEFL507061a145b8: bindings: Fix disposal of eolian state.
Sep 30 2019, 7:08 AM · efl (efl-1.24)
zmike updated subscribers of T7704: verify @since tags for stabilized apis.

@q66 this should be enforced by eolian at build time and fail the build if a stable class is detected without @since

Sep 30 2019, 5:32 AM · efl (efl-1.24), efl: docs, efl: api
segfaultxavi updated the task description for T7717: docs todo.
Sep 30 2019, 2:50 AM · efl (efl-1.24), efl: docs, efl: api
stefan_schmidt closed T8214: EDI Cursor issues as Resolved by committing rEFL8de8f059c94f: elm_code_widget: when the position is updated, set new geom to cursor.
Sep 30 2019, 1:47 AM · efl (efl-1.23), regression, Restricted Project
zmike closed T8274: Impossible to access Evas stabilize class by including Efl_Ui.h as Resolved by committing rEFL52d04bc52426: efl_ui: remove legacy component includes, include Efl_Layout.h and Efl_Canvas.h.
Sep 30 2019, 1:35 AM · efl (efl-1.23), efl: language bindings