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

Define the editor api workflow needed to implement teletype plugin #9679

Closed
sunix opened this issue May 11, 2018 · 5 comments
Closed

Define the editor api workflow needed to implement teletype plugin #9679

sunix opened this issue May 11, 2018 · 5 comments
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@sunix
Copy link
Contributor

sunix commented May 11, 2018

Subtask of #9434

@sunix sunix changed the title Defined the editor api workflow needed to implement teletype plugin Define the editor api workflow needed to implement teletype plugin May 11, 2018
@evidolob
Copy link
Contributor

evidolob commented May 11, 2018

@sunix Can you provide list of methods that you are use for teletype plugin?

@ashumilova ashumilova added kind/task Internal things, technical debt, and to-do tasks to be performed. team/ide2 labels May 18, 2018
@ashumilova
Copy link
Contributor

Almost all work is done on Editor API already.

@sunix sunix reopened this Jun 15, 2018
@sunix
Copy link
Contributor Author

sunix commented Jun 18, 2018

here it is

  • get opened editors

  • get opened editor

  • put/remove markers (cursor) - position row/column

  • on cursor/selection activity

    • selection start.row
    • selection start.col
    • selection end.row
    • selection end.col
  • on document ready

  • on document opened

  • on document active

  • on document changing (about to change)

    • startPosition.getrow
    • startPosition.getColumn
    • endPosition.getrow
    • endPosition.getcolumn
    • newText
  • document getContents

  • document replace(oldstartrow, oldstartcolumn, oldendrow, oldendcolumn, text)

  • document setCursorPosition

  • document setContents (could be using replace as well)

  • open a document

Nice to have but optional

  • custumize user markers (css, add text, image)

@sunix
Copy link
Contributor Author

sunix commented Jun 18, 2018

Also would be nice to have the ability to open an editor that is not in the file system. have a virtual file system but maybe this is out of scope.

@che-bot
Copy link
Contributor

che-bot commented Sep 7, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 7, 2019
@che-bot che-bot closed this as completed Sep 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants