Still applies and test runs cleanly.
Good to go.
Wed, Aug 21
The interface name was added to the struct name in order to avoid collisions between event arg structures with the same name. Removing this prefix leads at least to the following clashes:
Here is a list of generated events from the C# files. (without the prefix).
We could try hiding them but AFAIR they should be public so inherited classes can use them.
Evt today comes from the name of the event. Related to T8163
This could be kinda tricky to do in a generic way. We may end up having to build a list of irregular verbs and their past tense in order to generate them.
We may encounter some difficulty generating the files in sub folders as a meson issue  limits the output of custom_target command to be placed in the same folder as it is called.
Tue, Aug 20
This is a tentative patch with the C# syntax changes for factory binding static parts that are based on Efl.IContent.
Looks good alongside D9637.
Just one thing, can you test how do the generated DocFX pages look like when tuples are involved?
Mon, Aug 19
Oh, also updated after small conflict with @static in the test eo.
Update with header cleanup and testing properties
Update commit message
Fri, Aug 16
Patch is good for review and merging.
Thu, Aug 15
I'll leave the technical details to the c# people, but I think it is a bit late in the day to change the c# bindings syntax now. Not impossible, though.
All name clashes were already solved a long time ago by renaming properties named like classes. Only these three remained (Key, Hold and Text) because they were in a blacklist in the c# generator and I forgot about them.
Wed, Aug 14
Update the test after updates in the C binding process
Update getting the pd from the correct class and emitting the property,bound event.
Tue, Aug 13
Added the DO NOT MERGE tag so we can start reviewing this while we fix an issue regarding getting the part from the binder.
Mon, Aug 12
Still having some issues regarding package caching. Nuget seems too conservative to restore a recently built Efl.Csharp package, even with restore -f --no-cache, etc. Just works after cleaning the package registry.
I've updated the branch with some improvements:
Fri, Aug 9
Would it be a reasonable compromise to borrow the @static modifier from Python and use it alongside @class?
@static sounds like a good solution for T8118, but what's the advantage over just "floating"? Compatibility with languages that don't allow floating functions? How does C# handle "floating" structs btw? Do they have to be in a class too or is it OK to have them floating?
Thu, Aug 8
Do we have a use-case where we get the class type dynamically? If we use it statically, this is just syntax-sugar. And not even very sweet since it makes the code bigger.
Wed, Aug 7
Mhm - i have not looked in detail, but to me this seems like this breaks dependency tracking of the .cs files ? I a
Tue, Aug 6
I've been trying another approach, as dotnet seems to be designed to be used through its regular cli commands (dotnet build, dotnet run, dotnet pack, etc.).
Mon, Aug 5
Yeah, this is good to go. Regarding Text, it is being discussed in the mentioned task in the diff summary.
Rebase after conflict in klass_def.hh (doc_summary was added after this was accepted).
Rebase, updating with the new property name.
Fri, Aug 2
I think @jpeg did some patch for the C++ binding. I think it is required that everyone who did contribute code to this agree to the license change.
Thu, Aug 1
Wed, Jul 31
Updating after big changes.
- MVVM C# classes working
- Added some docs
- Improved testing
One change this version adds is that the Efl.Mono_Model_Internal class was moved to be built into the custom exports library instead of ecore, as it is a binding-specific class and this library is already imported by the binding.
For Efl.Canvas.Text, I think it should be TextView (since it is most basic text element), TextLabel is more advanced element to show one line text.
Efl.Ui.Text can be "Textbox" or "Textblock" but again it may be conflicted with legacy canvas textblock
Efl.Ui.Text and Efl.Canvas.Text are interfaces or objects ? if they are interfaces why donot we use "I" infront to detect that they are interfaces like Efl.UI.IText
Tue, Jul 30
Update with copyright notice directing to AUTHORS file
Update with copyright notice directing to AUTHORS file for better tracking
Rebase and some small updates: