Hi :)
Getting "out there" first does count for a lot but it's not the final answer.
The advantages do lead to the idea of "release early and release
often". AndrOO might not be great right now but at least it is "out
there" and attracting attention. As a result it might "snowball" and
become better faster and faster as it attracts an increasing
community. On the other hand initial reputation counts for a lot too
so the TDF approach is smart but all the smarter because AndrOO is out
there. Without AndrOO the DTF approach would suffer the usual
problems of perfectionism.
Kingsoft Office is attracting a lot of attention but it's proprietary
and therefore limited. If they could OpenSource it then it might last
but at the moment it looks like it's only good for the short-term
until MS squish it. Having a ribbon-bar is a huge pull. If only we
had an Extension that gave users one! As an Extension people wouldn't
have to use it and it wouldn't be the default. Many of us still kinda
hate the ribbon but having it as an option would be smart.
I've also heard that the hand-helds version of MSO is just a viewer
(that doesn't always work anyway (MS having trouble implementing their
own 'interoperable' format. Again)). So it's classic trialware and
likely to follow desktop MSO into being ransomware. MS do need to
regain the market-share they have lost to hand-helds and free viewer
trialware is the standard approach. it usually seems to work for MS.
It didn't work for Oracle when they tried it with OO but they had
other factors to deal with.
As for Cloud versions there is already Google-docs but apparently the
various portable apps versions of LO could also be installed to a
Cloud and used anywhere.
Really i was just hoping that a few people here could cast their vote
on the ZdNet article and support one of the few people in ZdNet that
supports OpenSource despite that constantly leading to him earning
less from his articles than the Windows fanboys earn from theirs.
Regards from
Tom :)
On 2 April 2014 12:08, Italo Vignoli <italo.vignoli@gmail.com> wrote:
On 02/04/14 05:20, Pedro wrote:
Have you tested it? Are your findings different from their claims?
It is clearly stated in the relevant iTunes pages.
Requirements: a qualifying Office 365 subscription is required to edit
and create Word documents. If you do not have a subscription, you can
buy Office 365 Home withing Word for Ipad app.
--
Italo Vignoli - italo.vignoli@gmail.com
mob IT +39.348.5653829 - mob EU +39.392.7481795
sip italo@libreoffice.org - skype italovignoli
GPG Key ID - 0xAAB8D5C0
DB75 1534 3FD0 EA5F 56B5 FDA6 DE82 934C AAB8 D5C0
--
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
Re: [libreoffice-users] Re: MSO for iPad, big deal or big yawn · Toki
Re: [libreoffice-users] MSO for iPad, big deal or big yawn · Jean-Francois Nifenecker
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.