[timmerk]

Hello all,

I recently removed APE from my system and it sped things up a lot and now my machine doesn't crash as often. I'm not trying to start a flame war, it just fixed my system.

Anyways, the only module I really need was WindowShade X. Is there an alternative that doesn't use APE?

Thanks!

[CharlesS]

Nope, and I don't think it's possible to do that without hacking the system anyway.

[goMac]

I've coded one up but it still involves patching. I don't notice it but there should be a minor speed hit.

It IS possible to make WindowShade happen without patching or APE, but it requires extensive and evil hackery in your system, quite possibly more evil than patching. You'd have to replace the whole Cocoa and Carbon frameworks in your system, which is not for the feint of heart, and is just plain dag nasty evil.

[Chuckit]

Originally Posted by goMac

It IS possible to make WindowShade happen without patching or APE, but it requires extensive and evil hackery in your system, quite possibly more evil than patching. You'd have to replace the whole Cocoa and Carbon frameworks in your system, which is not for the feint of heart, and is just plain dag nasty evil.

How would you create functional copies of the two main system frameworks without either a) a ridiculous investment of time to reverse engineer them, or b) patching?

[goMac]

Originally Posted by Chuckit

How would you create functional copies of the two main system frameworks without either a) a ridiculous investment of time to reverse engineer them, or b) patching?

MacDev magazine wrote an article on it in the Rhapsody days. I THINK the general idea was you copied out Cocoa, gave it a different name, created a new fake Cocoa framework, overrided the functions you wanted, and linked against your renamed copied Cocoa framework. Kind of like stacking an extra framework in between programs and Cocoa. Their example turned all the windows in Rhapsody purple.

[CharlesS]

Originally Posted by goMac

I've coded one up but it still involves patching. I don't notice it but there should be a minor speed hit.

It IS possible to make WindowShade happen without patching or APE, but it requires extensive and evil hackery in your system, quite possibly more evil than patching. You'd have to replace the whole Cocoa and Carbon frameworks in your system, which is not for the feint of heart, and is just plain dag nasty evil.

Not to mention the fact that it will get destroyed at the next Software Update (or, if you're really unlucky, it may cause everything to get mucked enough that you have to reinstall).

[Chuckit]

Originally Posted by goMac

MacDev magazine wrote an article on it in the Rhapsody days. I THINK the general idea was you copied out Cocoa, gave it a different name, created a new fake Cocoa framework, overrided the functions you wanted, and linked against your renamed copied Cocoa framework. Kind of like stacking an extra framework in between programs and Cocoa. Their example turned all the windows in Rhapsody purple.

Ah. I'd consider that the worst of both worlds: It's runtime patching that requires mucking around with system files. Yikes! Give me SIMBL any day of the week.