Leopard has many new features that speed up development. Implementing Leopard features in Tiger could be seen as a lot of effort for not much gain! That's what I think anyway, upgrade already!!

@INDIEKIDUK:
Indeed, Leopard has many new features.
This is not about implementing Leopard features in Tiger.
It's simply about running this app in Tiger on Intel Macs.

I can't notice anything about this program and what it assumed to do in Leopard that can not be handled by Tiger 10.4.10 or 10.4.11!
It's like saying that iTunes 8 is a Leopard only app because of all the new things and speedups in Leopard. iTunes 8 on a Tiger Intel Mac is exactly the same as iTunes 8 on a Leopard Intel Mac. That's called "backward compatible" and it's with a good reason too. Apple knows that Tiger is still in the run. It was the first official OS for the Intel Macs. People are still using Tiger for many good reasons (personal reasons or not). PPC Macs as well as Intel Macs.

I'm convinced of the fact that there are no so called Leopard features which are needed to be implomented in a Tiger version (at any cost of effort and gain).
Just like iTunes 8 or any other "backward compatible" app.

If your code is right, well written and when you use Xcode (Apple's SDK) it's just a mather of build settings and project settings. The developer from this program has a big chance, if he developed this great program with xCode, that a Tiger build is virtual at no extra costs and possible with a min. of effort! It could be done in 1 hour or less! Or maybe in a few houres, if you need to learn working with Xcode's settings. It depends on how much experiance you have with Xcode...

That's why "we" ask to upgrade already ;-). That's a Intel Tiger upgrade first! just that we understand each other ;).

Making the program Universal is a different story and will take some more time and effort. But sometimes it's very easy to do (have you ever seen the keynote on how fast developers made their app Universal?). If you have a Apple Developer account you can take a look in the developer section. There are tons of information on how to deal with this Universal issue. Normally this could be solved in a few days or maybe in a few weeks (the program is not that large, 16,4 Mb) if you have some time. The developer could release beta's for PPC users on "Tiger and Leopard" because you can't only depend on launching/testing the program with Rosetta on a Intel Mac. The developer will need real life PPC feedback on this Universal issue ;).

My 2 cents. My thoughts about this 2 issues and with much respect fot what you are thinking!

Greetz.
Leppe

The source list is Leopard only. That is the blue list on the left in iTunes/iPhoto/Mail etc.

@INDIEKIDUK

You wouldn't be an App$e employee wanting people to upgrade to generate more App$e dollars, would you? Frankly your call for upgrade sounds snobbish .

Leopard is great for App$e and developers in that it forces users to upgrade software at additional expense for no apparent change in benefit. At the same time users loose the valuable software and compatible drivers/hardware that comes with OS 9 (classic).

The fact is that Tiger does me (and others) perfectly well and, despite what you or App$e tells us, I consider Leopard (not to mention Intel crap) a downgrade. BTW at last check there were more still more Tiger users than Leopard out there. So the developer who charges for their labor miss out on a large user base. Frankly, that is not a very smart business model.

Nup I think it's just Leppe and Strop on Tiger LOL ;-)

I don't understand what you mean with: "The source list is Leopard only. That is the blue list on the left in iTunes/iPhoto/Mail etc."?
I guess you mean the sidebars? Remember Mail in 10.4. There was back then in iLife '08, like in iLife '09, also a MediaBrowser. iLife '09 is Leopard only. But iLife '08 has a mediabrowser which is virtual the same one as in iLife '09. iTunes8, the program we all use to sync our iPhones & iPods Touch, is Tiger compatible an works fine with the iLife'08 mediabrowser.

When you talked about the "source list" my first thought was that you had the source files :D [LOL].

