CPSC 225 Lab 1 Spring 2022 CPSC 225 Intermediate Programming Spring 2022 Lab 1: Linux and Eclipse Due: Tue Feb 1 at the start of lab Introduction This lab will introduce you to the computing and programming environment used in many of the CS courses at HWS. You'll learn how to start Linux, navigate the desktop, navigate the file system and copy files, and print things. You'll also learn about Eclipse, a professional-grade tool for Java development. A couple of notes: This lab contains a lot of information. Don't worry about memorizing all of the details right now! Instead, the key things are to make sure you understand the material as you work through the lab and that you remember (only) what topics are covered (e.g. there's something about printing) - you can come back and look up the specifics of how to print when you need them. Have an idea of what you expect to happen when you do something (so you can tell if it did or didn't work), and don't ignore something that you don't understand or that isn't what you expect - ask! You want to catch any problems quickly, and asking about things you don't know is how you build knowledge and experience. At least skim through the handout(s) even if you've used Linux and/or Eclipse before; you might find something new that you didn't know. About Due Dates Labs are due at the start of lab on the date listed. It is OK to hand in your files at the very beginning of lab, but you should not be spending part or all of a lab period finishing up the previous week's lab. Collaboration Policy This lab is a bit different from the others - you are learning to use some systems rather than producing a program, and everyone needs do the setup and configuration for themselves. There are no limits on getting help, and you can work through the lab together with someone else if you want (as long as you are both doing the steps for yourselves). Exercises Do these exercises in order. Read through The Math/CS Linux System at HWS document ("The Commandline" is optional - skip it for now), performing the steps outlined with a reddish-brown box. (While you should perform the steps in order, it is a good idea to read through all of each section to get an overview of what is there before beginning to carry out any of the marked steps in that section.) This is a demonstration of the step-marking system. This is only a demonstration. If this were an actual step to follow, there would be instructions here. Read through Using Eclipse document, performing the steps outlined with a reddish-brown box. Create a text file called answers.txt (named exactly as directed, case and all) in your lab1 project in Eclipse: Right-click on the project name in the Package Explorer on the left side of the workbench and choose "New"→"Untitled Text File". You should get a new editor tab. Put your name at the beginning of the file. Save. Choose your lab1 directory as the parent folder and enter answers.txt for the filename. Verify in the Package Explorer that answers.txt is under the top-level lab1 project folder, not inside src. Then answer the following questions, adding your responses to answers.txt. Is it legal to put spaces in filenames in Linux? Is it a good idea? Explain. For each of the following, give the full path name (starting from the filesystem root) for the file or directory mentioned. If there is more than one way to write the path (e.g. using shortcuts), give at least one alternative in addition to the full name. Your workspace directory. The project directory for your lab1 project. (It's in your workspace directory and has the same name as your project.) The answers.txt file where you are writing these answers. Your HelloWorld.java file. The Using Linux at HWS web site also contains a lot of information about the Linux environment at HWS. Use the "Emergencies" section to answer the following questions: (add the answers to answers.txt) If you accidentally delete a file, is there anything you can do to get that file back? Explain. Rebooting the Lansing lab computers should be avoided if possible because other users might be logged into the system remotely. If a program crashes or the computer freezes, what are two strategies for fixing problems that don't involve rebooting the computer? Almost done! The last step is to hand in your work as described in the "Handin" section below. Also remember to reboot your computer (Rosenberg 009) or log out (Lansing 310) when you leave the lab. Handin Handing in your labs and projects means copying all of the relevant files to your subdirectory within the course handin directory: Make sure all your Java files have been auto-formatted and saved. Copy the Eclipse project directory (and its contents) into your handin directory. (Note, just the project directory, not your entire workspace!) This is ~/cs225/workspace/lab1 (if you named everything as directed - if you didn't, fix that first!). Your handin directory is in /classes/cs225/handin and is identified by your username. You have full access to your own handin directory - you can copy files there, remove files you didn't mean to hand in, etc. Check that everything got handed in correctly - your handin directory should contain a directory lab1 which in turn contains a file answers.txt and a subdirectory src. Within src should be your project's three Java files - HelloWorld.java, Person.java, and JavaFXDemo.java. Make sure you have the case right! (e.g. Lab1 is not the same as lab1.) It is OK if you have extra things within lab1 (such as a bin directory) as long as the required elements are named/organized as directed. If You Have Time If you finish early, explore more about Linux and Cinnamon (such as the commandline) and/or about Eclipse. last updated: --Tue Jan 25 08:43:42 EST 2022-- page owned by: bridgeman@hws.edu
