Eyesis Panorama Database - Revision history

Oleg at 02:08, 22 June 2013

2013-06-22T02:08:32Z

← Older revision		Revision as of 02:08, 22 June 2013
Line 6:		Line 6:
	=Download=		=Download=
	==GIT==		==GIT==
	git clone git://~~elphel~~.~~git~~.~~sourceforge~~.net/~~gitroot~~/elphel/~~webgl_panorama_editor/~~ webgl_panorama_editor		git clone git://git.code.sf.net/p/elphel/webgl_panorama_editor

	The Panorama Database code is located inside the miscellaneous/Pano_DB/ directory		The Panorama Database code is located inside the miscellaneous/Pano_DB/ directory
Line 17:		Line 17:
	1. Create Data Base structure - import CreateTables.sql into DB		1. Create Data Base structure - import CreateTables.sql into DB
	MySQL export/import: https://my.bluehost.com/cgi/help/112		MySQL export/import: https://my.bluehost.com/cgi/help/112
	~~mysqldump -u username -p database_name > dbname.sql~~		'''mysql -p -u username database_name < CreateTables.sql'''
	'''mysql -p -u username database_name < ~~file~~.sql'''

	2. '''~~backend/db_gui~~.~~html~~''' ~~- Database Interface - Add/Delete/Update routes, Export/Import kml files~~		2. Add database and user to '''pano_db_functions.php'''

	3. '''~~pano_index~~.html''' - ~~Index of available~~ routes ~~in database and~~ kml files ~~- Create an editable copy.~~		3. '''backend/db_gui.html''' - Database Interface - Add/Delete/Update routes, Export/Import kml files

	4. '''~~webgl_panorama_editor~~.html''' - ~~Editor/Viewer~~		4. '''pano_index.html''' - Index of available routes in database and kml files - Create an editable copy.

	5. Image requirements:		5. '''webgl_panorama_editor.html''' - Editor/Viewer

			6. Image requirements:
	* Each panorama (*.jpeg) must be split into 8 subimages with the script - '''other_scripts/prepare_images_for_wpe.php'''		* Each panorama (*.jpeg) must be split into 8 subimages with the script - '''other_scripts/prepare_images_for_wpe.php'''
	* In the KML file the 'href'-tag should be assigned with the full address and initial image file name - see [http://wiki.elphel.com/index.php?title=Eyesis_Panorama_Database#KML_file_format_example KML record example]		* In the KML file the 'href'-tag should be assigned with the full address and initial image file name - see [http://wiki.elphel.com/index.php?title=Eyesis_Panorama_Database#KML_file_format_example KML record example]

Oleg at 20:17, 20 October 2011

2011-10-20T20:17:49Z

← Older revision		Revision as of 20:17, 20 October 2011
Line 31:		Line 31:

	6. Rules for editing routes:		6. Rules for editing routes:
	* Select a database route or an existing kml file from the list on '''pano_index.html''' and make an editable copy.		* Select a database route or an existing kml file from the list at '''pano_index.html''' and make an editable copy.
	* If the route does not exist in the database - create it at '''backend/db_gui.html'''.		* If the route does not exist in the database - create it at '''backend/db_gui.html'''.
	* Edit the copy.		* Edit the copy.

Oleg at 20:17, 20 October 2011

2011-10-20T20:17:18Z

← Older revision		Revision as of 20:17, 20 October 2011
Line 29:		Line 29:
	* Each panorama (*.jpeg) must be split into 8 subimages with the script - '''other_scripts/prepare_images_for_wpe.php'''		* Each panorama (*.jpeg) must be split into 8 subimages with the script - '''other_scripts/prepare_images_for_wpe.php'''
	* In the KML file the 'href'-tag should be assigned with the full address and initial image file name - see [http://wiki.elphel.com/index.php?title=Eyesis_Panorama_Database#KML_file_format_example KML record example]		* In the KML file the 'href'-tag should be assigned with the full address and initial image file name - see [http://wiki.elphel.com/index.php?title=Eyesis_Panorama_Database#KML_file_format_example KML record example]

			6. Rules for editing routes:
			* Select a database route or an existing kml file from the list on '''pano_index.html''' and make an editable copy.
			* If the route does not exist in the database - create it at '''backend/db_gui.html'''.
			* Edit the copy.
			* Import the the modified copy back at '''backend/db_gui.html'''.

	=Documentation=		=Documentation=

Oleg at 16:59, 20 October 2011

2011-10-20T16:59:30Z

← Older revision		Revision as of 16:59, 20 October 2011
Line 28:		Line 28:
	5. Image requirements:		5. Image requirements:
	* Each panorama (*.jpeg) must be split into 8 subimages with the script - '''other_scripts/prepare_images_for_wpe.php'''		* Each panorama (*.jpeg) must be split into 8 subimages with the script - '''other_scripts/prepare_images_for_wpe.php'''
	* In the KML file the 'href'-tag should be ~~named after~~ the initial image name.		* In the KML file the 'href'-tag should be assigned with the full address and initial image file name - see [http://wiki.elphel.com/index.php?title=Eyesis_Panorama_Database#KML_file_format_example KML record example]

	=Documentation=		=Documentation=

Oleg at 16:56, 20 October 2011

2011-10-20T16:56:55Z

← Older revision		Revision as of 16:56, 20 October 2011
Line 25:		Line 25:

	4. '''webgl_panorama_editor.html''' - Editor/Viewer		4. '''webgl_panorama_editor.html''' - Editor/Viewer

			5. Image requirements:
			* Each panorama (*.jpeg) must be split into 8 subimages with the script - '''other_scripts/prepare_images_for_wpe.php'''
			* In the KML file the 'href'-tag should be named after the initial image name.

	=Documentation=		=Documentation=

Oleg at 16:50, 20 October 2011

2011-10-20T16:50:42Z

← Older revision		Revision as of 16:50, 20 October 2011
Line 6:		Line 6:
	=Download=		=Download=
	==GIT==		==GIT==
	git clone git://elphel.git.sourceforge.net/gitroot/elphel/~~miscellaneous~~/ ~~miscellaneous~~		git clone git://elphel.git.sourceforge.net/gitroot/elphel/webgl_panorama_editor/ webgl_panorama_editor

	The Panorama Database code is located inside the miscellaneous/Pano_DB/ directory		The Panorama Database code is located inside the miscellaneous/Pano_DB/ directory
Line 12:		Line 12:
	==Direct Download==		==Direct Download==

	http://elphel.git.sourceforge.net/git/gitweb.cgi?p=elphel/~~miscellaneous~~;a=tree;f=~~Pano_DB~~;hb=~~HEAD~~		http://elphel.git.sourceforge.net/git/gitweb.cgi?p=elphel/webgl_panorama_editor;a=tree;h=refs/heads/master;hb=refs/heads/master

	==Work==		==Work==
Line 20:		Line 20:
	'''mysql -p -u username database_name < file.sql'''		'''mysql -p -u username database_name < file.sql'''

	2. Add/Delete/Update routes, Export/Import kml files ~~- backend/db_gui.html~~		2. '''backend/db_gui.html''' - Database Interface - Add/Delete/Update routes, Export/Import kml files

	3. ~~Viewer~~ - webgl_panorama_editor.html		3. '''pano_index.html''' - Index of available routes in database and kml files - Create an editable copy.

			4. '''webgl_panorama_editor.html''' - Editor/Viewer

	=Documentation=		=Documentation=

Oleg at 00:08, 14 October 2011

2011-10-14T00:08:08Z

← Older revision		Revision as of 00:08, 14 October 2011
Line 13:		Line 13:

	http://elphel.git.sourceforge.net/git/gitweb.cgi?p=elphel/miscellaneous;a=tree;f=Pano_DB;hb=HEAD		http://elphel.git.sourceforge.net/git/gitweb.cgi?p=elphel/miscellaneous;a=tree;f=Pano_DB;hb=HEAD

			==Work==
			1. Create Data Base structure - import CreateTables.sql into DB
			MySQL export/import: https://my.bluehost.com/cgi/help/112
			mysqldump -u username -p database_name > dbname.sql
			'''mysql -p -u username database_name < file.sql'''

			2. Add/Delete/Update routes, Export/Import kml files - backend/db_gui.html

			3. Viewer - webgl_panorama_editor.html

	=Documentation=		=Documentation=

OneArtPlease: /* PHPJavascript Interface Discussion */

2011-08-30T10:22:43Z

PHPJavascript Interface Discussion

← Older revision		Revision as of 10:22, 30 August 2011
Line 474:		Line 474:
	</Document>		</Document>
	</kml>		</kml>
	=~~PHP<->Javascript~~ Interface ~~Discussion~~=		=AJAX Interface=

	~~My idea~~ is ~~to write~~ a ~~panodb-interface~~.php that AJAX calls can communicate with.		There is a panodb_interface.php that AJAX calls can communicate with by using jQuery POST (careful: GET will not work).
			http://api.jquery.com/jQuery.post/
	~~Now we need to define which function calls this interface should contain and how bigger amounts of data can be transferred~~.

	~~Also its important to consider when such transactions are taking place: on initial loading of a Route only or every time the POV jumps to a different panorama?~~

			The function call names (cmd: "GetNodeData") are 1:1 the names used in the PHP framework.
			The parameters passed to the function are stored in an array called parameters.

	~~==Parameters and what they do==~~		This is a typical call:

	~~We can define a general~~ "~~CMD~~" ~~key which contains~~ the function ~~to execute 1:1 from the PHP framework plus all other parameters as additional keys like:~~		$("#example").submit(function(event) {
			// make sure we do a complete override of the submit function
			event.preventDefault();

	~~panodb~~-~~interface~~.php~~?CMD=GetNodeData&ID=id~~		// the URL where the panodb_interface.php file is located
			var url = "http://community.elphel.com/files/eyesis/pano-db/panodb_interface.php";

	~~When dealing with arrays or lots~~ of ~~data~~ as parameters ~~let use jQuery.post()~~		// Receive Node data of ID = 10 as KML
	~~http~~:~~//api.jquery.com/jQuery.post/~~		var parameters = { ID : 10 };
			var data = { cmd: "GetNodeData", return : "KML", parameters :parameters }

	~~Note: --[[User:Oleg\|Oleg]] 22:15, 25 August 2011~~ (~~UTC~~)		// Send the data using post and display the returned data in the console (requires firebug extension)
	$.~~ajax~~({		$.post(url, data, function(data) { console.log(data); });
	url~~: "modify_kml.php?kml="+filename,~~		}
	~~type: "POST"~~,
	~~dataType: "xml",~~
	data~~: xml~~,
	~~async:false,~~
	~~complete:~~ function(~~response~~){},
	~~contentType: "text/xml~~; ~~charset=\"utf-8\""~~
	});

	~~There the data you send in ''data'' goes~~ to ~~''php://input''. At the same time you can pass some control parameters through the url line~~.		On GIT there is a AJAX-Examples.html file that contains example calls to all implemented functions.

Oleg at 22:15, 25 August 2011

2011-08-25T22:15:37Z

← Older revision		Revision as of 22:15, 25 August 2011
Line 491:		Line 491:
	When dealing with arrays or lots of data as parameters let use jQuery.post()		When dealing with arrays or lots of data as parameters let use jQuery.post()
	http://api.jquery.com/jQuery.post/		http://api.jquery.com/jQuery.post/

			Note: --[[User:Oleg\|Oleg]] 22:15, 25 August 2011 (UTC)
			$.ajax({
			url: "modify_kml.php?kml="+filename,
			type: "POST",
			dataType: "xml",
			data: xml,
			async:false,
			complete: function(response){},
			contentType: "text/xml; charset=\"utf-8\""
			});

			There the data you send in ''data'' goes to ''php://input''. At the same time you can pass some control parameters through the url line.

OneArtPlease: /* Parameters and what they do */

2011-08-25T19:05:55Z

Parameters and what they do

← Older revision		Revision as of 19:05, 25 August 2011
Line 489:		Line 489:
	panodb-interface.php?CMD=GetNodeData&ID=id		panodb-interface.php?CMD=GetNodeData&ID=id

	When dealing with arrays or lots of data as parameters ~~we need to think of something different.~~		When dealing with arrays or lots of data as parameters let use jQuery.post()

	~~Can we~~ use jQuery.post() ?
	http://api.jquery.com/jQuery.post/		http://api.jquery.com/jQuery.post/
	~~or better JSON?~~