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

On 12/15/2012 01:20 AM, ubuysa wrote:
Jay Lozier wrote

The problem then is properly explaining to Win8 users what they should
expect in terms of compatibility. But even so, I fear a large number of
users will not either pay attention to the vendor statements or be
confused by the MS advertising and believe that all software will work
with the new UI like the advertised apps. It probably will be a lesser
problem with FOSS projects because a higher portion of the user base is
more technically astute. If we are having this discussion then the
majority of users will be confused by this issue. The scenario, IMHO, is
who will the user blame
: MS or the software vendor?

IMHO, I think the compatibility definition is caused by MS being
schizophrenic with the OS and trying to make work on tablets/phones and
desktops the same way.

FWIW it wasn't my intention to blame anybody. I had hoped I might be helping
by highlighting what appears to me to be a minor issue with LO3.6 and
Windows 8? I like to think I am more technically astute that the norm,
although now retired I spent over 30 years as a sysprog working with large
IBM mainframe operating systems.

I'm running Windows 8 only because the upgrade price was too good to miss,
other wise I'd have stayed with 7. I'm not using TIFKAM at all (sorry,
TIFKAM - The Interface Formerly Known As Metro) I'm a pure desktop user. I
suspect the vast majority of current Windows 8 users are pretty similar.

I also agree that MS is trying to face two ways at once with Windows 8, the
clunky integration of the desktop into TIFKAM looks to me like a product
rushed to market to prevent MS getting left behind in the rush to tablets.

I appreciate that there will always be a lag on FOSS when the base OS is
upgraded. I asked my original question on here to find out whether this was
a known issue and whether anyone else has seen this (very minor) problem. I
have posted it as a bug though I am still not certain that it's not my
problem after all. My main intention is to help not complain, I'm sorry if
my comment about LO not being Windows 8 ready came across as a complaint.

Thank you all for the help and advice you provide. I wish I were able to
help more but I think my skills are now probably best suited to a museum!
I think you brought a valid issue that needs to be addressed by all software developers and making sure the end users understand how to use the software on Win8. It may be less of an issue for most FOSS projects because of their user base. Where I see a problem is with ordinary users who may be confused by schizophrenic nature of Win8 and what is meant by being compatible with it - there are two some what different definitions. As a Linux user I am not directly affected but I see user questions about Metro/Modern/Whatever integration vs the traditional desktop integration occurring.

As I said early if I am confused then think of the confusion of ordinary users who primarily see advertising and store displays. Given that many will buy a new computer with Win8 preinstalled and are probably talking to sales staff marginally more knowledgeable than them I see nothing but confusion.

View this message in context:
Sent from the Users mailing list archive at

Jay Lozier

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.