LivelyKernel / LivelyKernel/lively.next
💻 Collection of developer tool improvements (mainly editor)
Open
@linusha is already working on this.
Since May 31, 2022.
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
This is meant as a collection for various improvements I'd like to get to sometime in the next months.
Feel free to add your own and/or provide feedback/thoughts on the ones listed:
- Code Folding (e.g. collapse an if block)
- Line Numbering (see #42 and #152)
- Useful Naming of Editor Windows (at least the module name should always be present!)
- Swap File Support (i.e. save the contents of an text editor every few seconds, without formatting/evaluating it, just to not loose code)
- TODO and FIXME comments are currently highlighted in the code, this should be done via markers, so that they are displayed on the code map
- One should be able to open the code map without the search widget~~
- in general, the text map (with and without search widget) should become a bit more robust. It happens often, that one uses e.g. the scrollbar to scroll in the text and doing so will results in the text map being closed
- Improve the search widget (i.e. affordable regex and case-(in)sensitive settings)
- Git Blame (multiline blame) is currently nearly impossible to read, should be improved upon
- It should never be possible to accidentaly browse in non-focused browsers. The keyboard navigation needs to respect unsaved changes!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.