This forum index was started as personal proof-of-concept project in June 2007. To keep it both comprehensive and updated can be a hard job, but with the collaboration of some users we could build something useful.
You may be wondering what is the purpose of such an index, when the forums already have a built-in search interface? Well, as some people have already expressed, the current size of the forum database is an obstacle for finding the required answers, even when those answers might already be there. People need a quick way to filter the "most important" threads or posts. Also, if we have the goal of porting the accumulated community knowledge from the forums towards this wiki, then we first need to organize and select the most valuable information posted on the forums. That's why I think this project could be helpful.
And how should we approach this? Ideally, we should be able to tag forum threads (or even individual posts), using a controlled set of tags, from within the forum interface itself. I don't know if the current forum software would allow that.
Another approach —one that I have adopted for gathering documentation-related threads— consists of building wiki pages with links to the forum, organizing them according to whatever criteria we are interested in. This page includes a more or less arbitrary sample of "interesting" threads. Some threads have been selected because of their importance, others because of their length (a probable indicator of its importance), and finally others just because some words in their titles match some selected keywords.
Do you want to discuss this? Please use the discussion tab above, or (better yet) visit this forum thread.
Accessibility
Application design, patterns, coding techniques
Bugs
Coding tools, IDEs
Context menus
Criticism
Cursor problems
Data proxies
Data readers
Dates
Debugging (includes logging)
DocumentationSee this wiki page
Drag and drop
Events
Feature requests
Font sizes
Forms
GridsPrerelease Builds Discussion > Why a Dynamic Grid/Store/Reader is important?
HTML Editor
JavaScript
Keyboard events
LicensingThe discussions that led to the choice of Ext's licensing model, and some related threads:
Localization, translations
Memory leaks
Menubar
Miscellanea
Modal components
Paging
Performance
Praise
QuickTips
s.gif (Ext.BLANK_IMAGE_URL)
Security
Serverless Ext
State, cookies
Synchronicity
Templates
Textareas
Themes
Trees
Validation
TO-DO: include some more links from http://del.icio.us/fgomez/extjs
TO-DO: read about vBulletin's search syntax. See also this thread.