or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx
Editor Preferences System
The editor will need a way to store user settings such as window size, graphics options, sound and music volumes and so on. These settings are typically per-user, but may also be per-project, or common to a set of related projects.
Preferences may be set explicitly (such as adjusting a music volume slider) or implicitly (like the fact that the user has already seen the tutorial and doesn't need to see it again), but in all cases are the result of user interaction.
All modern operating systems have designated locations for application preferences. For games that run in a browser, user preferences can either be saved in browser local storage, or stored on a server.
Background Work
Goals
Requirements
.TOML
file.Nice to Have
Negligible (Unnecessary)
List of Preferences
Here is a defined list of necessary preferences that the editor will need at minimum.
Object arrays
Hierarchical Structure of the Preferences
From lowest to highest priority, here is the current state of the layered preferences system. Note that this reflects future implementations that have not yet been completed.
*Current implementations won't reflect this behaviour until the editor is in a more complete state. For now, workspaces will be tied to projects. This is not the intended behaviour for the full release and will be changed in the future.
Hypothetical
Here are some other suggested solutions, significantly more hypothetical and should be regarded more as ideas as opposed to plans.
Open Questions
One thing to think about is what a "project" means in this case. Is it a rust crate? What if we are running on an artist's machine without rustc.