From 2e654b7771a2e0bc623ca1604f588a625737eec2 Mon Sep 17 00:00:00 2001 From: Dongdong Zhou Date: Fri, 17 Sep 2021 15:50:49 +0100 Subject: [PATCH] Update why-lapce.md --- docs/why-lapce.md | 27 ++++++++++++--------------- 1 file changed, 12 insertions(+), 15 deletions(-) diff --git a/docs/why-lapce.md b/docs/why-lapce.md index 48368ec5..e7d2572e 100644 --- a/docs/why-lapce.md +++ b/docs/why-lapce.md @@ -8,19 +8,16 @@ Then one day I experienced VSCode's remote development feature, and it felt so " So the new architecture I came up with was like this: - UI -Reads file from Proxy -Handle keyboard/mouse events and do the edits on the file buffer -Send the file editing delta to the proxy to keep the file in sync - | - | - | - Proxy -Receive save event from UI and flush the file buffer to disk -proxy the events between UI and the plugins - | - | - Plugin -Communicate with UI through proxy + UI +Reads file from Proxy
+Handle keyboard/mouse events and do the edits on the file buffer
+Send the file editing delta to the proxy to keep the file in sync
-UI sits locally. Proxy and Plugin will be in the remote box when doing remote development. With this architecture, I can make sure the editing experience is always the best, with other considerations like syntax highlighting is done in a different thread so nothing blocks the main thread at any time. I finally had a lighting-fast and powerful code editor. Lapce. (which can be beautiful as well) \ No newline at end of file + Proxy +Receive save event from UI and flush the file buffer to disk
+proxy the events between UI and the plugins
+ + Plugin +Communicate with UI through proxy
+ +UI sits locally. Proxy and Plugin will be in the remote box when doing remote development. With this architecture, I can make sure the editing experience is always the best, with other considerations like syntax highlighting is done in a different thread so nothing blocks the main thread at any time. I finally had a lighting-fast and powerful code editor. (which can be beautiful as well)