Re: [tdf-discuss] macro compatibility between LO and AOO?
I know that there were reasons for the fork and I respect that. I was wondering if libreoffice and aooo can't agree to some basic level api for 3rd party developers? Probably not, but I think it's worth asking. Fred On Tue, Mar 5, 2013 at 8:28 AM, Keith Curtis keit...@gmail.com wrote: On Mon, Mar 4, 2013 at 1:46 AM, Fernand Vanrie s...@pmgroup.be wrote: On 4/03/2013 8:27, M. Fioretti wrote: On Mon, Mar 04, 2013 08:16:25 AM +0100, Fernand Vanrie wrote: 99% percent , changes comes and will come from incompatiliteis in de API. for now this is OK, small changes from version to version, but nothing who not can been repaired or handled with the code( basic) itself I knew that. The sense of my question is, is there is a list of things to avoid beforehand, rather than wait that they break and fix the code? thats more a question for the developers list . libreoff...@lists.freedesktop.org and fore the aOO counterpart ooo-...@incubator.apache.org Thanks, Marco The reason why nobody responded is no one knows, and it will generally get worse over time as the codebases diverge. It is sort of like the Java: write once, test everywhere situation. One of the unintended consequences of the fork is the various ways it makes things more difficult for third-parties. Users will generally pick one product, but extension developers have a more complicated set of choices because they may want to support multiple brands. Here is an article I recently wrote about the power of brands that may be helpful: http://keithcu.com/wordpress/?p=3163 The good news is that in the free software world, code flows with less friction. Any typical (non-enterprise) who really wants an extension will likely be able to install a specific version of the product if it is required. It is just a download. Good luck! Regards, -Keith - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [tdf-discuss] macro compatibility between LO and AOO?
Hi guys, On Tue, 2013-03-05 at 09:19 -0800, Fred Ollinger wrote: I was wondering if libreoffice and aooo can't agree to some basic level api for 3rd party developers? It's an interesting discussion; but in the absence of any concrete code, patches etc. it doesn't belong on the libreoffice developer list; please drop that one from the CC. Thanks, Michael. -- michael.me...@suse.com , Pseudo Engineer, itinerant idiot -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [tdf-discuss] macro compatibility between LO and AOO?
On 03/06/2013 09:00 AM, Andre Fischer wrote: On 05.03.2013 18:29, Michael Meeks wrote: On Tue, 2013-03-05 at 09:19 -0800, Fred Ollinger wrote: I was wondering if libreoffice and aooo can't agree to some basic level api for 3rd party developers? It's an interesting discussion; but in the absence of any concrete code, patches etc. it doesn't belong on the libreoffice developer list; Talking about a concrete change is a good idea so please let me ask a question similar to one I asked at FOSDEM but to which I got no clear answer. Probably because of my bad English that is even worse when I speak it. Stephan Bergman talked about Well-typed UNO, something that would involve incompatible changes to the UNO API. I would like to know if LibreOffice and Apache OpenOffice could work together on this. I am just talking about changes on API level not the underlying implementation. That would be something that both projects would do independently. First off, depends on what you mean with UNO API. One customary meaning is the set of UNOIDL entities (mainly) declared in udkapi/ and offapi/ .idl files. (LibreOffice tries to meticulously track any incompatible changes it does there, see e.g., the API Changes section at http://www.libreoffice.org/download/4-0-new-features-and-fixes/.) Another customary meaning is the broader concept of stable interface the URE offers, including C ABI, file formats, wire protocols, etc. My hope is that my work on changing the type representation does not affect the former, only the latter (file formats etc.). And, obviously, it will need to take care of a backward-compatibility plan. That said, I can only repeat now what I already said at FOSDEM, that I'm going to well document all the changes to any specifications---just like I did for any other changes to UNO I did over the last ten years or so. And, as always, any input is highly welcome. Stephan -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [tdf-discuss] macro compatibility between LO and AOO?
On Mon, Mar 4, 2013 at 1:46 AM, Fernand Vanrie s...@pmgroup.be wrote: On 4/03/2013 8:27, M. Fioretti wrote: On Mon, Mar 04, 2013 08:16:25 AM +0100, Fernand Vanrie wrote: 99% percent , changes comes and will come from incompatiliteis in de API. for now this is OK, small changes from version to version, but nothing who not can been repaired or handled with the code( basic) itself I knew that. The sense of my question is, is there is a list of things to avoid beforehand, rather than wait that they break and fix the code? thats more a question for the developers list . libreoff...@lists.freedesktop.org and fore the aOO counterpart ooo-...@incubator.apache.org Thanks, Marco The reason why nobody responded is no one knows, and it will generally get worse over time as the codebases diverge. It is sort of like the Java: write once, test everywhere situation. One of the unintended consequences of the fork is the various ways it makes things more difficult for third-parties. Users will generally pick one product, but extension developers have a more complicated set of choices because they may want to support multiple brands. Here is an article I recently wrote about the power of brands that may be helpful: http://keithcu.com/wordpress/?p=3163 The good news is that in the free software world, code flows with less friction. Any typical (non-enterprise) who really wants an extension will likely be able to install a specific version of the product if it is required. It is just a download. Good luck! Regards, -Keith -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [tdf-discuss] macro compatibility between LO and AOO?
On 4/03/2013 8:27, M. Fioretti wrote: On Mon, Mar 04, 2013 08:16:25 AM +0100, Fernand Vanrie wrote: 99% percent , changes comes and will come from incompatiliteis in de API. for now this is OK, small changes from version to version, but nothing who not can been repaired or handled with the code( basic) itself I knew that. The sense of my question is, is there is a list of things to avoid beforehand, rather than wait that they break and fix the code? thats more a question for the developers list . libreoff...@lists.freedesktop.org and fore the aOO counterpart ooo-...@incubator.apache.org Thanks, Marco -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
[tdf-discuss] macro compatibility between LO and AOO?
(sorry if this comes in twice, my email server had problems earlier today)Reply-To: M. Fioretti mfiore...@nexaima.net Greetings, the subject says it all. I have already searched online, and am looking at the manual but apparently (maybe I used the wrong terms) it is not easy to find CURRENT information on macro compatibility between LO 4 and AOO 3.4.1: will all macros created in one tool also work in the other? If not, why and when? What are the reasons/cases when a macro is not portable? are there any guidelines/best practices to write portable macros? Thanks in advance for any pointer! Marco http://mfioretti.com -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [tdf-discuss] macro compatibility between LO and AOO?
Op 04/03/2013 07:53, M. Fioretti schreef: (sorry if this comes in twice, my email server had problems earlier today)Reply-To: M. Fioretti mfiore...@nexaima.net Greetings, the subject says it all. I have already searched online, and am looking at the manual but apparently (maybe I used the wrong terms) it is not easy to find CURRENT information on macro compatibility between LO 4 and AOO 3.4.1: will all macros created in one tool also work in the other? 99% percent , changes comes and will come from incompatiliteis in de API. for now this is OK, small changes from version to version, but nothing who not can been repaired or handled with the code( basic) itself If not, why and when? What are the reasons/cases when a macro is not portable? are there any guidelines/best practices to write portable macros? Thanks in advance for any pointer! Marco http://mfioretti.com -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [tdf-discuss] macro compatibility between LO and AOO?
On Mon, Mar 04, 2013 08:16:25 AM +0100, Fernand Vanrie wrote: 99% percent , changes comes and will come from incompatiliteis in de API. for now this is OK, small changes from version to version, but nothing who not can been repaired or handled with the code( basic) itself I knew that. The sense of my question is, is there is a list of things to avoid beforehand, rather than wait that they break and fix the code? Thanks, Marco -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
