Google Web Toolkit (GWT)

-

[GWT] Tutorials - Overview (gwtproject.org)


GWT is a development toolkit for building and optimizing complex browser-based applications.
GWT is used by many products at Google, including Google AdWords and Orkut.
GWT is an open source.
licensed under the Apache License version 2.0.

Google Web Toolkit (GWT) is a development toolkit to create RICH Internet Applications (RIA).
GWT provides developers option to write client-side application in JAVA.
GWT compiles the code written in JAVA to JavaScript code.
Application written in GWT is cross-browser compliant. GWT automatically generates javascript code suitable for each browser.
GWT is a framework to build large scale and high-performance web application while keeping them as easy-to-maintain.

Advantages of GWT
GWT provides easy integration with Junit and Maven.
Again, being Java based, GWT has a low learning curve for Java Developers.
GWT generates optimized javascript code, produces browser's specific javascript code by self.
GWT provides Widgets library provides most of tasks required in an application.
GWT is extensible and custom widget can be created to cater to application needs.

Disadvantages of GWT
Not Indexable − Web pages generated by GWT would not be indexed by search engines because these applications are generated dynamically.
Not Degradable − If your application user disables Javascript then user will just see the basic page and nothing more.
Not Designer's Friendly − GWT is not suitable for web designers who prefer using plain HTML with placeholders for inserting dynamic content at later point in time.

The GWT Components
The GWT framework can be divided into following three major parts −
1. GWT Java to JavaScript compiler 
2. JRE Emulation library − Google Web Toolkit includes a library that emulates a subset of the Java runtime library. The list includes java.lang, java.lang.annotation, java.math, java.io, java.sql, java.util and java.util.logging
3. GWT UI building library − This part of GWT consists of many subparts which includes the actual UI components, RPC support, History management, and much more.




Comments

Post a Comment

Popular posts from this blog

PL/SQL

-
PL/SQL PL/SQL stands for Procedural Language extensions to the Structured Query Language (SQL). PL/SQL can execute a number of queries in one block using single command. One can create a PL/SQL unit such as procedures, functions, packages, triggers, and types, which are stored in the database for reuse by applications. The PL/SQL engine resides in the Oracle engine. The Oracle engine can process not only single SQL statement but also block of many statements. Structure of PL/SQL Block: DECLARE     declaration statements; BEGIN     executable statements EXCEPTIONS     exception handling statements END; / Example : SET SERVEROUTPUT ON; SQL> DECLARE        var varchar2(40) := 'I love GeeksForGeeks' ;      BEGIN        dbms_output.put_line(var);      END;      / PL/SQL Functions PL/SQL functions are reusable blocks of code that can be used to perform specific tasks. They are...
Read more

JAVA8 Features

-
Java8 Features 1) Lambda Expressions : Concise functional code using ->. Lambda Expression basically expresses an instance of the functional interface, Lambda Expression provides a clear and concise way to represent a method of the functional interface using an expression. 2) Functional Interfaces : Single-method interfaces. An interface that contains only one abstract method is known as a functional interface. There is no restriction, that can have n number of default and static methods inside a functional interface. A functional interface is an interface that contains only one abstract method.  @FunctionalInterface annotation is used to ensure that the functional interface can’t have more than one abstract method. Runnable, ActionListener, and Comparable are some of the examples of functional interfaces.   Runnable –> This interface only contains the run() method.   Comparable –> This interface only contains the compareTo() method.   ActionListener –> ...
Read more

Build Automation

-
ANT: Ant was the first build tool released in 2000. Ant was developed on procedural programming idea. Ant was improved with an ability to accept plug-ins and dependency management over the network, with the help on Apache-IVY. Drawbacks: 1) XML is used as a format to write the build scripts. 2) Being hierarchical is not good for procedural programming, and 3) XML is relatively unmanageable.   MAVEN: Maven was introduced in 2004. Maven relied on the conventions and was able to download the dependencies over the network. Benefits : Life cycle of Maven, while following the same life cycle for multiple projects continuously. Problems: 1) Maven does not handle the conflicts between versions of the same library. 2) Complex customised build scripts are difficult to write in Maven, as compared to writing the build scripts in ANT. GRADLE : Gradle came into picture in 2012 Features  Declarative builds and build-by-convention 1) Gradle is available with separate Domain Specific Language ...
Read more