Resources:
1. The SmartGWT project on Google Code has JavaDoc and a Showcase with hundreds of samples, code included.
2. The core SmartClient Documentation, including the QuickStart Guide and the "Concepts" area of the SmartClient Reference, contain conceptual overviews which apply to SmartGWT
3. Use the forum search feature to look for existing threads that may answer your questions
4. Before reporting problems, be sure you have read the Debugging chapter of the SmartClient Reference, and have installed the recommended tools from that chapter, and become familiar with them.
5. When posting, include all the information necessary for someone to answer your questions.
Consider providing:
- what UI interaction you are trying to achieve, from the end user's perspective. The best answers often point out a simpler approach
- what you expected to happen
- browser(s) and platform(s) where you see the problem
- contents of the SmartClient Developer Console "Log messages" area, with appropriate log categories set to DEBUG or INFO level
- stack traces from either IE (in the Developer Console) or Firebug (in the Firebug console) for any JavaScript errors that have occurred.
- sample code and sample data (tip:enclosing code snippets in [ code] ...[/ code] tags will format them as code, making your report much more readable)
- SmartClient version (available on lower left of Developer Console)
1. The SmartGWT project on Google Code has JavaDoc and a Showcase with hundreds of samples, code included.
2. The core SmartClient Documentation, including the QuickStart Guide and the "Concepts" area of the SmartClient Reference, contain conceptual overviews which apply to SmartGWT
3. Use the forum search feature to look for existing threads that may answer your questions
4. Before reporting problems, be sure you have read the Debugging chapter of the SmartClient Reference, and have installed the recommended tools from that chapter, and become familiar with them.
5. When posting, include all the information necessary for someone to answer your questions.
Consider providing:
- what UI interaction you are trying to achieve, from the end user's perspective. The best answers often point out a simpler approach
- what you expected to happen
- browser(s) and platform(s) where you see the problem
- contents of the SmartClient Developer Console "Log messages" area, with appropriate log categories set to DEBUG or INFO level
- stack traces from either IE (in the Developer Console) or Firebug (in the Firebug console) for any JavaScript errors that have occurred.
- sample code and sample data (tip:enclosing code snippets in [ code] ...[/ code] tags will format them as code, making your report much more readable)
- SmartClient version (available on lower left of Developer Console)