Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Content

...	...	@@ -14,13 +14,6 @@
14	14
15	15	Wait till everything installs and the setup tasks finish. If you have any problems in this stage refer to the [[Getting Eclipse>>doc:KIELER.Getting Eclipse||shape="rect"]] guide.
16	16
17		-If you have problems in the workspace that are still there after a clean build do the following:
18		-
19		-* Disable Project>Build automatically
20		-* Select all Klighd and pragmatics plugins and do Project>Clean>Only selected and build only selected
21		-* Do the same for the semantics projects
22		-* Enable Project>Build automatically
23		-
24	24	To run the language server go to //Run Configurations// create a new E//clipse Application// run configuration and select //Run an application//  and //de.cau.cs.kieler.language.server.LanguageServer// (for semantics LS,//de.cau.cs.kieler.kgraph.language.server.LanguageServer// otherwise)
25	25
26	26	== [[image:attach:Screenshot from 2019-02-15 14-10-50.png]] ==
...	...	@@ -118,44 +118,8 @@
118	118
119	119	= Stuff that may help =
120	120
121		-== How to run KEITH in developer setup (socket) ==
	114	+== Running the already build LS ==
122	122
123		-Run the following to build and run KEITH in its developer setup (in socket mode, so the LS has to be started separately)
124		-
125		-=== Running KEITH in the browser ===
126		-
127		-\\
128		-
129		-{{code language="bash"}}
130		-yarn && cd keith-app && yarn run socket
131		-{{/code}}
132		-
133		-//yarn// builds all the stuff. //yarn run socket// in keith-app starts the application. After an initial build via yarn you can run //yarn watch //to watch the changes in your repository. In another console you run yarn run socket in keith-app. Now refreshing your browser is enough to apply the changes.
134		-
135		-Per default the KEITH opens on localhost:3000.
136		-
137		-{{info}}
138		-If you previously build keith electron, you have to execute {{code language="none"}}yarn run rebuild:browser{{/code}}
139		-{{/info}}
140		-
141		-Run Launch in Chrome via VSCode to open a chrome browser on localhost:3000
142		-
143		-This is necessary to be able to debug in VSCode.
144		-
145		-=== Running KEITH as (unbundled) electron app ===
146		-
147		-{{code language="bash"}}
148		-yarn && yarn run rebuild:electron && cd keith-app-electron && yarn run socket
149		-{{/code}}
150		-
151		-//yarn// builds all the stuff. //yarn run socket// in keith-app-electron starts the application. After an initial build via yarn you can run //yarn watch //to watch the changes in your repository. In another console you run yarn run socket in keith-app-electron. Now refreshing your browser is enough to apply the changes.
152		-
153		-{{info}}
154		-If you previously build keith electron, you have to execute {{code language="none"}}yarn run rebuild:electron{{/code}}
155		-{{/info}}
156		-
157		-== Running the already build LS (you normally do not want to do this) ==
158		-
159	159	Go to the latest [[Bamboo build>>url:https://rtsys.informatik.uni-kiel.de/bamboo/browse/KISEMA-NSI||shape="rect"]] and go to Artifacts.
160	160
161	161	[[image:attach:image2019-2-7_17-46-58.png]]
...	...	@@ -203,8 +203,40 @@
203	203
204	204	The {{code language="none"}}LSP_PORT{{/code}} option is used to activate the connection via socket. It is also possible to specify a relative location to a LS via {{code language="none"}}LS_PATH=<path to LS>{{/code}}.
205	205
206		-= Known Issues =
	163	+== How run KEITH in developer setup (socket) ==
207	207
	165	+Run the following to build and run KEITH in its developer setup (in socket mode, so the LS has to be started separately)
	166	+
	167	+=== Running KEITH in the browser ===
	168	+
	169	+\\
	170	+
	171	+{{code language="bash"}}
	172	+yarn && cd keith-app && yarn run socket
	173	+{{/code}}
	174	+
	175	+//yarn// builds all the stuff. //yarn run socket// in keith-app starts the application. After an initial build via yarn you can run //yarn watch // to watch the changes in your repository. In another console you run yarn run socket in keith-app. Now refreshing your browser is enough to apply the changes.
	176	+
	177	+Per default the KEITH opens on localhost:3000.
	178	+
	179	+{{info}}
	180	+If you previously build keith electron, you have to execute {{code language="none"}}yarn run rebuild:browser{{/code}}
	181	+{{/info}}
	182	+
	183	+\\
	184	+
	185	+=== Running KEITH as (unbundled) electron app ===
	186	+
	187	+{{code language="bash"}}
	188	+yarn && yarn run rebuild:electron && cd keith-app-electron && yarn run socket
	189	+{{/code}}
	190	+
	191	+//yarn// builds all the stuff. //yarn run socket// in keith-app-electron starts the application. After an initial build via yarn you can run //yarn watch // to watch the changes in your repository. In another console you run yarn run socket in keith-app-electron. Now refreshing your browser is enough to apply the changes.
	192	+
	193	+{{info}}
	194	+If you previously build keith electron, you have to execute {{code language="none"}}yarn run rebuild:electron{{/code}}
	195	+{{/info}}
	196	+
208	208	=== Known issues for windows: ===
209	209
210	210	nsfw.code not found: In the top level package.json exists a script called postinstall. Remove this on windows, delete the node_modules folder and rebuilt the application. This is a known issue of electron-builder.

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-75694098
	1	+73072823

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/75694098/Running KEITH
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/73072823/Running KEITH