The document discusses the history and architecture of Sencha Ext JS, a JavaScript framework. It describes how Ext JS was formed through the merger of Ext JS, JQTouch and Raphaël in 2010. It then explains the component-based architecture of Ext JS, with components inheriting functionality from parent classes and using the MVC pattern to separate representation from user interaction. The document also touches on key concepts like lazy rendering and how components manage their children.

1. Satyajeet Shaligram

2. 


2

3. 3

4. 4

5. 5

6. 6

7. 7

8. 



8

9. 9

10. 10

11. 11

12. 12

13. On 15 June 2010, the merger of Ext JS with
JQTouch and Raphaël was announced
forming a new organization called Sencha
Inc.
13

14. 14

15. 15

16. 





16

17. 17

18. 



 18

19. 


 19

20. 20

21. 21

22. 22

23. 23

24. 24

25. 25

26. 26

27. 27

28. 28

29. 29

30. 30

31. Class hierarchy here depicts how components
are extended in order to create more special
purpose elements such as the tip, gridpanel,
treepanel etc. Mind you, each of the subclasses
borrows heavily the functionality from its parent
class.
31

32. A component is the base for all the different components such as buttons, panels, windows,
accordions etc. It comes with a ‘managed lifecycle’ that allows the developer to focus on
functionality vs existence/maintenance.
32

33. A component is the base for all the different components such as buttons, panels, windows,
accordions etc. It comes with a ‘managed lifecycle’ that allows the developer to focus on
functionality vs existence/maintenance.
33

34. A component is the base for all the different components such as buttons, panels, windows,
accordions etc. It comes with a ‘managed lifecycle’ that allows the developer to focus on
functionality vs existence/maintenance.
34

35. A component is the base for all the different components such as buttons, panels, windows,
accordions etc. It comes with a ‘managed lifecycle’ that allows the developer to focus on
functionality vs existence/maintenance.
35

36. It is a phenomenon where components are rendered only once they are
needed e.g. when a component becomes visible to the user.
36

37. Being able to manage its children is an important task the
component performs.
37

38. 38

39. 39

40. 





 40


41. 




41

42. 42

43. 43

44. 44

45. 45

46. Model–View–Controller (MVC) is a design pattern for user-facing software that
separates the representation of information from the user's interaction with it.
46

47. 

 47

48. 48

49. 49

50. 50

51. 51

52. 52

53. 



 53

54. 



 54

55. 


55

56. 56

57. 57

58. 58

59. 59

60. “ 60

61. 


61

62. 62

63. 


Ask away!