User Tools

Site Tools


autoupdater

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
autoupdater [2011/01/16 20:53] glaubitzautoupdater [2012/11/26 08:51] (current) – [Automatic Updates for QHiMDTransfer on MacOS] glaubitz
Line 11: Line 11:
     - Omaha (Windows) - [[http://code.google.com/p/omaha/]]     - Omaha (Windows) - [[http://code.google.com/p/omaha/]]
  
-As mentioned before, Linux and most other Unix derivatives already include a package management system which takes care of periodic updates and thus there is no additional update management within the application necessary. In fact, all popular cross-plattform applications like Firefox or Google Chrome that provide an integrated update mechanism through a menu option, have this option disabled in their Linux versions since the package manager already take care of it. Thus, we will concentrate on integrating automatic updates into the software application on MacOSX and Windows only.+As mentioned before, Linux and most other Unix derivatives already include a package management system which takes care of periodic updates and thus there is no additional update management within the application necessary. In fact, all popular cross-plattform applications like Firefox or Google Chrome that provide an integrated update mechanism through a menu option, have this option disabled in their Linux versions since the package manager already takes care of it. Thus, we will concentrate on integrating automatic updates into the software application on MacOSX and Windows only.
  
 ===== Software versioning ===== ===== Software versioning =====
Line 26: Line 26:
 </code> </code>
  
-The parameter "//--always//" is required since no tags, i.e. version numbers, have been defined in the git tree yet and thus a fallback to the abbreviated commit ID is forced.+The parameter "//--always//" when no tags are defined, i.e. version numbers. But since we want human-readable version numbers, we will simply use tags in future to define these and call //git describe// to read the full //tag// from git and display it in the about dialog as shown below. 
 + 
 +An updated about dialog displaying the version should look like this mock-up: 
 + 
 +{{:aboutdialog-version.png|200}} 
 + 
 +See: 
 + 
 +  * [[http://www.qtcentre.org/wiki/index.php?title=Version_numbering_using_QMake]] 
 +  * [[http://www.qtforum.org/article/25050/build-date-from-compiler-using-qmake.html]]
  
-See: [[http://www.qtcentre.org/wiki/index.php?title=Version_numbering_using_QMake]] 
  
 ===== Automatic Updates for QHiMDTransfer on MacOS ===== ===== Automatic Updates for QHiMDTransfer on MacOS =====
Line 35: Line 43:
 We will be using Sparkle We will be using Sparkle
  
-===== Automatic Updates for QHiMDTransfer on MacOS =====+See: [[http://el-tramo.be/blog/mixing-cocoa-and-qt]] 
 + 
 +===== Automatic Updates for QHiMDTransfer on Windows =====
  
 We will be using WinSparkle We will be using WinSparkle
  
 +See: [[http://winsparkle.org/wiki/Doc/BasicSetup]]
autoupdater.1295211186.txt.gz · Last modified: 2011/01/16 20:53 by glaubitz

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki