User:Cpillsb1/Final project - Revision history

Jwashin1: /* Bugs / Known Issues */

2017-12-14T04:41:48Z

‎Bugs / Known Issues

Jwashin1: /* Code */

2017-07-12T04:00:30Z

‎Code

Cpillsb1 at 21:44, 10 May 2017

2017-05-10T21:44:25Z

Cpillsb1: /* Code */

2017-05-10T21:43:54Z

‎Code

Cpillsb1: /* Bugs / Known Issues */

2017-05-10T21:43:31Z

‎Bugs / Known Issues

Cpillsb1 at 21:20, 10 May 2017

2017-05-10T21:20:30Z

Cpillsb1: /* References */

2017-05-10T21:16:10Z

‎References

Cpillsb1 at 21:15, 10 May 2017

2017-05-10T21:15:31Z

Cpillsb1 at 21:09, 10 May 2017

2017-05-10T21:09:46Z

Cpillsb1 at 21:09, 10 May 2017

2017-05-10T21:09:13Z

@@ Line 39: / Line 39: @@
 *Zooming in or out resets the globe to the default position, not where it was previously
 *Certain values are still hardcoded, should be changed to be dynamic in the future
-*Tooltip doesn't fit long names. Perhaps make tooltip size scaleable in the future
+*[https://github.com/jonorthwash/Apertium-Global-PairViewer/issues/1 Tooltip doesn't fit long names. Perhaps make tooltip size scaleable in the future]
 *Currently ignores all two letter language codes. Should add conversions from two to three letter codes
 *Far away arcs fade a lot, making them difficult to be seen (e.g. Guarani to Warlpiri)

@@ Line 54: / Line 54: @@
 =Code=
 The code is currently located at my personal Github linked [https://github.swarthmore.edu/cpillsb1/Ling073-Final here]. The repo contains all of the files that I used along the way. The Readme file contains more specific details about individual files and how to run it.
 =References=

@@ Line 1: / Line 1: @@
 My goal for the final project was to create a useful application for Apertium. Jonathan showed me the existing [http://svn.code.sf.net/p/apertium/svn/trunk/apertium-tools/pairviewer/apertium.html Apertium PairViewer], which is an interactive tool that visualizes the existing language pairs in Apertium. One idea that was in the works but no one had gotten around to was to create a 3D globe to visualize the language pairs. I was interested in learning JavaScript and HTML/CSS, so I decided to tackle this task as my final project for the class.
-[[File:3D_Pairviewer.png|400px|thumb|right|Guarani IPA Keyboard]]
+[[File:3D_Pairviewer.png|400px|thumb|right|3D Pairviewer]]
 =Process=
 Going into this project, I had no prior knowledge of any web development or JavaScript, but had some programming experience (Python, C++). A good chunk of time was spent simply reading up on how JS, HTML, and CSS interact, and more broadly, how the internet works.

@@ Line 53: / Line 53: @@
 =Code=
-The code is currently located at my personal Github linked [https://github.swarthmore.edu/cpillsb1/Ling073-Final here]. The repo contains all of the files that I used along the way. The Readme file contains more specific details.
+The code is currently located at my personal Github linked [https://github.swarthmore.edu/cpillsb1/Ling073-Final here]. The repo contains all of the files that I used along the way. The Readme file contains more specific details about individual files and how to run it.
 =References=

@@ Line 41: / Line 41: @@
 *Tooltip doesn't fit long names. Perhaps make tooltip size scaleable in the future
 *Currently ignores all two letter language codes. Should add conversions from two to three letter codes
 =Future Improvements=

@@ Line 56: / Line 56: @@
 =References=
 As mentioned earlier, I had a lot of help from various examples of using D3.js to create globes. The example codes were all either open-source or unlicensed. The following were the most useful examples that I used:
-* [http://bl.ocks.org/dwtkns/4973620]
+* http://bl.ocks.org/dwtkns/4973620
-* [https://bl.ocks.org/mbostock/6619561]
+* https://bl.ocks.org/mbostock/6619561
-* [http://bl.ocks.org/KoGor/5994804]
+* http://bl.ocks.org/KoGor/5994804
-* [http://bl.ocks.org/d3noob/a22c42db65eb00d4e369]
+* http://bl.ocks.org/d3noob/a22c42db65eb00d4e369
-* [http://bl.ocks.org/dwtkns/4686432]
+* http://bl.ocks.org/dwtkns/4686432
-* [http://bl.ocks.org/d3noob/7030f35b72de721622b8]
+* http://bl.ocks.org/d3noob/7030f35b72de721622b8
-* [http://bl.ocks.org/danielzurawski/3414137]
+* http://bl.ocks.org/danielzurawski/3414137
 [[Category: sp17_FinalProjects ]]

@@ Line 9: / Line 9: @@
 The most common way of creating globes seemed to be by using D3.js and GeoJSON. I was able to find lots of incredibly helpful examples of people using these libraries (the examples I used are in the references). Most of the code is based on examples of somewhat similar problems.
-To test the code locally I used Python's SimpleHTTPServer. I began by using code for a simple globe, and then tried to stitch pieces from other examples together. My workflow consisted of a lot of poking around, print statement debugging, and of course, StackOverflow. I did run into several hurdles along the way. One of the first difficulties was getting point data into the GeoJSON format so that it could be drawn. I initially inputted the Ling073 Pairs into this format by hand. Because I only had coordinates for a subset of the Apertium languages, I wrote a Python script that scraped the regular pair data and creates a GeoJSON file with the pairs that have coordinates.
+To test the code locally I used Python's SimpleHTTPServer. I began by using code for a simple globe, and then tried to stitch pieces from other examples together. My workflow consisted of a lot of poking around, print statement debugging, and of course, StackOverflow. I did run into several hurdles along the way. One of the first difficulties was getting point data into the GeoJSON format so that it could be drawn. I initially inputted the Ling073 Pairs into this format by hand. Because I only had coordinates for a subset of the Apertium languages, I wrote a Python script that scraped the regular pair data and creates a GeoJSON file with the pairs that have coordinates. In the end I was able to implement all of the core functionality that I was aiming for.
 =Features=
@@ Line 40: / Line 38: @@
 | Language pairs that were worked on this semester!
 |}
 = Bugs / Known Issues =