However, even with ssh'ing into separate CS machines, the X-forwarding of logisim can be a bit slow. And, if you just can't stand it, you can avoid the lag by temporarily installing logisim on the ITS machine and use logisim locally (saving your work periodically as you go). If you do this it is VERY IMPORTANT that you copy your .circ file back to your CS account BEFORE logging out of the ITS machine, otherwise you will lose all your work.
For example, from a shell on the ITS machine you can copy over files from your CS account by doing the following:
cd Desktop # let's just copy stuff to Desktop # copy the alu.circ file from your CS account to the ITS machine scp your_user_name@cs.swarthmore.edu:./cs31/labs/02/alu.circ . # you can use the -r flag to scp to copy over an entire subdirectory contents: scp -r your_user_name@cs.swarthmore.edu:./cs31/labs/02 . open alu.circ # should start logisim on this file
# copy the alu.circ file from the ITS machine back to your CS account scp alu.circ your_user_name@cs.swarthmore.edu:./cs31/labs/02/alu.circIf you forget this step, you will lose all the work you saved on the ITS machine, which may be reason enough to endure the X-forwarding lag of ssh'ing into your CS machine and running logisim there.
You can (and I'd suggest that you do) periodically scp the changes to your .circ file back to your CS account as you work on an ITS machine.