There are name conflict cases between class and property. For example,
- Efl.Ui.Text Class name and Text property of Efl.Text interface. (D7394#129052)
- Efl.Canvas.Text Class name and Text property of Efl.Text interface.
- Efl.Input.Hold Class name and its Hold property.
- Efl.Input.Key Class name and its Key property.
In eolian_mono, Efl.IText.Text is listed in blacklist because of Compiler Error CS0542(https://docs.microsoft.com/en-us/dotnet/csharp/misc/cs0542). there are only getter, setter methods(GetText, SetText).
The other UI Frameworks text widget naming will help this discussion.
| EFL(elm) | EFL(Efl.Ui) | Xamarin | WPF | UWP | Android | |
|---|---|---|---|---|---|---|
| for presenting text | Label | Text | Label | TextBlock | TextBlock | TextView |
| for editing single line text | Entry | Text, TextEditable | Entry | TextBox | TextBox | EditText |
| for editing multi line text | Entry | Text, TextEditable | Editor | TextBox | TextBox | EditText |
Android:
TextView - https://developer.android.com/reference/android/widget/TextView
EditText - https://developer.android.com/reference/android/widget/EditText
WPF :
TextBlock - https://docs.microsoft.com/en-us/dotnet/api/system.windows.controls.textblock?view=netframework-4.8
TextBox - https://docs.microsoft.com/en-us/dotnet/api/system.windows.controls.textbox?view=netframework-4.8
UWP : https://docs.microsoft.com/en-us/windows/uwp/design/controls-and-patterns/text-controls
Xamarin : https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/text/
I'd like to suggest some widget names.
- TextView - It may make conflict with MVVM namespace.
- TextBlock - There is evas_object_textblock. but it is legacy evas_object(not eo). so, it won't be problem.
- EditableText - In this case, Text and TextEditable should be merged.