added small test
fenris

fenris commited on 2016-05-28 19:59:16
Zeige 4 geänderte Dateien mit 107 Einfügungen und 1 Löschungen.

... ...
@@ -1,5 +1,27 @@
1 1
 <project name="fs-workbench" default="build">
2
-	<target name="build">
2
+	<target name="build" depends="build-base,build-model,build-test">
3
+		<concat destfile="build/workbench.js">
4
+			<filelist dir=".">
5
+				<file name="build/base.js">
6
+				</file>
7
+				<file name="build/model.js">
8
+				</file>
9
+				<file name="build/test.js">
10
+				</file>
11
+			</filelist>
12
+		</concat>
13
+	</target>
14
+	<target name="build-base">
15
+		<mkdir dir="build">
16
+		</mkdir>
17
+		<concat destfile="build/base.js">
18
+			<filelist dir=".">
19
+				<file name="source/base.js">
20
+				</file>
21
+			</filelist>
22
+		</concat>
23
+	</target>
24
+	<target name="build-model">
3 25
 		<mkdir dir="build">
4 26
 		</mkdir>
5 27
 		<concat destfile="build/model.js">
... ...
@@ -9,4 +31,14 @@
9 31
 			</filelist>
10 32
 		</concat>
11 33
 	</target>
34
+	<target name="build-test">
35
+		<mkdir dir="build">
36
+		</mkdir>
37
+		<concat destfile="build/test.js">
38
+			<filelist dir=".">
39
+				<file name="source/test.js">
40
+				</file>
41
+			</filelist>
42
+		</concat>
43
+	</target>
12 44
 </project>
... ...
@@ -0,0 +1,56 @@
1
+(18:36:48) RayZa1: fenris_kcf: We were thinking about having a transformation DB right?
2
+(18:37:04) fenris_kcf: öhm
3
+(18:37:16) fenris_kcf: you mean for the tone-transitions?
4
+(18:37:20) RayZa1: yes
5
+(18:37:28) RayZa1: sound-transitions
6
+(18:37:31) fenris_kcf: yes, sry
7
+(18:37:35) fenris_kcf: i could create one
8
+(18:37:43) fenris_kcf: atm there is no such DB
9
+(18:38:46) RayZa1: I guess it might be helpful. We could create all sorts of visual representations like some sort of node diagram
10
+(18:39:21) RayZa1: so you see on one page which transitions have been applied to which source and what the result is
11
+(18:42:37) RayZa1: you could also have an algorithm to apply transformations to the word in the source language in order to achieve the specified word in the resulting language
12
+(18:44:08) RayZa1: for "braudana" in PG and "Brot" in German that would be -"ana", "au">"o", "d">"t"
13
+(18:45:13) RayZa1: for e.g. Danish "brød" it would be -"ana", "au">"ø"
14
+(18:45:31) fenris_kcf: i see
15
+(18:45:33) RayZa1: in case you'd look at direct transitions
16
+(18:46:24) RayZa1: you can think about having intermediate states "Old High German", "Old Norse" and what not
17
+(18:48:57) RayZa1: additionally it would be good to have an etymological DB for cases where the correct translation wouldn't be etymologically connected
18
+(18:53:27) RayZa1: we had a few false friends in terms of translations already which were however connected in etymology
19
+(18:54:51) RayZa1: also another thing one might somehow want to save is: "sprechen" and "talar" aren't connected etymologically but "talar" and "språk" are logically, and "Sprache" and "språk" are etymologically connected
20
+(18:59:31) fenris_kcf: i agree that it would be helpful, but it will take some time to create such a system
21
+(19:03:31) RayZa1: just to finish my thought: to come back to the transitions: one could then analyze those and decide which should be considered for FS in general. work on multiple representative examples to get a representative result and then have the transitions applied automatically. should you feel you made the wrong assumptions in general you can easily correct the transitions being applied or if you feel the algorithms works well in general bu
22
+(19:04:05) RayZa1: *algorithm
23
+(19:04:49) RayZa1: yes I agree such a system is not trivial but it's what's running in your head anyway
24
+(19:05:26) RayZa1: and this way everyone can see the "reasoning" without having to explain everything in length
25
+(19:06:09) RayZa1: you can also more easily try out things
26
+(19:06:59) fenris_kcf: maybe we can develop such a system together
27
+(19:07:10) RayZa1: that's what I was thinking as well
28
+(19:07:47) fenris_kcf: let me create a repository ...
29
+(19:09:25) RayZa1: I have to tell you know, I know Java, C#, Python and JavaScript but I don't know PHP
30
+(19:09:34) RayZa1: tell you though*
31
+(19:11:08) fenris_kcf: then i'd say Javasript or python
32
+(19:11:17) fenris_kcf: though i can program in Java, i don't likve to
33
+(19:11:19) fenris_kcf: *like
34
+(19:11:38) fenris_kcf: never programmed in C#
35
+(19:11:40) RayZa1: I'm rusty in Java anyway
36
+(19:11:58) RayZa1: we could try out how well it works with Node.js?
37
+(19:12:13) RayZa1: I haven't really developed for Node.js yet but I wouldn't mind
38
+(19:12:33) fenris_kcf: since the system will probably be used in the web, i vote for JS
39
+(19:12:43) fenris_kcf: Node-stuff can used on server side JS
40
+(19:12:55) fenris_kcf: but at first i would avoid using Node.js
41
+(19:13:16) RayZa1: yes it should work both on client and server side
42
+(19:13:40) RayZa1: I really like classes though :S
43
+(19:13:49) RayZa1: what to do?
44
+(19:14:18) RayZa1: it's the thing that annoyed me the most with JS, that there was no easy way to do classes
45
+(19:14:52) RayZa1: or no elegant way either
46
+(19:15:07) fenris_kcf: you can use classes since ES6
47
+(19:15:46) fenris_kcf: https://git.schokokeks.org/fs-workbench.git/
48
+(19:15:53) RayZa1: but they won't work in all browsers yet
49
+(19:15:56) fenris_kcf: you can use the public key, that you gave me
50
+(19:16:05) RayZa1: ok
51
+(19:16:13) fenris_kcf: that's not a problem, RayZa1, since one can convert ES6 to ES5
52
+(19:16:18) fenris_kcf: using Babel for example
53
+(19:17:37) fenris_kcf: https://babeljs.io/
54
+(19:18:49) RayZa1: ok
55
+(19:19:12) RayZa1: then ES6
56
+
... ...
@@ -0,0 +1,2 @@
1
+"use strict";
2
+
... ...
@@ -0,0 +1,16 @@
1
+
2
+/**
3
+ * @author fenris
4
+ */
5
+function main()
6
+{
7
+	let words = [
8
+		new Word("de", "Brot", "/bʁoːt/"),
9
+		new Word("pg", "braudą", "/ˈbrɑu̯.ðɑ̃/"),
10
+	]
11
+	
12
+	words.forEach(word => console.info(word.toString()));
13
+}
14
+
15
+main();
16
+
0 17