Test: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (→Sick markup) |
||
Line 2: | Line 2: | ||
"And now for a lesson in [ttttttttttttemplate] mmmmmmmmmanagement... [wikiwikiwiki] llllllllllllet's begin..." | "And now for a lesson in [ttttttttttttemplate] mmmmmmmmmanagement... [wikiwikiwiki] llllllllllllet's begin..." | ||
:Linkin Park, Cure for the Itch | :Linkin Park, Cure for the Itch | ||
:[[User:Geyser|geyser]], deprived of laptop and ICQ for a while ^^ ... which explains the "born to nag" attitude. | |||
;Foreach | ;Foreach | ||
{| border="1" cellspacing="0" cellpadding="0" style="empty-cells:show;" | {| border="1" cellspacing="0" cellpadding="0" style="empty-cells:show;" | ||
Line 16: | Line 17: | ||
| {{ProtokollTabelleDef|aqua|10|Absender-Adresse}} | | {{ProtokollTabelleDef|aqua|10|Absender-Adresse}} | ||
|} | |} | ||
:That solution is universal, and sorta authoritative, but it takes ''ages'' to evaluate : in any given situation, one should probably prefer a lighter, more specific solution. | :That solution is universal, and sorta authoritative, but it takes ''ages'' for the engine to evaluate : in any given situation, one should probably prefer a lighter, more specific solution. | ||
;How about this? | ;How about this? | ||
{|{{TightTable}} | {|{{TightTable}} | ||
|colspan=4|29 Bit CAN-ID | |colspan=4| 29-Bit CAN-ID | ||
|- | |- | ||
| | | | ||
Line 34: | Line 35: | ||
:Note how 1-bit, 2-bit and 3-plus-bit chunks are all handled by the same (small) template ^^ | :Note how 1-bit, 2-bit and 3-plus-bit chunks are all handled by the same (small) template ^^ | ||
:TightTable takes "optional" arguments called '''align''' and '''color'''. They're not really specified as optional, but when not provided, the relevant syntax gets screwed up "the smart way". | :TightTable takes "optional" arguments called '''align''' and '''color'''. They're not really specified as optional, but when not provided, the relevant syntax gets screwed up "the smart way". | ||
:The "skipped bits" span of every chunk is specified in pixels, which can be handy in case one wants a | :The "skipped bits" span of every chunk is specified in pixels, which can be handy in case one wants a more compact layout. The non-breaking space can then be replaced with a "..." to avoid confusion. | ||
:I think the skipped widths are best let custom, as well as the "header". Apart from arbitrarily shrinking the skip fields, one may want to rephrase the header, or omit it, or make it a caption : | :I think the skipped widths are best let custom, as well as the "header". Apart from arbitrarily shrinking the skip fields, one may want to rephrase the header, or omit it, or make it a caption : | ||
{|{{TightTable}} | {|{{TightTable}} | ||
Line 48: | Line 49: | ||
|} | |} | ||
:(again, maybe a "..." in the skip fields would look nicer) | :(again, maybe a "..." in the skip fields would look nicer) | ||
:(and a non-breaking space in front of the description, in the template) | |||
;Arithmetics (will only show fine if ''#expr'' parsing works OK...) | ;Arithmetics (will only show fine when and if ''#expr'' parsing works OK...) | ||
:One can calculate the width of the "skipped bits" internally, only feeding two bit IDs to the template. | :One can calculate the width of the "skipped bits" internally, only feeding two bit IDs to the template. | ||
:The template would then evaluate the difference, and decide upon a 1-bit, or on a 2-plus-bit layout with an adequate skip. | :The template would then evaluate the difference, and decide upon a 1-bit, or on a 2-plus-bit layout with an adequate skip. | ||
:However, the markup is a bit heavier, and makes a few assumptions about e.g. the order in which the bits are listed (unless one wants to | :However, the markup is a bit heavier, and makes a few assumptions about e.g. the order in which the bits are listed (unless one wants to emulate '''abs''', which is a little bit heavier still). | ||
:Right now, it produces a fatal error (then again, so does <nowiki>{{#expr:2+2}}</nowiki>, so there ''is'' a problem), but it would look something like this : | :Right now, it produces a fatal error parsing '''Expr.php''' (then again, so does <nowiki>{{#expr:2+2}}</nowiki>, so there ''is'' a problem), but it would look something like this : | ||
<nowiki>{|{{</nowiki>TightTable|color={{{4}}}}} | <nowiki>{|{{</nowiki>TightTable|color={{{4}}}}} | ||
|-align=center | |-align=center | ||
Line 71: | Line 73: | ||
---- | ---- | ||
---- | ---- | ||
==OBD file types== | ==OBD file types== | ||
{|cellspacing="0" | {|cellspacing="0" |
Revision as of 13:59, 4 August 2006
Sick markup
"And now for a lesson in [ttttttttttttemplate] mmmmmmmmmanagement... [wikiwikiwiki] llllllllllllet's begin..."
- Linkin Park, Cure for the Itch
- geyser, deprived of laptop and ICQ for a while ^^ ... which explains the "born to nag" attitude.
- Foreach
29 Bit CAN-ID | ||||||||||||||||||||||||||||
Template:ProtokollTabelleDef | Template:ProtokollTabelleDef | Template:ProtokollTabelleDef | Template:ProtokollTabelleDef |
- That solution is universal, and sorta authoritative, but it takes ages for the engine to evaluate : in any given situation, one should probably prefer a lighter, more specific solution.
- How about this?
29-Bit CAN-ID | |||
- Note how 1-bit, 2-bit and 3-plus-bit chunks are all handled by the same (small) template ^^
- TightTable takes "optional" arguments called align and color. They're not really specified as optional, but when not provided, the relevant syntax gets screwed up "the smart way".
- The "skipped bits" span of every chunk is specified in pixels, which can be handy in case one wants a more compact layout. The non-breaking space can then be replaced with a "..." to avoid confusion.
- I think the skipped widths are best let custom, as well as the "header". Apart from arbitrarily shrinking the skip fields, one may want to rephrase the header, or omit it, or make it a caption :
- (again, maybe a "..." in the skip fields would look nicer)
- (and a non-breaking space in front of the description, in the template)
- Arithmetics (will only show fine when and if #expr parsing works OK...)
- One can calculate the width of the "skipped bits" internally, only feeding two bit IDs to the template.
- The template would then evaluate the difference, and decide upon a 1-bit, or on a 2-plus-bit layout with an adequate skip.
- However, the markup is a bit heavier, and makes a few assumptions about e.g. the order in which the bits are listed (unless one wants to emulate abs, which is a little bit heavier still).
- Right now, it produces a fatal error parsing Expr.php (then again, so does {{#expr:2+2}}, so there is a problem), but it would look something like this :
{|{{TightTable|color={{{4}}}}} |-align=center |width=18|{{{1}}} |- |width={{#ifexpr:{{{1}}}>{{{2}}}|{{#expr:18*({{{1}}}-{{{2}}}-1)}}|0}}|{{#ifexpr:{{{1}}}>{{{2}}}+1|...|}} |width={{#ifexpr:{{{1}}}>{{{2}}}|18|0}}|{{#ifexpr:{{{1}}}>{{{2}}}|{{{2}}}|}} |colspan=3|{{{3}}} |}
- CAN-ID table
- It could be possible to embed the chunk tables into a big template table specific to the "29-Bit CAN-ID" usage, but most components would have to be in HTML. Bad idea.
OBD file types
0x000 : | 26 | 00 | 33 | 00 | 40 | 00 | 4D | 00 | 5A | 00 | 67 | 00 | 74 | 00 | 81 | 00 | 8E | 00 | 9B | 00 | A8 | 00 | B5 | 00 | C2 | 00 | CF | 00 | DC | 00 | E9 | 00 |
0x020 : | F6 | 00 | 03 | 01 | 10 | 01 | 5F | 45 | F9 | 3D | B6 | FA | 09 | 5F | 45 | F9 | 3D | B6 | FA | 18 | 39 | 1B | 34 | 88 | 77 | 09 | 18 | 39 | 1B | 34 | 88 | 77 |
Heh.
Type | Description | Notes | Type | Description | Notes | Type | Description | Notes | ||
---|---|---|---|---|---|---|---|---|---|---|
RGB Color Array | KeyI | Key Icons | L0 | StNA | String Array | L0 |
|
|
|
Templates
|
![]() |
ONI BINARY DATA |
---|
AKVA << Other file types >> CBPI |
BINA : Binary data |
[[OBD:File types/{{{family}}}|{{{family}}} file]] |