[Bug 163664] implement support for Apple Intelligence Writing Tools
https://bugs.documentfoundation.org/show_bug.cgi?id=163664 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||103303 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103303 [Bug 103303] [META] Desktop integration bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 163664] implement support for Apple Intelligence Writing Tools
https://bugs.documentfoundation.org/show_bug.cgi?id=163664 --- Comment #9 from Patrick (volunteer) --- Unfortunately LibreOffice has its own custom C++ layout engine and each NSWindow only has a single, customize NSView subclass that the LibreOffice code uses as a drawing canvas so we can't seamlessly integrate Apple Intelligence in its current form directly into Writer. I searched around for any non-GUI APIs like -[NSSpellChecker checkGrammarOfString:...] that we could send a chunk of text to and it would return some modified (or not) text but I didn't find anything that looked remotely promising. So, for now, I appears that Apple Intelligence is embedded within NSTextView on macOS. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 163664] implement support for Apple Intelligence Writing Tools
https://bugs.documentfoundation.org/show_bug.cgi?id=163664 --- Comment #8 from Patrick (volunteer) --- Created attachment 197557 --> https://bugs.documentfoundation.org/attachment.cgi?id=197557&action=edit Xcode project to build native window in attachment #197556 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 163664] implement support for Apple Intelligence Writing Tools
https://bugs.documentfoundation.org/show_bug.cgi?id=163664 --- Comment #7 from Patrick (volunteer) --- Created attachment 197556 --> https://bugs.documentfoundation.org/attachment.cgi?id=197556&action=edit Design concept of native AI window floating above LibreOffice Writer -- You are receiving this mail because: You are the assignee for the bug.
[Bug 163664] implement support for Apple Intelligence Writing Tools
https://bugs.documentfoundation.org/show_bug.cgi?id=163664 steve changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #6 from steve --- Setting to NEW as per comment 4 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 163664] implement support for Apple Intelligence Writing Tools
https://bugs.documentfoundation.org/show_bug.cgi?id=163664 --- Comment #5 from steve --- This feature is opt-in to begin with, as Apple Intelligence is opt-in. And when a user opts-in, they certainly will be happy to see support in LO should this happen. Since this only ever gets used, when users a) opted into Apple Intelligence on a system level and b) actively use one of the Writing Tools option, I am not sure an additional opt-in setting in LO would be needed or provide any use. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 163664] implement support for Apple Intelligence Writing Tools
https://bugs.documentfoundation.org/show_bug.cgi?id=163664 --- Comment #4 from Kush Srivastava --- Disclaimer: I am an assoc. member for the FSF, and genuinely believe in libre software. I am also new to understanding more on how Libreoffice works, but I have been a long time user (since 2015, at least), and use it on all my platforms (Alpine, Windows, and Mac). I am also new to contributing here. I second this bug, and the opinion that Apple Intelligence features should be implemented (which really just require Libreoffice to implement view windows that can be detected by the system). I do not know how feasible this is with Libreoffice, given that it uses it's own rendering engine, but having the feature available will be very beneficial to the vast majority of people wanting to use Libre software suites on Mac. On top of the comments mentioned above: * All writing tools on Apple Intelligence are on-device, and private. You get an option for when you want to send data to Apple's servers, but even then, this is the best server implementation I have seen. Refer to (https://security.apple.com/blog/private-cloud-compute/), where it can be seen that data is private, removed, and the servers themselves have zero privileged access or a shell. Also the server architecture and code is open to all for research purposes. (https://security.apple.com/blog/pcc-security-research/) * Writing tools do not explicitly need to be "implemented" in Libreoffice. As long as we're using a native way of rendering text, or making sure the system can detect text in our rendering engine. Clearly, there are steps taken from Apple to actually showcase that data is not stored/mined, users explicitly send data to the server if needed (and only for complex tasks like image generation), and writing tools are 100% locally run and stored, with their back-end open for scrutiny...I would love to see why this may not be viable. Especially, if it is something regarding how LibreOffice renders the UI, or how it runs on the Mac. I also believe that if we were to go down this route, a good option would be to have this be an opt in feature, instead of opt out. Open to hearing new thoughts on this matter. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 163664] implement support for Apple Intelligence Writing Tools
https://bugs.documentfoundation.org/show_bug.cgi?id=163664 --- Comment #3 from steve --- Hi Eyal, can you elaborate how you come to your conclusions? * Non-free, closed-source software Well, just like Apple Intelligence, macOS itself is closed source right, and yet LibreOffice runs on it. Integrating with Writing Tools is a matter of supporting * Sending your personal content to Apple, where it is stored, analyzed, mined etc. Again, what brings you to this conclusion? Can you share more resources about this? From what I understand most operations are done on device. I believe this is especially true for writing tools (https://support.apple.com/en-lk/guide/mac-help/mchlfc0d4779/15.0/mac/15.0). Apple Intelligence is optional and users who enable it, obviously want to make use of it. I don't understand the argument to not support it in LibreOffice, just because you personally don't like it. Why not leave the decision to users whether they want to use it or not? And adding support in LibreOffice adds obvious value and helps keep LibreOffice an attractive choice as a writing tool on macOS. 3:50 of the linked video explains how Writing Tools are integrated in third-party apps. Making it work is a matter of using UITextView, NSTextView WKWebView. I am not sure if this is possible in LibreOffice writer. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 163664] implement support for Apple Intelligence Writing Tools
https://bugs.documentfoundation.org/show_bug.cgi?id=163664 --- Comment #2 from Eyal Rozenberg --- (In reply to steve from comment #0) > It would be very useful and welcome to add support for Apple Intelligence > Writing Tools in LibreOffice Writer. I don't think it will. Correct me if I'm wrong, but this involves: * Non-free, closed-source software * Sending your personal content to Apple, where it is stored, analyzed, mined etc. assuming that is the case - is not welcome, and its usefulness is far outweighed by the detriment in using it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 163664] implement support for Apple Intelligence Writing Tools
https://bugs.documentfoundation.org/show_bug.cgi?id=163664 --- Comment #1 from steve --- Created attachment 197286 --> https://bugs.documentfoundation.org/attachment.cgi?id=197286&action=edit Apple Intelligence Writing Tools -- You are receiving this mail because: You are the assignee for the bug.
[Bug 163664] implement support for Apple Intelligence Writing Tools
https://bugs.documentfoundation.org/show_bug.cgi?id=163664 steve changed: What|Removed |Added URL||https://developer.apple.com ||/videos/play/wwdc2024/10168 ||/ -- You are receiving this mail because: You are the assignee for the bug.
