Hello,
I'm working with Sophie Gautier on implementing the Open Badges system
in our community: https://openbadges.org
In short, it lets us recognise achievements of community members, by
issuing badges when certain targets are reached (eg after a certain
number of code commits, or updates to
I lead several LO migration in small and big corporations in my
professional life. Macros is a symptom of IT default with respect of
the company business.
As life goes on anyway, support for VBA in LO is partial and solves a
lot of (very) simple situations(*). LO object model uniqueness is to
Well, it already has the same or better functionality with open source
solutions so it's already way cooler in that regard. Now it just needs to
support VBA so that more orgs will migrate to it and notice that it's way
cooler. :)
On Tue, Feb 12, 2019 at 10:09 AM kainz.a wrote:
> maybe it's
maybe it's true, but I would prefer to have first level support for open
source solutions instead of look that LibO is compatible with MSO macros.
Have the same (or better) functionality with open source solutions would be
way cooler (maybe in cooperation with LOOL and Cloud storage.
Am Di., 12.
These are the types of compatibility issues that really cripple LO
adoption, even moreso than full file format compatibility.
On Tue, Feb 12, 2019 at 9:57 AM Pedro Rosmaninho
wrote:
> Well adding support for VBA would be nice, since it's not developed by
> Microsoft anymore but they wont
Well adding support for VBA would be nice, since it's not developed by
Microsoft anymore but they wont remove.
So why not add support for it, even without removing LO's implementation?
On Mon, Feb 11, 2019 at 11:35 AM Olivier Hallot <
olivier.hal...@libreoffice.org> wrote:
> Hi Franklin
>
> Em
