Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Hi :)
Apparently there is a problem using MS Office macros in different
versions of MS Office itself.  So a macro 'written' for MS Office 2007
might not work very well in MS Office 2010 or 2013.  Let alone going
backwards to try using the macro on an earlier version of MS Office!!

So moving from 1 version of MS Office to another might well involve a
bit of macro re-writing (or 'just' editing if you are lucky) but then
will probably need re-re-writing the next time you move to another
version of MS Office.

By contrast moving to LibreOffice / OpenOffice means re-writing just
the once.  The macro will then work on pretty much any version of LO
and AOO even if you go back to earlier versions of either.

Also LO and AOO allow for a few other languages to be used so you
don't have to stick to Basic.  I think Java is possible but obviously
worth avoiding these days.  I'm fairly sure C++ is not an option for
macros.  So Python is probably the best option if it's possible.


LO and AOO make it easier to write Add-ons / Plugins which we call
"Extensions" these can be kept secret within your company or
published, preferably using an Open Source license such as GPL, LGPL
or MPL.  Publishing them to the LibreOffice website means other people
may well try it out and may be able to point out bugs or problems = so
you get a lot more testing for free.  If you Open Source'd it then you
might find some other people help to fix things or update things for
free.


I've never heard of OpenOffice or LibreOffice macros being used as an
attack vector so maybe MS Office should copy our way of handling
macros!
Regards from
Tom :)





On 10 February 2015 at 06:37, jonathon <toki.kantoor@gmail.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/02/15 18:44, Thisis theone wrote:

When will LibreOffice have 100% MS macro and function support?

Given that LibO currently has support for half a dozen programming
languages that can be used to write extensions, I doubt it will ever be
implemented.

_IF_ good coding practices were adhered to, when the macro was written,
and updated, then rewriting them in a language that LibO supports is
trivial.

OTOH, assuming the code is like 99.9999% of the code found in MSO
macros, it not only is undocumented, but a mess of spaghetti, of the
type that Richard Conway condemned back in 1978.

In the latter instance, the only migration path is to start with the
requirements, as _currently_ used, and go from there.

jonathon

  * English - detected
  * English

  * English

 <javascript:void(0);>
the original macro requirements, and work from there.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJU2acuAAoJEKG7hs8nSMR7lUIP/j+6ROzlPdUxgvgTHfosWMEx
19sMogHSaJwlmwF5tyoju35QNJIWIqC7r8mYzhLC7deZ65b+U5JuNEiBtz/EkBB/
gDwjRJzGqHV+CWaxG8BaeOgqscK5zzkM4fEV+s6ORvlSLLnw725tLginxr7UZo/z
QYWe6YMIAfp+AagG7CSPqRCiPfbG2RY4cKr68EtXk+vDdQ0qjFjT4YzSghuIn4fK
pr+Y+H87raoiQPVdutWc+MgFxwat/obgM8bSV0HZjEoixwgBTsz4e/qPw0tcOjw3
q4vyEPRYYx5lw8HivHKtUWMAF0xSTP47n8LTieJARqmFRxzao8d2x69JVdNRpmb4
a04BuNSpz3DmWUm6BfLQ3FkTz+SzBuI9n6/Ttf/93deWOSD6hfpOp1aN5ta0DJBG
0AIQ4sbYqmRBgDAspjBS9ItOOtywcKJRI6HVQP/Tmq+eF/D8FmxVDGswuYBW9jBs
MLDTpIYyrqZJRAsZbHZhmoJfVnA+pjc4w9vM2ZrVH4pSWtQ5JT7oiiTKCB2vN0rm
D2WjrUDS5NdCwiubfNruLlDCOPeOOHANdH2WMA+UtbFiaWzYbzFLNbmLwvOTyFZx
kxIkX+koK+1kCjRHvL21wIsJcNlfJZaYv7cD8KsWF3wmZzjGiA7I6VoSKOjW4X+0
WtSD9QLOU+pwEiMLYbe0
=g6Ss
-----END PGP SIGNATURE-----

--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.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.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.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.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.