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


Jay,

Yes, user confusion and frustrated expectations do seem to be risks.

I think the bigger problem will be with Windows RT systems, where Windows 7/8 and earlier desktop 
applications do not run at all.  

On Windows 8 systems, having both MX applications and desktop applications may or may not be a 
difficulty for users.  We'll have to see.  

Software producers that have both a desktop and an MX version will need to be careful about how 
things work when both are installed on a Windows 8 machine.  There are already examples of that 
with Internet Explorer, OneNote, Skype, SkyDrive, and Netflix.  That's something to think about for 
LibreOffice too.

 - Dennis

-----Original Message-----
From: Jay Lozier [mailto:jslozier@gmail.com] 
Sent: Friday, December 14, 2012 13:59
To: dennis.hamilton@acm.org
Cc: users@global.libreoffice.org
Subject: Re: Windows 8 Compatibility (was RE: [libreoffice-users] Re: 0xc0000005 error in 
RPCRT4.dll from soffice.bin)

On 12/14/2012 04:39 PM, Dennis E. Hamilton wrote:
Jay, I agree.

There are two kinds of compatibility for Windows 8.

First, desktop compatibility is essentially the same as for Windows 7.  There is more room for 
gradual upgrade to integrate more smoothly, including on x64 machines with Atom processors, 
solid-state drives, and storage in the cloud.  I think UX features will also adjust and improve, 
but that will be relatively gradual.

The second kind of compatibility is determined by whether or not an application is distributed 
via the Windows Store.  As far as I know, that's reserved for MX applications that run on either 
Windows 8 or Windows RT.  I also believe that is the only way a consumer can obtain MX 
applications that they didn't write themselves.  (There are apparently ways for Enterprises to 
create something like their own stores.)

So yes, there are two levels of capability.  The productivity software such as LibreOffice is 
going to be running on the desktop for a long time.  There is a great deal to figure out to see 
how to deploy on MX successfully.  In a way, the same issues arise for Android and iOS as targets 
for the desktop productivity software that we've been relying upon.

  - Dennis
Dennis,

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.

Jay
[ ... ]


-- 
For unsubscribe instructions e-mail to: users+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/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.