Re: [Development] RFC: QProcess variant or separate class for launching applications "GUI-style"

[Gustavsen Richard]

> True, or no, that'd rather be "/usr/bin/open [-n] -W -a 
> appbundle|bundle-exec". It wouldn't always be trivial to get the invocation 
> just right, as that is a wrapper to LSOpenURLWithRole() whereas we'd probably 
> use something more simple, with less ambiguous specification of the 
> arguments. Besides, we identified a need to know the pid and also to be 
> notified of process termination.

Note that this will also work on OS X (didn't read the other mails, ignore if 
it QDesktopServices has been discussed):
QDesktopServices::openUrl(QUrl("file:///Applications/Safari.app"));

-Richard
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] New Qt 5.6.0 Beta snapshot available

[Gustavsen Richard]

https://codereview.qt-project.org/#/c/140650/



-Richard



Fra: Development  på vegne av Edward Sutton 

Sendt: 12. november 2015 15:24
Til: Heikkinen Jani
Kopi: development@qt-project.org
Emne: Re: [Development] New Qt 5.6.0 Beta snapshot available

I installed Qt 5.6 beta on OS X 10.10.5 with Xcode 7.1.1.  ( I also have Qt 
5.5.1 commercial installed. )

It works fine if I open, build, and run a Qt Example app using Qt Creator 
3.5.82 (3.6.0-rc1).

However when I open an existing Qt project or create a new Qt Widgets 
Application with Qt Creator 3.5.82 (3.6.0-rc1) I get following error:

08:16:48: Running steps for project qt5-6-beta-widgets...
08:16:48: Starting: "/Users/edward3/Qt5.6.0/5.6/clang_64/bin/qmake" 
/Users/edward3/Documents/projects/qt5-6-beta-widgets/qt5-6-beta-widgets.pro -r 
-spec macx-clang CONFIG+=debug CONFIG+=x86_64 CONFIG+=qml_debug
Info: creating stash file 
/Users/edward3/Documents/projects/build-qt5-6-beta-widgets-Desktop_Qt_5_6_0_clang_64bit-Debug/.qmake.stash
dyld: Library not loaded: @rpath/QtCore.framework/Versions/5/QtCore
Referenced from: /Users/edward3/Qt5.6.0/5.6/clang_64/bin/uic
Reason: image not found
sh: line 1: 1965 Trace/BPT trap: 5 /Users/edward3/Qt5.6.0/5.6/clang_64/bin/uic 
-d ../qt5-6-beta-widgets/mainwindow.ui
08:16:49: The process "/Users/edward3/Qt5.6.0/5.6/clang_64/bin/qmake" exited 
normally.
08:16:49: Starting: "/usr/bin/make"
/Users/edward3/Qt5.6.0/5.6/clang_64/bin/uic ../qt5-6-beta-widgets/mainwindow.ui 
-o ui_mainwindow.h
dyld: Library not loaded: @rpath/QtCore.framework/Versions/5/QtCore
Referenced from: /Users/edward3/Qt5.6.0/5.6/clang_64/bin/uic
Reason: image not found
make: *** [ui_mainwindow.h] Trace/BPT trap: 5
08:16:50: The process "/usr/bin/make" exited with code 2.
Error while building/deploying project qt5-6-beta-widgets (kit: Desktop Qt 
5.6.0 clang 64bit)
When executing step "Make"
08:16:50: Elapsed time: 00:01.



-Ed


On Nov 3, 2015, at 6:06 AM, Heikkinen Jani 
mailto:jani.heikki...@theqtcompany.com>> wrote:

Hi all,

We have new Qt 5.6.0 beta snapshot available,

Windows: http://download.qt.io/snapshots/qt/5.6/5.6.0-beta/241/
Linux: http://download.qt.io/snapshots/qt/5.6/5.6.0-beta/265/
Mac: http://download.qt.io/snapshots/qt/5.6/5.6.0-beta/198/
src: http://download.qt.io/snapshots/qt/5.6/5.6.0-beta/latest_src/

Please test these packages carefully and inform me immediately all beta 
blockers which aren't already linked 
inhttps://bugreports.qt.io/browse/QTBUG-47958 .

br,
Jani

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

