the great adobe cs2 case-sensitive adventure, part 2: fsevents
digging around with fseventer, we can watch what files ps is actually opening. by placing a copy on a case-insensitive .dmg, it's possible to see what files a successful launch touches. unfortunately the api being used doesn't seem to show if shared library code is being loaded, which makes figuring out if all the frameworks are loading correctly a bit of a chore. there're a bunch more resources etc. that need to be fixed up, but unfortunately fseventer doesn't really tell us how. it's worth noting that while robert pointon's front end is certainly gorgeous, if you want to be doing any diff-style analysis, you'll have to build the included command-line tool and use that. fseventer is based on gfslogger, and the whole mess uses an as-yet undocumented (my favorite kind) apple api.
at this point, fixing the discrepant paths found with fsevents* I _think fixed the splash screen, and lets photoshop boot to the point where it generates a licensing error. unfortunately I know the licenses are just fine, so it's still a problem with the app itself.
I also started to examine some of the other cs2 apps. they all share what appear to be common frameworks, and the install of indesign even seems to have most of them with correct capitalization. however it appears as though the different product teams don't really share too much, as copying a framework from one app to another results in disaster. c'mon guys, the whole point of frameworks is to factor out shared code. work as a team, build a suite (the 's' in cs2, non?), and put one copy of each framework in /Library/Application Support/Adobe/ or wherever it's gonna be. this is just silliness.
at this point, fixing the discrepant paths found with fsevents* I _think fixed the splash screen, and lets photoshop boot to the point where it generates a licensing error. unfortunately I know the licenses are just fine, so it's still a problem with the app itself.
I also started to examine some of the other cs2 apps. they all share what appear to be common frameworks, and the install of indesign even seems to have most of them with correct capitalization. however it appears as though the different product teams don't really share too much, as copying a framework from one app to another results in disaster. c'mon guys, the whole point of frameworks is to factor out shared code. work as a team, build a suite (the 's' in cs2, non?), and put one copy of each framework in /Library/Application Support/Adobe/ or wherever it's gonna be. this is just silliness.
0 Comments:
Post a Comment
<< Home