Architect Pattern Library

RIA - A new world of possibility ready for the Enterprise. .Architecture .mature frameworks and libraries .process and standards Rich Internet Applications: .Load main page once .Dynamically replace content in response to user interaction .javascript central to UI Logic Traditional MVC with RIA: .UI Logic in view and client-side components .Views are specific to one UI .View-slow RIA without MVC: .Client-side components(javascript) .consume Enterprise API directly (SOAP) .API may not fit UI needs RIA with Slim MVC: .MOdel/Controller are used to expose a UI-specific API (JSON,REST etc) That can be consumed by different UIs. .ByPass controller when possible,avoid views Developing and Maintaining Javascript: .Limited error detection by IDE .Difficult refactoring .Different coding styles .Skill sets Logging: Log to Browser console or web page. .Javascript APIs Log to server File .Call a Logging Service via AJAX RIA technology: Partial screen updates Asynchronous communication ...

1.Why we need javascript Library? Javascript is an awesome language. It’s super flexible.Browsers are the modern UI paradigm. The javascript Libraries now must provide a rich set of UI Widgets. javascript libraries: * JQuery * Qooxdoo * Dojo * Prototype.js * mootools * extjs 2. Why did you choose Ext JS? The overall design of extjs is exemplary.One can learn a lot from it’s unified architecture – no matter which language one is programming in. Extjs requires you to start with one of their base classes – ensuring a consitent model. Consistency is extremely important for the library to be reusable. a.Extjs documentation seems to be very comprehensive and well maintained. b.key aspect of the EXTJS Library is the cross-browser support. c.Build rich Internet applications with Ext JS d. Ext JS framework is the multitude of rich UI elements provided. These elements include forms, dialog boxes, tabs, trees, and grids. e.The Ext JS framework includes support for Ajax implementations. f.Ext J...

EXTJS Component Life Cycle Component life cycle will become quite helpful. Following are the most important stages in the life cycle of every class based on Component: 1. Initialization: The config object is applied Classes that extend Component do not need to (and usually should not) provide a separate constructor. Component's constructor will not only apply any config passed into its subclasses, it also provides all of the following steps. The base Component events are created These are events that can be fired by any Component, and they are enable, disable, beforeshow, show, beforehide, hide, beforerender, render, beforedestroy, destroy (see the Component API docs for complete details). The component is registered in ComponentMgr As such it will always be available via Ext.getCmp. The initComponent method is called This is the most important initialization step for subclasses, as this is a template method intended to be implemented by ea...