Update README
This commit is contained in:
parent
68d7e34b03
commit
0ef66c7282
12
README
12
README
|
@ -40,6 +40,7 @@ figured out it would make sense:
|
||||||
- hsm - system monitor
|
- hsm - system monitor
|
||||||
- hss - spreadsheets
|
- hss - spreadsheets
|
||||||
- htd - translation dictionary
|
- htd - translation dictionary
|
||||||
|
- ht - terminal emulator
|
||||||
- htk - GUI toolkit library
|
- htk - GUI toolkit library
|
||||||
|
|
||||||
See Projects for more information about the individual projects.
|
See Projects for more information about the individual projects.
|
||||||
|
@ -50,7 +51,7 @@ Identity
|
||||||
--------
|
--------
|
||||||
The name merely hints at motivations and otherwise isn't of any practical
|
The name merely hints at motivations and otherwise isn't of any practical
|
||||||
significance other than that we need an identifier. This time I resisted using
|
significance other than that we need an identifier. This time I resisted using
|
||||||
something offensive.
|
something offensive for personal amusement.
|
||||||
|
|
||||||
A logo covering the entire project is not needed and it seems hard to figure out
|
A logo covering the entire project is not needed and it seems hard to figure out
|
||||||
anything meaninful anyway, though we might pick a specific font to use for the
|
anything meaninful anyway, though we might pick a specific font to use for the
|
||||||
|
@ -184,6 +185,9 @@ only the per-buffer input line is going to be desynchronized.
|
||||||
|
|
||||||
https://godoc.org/github.com/gorilla/websocket
|
https://godoc.org/github.com/gorilla/websocket
|
||||||
|
|
||||||
|
The higher-level client-server API could be made rather generic to allow for
|
||||||
|
smooth integration with non-IRC "backends" such as Slack or Mattermost.
|
||||||
|
|
||||||
htd -- translation dictionary
|
htd -- translation dictionary
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
This specific kind of application doesn't need a lot of user interface either,
|
This specific kind of application doesn't need a lot of user interface either,
|
||||||
|
@ -221,6 +225,8 @@ In the second stage, support for the Language Server Protocol will be added so
|
||||||
that the project can be edited using its own tools. Some scripting, perhaps
|
that the project can be edited using its own tools. Some scripting, perhaps
|
||||||
a tiny subset of VimL, might be desirable. Or other means of configuration.
|
a tiny subset of VimL, might be desirable. Or other means of configuration.
|
||||||
|
|
||||||
|
Visual block mode or the color column may still be implemented.
|
||||||
|
|
||||||
The real model for the editor is Qt Creator with FakeVIM, though this is not to
|
The real model for the editor is Qt Creator with FakeVIM, though this is not to
|
||||||
be a clone of it, e.g. the various "Output" lists could be just special buffers,
|
be a clone of it, e.g. the various "Output" lists could be just special buffers,
|
||||||
which may be have names starting on "// ".
|
which may be have names starting on "// ".
|
||||||
|
@ -249,6 +255,10 @@ Indexing and search may be based on a common database, no need to get all fancy:
|
||||||
http://rachbelaid.com/postgres-full-text-search-is-good-enough/
|
http://rachbelaid.com/postgres-full-text-search-is-good-enough/
|
||||||
https://www.sqlite.org/fts3.html#full_text_index_queries (FTS4 seems better)
|
https://www.sqlite.org/fts3.html#full_text_index_queries (FTS4 seems better)
|
||||||
|
|
||||||
|
ht -- terminal emulator
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
Similar scope to st(1). Clever display of internal padding for better looks.
|
||||||
|
|
||||||
The rest
|
The rest
|
||||||
~~~~~~~~
|
~~~~~~~~
|
||||||
Currently there are no significant, specific plans about the other applications.
|
Currently there are no significant, specific plans about the other applications.
|
||||||
|
|
Loading…
Reference in New Issue