Editing Online Geometry Viewer Back-end

Online geometry viewer (OGV) is aimed to enable users to view BRL-CAD's geometry files (.g files) on browser. Development started in 2013, efforts were made to make it
functional and no doubt it is working but lacks robust infrastructure. 

Development of OGV's back-end basically involves the basic infrastructure that includes rebuilding the whole project using some web application framework and adding new features. Rebuilding includes the basic part i.e. visualizing the geometry on browser (.g to .obj conversion and then read .obj in ThreeJS), sign-in sign-up module etc. 

Use of a full stack framework for back-end development would be desirable.

New features primarily includes user dashboard, file management, file
sharing with other users, conversion to other CAD formats etc. Check references for more details. If you have better idea regarding anything feel free to discuss at IRC or mailing list.

=References=
* Current implementation: [[Online_Geometry|Online Geometry Viewer]]
* Desired features: [[Online_Geometry/TODO|TODO]]

=Requirements=
* Familiarity with web development technologies(HTML, PHP, JavaScript).
@@ Line 1: / Line 1: @@
-<h1> <strong> Online Geometry viewer for GSOC - 2018 </strong> </h1>
+Online geometry viewer (OGV) is aimed to enable users to view BRL-CAD's geometry files (.g files) on browser. Development started in 2013, efforts were made to make it
+functional and no doubt it is working but lacks robust infrastructure.
-<h2> <b> Scope for GSoC 2018 </b> </h2>
+Development of OGV's back-end basically involves the basic infrastructure that includes rebuilding the whole project using some web application framework and adding new features. Rebuilding includes the basic part i.e. visualizing the geometry on browser (.g to .obj conversion and then read .obj in ThreeJS), sign-in sign-up module etc.
-We have been working on OGV for 5 years. It started with PHP and then was revamped to meteor.js (before it was cool). This year we want to focus on the backend of OGV, making sure it works properly, converts the models properly and basically finishing a version of OGV and launching it for the masses. So it's going to be a really exciting summer this year. We have arranged a list of features, bugs, and enhancements that we think should be handled this year and have put them (https://github.com/BRL-CAD/OGV-meteor/projects/1?fullscreen=true) here on github.   These issues are arranged via priority, so you will get an idea about what you can include in your proposal for this summer.
-<h2> <b> Checklist to write proposal for OGV </b> </h2>
+Use of a full stack framework for back-end development would be desirable.
-* Download and clone OGV from https://github.com/BRL-CAD/OGV-meteor
+New features primarily includes user dashboard, file management, file
-* Run OGV on your local. Can you find some steps missing in Readme?
+sharing with other users, conversion to other CAD formats etc. Check references for more details. If you have better idea regarding anything feel free to discuss at IRC or mailing list.
-* Fork OGV repo
-* Choose a couple of <b> low hanging </b> issues, solve then and send a pull request. More PRs equal better chances of selection!
+=References=
-* <b> Talk to mentors about your PR </b>
+* Current implementation: [[Online_Geometry|Online Geometry Viewer]]
-* Choose list of issues that you would like to solve this summer
+* Desired features: [[Online_Geometry/TODO|TODO]]
-* Make sure it contains as many(https://github.com/BRL-CAD/OGV-meteor/projects/1?fullscreen=true) high priority issues as possible.
-* Did you find a bug? Do you think there's a feature that's really important but it's not here? Feel free to add it to your proposal.
+=Requirements=
-* Make a detailed weekly plan for your summer. More detailed, the better. Include why, what and how whenever you can.
+* Familiarity with web development technologies(HTML, PHP, JavaScript).
-* <b> Share your proposal with your mentors </b>
-* Make any changes if required
-* Put the proposal on BRL-CAD wiki
-* <b> Talk about your proposal with your mentors. Get feedback. </b>
-* Submit it to Google Summer of Code website.