* Add basic touchscreen scrolling support
* Fix horizontal scroll direction
* Add touch deadzone
* Add drag by touch hold
* Fix touch drag behavior
The one before actually wasn't intended.
* Finetune default touch settings
* Move cursor to drag position upon touch drag start
* Create a simple Zola website on a subdirectory
This uses the [Juice theme](https://www.getzola.org/themes/juice/), with
small customizations. It could be further customized later.
* Automate website content update
RISS and Makefile are used to pull the website content from various
parts of the neovide repository (reusing images and the README.md file
for instance)
* Document how to build and edit the website
It can be counter-intuitive to have to make changes outside of the
`website` directory, adding documentation and scripting clarify it.
* Deploy automatically to GitHub Pages
Uses https://github.com/marketplace/actions/zola-deploy-to-pages to
build and deploy the website on GitHub Pages.
TODO (after merging)
* A `TOKEN` need to be set as explained in https://github.com/marketplace/actions/zola-deploy-to-pages#secrets
* I’ve tested with https://cljoly.github.io/neovide/, but we need to
change this to at least https://neovide.github.io/neovide/.
* Fix website URL
Co-authored-by: Keith Simmons <keith@the-simmons.net>
* Buttonless option for macOS
* Properly export PATH on macOS when ran from Finder #1072
* Merge conflicts resolved
* Refactoring frame options
* Adding frame file; forgot to add
* Updating window files
* Updated from revisions; .vscode folder added to .gitignore
* Formatting
* Remove comment of shadow option in frame decoration.
* Fix transparency for buttonless
* General fix for buttonless and transparency
* Formatting
* revert unecessary changes
Co-authored-by: Keith Simmons <keith@the-simmons.net>
Co-authored-by: Keith Simmons <keithsim@microsoft.com>
the next_dead_key should be changed only when a key_pressed or a dead key released,don't ask me why, it just make things work right with winit.(all test case passed)
The average character width in the font information is not always
reliable, so get the width from the character 'M' instead. It still
fall backs to the average if there's no 'M' in the font.
Previously the font width was always rounded down to the nearest
integer, which typically caused the fonts to look to squashed. To
correct the issue a fudge factor, which scales the fonts so that the
width is always an exact integer, was introduced.
Some of the load and save paths were fixed. And the json is now
structured to properly support saving and loading of both position and
size data, and is easily extendible for more fields and objects in the
future.