A word processor designed with students and cheatsheets in mind.
View the latest release and download the file that is compatible with your operating system.
Run the following command in your terminal after unzipping the downloaded file:
xattr -c <path/to/quicksheet.app>
quicksheet.app
should open with no issue after this.
Apple requires applications to be code signed and notarized to run on a user's machine without disabling additional operating system security checks.
This is a security feature used to certify that an application was created by a trustworthy source.
However, code signing certificates for macOS apps can only be obtained through Apple by purchasing a membership to the Apple Developer Program, which costs 99 USD.
As we are not currently members of the Apple Developer Program, we are unable to code sign and notarize our macOS distributables.
Hence, our macOS distributables get an extended attribute com.apple.Quarantine
which triggers the message: “quicksheet.app” is damaged and can’t be opened. You should move it to the Bin.
when trying to open quicksheet.app
.
To bypass this, we run xattr -c <path/to/quicksheet.app>
in the terminal to remove all extended attributes from quicksheet.app
- All credits to this discussion for helping us discover this workaround
Alternatively, if you do not wish to bypass these security measures, you can run QuickSheet by cloning this repository and running the development server:
- Run
git clone https://github.com/zackjh/quicksheet.git
to clone this repository - Run
cd quicksheet
to navigate to the correct working directory - Run
npm install
to install the dependencies - Run
npm start
to start the development server
-
Install VS Code extensions for EditorConfig, ESLint, Prettier, and Tailwind CSS
-
Add the following into your
settings.json
within VS Code (if they are not already there)"files.associations": { "*.css": "tailwindcss" // Always open .css files in Tailwind CSS mode - see Tailwind VS Code extension page for more details }, "editor.quickSuggestions": { "strings": "on" // Trigger completions when editing "string" content - see Tailwind VS Code extension page for more details }, "editor.formatOnSave": true, // Format on save (highly recommended) "tailwindCSS.experimental.classRegex": ["class:\\s*?[\"'`]([^\"'`]*).*?,"], // Enables Tailwind IntelliSense inside TipTap objects "tailwindCSS.classAttributes": ["class", "className", ".*Styles.*"] // Enables Tailwind IntelliSense inside variables containing 'Styles' in their name, as well as when defining classes
-
-
Run
npm install
to install dependencies -
Run
npm start
to start the development server
- Create branches when developing new features or making potentially breaking changes
- Use descriptive branch names such as
bugfix-broken-link
orfeature-settings-page
- It is acceptable to commit to
main
when making minor or low-impact changes such as updating documentation
- Use descriptive branch names such as
- Deal with all linting errors before committing
- Use Conventional Commits when writing commit messages
- Refer to
package.json
fornpm
scripts
- Run
npm run make --platform="darwin" --arch="arm64,x64"
to package and create the distributables - Navigate to
out/make/zip/darwin
and attachquicksheet-darwin-arm64-x.x.x.zip
andquicksheet-darwin-x64-x.x.x.zip
to the GitHub release
- Run
npm install
to ensure dependencies are installed - While on a Windows system, run
npm run make
to package and create the distributables
my-app/
├── out/
│ ├── make/
│ │ ├── squirrel.windows/
│ │ │ ├── MyApp Setup 1.0.0.exe
│ │ │ ├── RELEASES
│ │ │ ├── MyApp-1.0.0-full.nupkg
│ │ │ └── ... (other Squirrel-related files)
│ │ └── zip/
│ │ └── my-app-1.0.0-win32-x64.zip
- Navigate to
out/make/squirrel.windows
and attachquicksheet-x.x.x.Setup.exe
to the GitHub release or runnpm run publish
- Run
npm install
to ensure dependencies are installed - Run
npm run make
to package and create the distributables
my-app/
├── src/
│ ├── index.js
│ └── ... (other source files)
├── package.json
├── out/
│ ├── make/
│ │ ├── deb/
│ │ │ └── my-app_1.0.0_amd64.deb
│ │ ├── rpm/
│ │ │ └── my-app-1.0.0.x86_64.rpm
│ │ ├── zip/
│ │ │ └── my-app-1.0.0-linux-x64.zip
│ │ └── ... (other possible formats)
- Navigate to
out/make/deb
and attachquicksheet-x.x.x.amd64.deb
to the GitHub release - Navigate to
out/make/rpm
and attachquicksheet-x.x.x.x86_64.rpm
to the GitHub release