Félix's upcoming *Leo for vs-code* plugin will make Leo available on a 
platform with millions of users. This will be an important milestone in 
Leo's history.

Félix tells me that the first few weeks will be crucial, due to the metrics 
used to recommend new projects to the vs-code public.  We will want Leo for 
vs-code to have as few hangnails as possible, including distribution issues.

Installing Leo for vs-code should be relatively straightforward. Installing 
python is a snap on vs-code. There will be no need to install Qt. The 
present pypi package (pip install Leo) should suffice, because there will 
no need to install any files in the top-level leo-editor folder, *except* 
for leo-editor/leoserver.py (maybe with another name). 

*Summary*

Leo for vs-code will drive any changes to Leo in pypi (pip in stall Leo). 
I'd like to keep such changes to a minimum, so as not to add new 
distribution difficulties.

All comments welcome.

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/1b7a4a8d-e61e-4cfa-a120-5a355dcd73d8n%40googlegroups.com.

Reply via email to