I thought that I would like to explain the format before. It is now described here.
The setting data text consists of the following lines:
- Header
A string indicating the configuration data of SymbolsPanel.
Header is a line which just ”##SymbolsPanel" is written to. It contains no blank, and is nothing after.
At version 0.9b or before, Header must be the first line of configuration data.
Since 0.9c, SymbolsPanel will ignore text before Header.
- Footer
Available since version 0.9c.
A string indicating the end of the configuration data.
Footer is a line starting with "##end". So, "##end of data" is also Footer.
SymbolsPanel will ignore text after Footer.
- Page name
Start of page definition.
This is a line starting with "#:". It is followed by page name and tags separated by a space.
The first word is page name displayed on screen. Others are tags, which will be used when SymbolsPanel is launched as Mushroom plugin.
- Directives
Available since version 0.9b.
A line starting with "#!" specifies the various directions for loading process.
It will be used for the page after directive. It will not affect for current configuring page.
- #!create
Create a new page even if same name page is exists.
- #!update
If same name page is exists, overwrite it. Old settings in that page are erased.
- #!append
If same name page is exists, append new settings into it.
- #!merge
If same name page is exists, append new settings into it excluding same name button settings.
- #!create
- Comments
A line starting with "#" is a comment. it is ignored.
For future feature, it is recommended inserting a space character after "#".
A empty line is not handled as comment, but handled as button setting.
- Button settings
Other lines are button settings.
A button content is a text before the first space character. Text after it is a summary text of this button, just for displaying.
This means that a button content must not be a single character. You can specify a ascii art like a facemark. But it will not display properly because the size of each button is as large as one character at defaults. For avoid it, you can set the number of columns.
Otherwise, if a space character is at the first of the line (or nothink in the line), Space is defined. This is not visible, does not cause anything.
The button content can be specified as follows:- Plain Text
Specifying by a plain text directly. It is the most obvious and quick way.
- U+xxxx
Specifying by a code point of unicode. xxxx is a 4-6 digit hexadecimal number. In this way you can specify only one character.
- JIS:xxxx
Specifying by a character code of japanese JIS charset. xxxx is a 4 digit hexadecimal number. In this way you can specify only one character.
- SJIS:xxxx
Specifying by a character code of japanese Shift-JIS charset. xxxx is a 4 digit hexadecimal number. In this way you can specify only one character.
- :text
Available since version 0.9c.
Specifying by a Percent-Encoded text.
For example: specifying ":%23" for "#", "{%20}" for "{ }".
- :charset:text
Available since version 0.9c.
Specifying by a Percent-Encoded text in charset. Some charset may require escape sequence. For example, for character "友"(U+53CB) in japanese JIS charset, specify ":ISO-2022-JP:%1b%24%42%4d%27%1b%28%42".
- Plain Text
Even if you don't understand above, for example, you can collect your favorite symbols into a single page easily.
0 件のコメント:
コメントを投稿