On Jul 6, 2016, at 11:10 PM, Eike Ziller 
<[email protected]<mailto:[email protected]>> wrote:


On Jul 6, 2016, at 19:47, Jake Petroules 
<[email protected]<mailto:[email protected]>> wrote:

I agree this is a -1. Is this something we're just doing for the beta and the 
final should be correctly shipped as a drag n drop dmg?

On Jul 6, 2016, at 10:36 AM, Mike Jackson 
<[email protected]<mailto:[email protected]>> wrote:

Out of curiosity why was there a switch from a "Drag-n-Drop" installation of 
QtCreator to an actual "installer" that I have to run?

I would like to put a "-1" vote for the installer? Was there really a need for 
it? And where all is stuff being installed? I tend to use the nightlies which 
as a Drag-n-Drop install was easy to update on a daily basis and have multiple 
versions available at any one time.

This is the result of consolidating how we build Qt Creator standalone and the 
diverse Qt packages.
So far we had completely different setups for Qt Creator standalone and Qt 
packages, and it is far from optimal or even good.

That was extremely optimal and good. Besides, they are separate and unrelated 
products, why on earth would their setup processes have anything to do with 
each other?

Changes like this are not user friendly. People do not want an installer on 
macOS. They do not want bin and lib directories. They want drag n drop 
application bundles in a DMG. This is how virtually all applications are 
deployed on macOS. Whoever decided this:

  *   Doesn't own a Mac
  *   Is a KDE/Linux user/developer
  *   Is a developer and not a product manager

At least one of the three is true. Am I right?

It's really frustrating to see constant accumulation of concepts and ideas that 
arise from 90% of our developers being long time KDE/Linux developers and 
having no interest in anything else. The other platforms of the world are not 
KDE. Things are done differently there. Please start acknowledging this.

In any case, for running the opensource content Qt Creator does not require an 
installer on any platform, and you can just go ahead and unpack the sevenzips 
located in the “installer_source” sub-directories for the platform, e.g.
https://download.qt.io/development_releases/qtcreator/4.1/4.1.0-beta1/installer_source/mac_x64/
(on other than macOS, you should be aware that these do not contain any 
“qt-creator” subdirectory, and directly contain “bin/“, “lib/“, etc 
directories).

Br, Eike

--
Michael A. Jackson
BlueQuartz Software, LLC
[e]: [email protected]
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

--
Jake Petroules - [email protected]
Consulting Services Engineer - The Qt Company
Qbs build tool evangelist - qbs.io

_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

--
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
[email protected]
+123 45 6789012
http://qt.io
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 
144331 B


--
Jake Petroules - [email protected]<mailto:[email protected]>
Consulting Services Engineer - The Qt Company
Qbs build tool evangelist - qbs.io<http://qbs.io>

_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to