What's next !?

[fstuff-dev]

IMO we have now to define a list of "Done" or "Quite Done" and "Todo".

Done:

• Defined LvObj
• Defined LvWidgets
• Defined LvTimers
• Define LvStyle
• Defined LvAnim
• Defined LvAnimTimeline

Quite done:

• Defined LvDisplay - At moment only for "Make it works"
• Defined LvIndev - At moment only for "Make it works"
• Defined LvScr - At moment only for "Make it works"

Todo:

• Define Themes
• Define Layouts
• Choose a default interface for OS for locking lvgl function calls and make it Threadsafe ??!
• Others ...

LVGL Rocks !

[kisvegabor]

Sounds good. Let me know if you have any LVGL related questions! 🙂

[fstuff-dev]

Sounds good. Let me know if you have any LVGL related questions!

Yep. ! i have a little question about layouts !
Can the function defined in lv_flex/lv_grid be applied to any obj ? if so in your opinion can be integrated in the LvObj Class ?
The same for style functions that are implemented in lv_flex/lv_grid that works with style ? can be part of LvStyle Class ?

Thanks

[kisvegabor]

Can the function defined in lv_flex/lv_grid be applied to any obj ?

Yes, they can.

if so in your opinion can be integrated in the LvObj Class ?

IMO if a function starts with lv_obj_* it can be integrated into the LvObj class. Similarly, lv_style_* function can go to the LvStyle class.

[fstuff-dev]

Great ! 👍

[fstuff-dev]

@kisvegabor You can view some example on how to use Flex on lv_cpp_example in the repository.
https://github.com/lvgl/lv_binding_cpp/blob/master/lv_cpp_examples/FlexEx.cpp
This use also the standard "new" for create objects.
👍

[amirgon]

Hi @fstuff-dev ,

Are you planning at some point to generate the C++ API automatically from the C API? Or are you already doing this?
Otherwise, any future change to LVGL would require manual fix to lv_binding_cpp

[fstuff-dev]

Hi, I already use a python script to automatically generate cpp API from C code !
It's in a early stage but it works ...

[amirgon]

I already use a python script to automatically generate cpp API from C code !

That's great!
I didn't find the script in the repo, maybe I missed it?

Do you plan to run the script as part of your build process?
This could be useful if someone wants to use a different/modified version of LVGL, other than the one you converted and submitted.

[fstuff-dev]

As I said the script is in a really early stage, so at the moment i don't like to make it public ! In the near future I will clean and make it usable at user prospective, so i will make public
😊

[fstuff-dev]

@amirgon If you want to see the script you can find at https://github.com/fstuff-dev/lv_binding_cpp_generator/tree/earlystage .
As the link says is "earlystage" so don't use it. Some Class in /core folder are added manually !.
As i said i will write a clean script and complete script that i will upload in the repo !
👍

[amirgon]

As i said i will write a clean script and complete script that i will upload in the repo !

Ok, great!

On the long run I think it would make sense to generate the code as part of the build process, instead of comitting generated code into the repo. What do you think?

[fstuff-dev]

I think that is the best choice !

[amirgon]

A few questions:

• In an event callback, how do you get the CPP object from the event?
  You can get lv_obj by calling lv_event_get_target, but how do you get the CPP object from that?
• How do you handle object lifetime?
  Suppose I inherit from LvObj, what would happen if the underlying lv_obj is deleted either directly or indirectly (when its parent is deleted)?

[fstuff-dev]

A few questions:

• In an event callback, how do you get the CPP object from the event?

You can get lv_obj by calling lv_event_get_target, but how do you get the CPP object from that?

The library sacrifice the "user_data" to make C and CPP object match. But if someone have better idea will be appreciated.

• How do you handle object lifetime?

Suppose I inherit from LvObj, what would happen if the underlying lv_obj is deleted either directly or indirectly (when its parent is deleted)?

That's one of the problem to resolve !