This email and any files transmitted with it from The Charles Machine Works, 
Inc. are confidential and intended solely for the use of the individual or 
entity to which they are addressed. If you have received this email in error 
please notify the sender. Our company accepts no liability for the contents of 
this email, or for the consequences of any actions taken on the basis of the 
information provided, unless that information is subsequently confirmed in 
writing. Please note that any views or opinions presented in this email are 
solely those of the author and do not necessarily represent those of the 
company. Finally, the recipient should check this email and any attachments for 
the presence of viruses. The company accepts no liability for any damage caused 
by any virus transmitted by this email.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qmlscene from Qt 5.3 results segmentation fault

[Gustavsen Richard]

Fra: development-bounces+richard.gustavsen=digia@qt-project.org 
[development-bounces+richard.gustavsen=digia@qt-project.org] på vegne 
av Thiago Macieira [thiago.macie...@intel.com]
Sendt: 16. juni 2014 21:19
Til: development@qt-project.org
Emne: Re: [Development] Qmlscene from Qt 5.3 results segmentation fault

Em seg 16 jun 2014, às 14:28:36, rpzrpz...@gmail.com escreveu:
> Looks like a standard linux make. (qmake, I know.)
>
> I can just put my IOS/Android dev time on OSX
> (OSX kernel is BSD/linux kernel, so I know configure it will work)

> I have no clue about iOS or Android. I've never developed for them.

./configure -xplatform macx-ios-clang

-Richard
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Project structure for multi-platform mobile devices

[Gustavsen Richard]

When building a static application on iOS, Qt currently scans the project 
folder for all qml files and tries to figure out which imports they use. The 
result is used to copy and link the needed resources into the application.
This means that currently your qml files needs to be inside your application 
folder for it to work (or at least you need to add a dummy qml file there that 
contains all the imports needed).

-Richard



Fra: development-bounces+richard.gustavsen=digia@qt-project.org 
[development-bounces+richard.gustavsen=digia@qt-project.org] på vegne 
av Luca Bonifacio [luca.bonifa...@bbv.ch]
Sendt: 23. april 2014 00:38
Til: development@qt-project.org
Emne: [Development] Project structure for multi-platform mobile devices

Hi everyone

Actually, I’m getting serious problems by setting up a Qt/QML project 
integrating also unit tests for a multi-platform mobile application. The idea 
is to set up a project skeleton for the development of applications, which will 
run on Android and iOS; and at the same time, the unit tests will be executed 
on a continuous integration server.
For that purpose, I initially defined a subdirs project containing two 
projects: one for the application and one for the unit tests.
The HelloWorld application ran without any problems on both platforms. Also the 
unit test written in QML worked fine.

The problems began when I started to write my unit tests for the QML file that 
embeds C++ objects. By running the unit tests on the QML component that uses 
C++ objects, errors are displayed on the console: the C++ objects are not 
found. That makes also sense cause the C++ objects are set in the main.cpp file 
by using setContextProperty on my root context view. To get around to the 
problem I decided to do the following:
1.  Mock the C++ objects in my QML unit tests, and
2.  Add a new unit tests project for the C++ part.

For the first item, unfortunately, I didn’t find any information or example 
about how to mock a C++ object in QML.

For the second item, as I want to test the C++ objects, I decided to split my 
application into two parts. One part includes the application core (everything 
apart the main), which is statically built, instead the second part includes 
just the main functions which links against the application core and executes 
it. In the same way, I’m able to run my unit tests for my C++ objects.

Finally, I get the following project structure:
•   application-corestatic built
•   application-app links against the application-core
•   unit-tests-qml  tests only QML files of application-core
•   unit-tests-qt   links against the application-core and tests only C++ 
objects

The new application runs without problem on Android devices, instead on iOS 
devices I get an error message: module "QtQuick" plugin "qtquick2plugin" not 
found.

Here my questions:
1.  Is it possible to mock C++ objects or others components in QML? If yes, 
how?
2.  Is the structure of my project correct? Or generally, how to structure 
complex projects?

Thank a lot in advance for every kind of helps or suggestions.

Best regards

Luca Bonifacio
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt-iOS: Popover-Like Styled Frames

[Gustavsen Richard]

