Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Promote features of vscode-xml in docs #475

Closed
angelozerr opened this issue May 12, 2021 · 2 comments
Closed

Promote features of vscode-xml in docs #475

angelozerr opened this issue May 12, 2021 · 2 comments
Assignees
Milestone

Comments

@angelozerr
Copy link
Contributor

angelozerr commented May 12, 2021

It should be nice to add a new page features in docs to highlight all features with litle demo of vscode-xml like

  • auto close
  • linked editing range un thé future
  • hyperlink on end tag to jump to start tag
  • rename tag
  • codelens références inside xsd and dtd
  • complétion based on xsd
  • generate xsd from xml

I miss a lot of features and we should group features by topic like advanced editing support xsd support etc

I created this issue to start discussion and find the betterave organisation to promote vscode xml. The idea is to show that we support or will support some features that therme extension could support (i think for instance about rename tag extension which will be supportes when linked editing support will be supported)

@rgrunber
Copy link
Member

rgrunber commented May 14, 2021

I think this is a good start and we should do this. Even some small gifs showing the functionality would be great, particularly if it's something neat they may not have considered is possible.

Only thing I can say against such an approach is that I get the impression users very rarely read the welcome/new feature/help pages of extensions. I think more active approaches would probably be more successful. For example :

  • If the issue is informing the user of useful settings that are not the default, keeping track of every property whose value is queried for various code paths (eg. workspace.getConfiguration.get(..)), and then if a user selects some option like "Improve My Workflow", which displays a list of the properties associated with their most common usage, which they should consider modifying.
  • If we're talking about certain commands or keybindings, it would be cool (but sadly impractical) to have some listener that detects the inefficient behaviour and suggests the keybinding/command through a popup. Would be a pain to make one for each possible action.

@angelozerr
Copy link
Contributor Author

It should be nice to add on the xml features

  • path file completion inside attributs
  • format support by doing a simple démo and add a link to the format md page
  • hyperlink to open a références grammar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants