wb1j+@andrew.cmu.edu (William M. Bumgarner) (12/13/88)
I have several different projects that compile several different, but related standalone code resources (XFCN's). It would simplify my life greatly I could have all of the code resources in one resource file. Is there a way to do this from seperate projects, or do I need to do it from one project (which wouldn't be such a bad idea, after all)... or is it possible at all? thanks, b.bum wb1j+@andrew.cmu.edu
nick@lfcs.ed.ac.uk (Nick Rothwell) (12/14/88)
In article <MXd8Jvy00UgX4894xQ@andrew.cmu.edu> wb1j+@andrew.cmu.edu (William M. Bumgarner) writes: >I have several different projects that compile several different, but >related standalone code resources (XFCN's). It would simplify my >life greatly I could have all of the code resources in one resource file. This sounds like the kind of problem I'm having too. I'm developing an application with some custom CDEF's. The work on the application is fine - I'm in LSC, so I can alter things, hit %R, try it out, and so on. It's a real shame that life isn't this easy when I'm developing the CDEF. I have to make an alteration, do a "Build Code Resource", wait for the linker, MultiFind across to ResEdit, open the application's resource file, delete the old CDEF, open the CDEF file, copy and paste the new CDEF across, MultiFind to LSC, close the CDEF project, open the Appl one. I may end up writing an application (sort-of like a ResEdit script) to automate the ResEdit stage - or am I making life difficult for myself somehow? Nick. -- Nick Rothwell, Laboratory for Foundations of Computer Science, Edinburgh. nick@lfcs.ed.ac.uk <Atlantic Ocean>!mcvax!ukc!lfcs!nick ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ...while the builders of the cages sleep with bullets, bars and stone, they do not see your road to freedom that you build with flesh and bone.
peirce@claris.com (Michael Peirce) (12/16/88)
In article <1154@etive.ed.ac.uk> nick@lfcs.ed.ac.uk (Nick Rothwell) writes: >In article <MXd8Jvy00UgX4894xQ@andrew.cmu.edu> wb1j+@andrew.cmu.edu (William M. Bumgarner) writes: >>I have several different projects that compile several different, but >>related standalone code resources (XFCN's). It would simplify my >>life greatly I could have all of the code resources in one resource file. > >This sounds like the kind of problem I'm having too. I'm developing an >application with some custom CDEF's. Not to bad mouth the THINK environments (I think they're GREAT!), but when developing non-application code resources MPW really shines. You just write a script that does the compile, link, rez, rename or move the file into other folders (like the system folder), etc... In fact, whenever I'm building something that is even mildly complex (i.e. not just a simple application), MPW scripts make it oh so easy. -- michael Claris Corp. | Michael R. Peirce -------------+-------------------------------------- | 440 Clyde Avenue | Mountain View, CA 94043 | (415) 960-4011 | MCI-Mail: mpeirce | AppleLink: peirce1 | Internet: peirce@claris.com | uucp: {ames,decwrl,apple,sun}claris!peirce
jmunkki@kampi.hut.fi (Juri Munkki) (12/18/88)
In article <1154@etive.ed.ac.uk> nick@lfcs.ed.ac.uk (Nick Rothwell) writes: >a real shame that life isn't this easy when I'm developing the CDEF. I have >to make an alteration, do a "Build Code Resource", wait for the linker, >MultiFind across to ResEdit, open the application's resource file, delete >the old CDEF, open the CDEF file, copy and paste the new CDEF across, >MultiFind to LSC, close the CDEF project, open the Appl one. If you make changes only to your CDEF, you can compile your application to something like myCDEF.rsrc and have your CDEF project named myCDEF. Set the resulting file type to APPL and you can directly transfer to it from the compiler. Of course you can do this the other way around too. Your CDEF project might create a myProgram.rsrc file that could then be used as the resource file for your application. _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._ | Juri Munkki jmunkki@hut.fi jmunkki@fingate.bitnet I Want Ne | | Helsinki University of Technology Computing Centre My Own XT | ~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~
beard@ux1.lbl.gov (Patrick C Beard) (12/19/88)
Except for one thing, LSC code resources, FKEYs, DAs, you name it, support global variables. In MPW, you have to do that in ASM. Just thought I'd put in my $.02. Patrick Beard Lawrence Berkeley Laboratory
leonardr@uxe.cso.uiuc.edu (12/20/88)
nick@lfcs.ed.ac.uk(Nick Rothwell) in comp.sys.mac.programmer >In article <MXd8Jvy00UgX4894xQ@andrew.cmu.edu> wb1j+@andrew.cmu.edu (William M. Bumgarner) writes: >>I have several different projects that compile several different, but >>related standalone code resources (XFCN's). It would simplify my >>life greatly I could have all of the code resources in one resource file. > >This sounds like the kind of problem I'm having too. I'm developing an >application with some custom CDEF's. The work on the application is fine - >I'm in LSC, so I can alter things, hit %R, try it out, and so on. It's >a real shame that life isn't this easy when I'm developing the CDEF. I have >to make an alteration, do a "Build Code Resource", wait for the linker, >MultiFind across to ResEdit, open the application's resource file, delete >the old CDEF, open the CDEF file, copy and paste the new CDEF across, >MultiFind to LSC, close the CDEF project, open the Appl one. > I may end up writing an application (sort-of like a ResEdit script) to >automate the ResEdit stage - or am I making life difficult for myself somehow? > I too had the same problem recently and what I ended up doing was using Hypercard (yes, Hypercard) and Steve Maller's ResCopy XCMD which allows you not only to bring up the dialog, but also (what I do) specify the source and destination files and the resource you want copied. I just put some quick scripts on top to allows me to secify which files and resources to copy and everything works great! (on my 5meg MacII) +---------------------------------+-----------------------------------+ + + Any thing I say may be taken as + + Leonard Rosenthol + fact, then again you might decide+ + President, LazerWare, inc. + that it really isn't, so you + + + never know, do you?? + + leonardr@uxe.cso.uiuc.edu + + + GEnie: MACgician + MacNET: MACgician + + Delphi: MACgician + AppleLink: D0025 + + + + +---------------------------------+-----------------------------------+
wb1j+@andrew.cmu.edu (William M. Bumgarner) (01/17/89)
The easiest solution would be to be able to append code resources to an already existing resource file... but that isn't possible becuase of the use of the standard SFPutFile dialog and the impending Replace sub-dialog. A possible feature in future updates, Rich? b.bum wb1j+@andrew.cmu.edu