Will there ever be a ResEdit version for Mac OS X?? Is there another program for X that does the same thing, or is the Unix architerture making such apps impossible??
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
ResEdit X?
- Thread starter stoid
- Start date
- Sort by reaction score
I think the correct word is "unnecessary", not impossible.
The command-line gives you the freedom to modify system resources that the GUI hides from you. Since there was no CLI, pre OS X, you needed a GUI tool to do it for you, and that's the purpose ResEdit served.
It's possible for someone to make a ResEdit-like app for OS X, they would just have to take into consideration Unix file permissions, etc.
The command-line gives you the freedom to modify system resources that the GUI hides from you. Since there was no CLI, pre OS X, you needed a GUI tool to do it for you, and that's the purpose ResEdit served.
It's possible for someone to make a ResEdit-like app for OS X, they would just have to take into consideration Unix file permissions, etc.
How can I learn to use the CLI. I've heard talk about it, but frankly, I don't want to accidentally screw up my Mac. I accientally set the monitor Res upto 1280*1024, which my third party monitor doesn't support, and I forgot to let it revert, and I wound up having to reinstall X. Fourtunately, I hadn't useed it muxh, so it wasn't a big loss, but now I've used X for months, and I don't want to have to start over from scratch.
I found these tutorials to be pretty helpful when I was just starting:
http://www.oreillynet.com/pub/a/mac/2001/12/14/terminal_one.html
http://www.oreillynet.com/pub/a/mac/2001/12/14/terminal_one.html
I think saying that the mere fact that a CLI exists under OS X makes Res Edit for X is really exagerating. Most Mac users are GUI-dependent and are highly resistent to having to use a CLI to do things because it makes using the computer nolonger easy -- thus violating the whole concept of the Mac which was to be point and click simple. I'm not against CLIs, I use it all the time to do compiling work, but I wouldn't expect most Mac users to be happy with not having a version of Res Edit for X. Clearly you can't do everything in the CLI that you could do with Res Edit. If we could, I wouldn't have to run Res Edit every few weeks in Classic mode. CLI only has the power to manage files and their relative storage, it can't go deeper than that, into the files themselves..
Re: ResEdit X?
Most likely, no. But there are some alternatives
The Unix architecture really doesn't have much to do with it. The resource structure implementation is all Apple.
Under pre-Mac OS X, the resource and data forks were seperate. Under Mac OS X, the resource fork has been combined into the data fork, probably for cross-file-system compatibility reasons. The .rsrc file in the .app packages is the same as before, but has been combined into the data fork.
So all you need to do is seperate the resource from the data. The tool: QuickConvert. This will convert data->resource and vice versa, through drag-and-drop. Just drop, ResEdit, then drop again, and you're finished. Yes, you can use ResEdit through Classic to edit converted X .rsrc files.
Another program that acts similar to ResEdit is Resorcerer. This native X program alleviates the need to seperate the resource it just edits the one fork in place. But it is expensive, $256. I have used it and it works great.
A great site to go for more info/hacks: ResExcellence
Hope this helps.
Most likely, no. But there are some alternatives
The Unix architecture really doesn't have much to do with it. The resource structure implementation is all Apple.
Under pre-Mac OS X, the resource and data forks were seperate. Under Mac OS X, the resource fork has been combined into the data fork, probably for cross-file-system compatibility reasons. The .rsrc file in the .app packages is the same as before, but has been combined into the data fork.
So all you need to do is seperate the resource from the data. The tool: QuickConvert. This will convert data->resource and vice versa, through drag-and-drop. Just drop, ResEdit, then drop again, and you're finished. Yes, you can use ResEdit through Classic to edit converted X .rsrc files.
Another program that acts similar to ResEdit is Resorcerer. This native X program alleviates the need to seperate the resource it just edits the one fork in place. But it is expensive, $256. I have used it and it works great.
A great site to go for more info/hacks: ResExcellence
Hope this helps.
You can go into a .app and pull out/modify icons and such just like you could with ResEdit. For other application settings you can modify the .plist files with any text editor that understands XML. How is that not going into the files?
You're telling me that editing resources by ID number in ResEdit is "point and click easy"? Having to edit these files with ANYTHING violates the whole Mac ease-of-use concept. The people who use ResEdit are power users/tinkerers who have moved beyond the basics of computing.
I'm sure that people are working on some similar app for X, that's great. But there are other ways of getting at those files now, whereas ResEdit was the only tool you could use to get into files before.
Once in a while I use the OS 9 version of ResEdit 2.1.3 and it works fine. I would expect the CLI to have no more or less problems than the OS 9 version.
But I usually do not fool around with that stuff, unless I need to do so, such as getting certain applications to work with proper IDs...
And I would not want to pay $256 for an application that functions as ResEdit. I will stick with what I have.
__________________
Any time is a great time for iPod.
But I usually do not fool around with that stuff, unless I need to do so, such as getting certain applications to work with proper IDs...
And I would not want to pay $256 for an application that functions as ResEdit. I will stick with what I have.
__________________
Any time is a great time for iPod.
For the most part, X resources are the same as pre-OS X, just in a different form. ResEdit is needed for the tasks you cannot complete w/o a gui. CLI is needed for the Unix underpinnings. CLI/ResEdit work hand in hand. For example, you can't edit a picture resource with CLI and you can't edit Unix file permissions with ResEdit.
Apple hasn't changed their overall resource structure very heavily from pre-OS X. In fact, I think that there is more control, because you can go into the .app and edit all the pieces with different tools (like .nib with the DevTools and so on).