Text Editing - Revision history

Shane at 07:57, 8 April 2013

2013-04-08T07:57:14Z

Shane at 07:51, 1 December 2012

2012-12-01T07:51:41Z

Shane: /* Step 1: Choose Your Interface */

2012-12-01T07:46:05Z

Step 1: Choose Your Interface

Shane: /* Step 1: Choose Your Interface */

2012-12-01T07:45:27Z

Step 1: Choose Your Interface

Shane at 05:29, 26 September 2012

2012-09-26T05:29:41Z

Shane: moved Text Editors to Text Editing

2012-09-26T05:27:48Z

moved Text Editors to Text Editing

Shane at 05:24, 26 September 2012

2012-09-26T05:24:50Z

Shane: Created page with 'This page will contain info on text editors.'

2012-09-26T04:22:26Z

Created page with 'This page will contain info on text editors.'

New page

This page will contain info on text editors.

← Older revision		Revision as of 07:57, 8 April 2013
Line 1:		Line 1:
		+	'''''This article contains workflow recommendations from previous semesters of CSE 330. You should now instead refer to the [[Workflow]] guide.'''''
		+
	Okay, so you've set up your server and are ready to start writing HTML, CSS, PHP, Python, and Ruby. How can you do it?		Okay, so you've set up your server and are ready to start writing HTML, CSS, PHP, Python, and Ruby. How can you do it?

Line 70:		Line 72:

	[[Category:Module 2]]		[[Category:Module 2]]
		+	[[Category:Obsolete Content]]

@@ Line 11: / Line 11: @@
 # You can use a full-scale integrated development environment (IDE), like [http://www.aptana.com/ Aptana Studio -- Eclipse] (open source) or [http://www.jetbrains.com/phpstorm/ PHPStorm] (paid, but highly recommended).
-The most important aspect to consider is what you are most comfortable using.  In particular, ''you don't have to keep using command-line text editors for this class.''  The graphical user interface was invented for a reason.  Don't feel like using vi or emacs will make you a good programmer, because I promise: ''it doesn't''.  If you like emacs or vi, that's great, but know that there are other equally powerful options.
+The most important aspect to consider is what you are most comfortable using.  In particular, ''you do NOT need to use command-line text editors as your primary development environment  in this class.''  The graphical user interface was invented for a reason.  Don't feel like using vi or emacs will make you a good programmer, because I promise: ''it doesn't''.  If you like emacs or vi, that's fine, but know that there are other equally powerful options.
 == Step 2: Set Up Your Editor ==
@@ Line 67: / Line 67: @@
 If you need help setting up an SSH filesystem or an SFTP client, you may ask a TA.  Once everything is up and running, you will be able to easily upload files to your server for the remainder of this course.
-'''To reiterate:''' It is highly recommended, although not required, to backup files using SVN no matter how you edit and save them.
+'''To reiterate:''' It is ''highly'' recommended, albeit not ''required'', to backup files using SVN no matter how you edit and save them.  If you accidentally terminate your instance but didn't save your files to your SVN, don't expect a large amount of sympathy.  ;-)
 [[Category:Module 2]]

@@ Line 9: / Line 9: @@
 # You can use a command-line text editor, like emacs, vi, or nano.
 # You can use a GUI text editor, like Notepad++ or TextWrangler.
-# You can use a full-scale integrated development environment (IDE), like [http://www.aptana.com/ Aptana Studio -- Eclipse] (open source) or [http://www.jetbrains.com/phpstorm/ PHPStorm] (paid).
+# You can use a full-scale integrated development environment (IDE), like [http://www.aptana.com/ Aptana Studio -- Eclipse] (open source) or [http://www.jetbrains.com/phpstorm/ PHPStorm] (paid, but highly recommended).
 The most important aspect to consider is what you are most comfortable using.  In particular, ''you don't have to keep using command-line text editors for this class.''  The graphical user interface was invented for a reason.  Don't feel like using vi or emacs will make you a good programmer, because I promise: ''it doesn't''.  If you like emacs or vi, that's great, but know that there are other equally powerful options.

@@ Line 9: / Line 9: @@
 # You can use a command-line text editor, like emacs, vi, or nano.
 # You can use a GUI text editor, like Notepad++ or TextWrangler.
-# You can use a full-scale integrated development environment (IDE), like Eclipse.
+# You can use a full-scale integrated development environment (IDE), like [http://www.aptana.com/ Aptana Studio -- Eclipse] (open source) or [http://www.jetbrains.com/phpstorm/ PHPStorm] (paid).
 The most important aspect to consider is what you are most comfortable using.  In particular, ''you don't have to keep using command-line text editors for this class.''  The graphical user interface was invented for a reason.  Don't feel like using vi or emacs will make you a good programmer, because I promise: ''it doesn't''.  If you like emacs or vi, that's great, but know that there are other equally powerful options.

← Older revision		Revision as of 05:29, 26 September 2012
Line 68:		Line 68:

	'''To reiterate:''' It is highly recommended, although not required, to backup files using SVN no matter how you edit and save them.		'''To reiterate:''' It is highly recommended, although not required, to backup files using SVN no matter how you edit and save them.
		+
		+	[[Category:Module 2]]

