FrameRate
Frames a second as an exact fraction, written 30000/1001 for 29.97 and 25/1 for 25: both parts at least 1, held as written.
Media and visual; not ordered; since Jadpo 0.1.0.
Make one
Build one from its fields, FrameRate { numerator: ... denominator: ... }.
text.parse(raw, as: FrameRate) reads one from its text; text that isn't one at all fails malformed, such as 29.97, 30 or 0/1.
Fields
| Field | Type |
|---|---|
numerator |
Int |
denominator |
Int |
Text, JSON and storage
text.from writes its canonical text, the one form text.parse reads back. JSON sends its canonical text as a string.
| Text | JSON |
|---|---|
24/1 |
"24/1" |
25/1 |
"25/1" |
24000/1001 |
"24000/1001" |
30000/1001 |
"30000/1001" |
60000/1001 |
"60000/1001" |
It is stored in 2 columns, each named for the field, _ and its suffix. This is 24000/1001:
| Column | Type | Holds |
|---|---|---|
<field>_numerator |
integer |
24000 |
<field>_denominator |
integer |
1001 |
Shown to people
text.format(value, locale:) shows it to people in their locale.
With locale: Locale.en_gb:
| Value | Shown |
|---|---|
24/1 |
24/1 |
25/1 |
25/1 |
24000/1001 |
24000/1001 |
30000/1001 |
30000/1001 |
60000/1001 |
60000/1001 |
Operations
It has the contract's own operations: text.parse, text.from, text.format, json.read, json.write and ==. It isn't ordered, so < and sorting don't take it. Every standard type meets one contract says how they work.
Markdown for agents: /docs/types/type-frame-rate.md.Built from Jadpo main at e00e61f.