Skip to main content

Pros and Cons of using DOJO

DOJO is one of the leading JavaScript framework, and few of its competitors are JQuery and YUI.

There are few reasons why anyone would want to use a JavaScript framework like DOJO. 
Since these toolkits provides lot of features out of the box

example:
  1.       Rich html components (i.e. Tables, Menus, Textboxes, buttons, Tooltip, Dialog box etc)
  2.       Event handling (ie onclick, onhover etc)
  3.       AJAX

As we all know the issues(i.e browser incompatibility and many more) we encounter if we write all of these things in regular JavaScript, HTML and CSS. So using any JavaScript library makes a better choice.

Let me summarize my experience using DOJO. First the good things

  1. DOJO has all the components you would most likely use (i.e Calendar, Menus, Trees, Validation, Grids, Event Propagations, Layouts etc)
  2. DOJO supports different themes (i.e Tundra, Soria etc). Also you can write your own look and feel and customize accordingly
  3. DOJO executes fastest on the browser
  4. DOJO is more mature than its competitors (i.e it has enterprise grade quality)
Now comes the bad things which are not exactly bad but could have been better
  1. Less documentation or not a vibrant community who would like to share there hacks
  2. DOJO library is around 1MB of size (i.e problem if your clients doesn't have good bandwidth)
checkout Dojo home page http://www.dojotoolkit.org/ for more updates 






Comments

Jun Zhang said…
"DOJO executes fastest on the browser" Are you kidding me?
vasudha dharani said…
DOJO Toolkit Online Training - 21st Century Software ...
www.21cssindia.com/courses/dojo-toolkit-online-training-174.html
DOJO Toolkit Online Training, DOJO Toolkit training, DOJO Toolkit course contents, DOJO Toolkit , call us: +919000444287,dharani@21cssindia.com.
Nebuna La Cap said…
bad: the messiest markup i have EVER seen

Popular posts from this blog

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax.

Example 1: Stores list of Strings in an Entity

@Entity
public class Users implements Serializable {

    private static final long serialVersionUID = 1L;
    @Id
    @GeneratedValue(strategy = GenerationType.AUTO)
    private Long id;
@ElementCollection
    private List<String> certifications = new ArrayList<String>();

    public Long getId() {
        return id;
    }

    public void setId(Long id) {
        this.id = id;
    }

    public List<String> getCertifications() {
        return certifications;
    }

    public void setCertifications(List<String> certifications) {
        this.certifications = certifications;
    }
..
}

        Users u = new Users();
        u.getCertifications().add("Sun Certified Java Programmer");
        em.persist(u);

Generated Tables

   Users
Column --> ID
    Row             1

Users_CERTIFICATIONS

Validating CSV Files

What is CsvValidator ?
  A Java framework which validates any CSV files something similar to XML validation using XSD.

Why should I use this ?
  You don't have to use this and in fact its easy to write something your own and also checkout its source code for reference.

Why did I write this ?
  Some of our projects integrate with third party application which exchanges information in CSV files so I thought of writing a generic validator which can be hooked in multiple projects or can be used by QA for integration testing.

What is the license clause ?
GNU GPL v2

Are there any JUnit test cases for me checkout ?
 Yes, source

How to integrate in my existing project ?

Just add the Jar which can be downloaded from here CsvValidator.jar and you are good.

Instantiate CsvValidator constructor which takes these 3 arguements

         // filename is the the file to be validated and here is a sample         // list - defines all the fields in the above csv file ( a field has index, type, isOptional, rege…

ArrayList vs LinkedList vs HashSet Performance Comparision

ConclusionsInserting & Reading sequentially from Collection prefer LinkedList/ArrayListInserting & Reading/Deleting by Search/equals from Collection prefer HashSetInserting, ArrayList & LinkedList performs best while HashSet takes double the timeReading, HashSet performs best while ArrayList & LinkedList are marginally lessDeleting, HashSet performs 10 times better than ArrayList & ArrayList performs 4 times better than LinkedList. LinkedList is slow because of sequencial search Bottom line : unless you are not going to iterate using for(Integer i : list ) then prefer HashSet
Inserting/Reading/Deleting integer's from zero till countJDK7Collectionactioncounttime msArrayListInsert1000/1LinkedListInsert1000/1HashSetInsert1000/1ArrayListInsert100005LinkedListInsert100004HashSetInsert100007ArrayListInsert10000011LinkedListInsert10000011HashSetInsert10000021ArrayListGet/Read1000LinkedListGet/Read1000HashSetGet/Read1000ArrayListGet/Read100004LinkedListGet/Read100003Has…