- User Since
- Sep 27 2013, 1:37 AM (242 w, 3 d)
Wed, May 16
Fri, May 11
I'm not sure the cause but the result is that there is documentation outside of the normal guards that hold back those beta APIs.
Can we please change the documentation then? Evas_Object_Vg Is public documentation marked as @since 1.14...
Sun, Apr 22
Mar 30 2018
With the current widget setup I cannot find a way to make this work.
The mouse move event is not triggered on the text as the mouse is somehow tied to the background where the drag started.
Mar 29 2018
Mar 22 2018
Looking at some editors (on OS X):
When you right click the cursor jumps to the location so that the operation will happen where expected.
If you are outside the area and there is a long line of text on the last line it does not make sense to paste at the end of it - the content will not appear in the expected position.
Where in the last line? The pointer position may not be after the end of the last line...
I had thought that would be the correct behaviour... Given that there is no context at that location what do you imagine the menu should contain?
Feb 10 2018
Feb 4 2018
Jan 29 2018
Jan 25 2018
Jan 19 2018
I disagree with the combining of toolbar and tab bar. Whilst they may be similar from a ui (and also external api) point of view the function differently.
Jan 18 2018
p.s. would this not be better described as "navigation" rather than "accessibility" issues
Its all linked from the menu in any Contribute page - https://www.enlightenment.org/contrib/start
I don't think this can be closed once elm_interface*.eo is done - there are other relationships still using the Elm namespace, vis:
Jan 15 2018
This is progressing but hit a wall.
The current work in progress is at efl.git/devs/ajwillia-ms/elm_code_wrap.
Unfortunately when you make the window smaller so it wraps I get a corruption in evas_textgrid that I cannot figure out.
Jan 14 2018
Jan 5 2018
Done, at least a first pass https://www.enlightenment.org/contrib/devs/enlightenment-regression.md
Editors remain in phab for now. All docs in phab that have been replaced should link out to the new website pages.
Jan 4 2018
Should we go down the Efl_Core, Efl_Net and Efl_Ui grouping route again? @cedric
Also should be discussed at our next meeting
All child tickets resolved, nothing additional remains in this ticket.
Packaging in Edi was deemed out of scope but will be completed later in my spare time.
In essence we have done all we can here until the Beta API progresses. Progress is being tracked in T5835
Trying to figure out how to solve this without T6126, which has been deprioritised.
last .eo files merged today.
The doxygen integration remains, I will ensure there is a separate ticket.
On looking at it the Clouseau outstanding issues belong on a separate tooling ticket (if the work is still outstanding).
This was not discussed or the conclusion not registered
It is just the editor links that remain. Should we port that over or is it comfortably part of the "developing EFL and E" scope of our phabricator installation?
I believe that, for the examples that are being ported (and thus more discoverable) we have done the cleanup required.
There are more comments than I would like but that is mostly to illustrate for tutorial purposes.
Pretty sure we have converted what is needed