Occasionally i need to open a resource fork and export a resource or two.
I made ResEditX to help me. Hope it helps someone else.
Feature requests and bug reports are welcomed.
Thanks
http://macintoshgarden.org/apps/reseditx
Change Log
Image Preview
Sound Preview
Wanted this application since I've been forced to use Mac OS X. Thanks.
@IIGS_User
I'm very glad it can help you. I know you are a great supporter/contributor of this site and the community and one of the reasons for me to make ResEditX, was to contribute something back.
I'd like to keep developing this app and create others. As I wrote this in RealBasic 2009, I can't compile for 68k. But I think it would be interesting now to see how much software I could write for the 68k, using current software patterns. For instance, for ResEditX I used the repository pattern(https://msdn.microsoft.com/en-us/library/ff649690.aspx). And now that we have access to many online API's, most of the application calculations can be done by another system. My Macintosh Classic could literally become useful again.
I really need to discuss this with as many minds as possible, but I don't have time to chat. I'd love to hear a lot of opinions.
You might want to talk to Paul Pratt over at the Gryphel project; his reason behind converting vMac into Mini vMac was to have a central engine where he could deploy to multiple targets. His MPW integration is really neat.
But if someone could write a performant HTML5 runtime for 68k... that would be amazing. It'd be like Hypercard all over again, but cross-platform.
Thx a lot for making it 68k, too!
thanx for sharing....
what updates/features do you guys want?
a console?
more previews/editors?
i can't really think of much else. the one thing i am working on will allow for uploading resource data to a web server.
Hi nil0bject! Once again, thank you so much for ResEditX! It is simply awesome! More previews/editors would be cool, bringing the expected functionality closer to regular ResEdit on Classic Mac OS. Old habits die hard, you know 
Don't get back in the saddle just for me, though. All my files are stored on a SMB-share which corrupts the resource forks 
So playing safe on OS X, keeping all my Classic Mac OS files compressed - only uncompressing them safely inside SheepShaver/PPC hardware.
which format are you compressing them in? i might be able to write an in-memory decompressor
Would be awesome, nil0bject 
I'm compressing them in .sit. I know I should be .hqx-ing them as well, but as I have been dealing with such massive amounts of files (10s of thousands) between OS 9/OS X 10.4 for use and OS X 10.10/SMB-share for backup, .hqx-ing became a hassle I just wasn't willing to deal with
I'm compressing them in .sit. I know I should be .hqx-ing them as well
@BryMD: Hi, you do not need to add .hqx to archives if you've compressed them to .sit - StuffIt .sit is a flat-file format that travels well across networks. And applications that can decompress .sit at the other end, read the header of the .sit to work out what type of file it is. That is; they don't bother with Mac File or Creator Types in order to work with them.
So, no need to feel any guilt for not using .hqx on .sit files
Hehe Good to hear 
That said, for some reason I always thought .hqx-ing would have some archival benefits over simply .sit-ing the files. Thought I'd read it somewhere in the past, but it might as well have been my observation that StuffIt offers to .hqx and .sit files simultaneously and automatically landed on the conclusion that there would be some benefit to that 
Most of my .sit archives are not archives of single files though, but rather collection of files (mostly applications/read me files/accessory files), which would make a file chooser a necessity. Once again, don't go out of the way just for me, though. Would be an AWESOME addition til ResEditX, though
