Skip to content
This repository has been archived by the owner on Aug 29, 2024. It is now read-only.

Running or contributing to Graycrown with KDevelop

zeankun.dev edited this page Mar 28, 2023 · 2 revisions

After the commit, Graycrown is now editable with KDevelop with tools that I have provided. To start, you must have the following:

  • KDevelop at least v5.8 (I ran on 5.10)
  • Any machine that has KDevelop
    • It could be Mac, Linux or BSD. Windows KDevelop is unrecommended to run.
    • According to Chrome specs, your minimal CPU must be Intel Pentium 4 and SSE3 capable or ater
    • 4GB is the RECOMMENDED amount of RAM. You may go over than 4GB, as it will enhance the editing of Graycrown codebase
    • 1GB is the MINIMUM amount of RAM

Steps

1. Install KDevelop (if you don't have one, typically)

If you don't have KDevelop and want to contribute with my style (I used KDevelop to edit Graycrown), you may grab it for free here.

2. Git clone the repository

After you have installed KDevelop, open KDevelop and click on Fetch Project. Select GitHub and look up for my username (zeankundev). Scroll down till you see Graycrown.

image

If you have already cloned before, pull the latest commit and find for the primary kdev4 at the project root. If you are on Windows, click Open/Import Project and find for the kdev4 file. If you are on Linux, simply double-click the kdev4 file and get it opened

3. Enjoy!

Notes:

  • IMPORTANT FOR WINDOWS USERS: Tackle the scripts on your own, KDevelop has issues running npm start when Execute is clicked
  • In order to execute Graycrown in KDevelop, make sure you have opened a file. Any file would work. After that, click Execute and you are good to go.
  • To commit, simply right-click graycrown and hover to Git. You would find a ton of options there.
  • Debug is unavailable for Graycrown
  • @types/node wasn't working well with KDevelop. If you see a message like Unexpected token: {, completely IGNORE it and if you are sure, double-check the documentation for Node
  • Autocomplete for Node modules weren't working (maybe?)