On Sat, May 15, 2021 at 8:06 AM [email protected] <[email protected]> wrote:
> I'm not necessarily saying that it doesn't do what it's supposed to. I'm > saying that the draft doc doesn't say what it is supposed to do, at least > not so an inexperienced user can do anything with it. At present (I've just pushed some changes to the ekr-docs branch), the first two sentences of the new chapter are: QQQ leoserver.py is a stand-alone web server that provides access to Leo’s capabilities using Leo’s bridge. leoserver.py exists to support leoInteg: Leo hosted on Visual Studio Code. QQQ leoserver.py is not for inexperienced users. Imo, the above description does describe what the server does, and is supposed to do :-) > I'm saying that this draft doc doesn't tell the reader what and how it's > doing those things. OK, it says to run it with parameters. But it doesn't > say how to compose a message nor how to receive one, nor which of those > **_do_message things are supported. For that one needs to look at the code. I don't think it's necessary to go into the details. The code should be easy enough to understand, for those who really want to know. Let's let Félix comment on the docs before continuing this discussion. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS3%2BBxGUu6_aBHbsxsjdCiixWkTz9NQ9j78NM2jX0KRhXQ%40mail.gmail.com.
