To Summarise: Problem 0: You transport development code (projects) between school & home on your USB disk. The USB disk gets different drive letter depending on the computer you plug it in to so the J installation on your roaming profile doesn't know where to find your projects.
Problem 1: When you build your project(s), the desired location of the build target depends on whether you are at work or at home. Problem 2: Keeping a back up of development code. I solve problems 0 & 2 myself by using a source code management (SCM) solution. The code repository is available to me both at work and at home (via the internet) so it is easy to update the local versions at my current location with any changes I made somewhere else. As a bonus not only is the most current version automatically backed up, but all the interim versions are as well! Is there a reason you haven't gone down this route? I think I'd solve Problem 1 by using a custom build script that detected whether I was at home or work (e.g. IP number, available drives, hostname, or it could prompt you) and chose/built the path for the build target appropriately. What do the "clueless teachers" have on their USB drives? How does that fit in to the problem? > From: Henry Rich > > This looks like getting somewhere. A change to cfgread.ijs, if it > could > be thought out & made standard, would be a step forward. > > "Put J on your USB drive" is not part of a solution, though. It would > work for me, but there are lots of clueless teachers at school and they > need to be able to plug in their USB drive and click the icon on their > machine to start my app. The app MUST be on a shared disk and J must > come from the school computer, NOT the USB drive. > > Henry > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
