ThemeChanger 0.5

Well, i got some things about the current version that i wanna say

i dont like the auto restart of the finder
i dont like how there is no deselect all or select all button
i dont like how the interface is really simple and...oh wait..i do like that

and how it works..i like that

but the first two are real

I'd love to beta test it.

Well the final is out now. Changes:

• Now searches for Themes in Library in all domains (~, /, /Network, /System), in correct order. Of course, you shouldn't put stuff in /System/Library/Themes, and probably won't put stuff in /Network/Library/Themes, but it looks there anyway :-)
• Ignores themes with names starting "." - these are generally broken Duality internal things.
• Automatic Aqua back-up.
• Switching code factored out to a tool. A side-effect of this is that previewing is much more robust since we now know when things happen rather than having to take a guess. The app verifies the tool has not been tampered with against a build-time checksum.
• ThemePreview source is now included, and was modified to make sure it's the front process after it's launched (workaround for oddity when launching it from ThemeChangerTool).
• Now authorises using the "system.preferences" right, so no need to keep reauthorising if you're an admin user.
• Enhanced status readout.
• Installs tool to repair theme files if they become corrupted ("tcfix").
• Installs Aqua before switching themes, so there will never be a mix of components from different themes.
• Restarting the Finder is now a user preference.
• Can optionally restart the Dock.

[*]Automatic Aqua back-up.
How does it do that? If I already have my own theme installed will it label that Aqua?
[*]Installs Aqua before switching themes, so there will never be a mix of components from different themes.
Uh, what if I haven't had Aqua on my computer for months? And is this optional? I loved themechanger because I could use it to mix themes. I hope this 'feature' is not gone.
[*]Restarting the Finder is now a user preference.
That's good. If a theme is botched I'd rather test it on a less important program first!
[*]Can optionally restart the Dock.
Good, I guess.

It prompts you to either quit and revert using another app, reinstall Aqua from an "Aqua Restore" theme, or continue. If you continue, it will label your own theme as Aqua.

See above. The thought that people would want an inconsistent mix of different themes didn't even occur to me, so no, it's not optional. I can make it optional if you think that would be useful.

Really, I thought that was the whole point of Themechanger's ability to install parts of themes without the whole enchilada like other themeswitchers. What's the deal with all those little checkboxes in the right window, if not to take parts of themes and leave others? Just to mix theme's with Aqua? Yuk! Definitely make it an option. You can never have too many options. The Aqua backup thing could be expanded into a 'Save Custom Theme' function so once you get the right mix you can save it off and get it back. I'm made a custom theme that's a mix of MMX elements, Brushed windows, AluminiteX widgets and sliders and a bunch of other stuff. There might be other people who can't do decent themes, but can at least play mix and match!!!

Thanks for your input mr tew

Well definitely make it a feature.
I'm sure this feature will make users happy, including me.
I mean, when I install BBX and then revert back to SmoothStripes, several BBX components are still there. e.g. bootx, the browser's resize buttons, the boot panel, etc. It's very frustrating, and I'm sure it is frightening a lot of users.

Oboy...
I tryed to use ThemeChanger 0.5 version today. And it really blew my system to macheaven. After running a theme-switch on my first OS X HD it wouldn�t boot from that disc anymore. It switched automatically to my second HD.I couldn�t even force it to boot on my first HD.
Then I reinstalled OS X on to my first HD and everything was fine again. Then I tryed ThemeChanger again and the same thing happened when I did a reboot. After that I was a bit annoyed over this and I tryed to find reasons why this could happen.

By accident I found in these forums that some users was not happy that themchangers alter the bootX file. So I replaced the bootX file found in coreservices with the original one.
And after that my system booted normally from my first HD.

Am I the only one that have had this problem with themechanger?

Read the Readme. It has instructions on how to fix things if they go awry.

BTW, what theme were you using?

I was using BBX and Simplex 1.5

SimpleX 1.5 is way out of date, you should use the new one here : http://swizcore.com/SS/macOSX.php

Hey Angus_D,

The new ThemeChanger is for words.

Now For the third time it has happened again. I can�t no longer boot from my first HD 1. The computer automatically switches too my second HD. And my trick to switch back some elements does�nt seemed to work this time.