I've just downloaded this program on a PPC Mac ;-).
-What do I see when I open the programs Package Contents:
/Contents/Frameworks => The only framework is Sparkle (1.5beta(?) build only for Intel). This free "SoftwareUpdate framework" comes with Universal source code. You can download the framework from http://sparkle.andymatuschak.org/ and besides the source code there is also a precompiled "Sparkle.framework" in there. The precompiled Sparkle.Framework is already Universal.
For the Sparkle framework the developer used definitely Xcode and builded a "current hardware" or "Intel only" version from this great framework. So this source code, if you want to compile it yourself, Universal ready. There is also a precompiled Universal Sparkle.framwork into the download folder.

Contens/Recources/FirmwareBundles => This 9 bundles are the same for Intel and PPC.

Contens/Resources => 2 compatible PPC/Intel audio files in aif format. 5 compiled Nib files. As far I know the program which builds nib files (Interface Builder) makes no difference between Intel or PPC. I believe the developer uses Xcode 3.1.2 (latest release), for Leopard only but backward compatible. Just set "Deployment Target" in Interface Builder at 10.4.x and you are good. Now you can make all the nib files you need for this nice "Cocoa" program. You can create the same program window (NSwindow) as before. You can adjust Document Locking if you wish to build the nib files ready for translations in other languages or not, or you can do nothing, etc.
In the rest from the /Contents/Resources folder there are a lot of .png files (for the UI from the program and recogniced the same on Intel & PPC) and one language folder (English) with 5 compiled nib files (MainMenu.nib, etc.) which you can be created with the right Deployment Target (10.4.x instead of 10.5.x). There is virtual no difference between 10.4x Deployment Target and the used 10.5.x Deployment Target. The Menubar is the same, NSwindow is the same, etc. The artwork (.png files) will work just fine with the 10.4.x Deployment Target. So in the end the Look & Feel from the UI will be the same!

So far all the files above, they are Universal ready when followed the instructions. Even the Sparkle framework!
Maybe it's better to pay attention at the files which are needed to be recompiled.

First of all /Contents/MacOS/InstallerApp is Intel only. The developers source code, later compiled into InstallerApp, should be checked if it's possible to compile it in a universal app without changing the source code (which is written by the developer). Go to the MenuBar with the mouse, go to Project, select Edit project settings. In here you can adjust the settings for compiling into a Universal program. For instance: into "General" you need to change the "Base SDK for All Configurations", into Mac OS X 10.4 ;). Then you select "Build" and you start change Architectures into "Standard (32-bit Universal)" or into "32/64-bit Universal". Then you go to "Valid Architectures". Since this program is Intel only the two architectures will be i386 and x86_64 (with a space in between). Now add at least 3 new architectures sepperated with a space: ppc ppc64 ppc970. In the end you will have 5 valid architectures for your program looking like this: "i386 x86_64 ppc ppc64 ppc970".
Now you can close the "Edit Project settings" window where you made the above changes. Via the Menubar, Project, Set active SDK you need to change it into Mac OS X 10.4. Now open the "Edit Project settings" again and select "General" again. Click on "Rebuild Code Sense Index" (big files could take a while...); Now you can close the "Edit Project settings" window again!
Now select in your Xcode sidebar window the target file(here is this of course InstallerApp) and Right click the Target. Select build and try, as a test, to compile/build the source code into a new "InstallerApp" unix file that is Universal. Fingers crossed and hope the file is building correctly without any Faults!


Wow, seems this reply is a bit long :-). Sorry for this :-/
My conclusion is, after seeing the Intel program, that a Universal release or update is realistic. Sparkle is already Universal. The source code from Sparkle builds with Xcode and I think that the "Xcode build settings" where set to "Current Mac OS" and the architecture as "Native Architecture of build machine" (instead of 32/64-bit Universal or 32-bit Universal). Resulting in a Intel only Sparkle Framework... Resulting in a Intel only InstallerApp...
My only conserne is the source code from the Developer. Is the code Universal ready? If so, you can start building and testing ;).
If not, you will have to search on the internet for information and experiances from other developers which had the same issues (which is in fact a reversed Universal program Intel=>PPC instead of PPC=> Intel)...

Greetz.
Leppe