← Older revision	Revision as of 05:27, 26 September 2012
(No difference)

← Older revision		Revision as of 05:24, 26 September 2012
Line 1:		Line 1:
−	This ~~page~~ will ~~contain info~~ on text ~~editors~~.	+	Okay, so you've set up your server and are ready to start writing HTML, CSS, PHP, Python, and Ruby. How can you do it?
		+
		+	It is essential that you set up a workflow that suits your needs. Reading this article will make your life 10× easier for the rest of the semester.
		+
		+	== Step 1: Choose Your Interface ==
		+
		+	You first need to choose how you want to approach file editing. You have a few choices:
		+
		+	# You can use a command-line text editor, like emacs, vi, or nano.
		+	# You can use a GUI text editor, like Notepad++ or TextWrangler.
		+	# You can use a full-scale integrated development environment (IDE), like Eclipse.
		+
		+	The most important aspect to consider is what you are most comfortable using. In particular, ''you don't have to keep using command-line text editors for this class.'' The graphical user interface was invented for a reason. Don't feel like using vi or emacs will make you a good programmer, because I promise: ''it doesn't''. If you like emacs or vi, that's great, but know that there are other equally powerful options.
		+
		+	== Step 2: Set Up Your Editor ==
		+
		+	This section covers how to configure your editor of choice to be most efficient at web development.
		+
		+	=== Command Line Text Editors ===
		+
		+	The communities behind command-line text editors are strong, and so there are plugins available to make your editor of choice more well suited to programming in HTML, CSS, PHP, and other web languages. Here are some links to tutorials that will show you how to set up your command line text editor of choice:
		+
		+	* '''Emacs:''' http://emacswiki.org/emacs/PhpMode
		+	* '''Vim:''' http://net.tutsplus.com/sessions/vim-essential-plugins/
		+	* '''Nano:''' http://www.nublue.co.uk/blog/tuning-nano-for-web-development-syntax-highlighting/
		+
		+	=== Graphical Text Editors ===
		+
		+	Notepad++ and TextWrangler are free GUI text editors for Windows and Mac OS X, respectively. You can download them from here:
		+
		+	* '''Notepad++:''' http://notepad-plus-plus.org/ (you might want to save it to your H: drive)
		+	* '''TextWrangler:''' Available from the Mac App Store or from http://www.barebones.com/products/TextWrangler/
		+
		+	There are tools available for both to speed up your web development routine. Here are some helpful web sites:
		+
		+	* '''Notepad++:''' http://adamzwakk.com/?p=512
		+	* '''TextWrangler:''' http://magp.ie/2011/01/10/tidy-and-format-your-php-and-meet-wordpress-standards-on-coda-and-textwrangler/
		+
		+	=== Integrated Development Environment ===
		+
		+	'''Aptana''' is a web development toolkit that can be installed as a plugin to Eclipse or as a separate application. Web site: http://www.aptana.com/
		+
		+	Follow these instructions to install Aptana as a plugin to Eclipse.
		+
		+	# In Eclipse, go to '''Install New Software...'''
		+	# Add the following URL: http://update.aptana.com/update/studio/
		+	# Load the packages and install Aptana Studio.
		+	# Restart Eclipse.
		+	# In the Aptana Studio welcome screen, go to Plugins
		+	# Install the Aptana Studio PHP plugin
		+	# Restart Eclipse again.
		+
		+	== Step 3: Saving Your Project ==
		+
		+	If you edit your files directly on the server using a command-line text editor, you can use them right away. However, if you do, you are in danger of accidentally losing your code because you don't have it backed up anywhere. It is easy to destroy your entire project by pressing the wrong key in vim/emacs/nano! CSE330 students in past semesters have lost days worth of work because they used vim/emacs/nano to edit their files but didn't commit them to SVN.
		+
		+	If you edit your files on your desktop, you will always have a second copy, so this is less of an issue. However, since SVN is a version control system, you should still backup your files to SVN at the end of the day.
		+
		+	=== Uploading Files to Your Server ===
		+
		+	If you edit files on your desktop, there are several ways to upload those files to your server.
		+
		+	* If you edit the files in Eclipse, just commit changes to your repository, and on your server, run <code>svn update</code> to pull the changes down. This works best if you have [[Web Server Configuration#Pointing Apache to your Repository\|configured Apache to point to your SVN repository]].
		+	* You can use as SSH filesystem client to make local files automatically update on your server. For instructions, see [[Web Server Configuration#SSHFS\|the Web Server Configuration guide]] from Module 1.
		+	* You can use an SFTP client like FileZilla (universal) or WinSCP (if on Windows) to upload files to your server. For instructions, see [[Web Server Configuration#SFTP\|the Web Server Configuration guide]] from Module 1.
		+
		+	If you need help setting up an SSH filesystem or an SFTP client, you may ask a TA. Once everything is up and running, you will be able to easily upload files to your server for the remainder of this course.
		+
		+	'''To reiterate:''' It is highly recommended, although not required, to backup files using SVN no matter how you edit and save them.