<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>« Simple and Pragmatic Thoughts » &#187; Dislikes</title>
	<atom:link href="http://isagoksu.com/categories/development/developer-tools/dislikes/feed/" rel="self" type="application/rss+xml" />
	<link>http://isagoksu.com</link>
	<description>Nobody can be perfect, but you can think better, design better, and always use baby steps!</description>
	<lastBuildDate>Tue, 16 Mar 2010 03:39:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>OSX Keyboard Bindings Cheat Sheet</title>
		<link>http://isagoksu.com/2009/development/developer-tools/dislikes/eclipse/osx-keyboard-binding-cheat-sheet/</link>
		<comments>http://isagoksu.com/2009/development/developer-tools/dislikes/eclipse/osx-keyboard-binding-cheat-sheet/#comments</comments>
		<pubDate>Thu, 16 Jul 2009 07:29:08 +0000</pubDate>
		<dc:creator>Isa Goksu</dc:creator>
				<category><![CDATA[Eclipse]]></category>
		<category><![CDATA[bindings]]></category>
		<category><![CDATA[keyboard]]></category>
		<category><![CDATA[osx]]></category>
		<category><![CDATA[shortcuts]]></category>

		<guid isPermaLink="false">http://isagoksu.com/2009/general/osx-keyboard-binding-cheat-sheet/</guid>
		<description><![CDATA[It's very obvious to everyone who knows me that I hate Eclipse :) Since it's sort of a standard for all enterprise software companies, we all have to use it whether we like it or not. Anyway it's not a big deal, but I decided to share the OS X keyboard bindings cheat sheet for Eclipse that I've created for myself.]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s very obvious to everyone who knows me that I hate <strong>Eclipse</strong> :) Since it&#8217;s sort of a standard for all enterprise software companies, we all have to use it whether we like it or not. Anyway it&#8217;s not a big deal, but I decided to share the <em>OS X</em> keyboard bindings cheat sheet for <strong>Eclipse</strong> that I&#8217;ve created for myself. Since I&#8217;m not an expert <strong>Eclipse</strong> user, I created a keyboard bindings cheat sheet.</p>]]></content:encoded>
			<wfw:commentRss>http://isagoksu.com/2009/development/developer-tools/dislikes/eclipse/osx-keyboard-binding-cheat-sheet/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>How to Put Exception Breakpoint?</title>
		<link>http://isagoksu.com/2009/development/developer-tools/dislikes/eclipse/how-to-put-exception-breakpoint/</link>
		<comments>http://isagoksu.com/2009/development/developer-tools/dislikes/eclipse/how-to-put-exception-breakpoint/#comments</comments>
		<pubDate>Tue, 19 May 2009 04:21:11 +0000</pubDate>
		<dc:creator>Isa Goksu</dc:creator>
				<category><![CDATA[Eclipse]]></category>
		<category><![CDATA[breakpoint]]></category>
		<category><![CDATA[exception]]></category>
		<category><![CDATA[stupid]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://isagoksu.com/?p=398</guid>
		<description><![CDATA[If you're an IntelliJ user, there are many many ways to trace your code like Exception Breakpoints, Field Watchpoints, Method Breakpoints and even JS breakpoints :) Anyways, today I needed to trace an exception in one of Eclipse project for work.]]></description>
			<content:encoded><![CDATA[<p>Tracing <strong>stacktrace</strong> is sometimes very boring. Especially your code is not above certain quality. If you&#8217;re an <a href="http://intellij.com" title="IntelliJ Official Site" target="_blank">IntelliJ</a> user, there are many many ways to trace your code like Exception Breakpoints, Field Watchpoints, Method Breakpoints and even JS breakpoints :) Anyways, today I needed to trace an exception in one of Eclipse project for work. I was gonna place an <strong>Exception Breakpoint</strong>, but then I remember that this is not <a href="http://intellij.com" title="IntelliJ Official Site" target="_blank">IntelliJ</a>. So a little investigation showed me that it is possible to place an <strong>Exception Breakpoint</strong> in Eclipse as well. Here is how I do it:</p>]]></content:encoded>
			<wfw:commentRss>http://isagoksu.com/2009/development/developer-tools/dislikes/eclipse/how-to-put-exception-breakpoint/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>How to Exclude Files from Build Path?</title>
		<link>http://isagoksu.com/2009/development/developer-tools/dislikes/eclipse/how-to-exclude-files-from-build-path/</link>
		<comments>http://isagoksu.com/2009/development/developer-tools/dislikes/eclipse/how-to-exclude-files-from-build-path/#comments</comments>
		<pubDate>Sat, 04 Apr 2009 04:24:03 +0000</pubDate>
		<dc:creator>Isa Goksu</dc:creator>
				<category><![CDATA[Eclipse]]></category>
		<category><![CDATA[build]]></category>
		<category><![CDATA[exclude]]></category>
		<category><![CDATA[path]]></category>
		<category><![CDATA[stupid]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://isagoksu.com/?p=283</guid>
		<description><![CDATA[Anyways :) Let's get back to tip :) If you're having trouble with a legacy unit test, and if your build is failing, sometimes you might want to exclude those failing tests from build path.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m known as an enemy for Eclipse, &#8216;coz I hate it. And I&#8217;ll stick to be like this till they change some major usability issues. And one more final side-note; yes Eclipse RCP sucks!</p>]]></content:encoded>
			<wfw:commentRss>http://isagoksu.com/2009/development/developer-tools/dislikes/eclipse/how-to-exclude-files-from-build-path/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

