blood on the keyboard
Download
Skip this Video
Download Presentation
Blood on the Keyboard

Loading in 2 Seconds...

play fullscreen
1 / 29

Blood on the Keyboard - PowerPoint PPT Presentation


  • 67 Views
  • Uploaded on

Blood on the Keyboard. Experiences in developing Rich Internet Applications. Brendan Lawlor, DSI. Decare Systems Ireland. Based in Bishopstown, Cork. 150+ 140+ actually writing code for a living Java and .NET Enterprise Intranet Applications E-commerce Internet Applications. Themes.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Blood on the Keyboard' - nat


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
blood on the keyboard

Blood on the Keyboard

Experiences in developing

Rich Internet Applications.

Brendan Lawlor, DSI.

decare systems ireland
Decare Systems Ireland
  • Based in Bishopstown, Cork.
  • 150+
  • 140+ actually writing code for a living
  • Java and .NET
  • Enterprise Intranet Applications
  • E-commerce Internet Applications
themes
Themes
  • Rich Internet Application development
  • Creative Development, XHTML, CSS, Javascript.
  • AJAX – a small but vital part of RIA development.
  • DSI’s experience in building RIAs.
ria philosophy before
RIA Philosophy: Before

Javascript Sucks

ria philosophy after
RIA Philosophy: After

Javascript Still Sucks

-but DOJO makes it a lot less sucky

why dojo
Why DOJO?

We needed a safer way to use Javascript.

JSF ?

the ria platform

JSF

The RIA Platform

GWT

DOJO

CSS

XHTML

JS

Browser

what is dojo
What is DOJO?
  • It is a set of JavaScript libraries
  • Handles browser incompatibilities
  • Hides XMLHttpRequest processing
  • Provides for the building of Widgets
  • AOP in JavaScript!
dojo packages
DOJO packages
  • dojo.widget
  • dojo.event
  • dojo.io

dojo.require(“dojo.widget.*”);

dojo libraries dojo widget
DOJO Libraries: dojo.widget

<select class=“cb”>

<option value=“Java">java</option>

<option value=“Script">script</option>

<option value=“Still">still</option>

<option value=“Sucks">sucks</option>

</select>

combobox html
ComboBox.html

<select class=“cb” dojoType=“ComboBox”>

<option value=“Java">java</option>

<option value=“Script">script</option>

<option value=“Still">still</option>

<option value=“Sucks">sucks</option>

</select>

combobox css
ComboBox.css

.cb{

position: relative; top: 0px;

}

combobox js
ComboBox.js

dojo.provide(“ComboBox");

dojo.widget.defineWidget( “ComboBox”,

templatePath:/ComboBox.html

templateCssPath:/ComboBox.css

//Event-Driven Behaviour

creating the widget
Creating the Widget

<div dojoType=“ComboBox">

dojo packages1
DOJO packages
  • dojo.widget
  • dojo.event
  • dojo.io
dojo libraries dojo event
DOJO Libraries: dojo.event
  • RIA = component-based, event-driven
  • JS Events = cross-browser hell
  • DOJO = cross-browser event management
  • Also abstracts over all events.
dojo packages2
DOJO packages
  • dojo.widget
  • dojo.event
  • dojo.io
dojo libraries dojo io
DOJO Libraries: dojo.io
  • Abstracts the XMLHttpRequest
  • Everything is a ‘bind’

dojo.io.bind({

url: "http://foo.bar.com/read",

load: function(type, data, evt){ /*read something*/},

mimetype: "text/json“

formNode: dojo.byId(“myForm”)

});

natural habitats
Natural Habitats

We have a dedicated creative team:

  • No advantage of Java over Javascript.
  • They could work on both server platforms using DOJO alone.
  • Unity of platform gives unity of standards.
dojo and presentation process
DOJO and Presentation Process.

Pictures

Wireframes

WF & data

our dojo architecture

JS Controller

read.json

Read

read.json

Edit

Controller

edit.json

.html

Search

Struts Actions

Our DOJO Architecture
summary
Summary
  • What we liked
  • What we hated
  • What we’re gonna do about it
  • What we wish somebody else would do
what did we like
What did we like?
  • Easy access for our creative staff
  • Very little change from Struts actions downwards
  • JS widgets are more easily reusable
  • Client development without the server!
look ma no server

read.json

read.json

read.json

C:\test

.html

Look Ma – No Server!
what did we dislike
What did we dislike?
  • Widgets on Internet Explorer 6
  • DOJO 0.3 and IE6: a match made in Hell
  • Irresistible force meets immovable object
what next
What Next?
  • DOJO 0.9 just released
  • Hopefully will deal with IE6 problem
final thoughts
Final thoughts
  • Just another view on how to write RIAs.
  • Not an attempt to say that DOJO is better.
  • Whatever framework we use, we need to live with JS.
  • Would somebody write a JS GUI builder already!?
resources and credits
Resources and Credits
  • DSI: Paul Sheehan, Michal Bali, Conor Goulding
  • Sun: Sang Shin (Introduction to Dojo Toolkit)
  • http://dojotoolkit.org
  • http://blog.decaresystems.ie
ad