I can�t boot HD 1 into and therefore use tcfix.

Any ideas what to do?!

_

double post!

Email me solitaire

swizcore at swizcore dot com

This is a screenshot of bootoptions on my First HD. It does look strange doesn�t it!
the "classic" screenshot!

I�m absolutely surtein that themechanger have something to do with it!

Well, I see what you mean. If BootX is fuxx0red then you can't even get into single-user mode. As I have said, themes SHOULD NOT REPLACE BOOTX. And here is the reason why. *sigh*

No, the themes do. Startup Disk looks for bootable "System Folders" by looking for BootX (or the System file for Classic). As I have repeatedly stated, themes should not include or replace BootX, because bad things will happen. I only hope people will take more notice of me now.

Whoa! That is mega whack!. Im in the process of compiling your solution. I'll be sending it to you this evening.

how is one to know which themes will do this and which wont?

By looking at the list of components. Of course, if it's a .theme you might not be able to unselect it. I should probably make TC refuse to overwrite BootX.

But please make it an option!

You could make the BootX box unchecked by default, and when the user tries to check it a warning comes up that says overwriting the BootX file could do damage or whatever and make them click "Yes, I Insist".

Also, when I tried to delete my Aqua backup, I got the eternal progress bar, but after I did force it to quit it seemed like it did delete it. Where does it store the Aqua backup anyway? Another thing about the Aqua backup, it doesn't seem to be backiing up the BootX (very important I'd think) or the menu items that several themes change. Is this right? Can you make it do these in the next version? I love how ThemeChanger is going. It's the only one that's consistantly worked for me. Good job!

hey angus.

a little feedback for you.

using the most recent version of themechanger, and watercolor 1.3, when i clicked install, the progress bar progressed pretty well until it got to somewhere towards the very end where it said "killing dock" and it froze. i think it was frozen, i let it sit for about 8 minutes, my system percentage meter was maxed out so i dont know if it was churning on something or not? regardless, i force quittedout, logged out and back in and it works.

any idea why it froze?

Odd. No idea why that happened. /Library/Application Support/ThemeChanger, of course! It backs up items that themes change on the fly. So, if you install a theme that changes BootX, it backs up BootX before installing the theme's one. Of course, this is completley unuseful because if BootX is broken, you can't boot your comp to replace it anyway. You mean Menu Extras? maybe you didn't revert them to the Aqua ones and you ended up with a theme's resources in your back-up? Glad it works for you.

Well it uses a really lame method for killing the Finder and the Dock, because I added it right at the end of working on 0.5 and I was fed up with trying to find a nice way of doing it (it's easy to get the PID of the Finder, not so easy to get the PID of the Dock). It looks like NSFileHandle is a bit broken when reading from pipes, and it keeps on returning immediately rather than waiting until new data is available. This means that ThemeChanger sits there repeatedly reading data of length 0 while the tool isn't doing anything.

Silly me! I was looking for ~/Library/Application Support/ThemeChanger, of course!




Well I see the purpose of the Aqua backup as a way to return to a cohesive look, not just save a broken computer. Let's say I have stock Aqua installed and install a theme with no BootX. My Aqua backup won't have a BootX backup right? Then I install a theme that does have a BootX. Then I revert to Aqua. Won't I be stuck with that second theme's BootX? Or will it back it up when I install the second theme?



Well I have to admit that I am misusing the AquaBackup feature, because I'd never want to go back to Aqua. I am trying to use it to restore my custom theme after I try out other themes. I set up my computer just like I like it and then clear the Aquabackup and install a new theme. The backup then only contains the items that THAT theme replaced, not everything in my 'theme'. I guess I could get your program to do what I want if I find some theme that replaces EVERYTHING so the ThemeChanger would backup everything in my theme, but I guess the deeper question is what exactly IS everything that a theme could/should replace?



Oh yeah, I love it. It's the first themeswitcher that had brought me anything but grief!

It was designed as a way to save a broken computer. Right. TC looks, finds it doesn't have a BootX backup, backs up your current one and installs the theme's BootX. Well if you just install your theme by hand, remove the aqua backup and restart, then click continue, it should be good. Why can't you do that? Since themes just replace arbitrary files, they could theoretically replace anything. For your purposes, you don't really need to know.