Eclipse is one of the most popular tools used by web designers all over the world.
1. Text File Encoding: Under the default setting eclipse uses the encoding that suits your operating system. But if you’re looking to build a platform independent application then you will have to use the UTF-8 encoding. This takes care of problems with issues with special characters when running on a different OS. You can do this from the Preferences Menu -> General -> Workspace from your project specific settings.
2. Save automatically: Before starting on a build, choose the save automatically feature. This makes it easier to work on your project. This you can do from Preferences -> General -> Workspace.
3. Type Filters: This one is especially useful for RCP and SWT developers. Type filters can be used in order to remove suggestions for specific types like classes, interfaces etc. from the ‘Open Type’ dialog. These can be set from Preferences -> Java -> Appearances -> Type Filters.
4. “Step Filtering” not Debugging: This can be used in order to remove the types that you don’t want to see during debugging. Many developers like to do this as it helps them focus on the actual code without being distracted by other tasks. It is available under Preferences -> Java -> Debug -> Step Filtering.
5. Launch the previously launched application: This is important because it makes sure that the last configuration that you used is used in your new project as well. Without this, Eclipse’s default setting is to try to determine what the most appropriate configuration for the current projectis. You can set this using Preferences -> Run/Debugg-> Launching.
6. Store your Launch Configuration in a Project: The launch configuration is often something that developers spend a lot of time on. This can be saved into a file that can be further used in your various projects or builds. This comes from Menu -> Run -> Run Configurations -> Launch Configuration Tab -> Common.
7. Make a Launch Configuration always appear in the Menu: You can choose your favourite launch configuration and make them your permanent launch or debug menu. For this go to, Menu: Run -> Run Configurations -> Launch Configuration.
8. Organise imports on save: Removing and changing codes can lead to imported files becoming obsolete. In order to fix this and organise your import you will need to use Shift+Ctrl+o for Windows and Shift+CMD+o on Mac. This can be done from Preferences -> Java ->Editor -> Save Actions or in project specific settings.
9. Format edited lines on save: No matter who rode it, the Eclipse IDE makes sure that the code look uniform irrespective of who is writing the code. In this though, it is advisable to format only the edited lines of a code rather than formatting the entire body.
10.The code formatter in Eclipse is a very useful thing. It ensures that the code looks consistent in your projects — no matter who wrote it — and can be easily read and understood by anyone else. But, formatting the whole file can seriously mess up a diff between two versions of the file. So ‘format only edited lines on save’ might be the right choice if you want the have your code formatted and still be able to see what was changed in your code later on. This is available from Preferences > Java > Editor > Save Actions.
Enjoy Eclipse
Shivam Kotwalia, CodeKill
| It is surprising how many well trained and experienced developers use Eclipse in an inefficient manner. Many don't know how useful the IDE can actually be. Here are 10 tricks that will help you manage Eclipse and boost your productivity. |  |
2. Save automatically: Before starting on a build, choose the save automatically feature. This makes it easier to work on your project. This you can do from Preferences -> General -> Workspace.
3. Type Filters: This one is especially useful for RCP and SWT developers. Type filters can be used in order to remove suggestions for specific types like classes, interfaces etc. from the ‘Open Type’ dialog. These can be set from Preferences -> Java -> Appearances -> Type Filters.
4. “Step Filtering” not Debugging: This can be used in order to remove the types that you don’t want to see during debugging. Many developers like to do this as it helps them focus on the actual code without being distracted by other tasks. It is available under Preferences -> Java -> Debug -> Step Filtering.
5. Launch the previously launched application: This is important because it makes sure that the last configuration that you used is used in your new project as well. Without this, Eclipse’s default setting is to try to determine what the most appropriate configuration for the current projectis. You can set this using Preferences -> Run/Debugg-> Launching.
6. Store your Launch Configuration in a Project: The launch configuration is often something that developers spend a lot of time on. This can be saved into a file that can be further used in your various projects or builds. This comes from Menu -> Run -> Run Configurations -> Launch Configuration Tab -> Common.
7. Make a Launch Configuration always appear in the Menu: You can choose your favourite launch configuration and make them your permanent launch or debug menu. For this go to, Menu: Run -> Run Configurations -> Launch Configuration.
8. Organise imports on save: Removing and changing codes can lead to imported files becoming obsolete. In order to fix this and organise your import you will need to use Shift+Ctrl+o for Windows and Shift+CMD+o on Mac. This can be done from Preferences -> Java ->Editor -> Save Actions or in project specific settings.
9. Format edited lines on save: No matter who rode it, the Eclipse IDE makes sure that the code look uniform irrespective of who is writing the code. In this though, it is advisable to format only the edited lines of a code rather than formatting the entire body.
10.The code formatter in Eclipse is a very useful thing. It ensures that the code looks consistent in your projects — no matter who wrote it — and can be easily read and understood by anyone else. But, formatting the whole file can seriously mess up a diff between two versions of the file. So ‘format only edited lines on save’ might be the right choice if you want the have your code formatted and still be able to see what was changed in your code later on. This is available from Preferences > Java > Editor > Save Actions.
Enjoy Eclipse
Shivam Kotwalia, CodeKill
No comments:
Post a Comment