[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[libreoffice-documentation] Fwd: [libreoffice-marketing] Libo discussion group on LinkedIn
[Thread Prev] | [Thread Next]
- Subject: [libreoffice-documentation] Fwd: [libreoffice-marketing] Libo discussion group on LinkedIn
- From: Jean Weber <jeanweber@gmail.com>
- Date: Sat, 28 Jul 2012 14:40:34 -0700
- To: documentation@global.libreoffice.org, Andrew Pitonyak <andrew@pitonyak.org>
Andrew, any comment or suggestions? --Jean
Begin forwarded message:
> From: Kostas Mousafiris <kvisitor@gnugr.org>
> Date: 28 July 2012 11:11:06 PDT
> To: marketing@global.libreoffice.org
> Subject: [libreoffice-marketing] Libo discussion group on LinkedIn
> Reply-To: marketing@global.libreoffice.org
>
>
> Hi everyone!
> I intercepted the following winging about some LibreOffice feature., in
> a LinkedIn discussion group
> I am not sure if this is the appropriate list
> and I also think that it may well be a known issue,
> but I would like to report it all the same, in the hope that something
> can be done:
>
>>
>> LO macro recorder.
>>
>> In LibreOffice, the macro recorder is even worse than in OpenOffice.
>> Compared with Ms Office, OO's one it is a little hell for "simple
>> users", but LO's is just impossible.
>>
>> As a trainer, I had to face my disappointed trainee's after their
>> company has changed from OO to LO.
>>
>> Does anyone has an experience or comment about that?
>>
>> 22 days ago
>> ✔ Jan V.
>> <http://www.linkedin.com/groups?viewMemberFeed=&gid=3718834&memberID=126096217&goback=%2Egde_3718834_member_131211305>
>> likes this
>>
>> 1 comment
>>
>> ✔ Jan V.
>> <http://www.linkedin.com/profile/view?id=126096217&goback=%2Egde_3718834_member_131211305>
>>
>>
>> ✔ Jan
>>
>> ✔ Jan V.
>> <http://www.linkedin.com/groups?viewMemberFeed=&gid=3718834&memberID=126096217>
>> • I do fully agree - I've been using OO since version 1.0. And have
>> former been developing in MSO 95,97 and 2000. The Experience of the
>> API in MSO was a mixture of frustration over incompatibility between
>> versions and a clear picture of the object model. I think that the
>> OOo/LO API lacks clarity and the Macro is even worse. "ooo macro
>> programming by andrew pitonyak" gives, I think, the best
>> dokumentation. :o)
>>
>
>
> --
> Unsubscribe instructions: E-mail to marketing+help@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/marketing/
> All messages sent to this list will be publicly archived and cannot be deleted
--
Unsubscribe instructions: E-mail to documentation+help@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/documentation/
All messages sent to this list will be publicly archived and cannot be deleted
| Re: [libreoffice-documentation] Fwd: [libreoffice-marketing] Libo discussion group on LinkedIn | Andrew Douglas Pitonyak <andrew@pitonyak.org> |
- Prev by Date: [libreoffice-documentation] Help needed to update Getting Started guide for v3.5 & v3.6
- Next by Date: [libreoffice-documentation] Small writing job seeks writer
- Previous by thread: [libreoffice-documentation] Help needed to update Getting Started guide for v3.5 & v3.6
- Next by thread: Re: [libreoffice-documentation] Fwd: [libreoffice-marketing] Libo discussion group on LinkedIn
- Index(es):
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 GNU Lesser General Public License (LGPLv3). "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.