No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
| | ||
=== Thuan: Yes, it should be. Do you remember we deleted a lot of example code when we reviewed the document? At that time, the document was written in word file and perhaps would be added to AuthorIT. So much code would pollute it. However, time's changed. We have wiki now. I think there are two ways to write examples: | === Thuan: Yes, it should be. === | ||
Do you remember we deleted a lot of example code when we reviewed the document :-D ? At that time, the document was written in word file and perhaps would be added to AuthorIT. So much code would pollute it. However, time's changed. We have wiki now. I think there are two ways to write examples: | |||
- Simple, short examples: write directly in the guideline. | - Simple, short examples: write directly in the guideline. | ||
Latest revision as of 02:55, 3 February 2009
Chinh: Shouldn't we create example for each case? To me, the guideline MUST be very practical. So, the more example we give the more exactly that people can follow the guidelines
Thuan: Yes, it should be.
Do you remember we deleted a lot of example code when we reviewed the document :-D ? At that time, the document was written in word file and perhaps would be added to AuthorIT. So much code would pollute it. However, time's changed. We have wiki now. I think there are two ways to write examples:
- Simple, short examples: write directly in the guideline.
- Otherwise, make a new topic and link to it. For example: handling exceptions of server methods (already had), a topic about adding a new Session key and generate the SessionManager class.
I prefer other developers get involved in this. For instance, a CORE member may help write a topic about SessionManager.