Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!tandem!zorch!amiga0!mykes From: mykes@amiga0.SF-Bay.ORG (Mike Schwartz) Newsgroups: comp.sys.amiga.programmer Subject: Re: ResEdit for the Amiga? Message-ID: Date: 7 Jun 91 22:21:45 GMT References: <2971@public.BTR.COM> Organization: Amiga makes it possible Lines: 57 In article <2971@public.BTR.COM> eeh@public.BTR.COM (Eduardo E. Horvath eeh@btr.com) writes: >In article stevek@amiglynx.UUCP (Steve K) writes: >>Would it be possible to construct a ResEdit (MAC) type program for the Amiga? > [...] > >Then, >In article mykes@amiga0.SF-Bay.ORG (Mike Schwartz) writes: >>Actually, I've been discussing somethine like this with a friend of >>mine who programs X-Windows.... >[...] >>So what I have been thinking is that you sould make a ResEdit type program that >>works with an external file. The application program would use the resources > > Let's not. I have recently been forced to suffer through Motif >development, and find this entire descussion extremely nauseating. Motif >currently supports two highly involved and painfully slow methods to make >alterations to programs without changing the executable. The first is the >resource file. > [ discussion of why X-Windows sux :) deleted ] > To answer the question of how resource editing could be handled >on an Amiga, to start with PowerWindows could use an update. I am not >particularly happy with its overemphasis on the menu as the end-all in >man-machine interfaces. Secondly, debug information could be used, or >some new hunk could be added, that points at and describes the data >structures used in creating the UI. There could be a little program >that allows the user to go in and modify those values in the actual >executable. Yes, you could totally trash the program, but since when >has AmigaDOS prevented you from shooting your own foot off? 8^) > The only reason I suggest an external file is for development purposes only. Compilers and assemblers generate Debug hunks which will wipe out what your ResEdit program would put there each time you compile/assemble. When you SHIP the program, you would delete the compiler debug hunk and move the resource file into the debug hunk... There is NO way I'd want to have to copy lots of resource files, or even just one resource file, anytime I want to move the application to a different location. You describe exactly what I did before. By the way, it should be possible to add similar resource/debug hunks to .library files, too, thus making public access Resource possible. > >-- >========================================================================= >Eduardo Horvath eeh@btr.com > ..!{decwrl,mips,fernwood}!btr!eeh > "Trust me, I am cognizant of what I am doing." - Hammeroid -- **************************************************** * I want games that look like Shadow of the Beast * * but play like Leisure Suit Larry. * ****************************************************