Discuss: load-leo.html should refer visitors to vscode.dev

[Edward K. Ream]

load-leo.html hasn't worked for some time. It's always been pretty feeble.

Imo, load-leo.html should refer visitors to vs.code.dev, vs-code in the browser. Doing so will resolve #3441.

At present, vs.code.dev has a few limitations. It:

- works only on Edge and Chrome.

- has limited support for python.

- does not yet support leoInteg.

As a result, users will see Leo's outlines as xml.

Despite these limitations, the sooner we steer people to vs.code.dev, the better.

Your thoughts, please.

Edward

[Thomas Passin]

As we have discussed in the PR conversation, I think leoad-leo.html needs to go away, one way or another.  It's way too feeble even if we got it working again.  It wouldn't either give visitors a feel for what Leo can do or even a feel that it is well designed.  OTOH, who knows when vscode.dev will be able to support Leo.  I don't think that showing a visitor and XML outline file would be enlightening at all.

So between now and vscode.dev's maturing, I think that either we should just remove the link, or think carefully about what it was intended to do.  I'm inclined to think that it should link to one or more videos of Leo in action, if any of the existing ones seems suitable (I'm not very familiar with them).

[Edward K. Ream]

On Sunday, July 16, 2023 at 4:21:26 PM UTC-5 Thomas wrote:

OTOH, who knows when vscode.dev will be able to support Leo.  I don't think that showing a visitor and XML outline file would be enlightening at all.

Yes. Otoh, I want to ensure people start tracking vscode.dev.

 

I think that either we should just remove the link, or think carefully about what it was intended to do.

Let me sleep on this :-)

Edward

[Edward K. Ream]

>> Thomas: I think that either we should just remove the link, or think carefully about what it was intended to do.

> Me: Let me sleep on this

The question seems moot. How many people have complained that the load-leo page didn't work?

Assuming that hardly anyone ever visits the page, a plug for vscode.dev seems reasonable. I'm going to merge PR #3441. Let's move on.

Edward