Hi!
Native menus are on the todo list, but currently not implemented on iOS. You 
can take a look at this example (https://github.com/richardmg/qtdd13_qmlapp) to 
get an idea on how you can make use of native view controllers (like a 
UIPopoverController ) in your app.

-Richard

Fra: development-bounces+richard.gustavsen=digia@qt-project.org 
[development-bounces+richard.gustavsen=digia@qt-project.org] på vegne 
av Robert Iakobashvili [corobe...@gmail.com]
Sendt: 7. april 2014 18:07
To: development@qt-project.org
Emne: [Development] Qt-iOS: Popover-Like Styled Frames

Hi,
There are some icons on the top toolbar of my Qt-application.

I'd like to have dropdown popover-like frames i.e. for fast selection
of some settings or selection of applications to share with, etc
with maximum "nativity" like have most iPad applications.

Is there any way to code it with Qt?

If not, are there any ideas how to make the integration between
QMenu action menu over QMainWindow with Objective-C written Controllers.

Your directions would be very much appreciated.
Thank you in advance!

Regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Errors creation iOS OpenSSL project (Repost)

[Gustavsen Richard]

This bug report contains some extra information: 
https://bugreports.qt-project.org/browse/QTBUG-36891

-Richard


Fra: development-bounces+richard.gustavsen=digia@qt-project.org 
[development-bounces+richard.gustavsen=digia@qt-project.org] på vegne av 
Derek Cole [derek.c...@gmail.com]
Sendt: 21. mars 2014 23:49
To: development@qt-project.org
Emne: [Development] Errors creation iOS OpenSSL project (Repost)

Hello,

I have been trying to enable OpenSSL using my own compiled OpenSSL version 
(different from my system's OpenSSL) in my iOS app.  I have been unable to get 
past an error when I try to build the project:

http://pastebin.com/S73rSp33

The OpenSSL version I built was from here: https://github.com/st3fan/ios-openssl

Afterwards, I created my QtQuick (qtcreator) project iwth the iOS simulator kit.

I added a build environment variable pointing to the /lib folder of that 
OpenSSL compile.

I also added the following in my .pro file


LIBS += -L/Users/derek/software/ios-openssl/lib -lssl -lcrypto

INCLUDEPATH+=/Users/derek/software/ios-openssl/include

QT += network



I am using Mac OSX 10.9, QtCreator 3.01, and Qt 5.2.1


I spoke with  in the freenode #qt channel and he said it was worth 
posting here


because he was unaware of any problem using the QtNetwork modules with  OpenSSL 
on iOS.


Thanks for any help.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Android / IOS

[Gustavsen Richard]

> Most of the day-to-day discussion happens on IRC: Android developers hang out
on #necessitas on freenode, but mainly during European working hours. I'm not
really sure where the iOS developers hang out, but you can find some of them on
#qt-labs, #qt-platforms or #qt-lighthouse :)

#qt-ios

-Richard
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qmake variable for iOS

[Gustavsen Richard]

To shed some more light,
QtCreator has extra logic on top of QMake to let it create different 
shadowbuilds (and different XCode projects with different build settings) for 
device and simulator. The config variables "iphoneos" and "iphonesimulator" is 
set by QtCreator.

But QMake alone does not distinguish between device and simulator. Any XCode 
project that you create with QMake (from QtCreator or from the terminal) will 
always support both simulator and device. This is how XCode works. You switch 
between device and simulator from the scheme menu inside XCode.

-Richard


Fra: development-bounces+richard.gustavsen=digia@qt-project.org 
[development-bounces+richard.gustavsen=digia@qt-project.org] på vegne av 
Shobana Suresh [ssur...@esri.com]
Sendt: 17. februar 2014 04:33
To: Mohamed Fawzi
Cc: development@qt-project.org
Emne: Re: [Development] Qmake variable for iOS

Hi Fawzi,

Thanks for the explanation.
You are right. Though the message is misleading, it appears to work.
I tried the below simple test and it worked as expected.

App1.pro:

ios {

iphonesimulator {

  message("iphonesimulator")

  DEFINES += iphonesimulator

}

iphoneos{

  message("iphoneos")

  DEFINES += iphoneos

}

}


Mainwindow.cpp


void MainWindow::on_pushButton_clicked()

{

QMessageBox msgBox;

#ifdef iphonesimulator

msgBox.setText("Simulator");

#elif defined (iphoneos)

msgBox.setText("Phone");

#endif

msgBox.exec();

}


Thanks

Shobana

From: Mohamed Fawzi mailto:fawzi.moha...@digia.com>>
Date: Sat, 15 Feb 2014 01:36:31 +1100
To: Shobana Suresh mailto:ssur...@esri.com>>
Cc: "development@qt-project.org" 
mailto:development@qt-project.org>>
Subject: Re: [Development] Qmake variable for iOS

Hi,

qmake for ios is a bit strange, in the sense that it treats device and 
simulator as two build  versions.
This is like debug and release, setting it in CONFIG sets the default used in 
Makefile, but it also still generates specific makefiles for each possible 
combination (iphoneos debug/relase,...).
This is a bit unecessary, especially for how it is used in creator (shadow 
build, always setting the default, and always building using the default 
Makefile.
So message is misleading because it is called for each Makefile version.
Thill it should work, have you tried to see?

Fawzi

On 10 Feb 2014, at 01:30, Shobana Suresh 
mailto:ssur...@esri.com>> wrote:


Hello All,

I am trying to find the qmake variable that could be used to differentiate 
between the iPhone simulator and iPhone arm kits.
In my .pro file, I would like to use conditions like

  1.
ios {
  2.
CONFIG += c++11
  3.
iphonesimulator {
  4.
  message("iphonesimulator")
  5.
  #Do Something
  6.
}
  7.
iphoneos{
  8.
  message("iphoneos")
  9.
 #Do Something
  10.
}
  11.
}

On running qmake with the iphonesimulator kit, it prints out

  1.
Project MESSAGE: iphonesimulator
  2.
Project MESSAGE: iphonesimulator
  3.
Project MESSAGE: iphonesimulator
  4.
Project MESSAGE: iphonesimulator
  5.
Project MESSAGE: iphoneos
  6.
Project MESSAGE: iphonesimulator
  7.
Project MESSAGE: iphonesimulator
  8.
Project MESSAGE: iphoneos

With iPhone device kit , it prints

  1.
Project MESSAGE: iphoneos
  2.
Project MESSAGE: iphoneos
  3.
Project MESSAGE: iphoneos
  4.
Project MESSAGE: iphonesimulator
  5.
Project MESSAGE: iphoneos
  6.
Project MESSAGE: iphoneos
  7.
Project MESSAGE: iphonesimulator
  8.
Project MESSAGE: iphoneos


I tried using the QT_ARCH variable, but message($$QT_ARCH) prints out “arm” for 
both the kits.

What is the correct qmake variable to use to differentiate between iPhone 
simulator and iPhone arm kits?


Regards

Shobana

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development



__ Information from ESET NOD32 Antivirus, version of virus signature 
database 9109 (20131128) __

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt for iOS - iOSStyle

[Gustavsen Richard]

On Mar 13, 2013, at 12:58 PM, Frank Hemer 
 wrote:

> On Wednesday 13 March 2013 04:46:43 joao morgado wrote:
>> I really don't understand why QtWidgets are not suitable for mobile
>> plataforms. What is the technicall reason ? Following the Qt "code once
>> deploy everywhere" I have apps with pratically the same code for desktop,
>> symbian and Blackberry. Sometimes the requirements for technicall /
>> engineering apps are just to have minimal, simple, accurate, funtional app
>> interface instead of a shiny, full of glow interface, and thats perflectly
>> achievable with Widgets. As for iOS style, I think it could be done for
>> mobile the same way it is done for desktop, even if it's not 100% native.
> 
> Indeed - even though there a some issues to be taken into account (screensize 
> etc). I fully agree with you.
> 
> I have a (huge) application developed for any kind of device - with a really 
> long product livecycle - which was initially designed to support multiple 
> screen sizes as well as different mobile devices (tablets and such) and I see 
> absolutely no reason for not using this approach. Especially in case where 
> the 
> usability and way of usage are defined off the default road: i.e. having an 
> application private style and usage metaphors.
> 
> Frank@

Note that you _can_ use QtWidgets if you want to. This works, and we support 
it. If this solves things for you, all is good.

But writing fluid interfaces using widgets is time consuming and laborious. For 
sure, some developers don't care about creating fluid interfaces. That simply 
means they have a relaxed approach to native look and feel for their app in the 
first place.

To me it looks like app developers in iOS wants their apps to be fluid and 
shiny. And not only do we want Qt/iOS to be a framework for writing such 
applications, we want it to be the best choice on the market. And we simply 
think QML is a better technology to meet those needs, which explains why we 
don't focus the iOS development around styling up widgets. How to best support 
QML controls with a style that blends nicly into iOS, is yet to be decided.

-Richard (Qt/iOS team)


> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development