From dfb87398c72e9248aa709ae212e6ab7f2209003d Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Thu, 5 Mar 2015 20:59:01 -0600 Subject: Automated update from Qt3 --- doc/qtmac-as-native.doc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'doc/qtmac-as-native.doc') diff --git a/doc/qtmac-as-native.doc b/doc/qtmac-as-native.doc index 831250307..5b1490926 100644 --- a/doc/qtmac-as-native.doc +++ b/doc/qtmac-as-native.doc @@ -4,7 +4,7 @@ ** ** Copyright (C) 2002-2008 Trolltech ASA. All rights reserved. ** -** This file is part of the Qt GUI Toolkit. +** This file is part of the TQt GUI Toolkit. ** ** This file may be used under the terms of the GNU General ** Public License versions 2.0 or 3.0 as published by the Free @@ -13,7 +13,7 @@ ** Alternatively you may (at your option) use any later version ** of the GNU General Public License if such license has been ** publicly approved by Trolltech ASA (or its successors, if any) -** and the KDE Free Qt Foundation. +** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General ** Public Licensing requirements will be met: @@ -91,8 +91,8 @@ it can interact with specific components of the Mac OS X experience: This is a bit more subjective, but certainly Qt/Mac strives to provide the same feel as any Mac OS X application (and we consider situations where it doesn't achieve this to be bugs). - Of course Qt has other concerns to bear in mind, especially - remaining multiplatform. Some "baggage" that Qt carries is in + Of course TQt has other concerns to bear in mind, especially + remaining multiplatform. Some "baggage" that TQt carries is in an effort to provide a widget on a platform for which an equivelant doesn't exist, or so that a single API can be used to do something, even if the API doesn't make entire sense for a @@ -128,11 +128,11 @@ it can interact with specific components of the Mac OS X experience: \i Accessiblity
Although many users never use this, some users will only interact - with your applications via assistive devices. With Qt the aim is to + with your applications via assistive devices. With TQt the aim is to make this automatic in your application so that it conforms to accepted practice on its platform (X11 accessiblity support is still in the works due to the developing nature of its - accessibility design). With Qt 3.3 Qt/Mac will support + accessibility design). With TQt 3.3 Qt/Mac will support accessiblity, and hopefully a host of assistive devices. \i Build tools
@@ -152,7 +152,7 @@ it can interact with specific components of the Mac OS X experience: and uic) since qmake automatically handles them and ensures that everything necessary is linked into your application. - Qt does not entirely interact with the development environment (for + TQt does not entirely interact with the development environment (for example plugins to set a file to 'mocable' from within the Xcode user interface). Trolltech is actively working on improving Qt's interoperability with various IDEs, so hopefully this will be -- cgit v1.2.1