Skip to main content

Good features of Eclipse3.5 (Eclipse Galileo) JDT


This blog will list down the new features of Eclipse Galileo JDT. I will write another blog regarding the features of Eclipse Helios and Eclipse Indigo.

Read about Eclipse Helios features @ http://tips4ufromsony.blogspot.com/2011/11/good-features-of-eclipse-36-eclipse.html

==========================================================
1. Toggle Breadcrumb —> Will list the name of the file and the method name with respect to your cursor position , on the top of the Eclipse IDE. From here you can go to other methods, other classes in same package , ….

Screen shot of Toggle Breadcrumb:



==========================================================
2. From the method call , you can either go to declaration or to implementation

Screen shot of implementation call:



==========================================================
3. Advanced Open Type –> You can restrict the open type to a selected Working set only.

Screen shot of Advanced Open Type:



==========================================================
4. Embedded Telnet connection window —> You can have the telnet connection as a window in Eclipse

Screen shot of Telnet connection:



==========================================================
5. Embedded Sql developer —> You can view the database tables , run queries , can see the history of queries ran and the results …

Screen shot of Sql Developer:



==========================================================
6. Enhanced Local History —> You can view all the changes that you made in a file in all the file save that you done. —> Just like clear case/SVN / CVS , you can compare with the previous versions of the files to see each line changes

Screen shot of Enhanced Local History:



==========================================================
7.A new property window to view the properties of the selected file

Screen shot of property window:



==========================================================

8.Exclude selected packages or files from the build path

Screen shot of Exclusion of build path:



==========================================================
9. Ctrl +3 —> Advanced quick access to the available screens by typing the start letters

Screen shot of Ctrl +3:



==========================================================

10. XML files can be open in a Design View

Screen shot of XML Design View:



==========================================================

11. Quick search in window – Preference

Screen shot of  Quick search in window – Preference:



Labels:

Comments

  1. Legin Kallarackal Antony31 October 2011 at 20:08

    Good materials to learn the features. We started using the Eclipse Indigo...waiting for the blog on that :-)

    ReplyDelete
  2. Sony Thomas1 November 2011 at 11:03

    Thank you Legin, will update you guys regarding the Eclipse Helios and Eclipse Indigo.

    ReplyDelete

Post a Comment

Popular posts from this blog

Google Chrome shortcut keys

If you are a Google Chromey guy, please find below the list of shortcut keys for some of the most used features  :-) Find more shortcut keys @  http://www.google.com/support/chrome/bin/static.py?page=guide.cs&guide=25799&topic=28650
4 comments
Read more

ATG - how to create and deploy a new atg module

ATG products are packaged as a number of separate application modules. Application modules exist in the ATG installation as a set of directories defined by a manifest file. To create a new module, follow the below steps : Create a module directory within your ATG installation.  Create a META-INF directory within the module directory. Note that this directory must be named META-INF.  Create a manifest file named MANIFEST.MF and include it in the META-INF directory for the module. The manifest contains the meta-data describing the module. A module located at <ATG2007.1dir>/MyModule is named MyModule and a module located at <ATG2007.1dir>/CustomModules/MyModule is named CustomModules.MyModule. Within the subdirectory that holds the module, any number of files may reside in any desired order. These files are the module resources (EAR files for J2EE applications, WAR files for web applications, EJB-JAR files for Enterprise JavaBeans, JAR files of Java class...
4 comments
Read more

ATG Search troubleshooting tips

In this blog, I have listed some basic ATG Search troubleshooting tips in some general scenarios. 1. If the index did not deploy, consider the following possible causes : Is the DeployShare property configured @ /atg/search/routing/LaunchingService component ?  Is enough space available @ deployment share box for the index ?  Are the RMI ports configured correctly in the RoutingSystemService component ?  If the search engine application is running in a separate box, this application is invoked through a RemoteLauncher running in these boxes. Check whether these RemoteLaunchers are running in these boxes ? 2. If you have trouble in launching one or more search engines, try the following remedies: If the Search engine is standalone, set the /atg/search/routing/LaunchingService component’s engineDir property to the absolute path of the Search engine directory.  3. Search unavailable in the estore page, even when the SearchEngine is in "Running" st...
5 comments
Read more

ATG Search - how estore(commerce instance) forms the search engine SOAP URL ?

The comminucation between the Commerce box and the Search engine is through SOAP. Read  more about this architecture @  http://tips4ufromsony.blogspot.in/2011/11/atg-search-architectural-flow-search.html The commerce instance forms the SOAP url just like the below code: private URL getSearchEngineURL(SearchEngine engine) {       SearchEnvironmentHost h =  engine.getSearchEnvironmentHost();       SearchMachine hi = h.getSearchMachine() ;       return new URL( "http://" + hi.getHostname() + ":" + engine.getPort() + "/AEXmlService/" );   } So the commerce instance need the hi.getHostname()  and engine.getPort() to form the url. It is obtained as below: 1. The component / atg/commerce/search/refinement/ CommerceFacetSearchService has the siteName defined, which will be pointing to the environment name defined in the Search Project. Read  more about this search project setup @  http://...
4 comments
Read more

ATG - more about Forms and Form Handlers

An ATG form is defined by the dsp:form tag, which typically encloses DSP tags that specify form elements, such as dsp:input that provide direct access to Nucleus component properties. Find below a sample dsp:form tag.    <dsp:form action="/testPages/showPersonProperties.jsp" method="post" target="_top">      <p>Name: <dsp:input bean="/samples/Person.name" type="text"/>      <p>Age: <dsp:input bean="/samples/Person.age" type="text" value="30"/>      <p><dsp:input type="submit" bean="/samples/Person.submit"/> value="Click to submit"/>    </dsp:form>   When the user submits the form, the /samples/Person.name property is set to the value entered in the input field.Unlike standard HTML, which requires the name attribute for most input tags; the name attribute is optional for DSP form element tags. If an input tag omits the n...
11 comments
Read more