Build update checker for Mixxx
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
We have too many people using out-of-date versions of Mixxx.
I propose adding a simple request to mixxx.org:
http://
which returns a simple JSON object:
{ 'version': '1.10.0' }
or something similar. Then we can add a check on startup to notify the user if their version of Mixxx is out of date.
It has to be disable-able via scons flag (for Debian packaging, Mac App Store, etc.). There is also the issue of tracking people -- some will not want Mixxx to go check mixxx.org by default. We should make it easy to turn off via a checkbox in the installer. I am in favor of letting it default to checked, though.
On OS X, there is no installer so we may have to ask via a pop-up on first-run. Perhaps we could make use of the intro-dialog that Mixxx 1.8.0 used for promo-tracks agreement for this.
Changed in mixxx: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
tags: | added: website |
description: | updated |
tags: |
added: usability removed: website |
We could use Sparkle and WinSparkle instead of rolling our own.
On Nov 23, 2011 2:35 PM, "RJ Ryan" <email address hidden> wrote:
> Public bug reported: mixxx.org/ api/latestVersi on mixxx.org/ api/latestVersi on /bugs.launchpad .net/bugs/ 894176 /bugs.launchpad .net/mixxx/ +bug/894176/ +subscriptions
>
> We have too many people using out-of-date versions of Mixxx.
>
> I propose adding a simple request to mixxx.org:
>
> http://
>
> which returns a simple JSON object:
>
> { 'version': '1.10.0' }
>
> or something similar. Then we can add a check on startup to notify the
> user if their version of Mixxx is out of date.
>
> It has to be disable-able via scons flag (for Debian packaging, Mac App
> Store, etc.). There is also the issue of tracking people -- some will
> not want Mixxx to go check mixxx.org by default. We should make it easy
> to turn off via a checkbox in the installer. I am in favor of letting it
> default to checked, though.
>
> On OS X, there is no installer so we may have to ask via a pop-up on
> first-run. Perhaps we could make use of the intro-dialog that Mixxx
> 1.8.0 used for promo-tracks agreement for this.
>
> ** Affects: mixxx
> Importance: Wishlist
> Status: Confirmed
>
>
> ** Tags: website
>
> ** Changed in: mixxx
> Status: New => Confirmed
>
> ** Changed in: mixxx
> Importance: Undecided => Wishlist
>
> ** Tags added: website
>
> ** Description changed:
>
> We have too many people using out-of-date versions of Mixxx.
>
> I propose adding a simple request to mixxx.org:
>
> http://
>
> which returns a simple JSON object:
>
> { 'version': '1.10.0' }
>
> or something similar. Then we can add a check on startup to notify the
> user if their version of Mixxx is out of date.
>
> - It has to be disable-able via scons flag (for Debian packaging, etc.).
> - There is also the issue of tracking people -- some will not want Mixxx
> - to go check mixxx.org by default. We should make it easy to turn off via
> - a checkbox in the installer. I am in favor of letting it default to
> - checked, though.
> + It has to be disable-able via scons flag (for Debian packaging, Mac App
> + Store, etc.). There is also the issue of tracking people -- some will
> + not want Mixxx to go check mixxx.org by default. We should make it easy
> + to turn off via a checkbox in the installer. I am in favor of letting it
> + default to checked, though.
>
> On OS X, there is no installer so we may have to ask via a pop-up on
> first-run. Perhaps we could make use of the intro-dialog that Mixxx
> 1.8.0 used for promo-tracks agreement for this.
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https:/
>
> Title:
> Build update checker for Mixxx
>
> To manage notifications about this bug go to:
> https:/
>