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:



Comments

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

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

    ReplyDelete

Post a Comment

Popular posts from this blog

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...

Search Facets - how to create a new search facets in ATG Search

A Facet is a search refinement element that corresponds to a property of a commerce item type. ATG supports the search result refinement using the Faceted Search concept. Read more about facted search @  http://en.wikipedia.org/wiki/Faceted_search . Facet can either be ranges or specific values. Each facet is stored in the RefinementRepository as a separate refineElement repository item. Facets are divided into Global and Local facets. Global facets apply to all the categories and local facets only to the category in which they are created. For example Price/Brand can be considered as the facets that are common for all skus and New Release/Coming Soon can be considered as the facets that are specific to Physical Media products like Vidoe/DVD/Blue-ray/Books. We can use the ATG BCC - Merchandising UI to create facets. The Faceting Property depends on the meta-properties defined in the \atg\commerce\search\product-catalog-output-config.xml ( the def...

Basic design decisions for a commerce search setup ( with an ATG Search view)

In this blog I would like to explain the basic set of configuration/design decisions needed to setup an ATG search project. Most of these design decisions are common for all Enterprise search applications. 1. Decide the searchable properties :   This means the properties that the business want the user to search in the ecommerce platform. In ATG search these are configured as the text properties in the product-catalog-output-config.xml ( the definitionFile of the \atg\commerce\search\ProductCatalogOutputConfig). Usually the displayName of product/sku, displayName of department/category/sub-category, skuId, brandName are the properties configured as searchable. 2. Decide the search refinement properties or the faceted properties :   After a user search for a keyword, search refinement is the next step done to filter his results. ATG supports the search refinement using the Faceted Search concept. Read more about facted search @...

ATG Product Catalog schema ER diagram

Check out the O rder schema ER-Diagram @   http://tips4ufromsony.blogspot.in/2012/02/atg-order-schema-er-diagram.html Check out the User Profile  schema ER-Diagram @ http://tips4ufromsony.blogspot.in/2012/03/atg-user-profile-schema-er-diagram.html If you would like to know the relationship between different Product Catalog tables, please find below screen shots of  Product Catalog schema ER Diagrams.

ATG Search and Search engine activity log

We could use the SearchEngineActivity log files to get the request/response to the search engine from a commerce instance. This folder is located in each commerce instance or the instances from which the call to the search engine is done. The SearchEngineActivity log file folder can be configured @ SearchEngineService component ( /dyn/admin/nucleus/atg/search/routing/SearchEngineService). To get the log files for the search engine calls, you need to specify the SearchEngineService.dumpingRequests as true. Then you need to specify the engineActivityPath as the folder in which you need the SearchEngineActivity logs. Below you could find my SearchEngineActivity log folder. Each successful call to the search engine from the commerce instance will create 5 files in the SearchEngineActivity folder : namely  request, response, search engineinfo, stack trace and response row . Each file name start with a specific sequence. You ...