I tried just using one preview window, but that meant I had to close and open a preview each time I switched pages. I tiled the preview windows to help, but got confused as to which preview window to look at when I made a change to a HTML file. This is because BBEdit’s preview window is tied to the editor frame that is current when opening it, and it does not switch when you change to another editor frame containing a different file. I needed one BBEdit project window open for the mockup HTML (bottom left), another project window open for the processor’s templates (top left) and one preview window open for each page being mocked up. As you do.īut that led to a problem, one of navigation. I would then copy the final pages to a new BBEdit project where I could then insert the payment processor’s funky markup to make it work. So, my plan was to mock up the pages as plain old HTML and use BBEdit’s live preview window to check that it looked right. BBEdit’s handling of HTML and CSS is excellent. Since our payment processor’s servers could only handle plain-old HTML and CSS files, this looked like a job for my trusty hammer tool, BBEdit. Think of it as a customized set of Paypal pages that run on Paypal’s servers, yet are customized to the look and feel of the parent. This was for some non-profits to enable them to accept credit-card donations and electronic payment of member fees. Last week I was working on an odd project to create a set of web pages that would be hosted on a payment processor’s site, but must look and feel like they are running on the actual site. Unless it was to trigger a software update. I upgraded to Panic’s Coda 2 when it came out, and never used it.

Coda 2 editor