5 ms·

Just build with --without-java

bobajeff 11y ago
Thanks, now the only question is how hard will it be to use my own UI framework instead of VCL (to avoid complexity and overhead)?
- TD-Linux 11y ago
  I feel like if you have to ask this question, the answer is "too hard".
  - bobajeff 11y ago
    Because building a frontend and other missing components from scratch is hard or because the backend is tied too closely with VCL?
    - TD-Linux 11y ago
      Just because writing a whole new GUI would be a huge undertaking. I mean, if you need to do it, don't let me stop you. But I don't think it makes sense if your goal is simply "lighter weight" (I don't even know what that means exactly)
      - bobajeff 11y ago
        I might not need to. I just have a feeling that layering my existing framework over VCL would mean a lot of redundant and unoptimized things happening during runtime. I basically just want LibreOffice for it's mature support for Microsoft Office files. I think if I can just have that as a standalone library that would be ideal.
        icebraining 11y ago
        Microsoft has released an SDK for reading and writing Office files, under the Apache 2 license: https://github.com/OfficeDev/Open-Xml-Sdk https://github.com/OfficeDev/Open-Xml-Sdk It's in C#, but it builds on Mono, and it's probably still easier than hacking LO to act as a library.
        bobajeff 11y ago
        That might be better for compatibility. Except the mono/coreclr runtime requirement adds a bit of complexity. I'd have to port and optimize that as well as call into and from C# code. So for right now it's just not a good solution. Also, I'm not sure if it can be used to open all MS Office files or just Office 2007+ or any files for that matter.
- khaled 11y ago
  Look at the LibreOfficeKit API and the sample gtktiledviwer application, very easy to use (that the base of the Android and LibreOffice Online application), now all you need is writing the actual UI…
  - bobajeff 11y ago
    Thanks, that looks like it was made for what I'm wanting to do.

Thanks, now the only question is how hard will it be to use my own UI framework instead of VCL (to avoid complexity and overhead)?

TD-Linux 11y ago
I feel like if you have to ask this question, the answer is "too hard".
- bobajeff 11y ago
  Because building a frontend and other missing components from scratch is hard or because the backend is tied too closely with VCL?
  - TD-Linux 11y ago
    Just because writing a whole new GUI would be a huge undertaking. I mean, if you need to do it, don't let me stop you. But I don't think it makes sense if your goal is simply "lighter weight" (I don't even know what that means exactly)
    - bobajeff 11y ago
      I might not need to. I just have a feeling that layering my existing framework over VCL would mean a lot of redundant and unoptimized things happening during runtime. I basically just want LibreOffice for it's mature support for Microsoft Office files. I think if I can just have that as a standalone library that would be ideal.
      - icebraining 11y ago
        Microsoft has released an SDK for reading and writing Office files, under the Apache 2 license: https://github.com/OfficeDev/Open-Xml-Sdk https://github.com/OfficeDev/Open-Xml-Sdk It's in C#, but it builds on Mono, and it's probably still easier than hacking LO to act as a library.
        bobajeff 11y ago
        That might be better for compatibility. Except the mono/coreclr runtime requirement adds a bit of complexity. I'd have to port and optimize that as well as call into and from C# code. So for right now it's just not a good solution. Also, I'm not sure if it can be used to open all MS Office files or just Office 2007+ or any files for that matter.
khaled 11y ago
Look at the LibreOfficeKit API and the sample gtktiledviwer application, very easy to use (that the base of the Android and LibreOffice Online application), now all you need is writing the actual UI…
- bobajeff 11y ago
  Thanks, that looks like it was made for what I'm wanting to do.