Path: csiph.com!news.swapon.de!news.szaf.org!3.eu.feeder.erje.net!feeder.erje.net!nntp.comgw.net!peer03.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!peer05.ams1!peer.ams1.xlned.com!news.xlned.com!fx15.ams4.POSTED!not-for-mail From: Speccie Mime-Version: 1.0 User-Agent: Hogwasher/5.24 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Message-ID: <0001HW.2E97969502E2F6EC30D87C38F@eu.astraweb.com> Subject: Re: Integrated development on emulators: The next step Newsgroups: comp.sys.apple2.programmer Reply-To: someone@somewhere.com References: Lines: 11 X-Complaints-To: https://www.astraweb.com/aup NNTP-Posting-Date: Thu, 09 Oct 2025 07:07:01 UTC Date: Thu, 09 Oct 2025 08:07:01 +0100 X-Received-Bytes: 1491 Xref: csiph.com comp.sys.apple2.programmer:6334 > You've basically described the dream workflow for a lot of retro developers. Having the edit-assemble-test loop all happen in one environment without swapping files around is a huge time saver. I have never found that to be a problem. I write the code files in BBEdit on the Mac that Sweet16 is running on, then have a Favourite entry in SAFE2 on the emulated IIgs pointing to tthe folder on the Mac where the source files are saved. It then takes seconds to copy the file or files over, and start the assembly in ORCA/M. I don’t of course need to run BBEdit on the same Mac. As long as the computer I am writing the source files on can be reached by FTP, that sequence works just the same... Cheers - Speccie