Difference between revisions of "User:Hawk"
From Documentation
| Line 11: | Line 11: | ||
=== Under Review === | === Under Review === | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[User:Hawk/Building User Interface Programmatically with Richlet]] | [[User:Hawk/Building User Interface Programmatically with Richlet]] | ||
Revision as of 01:11, 3 January 2013
Documentation
Under Editing
User:Hawk/Create Data Binding Programmatically
User:Hawk/Tutorial Extension-UnitTest
Under Review
User:Hawk/Building User Interface Programmatically with Richlet
Ready for Publish
Already published
- Small_Talks/2011/December/MVVM_in_ZK6:in_Contrast_to_MVC
- Small Talks/2012/January/Ajax GSP with ZK
- Small Talks/2012/January/Enrich Grails Server Pages (GSPs) with ZK
- Small_Talks/2012/January/MVVM_Extension:_Access_UI_Components_Inside_ViewModel
- Small_Talks/2012/February/MVVM_in_ZK6:_Form_Binding
- Small_Talks/2012/February/MVVM_in_ZK6:_Work_with_Spring
- ZK Developer's Reference/MVVM (whole chapter)
- Small Talks/2012/April/The Dawn of ZK Application Test Suite:Mimic Library
- Small Talks/2012/April/Shining ZATS Mimic
- ZATS Essentials
- ZK Getting Started/Learn ZK in 10 Minutes
- ZK Getting Started/Get ZK Up and Running with MVC
- ZK Getting Started/Get ZK Up and Running with MVVM
- Small Talks/2012/October/Binding with Collection and Selection
- Small_Talks/2012/November/How_to_Apply_Responsive_Design
- Small Talks/2012/October/Practices Of Using Spring In ZK (only revise)
Writing Check List
- Describe the purpose or context at the begining.
- To start from a basic, simple concept or fewer concepts.
- 1 paragraph presents 1 idea.
- Give the overall concept first, then the detail of implementation.
- Summary at the end. (for small talk)
- Check header, footer, TOC, subsections, references
- Check overall article's layout.
- Picture is better than words.
- Picture should be elegant.
- Picture should present just exactly enough information.
- Set align to center.
- Code snippet:
- Focus on a general case not a specific one.
- Keep as short as possible.
- Demonstrate only key concepts and remove irrelevant codes.
- Demonstrate the correct API usage.
- Keep number of codes as fewer as possible to reduce readers' burden.
- Highlight key points in descriptions of code example. (Because most engineers read code first instead of text)
Message Template
Standard:
Note: note message
Deprecated:
[i] Note: note message
Warning: warning message
Not Work sample:
/_w/images/e/e2/Icon_info.png
Font design
http://3.7designs.co/blog/2008/06/10-examples-of-beautiful-css-typography-and-how-they-did-it/