We want to keep implementation for file interface in a safe place and remove it from our side world (eo).
This is a simple copy-paste, from efl.ui.textbox into efl_ui_internal_text_interactive
woohyun | |
bu5hm4n |
We want to keep implementation for file interface in a safe place and remove it from our side world (eo).
This is a simple copy-paste, from efl.ui.textbox into efl_ui_internal_text_interactive
Automatic diff as part of commit; lint not applicable. |
Automatic diff as part of commit; unit tests not applicable. |
It seems that this patch has no reviewers specified. If you are unsure who can review your patch, please check this wiki page and see if anyone can be added: https://phab.enlightenment.org/w/maintainers_reviewers/
I'm ok with this patch because efl_ui_textblock class has a composite relation with efl_ui_internal_text_interactive class
So, the file method would not be exposed from efl_ui_textblock.
In conclusion, we achieve the goal for keeping file codes internally :)
@bu5hm4n
Do you have better idea on this ?