As architects of a product, we always need to consider how to make our product exemplary, how to make sure the user experience is a good one, how to exceed the expectations of our stakeholders. The starting step is to work out in exacting detail the facets on the product we'd like to build.
How do the requirements we've spelled out translate into the underlying tech?
- We want to display a login form with a "remember me" feature, so we need some kind of persistent storage
- We want to display thread data in a custom format
- We want to display full message threads in a custom format
- We want a basic HTML editor for message bodies
- We need an autocomplete box for recipients
- We need to display search results in the same format as message threads
- We need an autocomplete box for tags to be used in various locations
Let's translate each of these into Ext JS features:
- We can use cookies or local storage to hold login information between systems (either using native browser methods or an Ext JS-powered session class)
- We can use an Ext JS DataView to create a templated view of thread data
- We can use an Ext JS DataView to create a templated view of message data
- Ext JS provides an HTML editor widget
- The Ext JS combo box can be powered by a store that retrieves remote contact data
- We can reuse the message thread DataView with a different store
- We can use the
editable:trueoption of the Ext JS combo box in cases where we need to add new tags
There are a couple of gray areas there that we'll review later, but it does look like Ext JS can provide all of the features we're going to need to build this application.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.