5 ms·

Thanks for point out this, I can explain more details here: It's easy to write apps in C language to support both android and ios platform if using libphone. Wr

Thanks for point out this, I can explain more details here: It's easy to write apps in C language to support both android and ios platform if using libphone. Write once, target both. There is a similar project xamarin but it use C# and it is IDE, libphone is just a library though with also some tools for platform resources generating and layout.

biokoda 10y ago
so this is a GUI library for iOS/Android?
- huxingyi 10y ago
  Yes, and not just GUI, there are also other fundamental apis provided like timer, work queue.
  - biokoda 10y ago
    Have you thought about integrating with https://github.com/andlabs/libui https://github.com/andlabs/libui edit: What about maybe as an optional backend? That way one could develop on a desktop easier.
    - huxingyi 10y ago
      It's turely an optional backend for just DEBUG purpose, like preview layout on desktop. I'll think about it, thank you. Welcome to post more ideas. It' realy helpful for me.
    - huxingyi 10y ago
      libui is a nice work, thank you for this information. But no, It's hard to unify the behavior of desktop and mobile app. And I want keep libphone native, jut use or extend the native ui elements, and simple, and easy to integrate other Java or Object-C modules into it.
    - biokoda 10y ago
      I would not limit it to DEBUG. Lots of apps have separate layouts for tablets. Tablet views while not ideal, can work as desktop apps.
      - huxingyi 10y ago
        Yes, you are right, tablet views can work as desktop apps. But if I am not misunderstood, the tablet view and mobile view share the same native ui apis. Maybe there is no need to implement another backend for tablet seperatly in the library?
        biokoda 10y ago
        There is no need to implement anything for the tablet. But to make the tablet view work on the desktop you need a desktop backend, which is what libui could be.
        huxingyi 10y ago
        Understand, that make sense. Maybe there will be a huge work to do, because the mobile ui elements and the desktop ui elements are not matched mostly.

biokoda 10y ago

so this is a GUI library for iOS/Android?

huxingyi 10y ago
Yes, and not just GUI, there are also other fundamental apis provided like timer, work queue.
- biokoda 10y ago
  Have you thought about integrating with https://github.com/andlabs/libui https://github.com/andlabs/libui edit: What about maybe as an optional backend? That way one could develop on a desktop easier.
  - huxingyi 10y ago
    It's turely an optional backend for just DEBUG purpose, like preview layout on desktop. I'll think about it, thank you. Welcome to post more ideas. It' realy helpful for me.
  - huxingyi 10y ago
    libui is a nice work, thank you for this information. But no, It's hard to unify the behavior of desktop and mobile app. And I want keep libphone native, jut use or extend the native ui elements, and simple, and easy to integrate other Java or Object-C modules into it.
  - biokoda 10y ago
    I would not limit it to DEBUG. Lots of apps have separate layouts for tablets. Tablet views while not ideal, can work as desktop apps.
    - huxingyi 10y ago
      Yes, you are right, tablet views can work as desktop apps. But if I am not misunderstood, the tablet view and mobile view share the same native ui apis. Maybe there is no need to implement another backend for tablet seperatly in the library?
      - biokoda 10y ago
        There is no need to implement anything for the tablet. But to make the tablet view work on the desktop you need a desktop backend, which is what libui could be.
        huxingyi 10y ago
        Understand, that make sense. Maybe there will be a huge work to do, because the mobile ui elements and the desktop ui elements are not matched mostly.