Updated todo file.

This commit is contained in:
Nathan Vegdahl 2015-02-07 23:38:32 -08:00
parent 2d50906f43
commit ed888939bf

16
todo.md
View File

@ -10,17 +10,13 @@
Or should there be an accompanying structure on the side for that? Or should there be an accompanying structure on the side for that?
- What do other editors do? - What do other editors do?
- Scripting: - Text encoding support:
- What language to use for scripting? Javascript, Lua, Python, Scheme, ... - Buffers need to know what encoding they represent.
It should be something easy to integrate and small, so probably not - Loading/saving code for different encodings.
Python. Javascript, Lua, and Scheme all have small implementations - Auto-detecting text encodings from file data (this one will be tricky).
that would be easy to integrate. Scheme limits the target audience
somewhat, as does Lua. So Javascript is probably the best idea,
even though it's not as simple/clean as lua or scheme.
- In the end, only hard-code the core editing operations, and leave the
rest to scripting. If something ends up being too slow, you can always
move it to be hard-coded for performance later.
- Word wrap.
- Get non-wrapping text working again.
- Line number display - Line number display
- File opening by entering path - File opening by entering path
- UI that wraps editors, for split view. - UI that wraps editors, for split view.