Docs need to list valid SDL constants

[kthakore]

Having to manually search Constants.pm for valid constants is a pain, and probably the source of many "magic values".

Ideally, each method call should be documented with a list of valid constants. I realize that this is a task of near-epic proportions.

As a start, an exhaustive list should be shown (or referred to) in the SDL documentation.

[kthakore]

Author: kthakore
Time: 1254817437
Field: keywords
Value: Pod

[kthakore]

Author: kthakore
Time: 1254817437
Field: difficulty
Value: Easy

[kthakore]

Author: kthakore
Time: 1254817437
Field: type
Value: task

[kthakore]

Author: kthakore
Time: 1254817437
Field: milestone
Value: Exit Legacy

[kthakore]

Author: kthakore
Time: 1254817437
Field: comment
Value:

[kthakore]

Author: garu
Time: 1254980591
Field: comment
Value: Just so people can help, the task ahead is:

• open SDL/Constant.pm
• create a pod for each Constant, describing it.
• group constants in pod by their purpose (i.e. where each set should be used.

[kthakore]

Author: garu
Time: 1254982069
Field: blocking
Value: 25

[kthakore]

Author: kthakore
Time: 1257958743
Field: status
Value: assigned

[kthakore]

Author: kthakore
Time: 1257958743
Field: owner
Value: selvaraj

[kthakore]

Author: kthakore
Time: 1257958743
Field: comment
Value:

[kthakore]

Author: FROGGS
Time: 1269299546
Field: status
Value: accepted

[kthakore]

Author: FROGGS
Time: 1269299546
Field: owner
Value: FROGGS

[kthakore]

Author: FROGGS
Time: 1269299546
Field: comment
Value: for Pango and TTF they are in their namespace. Other modules will follow.

[kthakore]

Author: FROGGS
Time: 1269299613
Field: comment
Value: Constants are documented in the pods in the CONSTANTS section (right above METHODS).

[kthakore]

Author: FROGGS
Time: 1269561235
Field: status
Value: closed

[kthakore]

Author: FROGGS
Time: 1269561235
Field: resolution
Value: fixed

[kthakore]

Author: FROGGS
Time: 1269561235
Field: comment
Value: Done