Skip to content

Commit 174e345

Browse files
authored
Refine README.md
1 parent 5fb9510 commit 174e345

File tree

1 file changed

+22
-23
lines changed

1 file changed

+22
-23
lines changed

README.md

Lines changed: 22 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -2,48 +2,46 @@
22

33
Next-Generation scientific mind mapping.
44

5+
Inspired by [Docear](https://docear.org/)
56

67
## 📸 Screenshots
78

89
<img width="1429" alt="JabMap-Example" src="https://github.com/user-attachments/assets/4a175c10-a0eb-438f-b5f6-1dcfb4e2520c" />
910

10-
1111
## ⌨️ Shortcuts
1212

1313
You can find a list of shortcuts at [shortcuts.md](shortcuts.md).
1414

15-
1615
## 🌟 Try It Out!
1716

18-
There are a couple of ways to try out JabMap. In any case, you first have to start the HTTP-Server on your machine since Saving, Loading and JabRef-related features like BibTeX-Nodes and importing attached PDF-files as nodes won't work unless you are running JabRef's HTTP-Server (see [below](#-getting-the-server-running) for setup). Afterwards check out [github pages](https://jabref.github.io/jabmap/) where you can try JabMap in your browser!
17+
1. Launch JabRef
18+
2. File > Preferences > Check "HTTP Server"
19+
3. If you don't have any BibTeX files at hand:
20+
21+
1. Click on "Create example Library"
22+
2. Save (Button in the top left or <kbd>Ctrl/Ccmd</kbd> + <kbd>S</kbd>)
1923

20-
> Note: It's still possible your browser blocks access to the server due to HTTP/HTTPS issues
21-
> If you see an Error 404 page, this is most likely the cause. Check if the server has started properly or use another browser and try again.
22-
>
23-
> For the best experience follow the steps below on how to try JabMap.
24+
4. Visit <https://jabref.github.io/jabmap/>
2425

26+
Hint: At click on "Save", a `.jmp` file is created next to your `.bib` file.
2527

26-
### Quick-Start-Guide
28+
## Running locally
2729

2830
The following commands get the code in place and start JabRef and JabMap with the help of a handy wrapper tool called [gg.cmd](https://github.com/eirikb/gg).
2931
A little terminal magic is required, but don't worry, we have the commands all laid out for you!
3032

31-
#### JabRef:
33+
#### JabRef
3234

3335
1. Go to your git-repositories folder and start a new terminal session
3436
2. `git clone --recurse-submodules https://github.com/JabRef/jabref.git`
3537
3. `cd jabref`
3638
4. Enable nice wrapper: `curl -L ggcmd.io > gg.cmd`
37-
5. `sh ./gg.cmd just run-pr 13519`
39+
5. `sh ./gg.cmd just run-gui`
3840
6. Wait for JabRef to come up
39-
7. Click on "Create example Library"
40-
8. Save (Button in the top left or <kbd>CTRL/CMD</kbd> + <kbd>S</kbd>)
41-
9. File > Preferences > Check "HTTP Server"
4241

42+
#### JabMap
4343

44-
#### JabMap:
45-
46-
After setting up JabRef, you can either use [JabMap on GitHub pages](https://jabref.github.io/jabmap/) or follow these steps to run it locally.
44+
After setting up JabRef, follow these steps to run it locally.
4745

4846
1. Go to your git-repositories folder and start a new terminal session
4947
2. Clone it: `git clone git@github.com:JabRef/jabmap.git`
@@ -55,25 +53,23 @@ After setting up JabRef, you can either use [JabMap on GitHub pages](https://jab
5553
8. Run: `sh ./gg.cmd npm run preview`
5654
9. Now you can open http://localhost:4173/ and open a library with the corresponding map.
5755

58-
5956
## 🤖 Getting the server running
6057

61-
As mentioned above, several features are handled by JabRef's HTTP server. Currently you have to start it manually. Luckily, there are multiple ways to do that:
58+
Instead of having the JabRef GUI running, you can just run JabRef's HTTP server. There are multiple ways to do that:
6259

63-
### using gg.cmd
60+
### using `gg.cmd`
6461

65-
If you followed the setup for JabRef [above](#jabref), instead of steps 6. - 9. you can simply do the following to start the server without JabRef's GUI:
62+
If you followed the setup for JabRef [above](#jabref), instead of steps 5 and 6 you can simply do the following to start the server without JabRef's GUI:
6663

6764
```
6865
sh ./gg.cmd jbang .jbang/JabSrvLauncher.java
6966
```
7067

7168
> Note: this is **not** recommended for trying out JabMap for the first time since it will not allow you to create a new library. Use this only if you already used JabRef before :)
7269
73-
7470
### Starting it from an IDE
7571

76-
1. If you haven't already, clone our [JabRef's fork repository](https://github.com/iloveskittles82/jabref) (_Note: It is recommended to complete this step of_ [_JabRef's setup guide_](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/intellij-12-build.html)).
72+
1. If you haven't already, clone our JabRef and follow [JabRef's setup guide](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/).
7773
2. Afterwards, open it in editor of your choice (_IDEA works well for this_) and locate the `jabsrv/src/test/rest-api.http` file.
7874
3. Follow the steps described at the top of the file to start the server.
7975

@@ -83,14 +79,14 @@ _Alternatively_ you can do the following:
8379

8480
More about starting the server in [JabRef's server documentation](https://devdocs.jabref.org/code-howtos/http-server.html)
8581

86-
8782
## 💾 Install by building the application
8883

8984
Now that you've tried it, here is how to build and install it. We hope to provide a downloadable installer in the future, but for now you have to build the app yourself.
9085
This section is more targeted towards
9186
Currently, there is no production build available for download so you have to build it yourself :3
9287

9388
### Basic Setup
89+
9490
Firstly ensure you have `nvm` (_Node version manager_) and `Node.js` installed:
9591

9692
1. Open terminal (_you may have to run it with administrator permissions_)
@@ -106,7 +102,9 @@ Firstly ensure you have `nvm` (_Node version manager_) and `Node.js` installed:
106102
After you ensured the basic setup is complete, clone this repository onto your machine and open a terminal session at the project root.
107103

108104
### Building
105+
109106
Now you should be able to run the following commands:
107+
110108
1. `npm install` - this will install / update all necessary packages in a `./node_modules` directory.
111109
2. `npm run bundle` - this will bundle the project into the `./electron-dist` directory.
112110

@@ -121,6 +119,7 @@ _More about this workaround in [this issue](https://github.com/electron-userland
121119
On Linux and Mac, there is a bug with npm and optional dependencies (See [this issue](https://github.com/npm/cli/issues/4828). Should you encounter this bug after running `npm install`, remove the `package-lock.json` file and `node-modules` directory and run `npm i`. Then, simply continue with step 2.
122120

123121
### Starting
122+
124123
After a successful build you can finally start the app located at `./electron-dist/win-unpacked/JabMap.exe`.
125124

126125
_Optionally you can install it by opening_ `./electron-dist/JabMap Setup 1.0.0.exe`

0 commit comments

Comments
 (0)