www: aeae47e2: Let's not show a big download button whe...
markdoliner at pidgin.im
markdoliner at pidgin.im
Sat Mar 10 17:50:44 EST 2012
----------------------------------------------------------------------
Revision: aeae47e2b34ecceaad4b3f0ddf10214c98eeb080
Parent: 4728c0f5f4266e77e1514e2cacd01e0da2d8b9a0
Author: markdoliner at pidgin.im
Date: 03/10/12 17:50:38
Branch: im.pidgin.www
URL: http://d.pidgin.im/viewmtn/revision/info/aeae47e2b34ecceaad4b3f0ddf10214c98eeb080
Changelog:
Let's not show a big download button when people try to download Pidgin for
OS X. Do people think it's common to use Pidgin on OS X? I feel like most
people won't know what to do when they click the download button and get a
source package. So instead I linked to the source download page at the
bottom of the page. Does this change sound reasonable to people?
Changes against parent 4728c0f5f4266e77e1514e2cacd01e0da2d8b9a0
patched htdocs/download/mac/index.php
-------------- next part --------------
============================================================
--- htdocs/download/mac/index.php d793141e618783a461d27b28558118fdde5a44d4
+++ htdocs/download/mac/index.php 439c81698ba5a1d19ff057441e03a0ffa3a943f9
@@ -20,29 +20,10 @@
<div class="box_download">
-<p>
-<span class="download_header"><a class="sourceforge_accelerator_link" href="http://sourceforge.net/projects/pidgin/files/Pidgin/<?php echo $pidgin_version; ?>/pidgin-<?php echo $pidgin_version; ?>.tar.bz2/download"
-onclick="javascript:pageTracker._trackPageview('/goals/downloads/source');"
->Download Now</a></span>
-<script>
-(function() {
- var script = document.createElement('script');
- script.src = '//sourceforge.net/accelerator/js?partner_id=62&button_size=large';
- script.defer = true;
- var s = document.getElementsByTagName('script')[0];
- s.parentNode.insertBefore(script, s);
-})();
-</script>
-</p>
+<p>For a native Mac OS X experience we recommend <a href="http://adium.im" onClick="javascript:pageTracker._trackPageview('/external/adium.im');">Adium</a>, which uses libpurple (the core of Pidgin) for much of its protocol support.</p>
+<p>If you're sure you want to use Pidgin on OS X, you may find the packages provided through <a href="http://finkproject.org/download/" onClick="javascript:pageTracker._trackPageview('/external/finkproject.org');">Fink</a> or <a href="http://www.macports.org/install.php" onClick="javascript:pageTracker._trackPageview('/external/macports.org');">Macports</a> more convenient than compiling from source. <i>Please note, we do ot provide support for issues related to installing Fink, Macports, or their packages of Pidgin. Contact those projects directly with questions or concerns.</i></p>
+<p>If you're sure you want to use Pidgin on OS X and you don't want to use Fink or Macports, you can <a href="/download/source/">download the Pidgin source</a> and compile.</p>
-<p>For a more native Mac OS X experience, you may be interested in using <a href="http://adium.im" onClick="javascript:pageTracker._trackPageview('/external/adium.im');">Adium</a> instead, which uses libpurple (the core of Pidgin) for much of its protocol support.</p>
-<p>For Pidgin on OS X, you may find the packages provided through <a href="http://finkproject.org/download" onClick="javascript:pageTracker._trackPageview('/external/finkproject.org');">Fink</a> or <a href="http://www.macports.org/install.php" onClick="javascript:pageTracker._trackPageview('/external/macports.org');">Macports</a> more convenient than compiling from source.</p>
-<p><i>Please note, we do <b>not</b> provide support for issues related to installing Fink, Macports, or their packages of Pidgin. Contact those projects directly with questions or concerns.</i></p>
-<!--
-
-
--->
-
</div>
</div>
More information about the Commits
mailing list