Compo4AllSDK - Revision history

Skeezix: /* Getting the execution info */

2013-05-11T00:27:36Z

‎Getting the execution info

Skeezix: /* Getting the execution info */

2013-05-11T00:27:08Z

‎Getting the execution info

Skeezix: /* Launcher Developer */

2013-05-11T00:23:58Z

‎Launcher Developer

Skeezix: /* SC Exec Return Values */

2013-05-03T14:38:26Z

‎SC Exec Return Values

Skeezix: /* SC Exec Return Values */

2013-05-03T14:38:04Z

‎SC Exec Return Values

Skeezix: /* Spaghetti Client */

2013-05-03T14:37:49Z

‎Spaghetti Client

Skeezix: /* Getting the Score Board */

2013-05-03T14:32:46Z

‎Getting the Score Board

Skeezix: /* Getting the Score Board */

2013-05-03T14:32:13Z

‎Getting the Score Board

Skeezix: /* Getting the Score Board */

2013-05-03T14:27:42Z

‎Getting the Score Board

Skeezix: /* Getting the Games List */

2013-05-03T14:22:34Z

‎Getting the Games List

@@ Line 100: / Line 100: @@
 #include "pnd_container.h"
 #include "pnd_discovery.h"
 // run a discovery

← Older revision		Revision as of 00:27, 11 May 2013
Line 67:		Line 67:

	Command line add could be: "--c4a --game foo" or whatever the application needs to tell it we're running from a c4a frontend.		Command line add could be: "--c4a --game foo" or whatever the application needs to tell it we're running from a c4a frontend.
		+
		+	The actual invocation could be done a number of ways, such as by using pnd_run or pnd_run.sh directly; you can use libpnd (built into the firmware) for all the heavy lifting .. it has utility functions for most everything you need.
		+
		+	Some quick off-memory pseudocode follows-- though its so close it would nearly compile:
		+
		+	<code>
		+	Now, libpnd gives you everything you need to run stuff, but you have to call a few functions.. its not all rolled into one.
		+
		+	Why?
		+
		+	Because it lets you be efficient; your steps are usually..
		+	i) Ask it to find pnd_run.sh <- you can skip it, and use the firmware path if you want
		+	ii) Ask it for a path set from config <- you can skip it, hardcode it if you like: the fw conf is:
		+	/media//pandora/apps:/media//pandora/desktop:/media/*/pandora/menu:/usr/pandora/apps
		+	- you feed that to the discovery function
		+	iii) Ask it to run a discovery (return all apps within a path set)
		+	--> keep this value; it returns a 'box', a linked list, save it so that you don't have to re-discover for every run; discover once, and then you are run-instantly next run
		+	iv) for loop over the result list, looking for unique-id match
		+	v) ask libpnd to run the entry you found (just pass the box pointer into the run function)
		+
		+	Its pretty easy for me anyway :) All you need is steps 3-5.
		+
		+	If I roll you a utility 'run the damned pnd' function, it'll be doing all that stuff every time... pretty inefficient.
		+
		+	The code would be like this:
		+
		+	Given char *my_unique_id that you know from the server.
		+
		+	#include "pnd_pxml.h"
		+	#include "pnd_utility.h"
		+	#include "pnd_conf.h"
		+	#include "pnd_container.h"
		+	#include "pnd_discovery.h"
		+
		+	// run a discovery
		+	pnd_box_handle g_active_apps = NULL;
		+	char searchpath = "/media//pandora/apps:/media//pandora/desktop:/media//pandora/menu:/usr/pandora/apps" <- from conf file!
		+
		+	g_active_apps = pnd_disco_search ( searchpath, NULL ); <- keep this value for the life of the frotnend session
		+
		+	if ( ! g_active_apps ) {
		+	printf ( life is hell )
		+	return ( sucks )
		+	}
		+
		+	pnd_disco_t *a = pnd_box_get_head ( g_active_apps );
		+	void *nexta = NULL;
		+
		+	while ( a ) {
		+	nexta = pnd_box_get_next ( a );
		+
		+	if ( strncmp ( a -> unique_id, my_unique_id, strlen ( my_unique_id ) ) == 0 ) {
		+	// found disco-t entry, run it
		+
		+	ret = pnd_apps_exec_disco ( "/usr/scripts/pnd_run.sh", a, 0 /* options */, NULL );
		+	if ( ret ) .....
		+
		+	}
		+
		+	a = nexta;
		+	}
		+
		+	..
		+
		+	Thats it :)
		+
		+	Now, the pnd_run.sh path might be wrong, I dont' sleep much :)
		+
		+	....
		+
		+	Now, you want to pass args.. theres some params to pnd_apps_exec_disco() so you can pass it args, I think:
		+
		+	pnd_apps_exec_info_t extra;
		+	extra.args = "--game foo"
		+	then pass PND_EXEC_OPTION_INFO into the 'args' bit instead:
		+
		+	ret = pnd_apps_exec_disco ( "/usr/scripts/pnd_run.sh", a, PND_EXEC_OPTION_INFO /* options */, &extra );
		+
		+	That should do it, but I'm going from memory. Still, thats pretty damned close pseudo-code... probably compiles ;)
		+	</code>

	== Game Developer ==		== Game Developer ==

@@ Line 49: / Line 49: @@
    - hi -> the actual score number (for single-score style of games); TBD for time-attack, and other kinds of games
    - time -> the epoch time the event occured
 == Game Developer ==

@@ Line 97: / Line 97: @@
 ! -1
 ! General error (such as bad arguments to sc); maybe failure to get RAM; possibly a problem with plugins (scoreonly module submissions.)
-!-
+|-
 ! -2
 ! Could not write file that was pulled; coudl not find player profile

@@ Line 97: / Line 97: @@
 ! -1
 ! General error (such as bad arguments to sc); maybe failure to get RAM; possibly a problem with plugins (scoreonly module submissions.)
+!-
 ! -2
 ! Could not write file that was pulled; coudl not find player profile

@@ Line 56: / Line 56: @@
 The [http://boards.openpandora.org/index.php/topic/12127-release-compo4all-mame-ladderscoreboard-competition-for-classic-arcade-games/page-18#entry237182 Spaghetti Client] can be downloaded from the thread, and you can easily submit scores by starting a process with the following command line (assuming sc is bundled in your working directory)
-<source lang="bash">./sc MODE OPERATION GAMENAME PLATFORM SCORE</source>
+The paramater's vary by module;
 ==== SC Modes ====
@@ Line 79: / Line 84: @@
 ! pull
 ! Get data from the server (not implemented)
 |}

@@ Line 39: / Line 39: @@
 Requesting [http://skeezix.wallednetworks.com:13001/json_1/bublbobl /json_1/(gamename)] will return you scoreboard details
    - You can also pull a simple HTML (ASCII) dump: skeezix.wallednetworks.com:13001/scoreboard_1/mspacman/
    - Getting previous months can use backdating for both JSON and ASCII pulls; for example: skeezix.wallednetworks.com:13001/scoreboard_1/mspacman/201304/
 The scoreboard is an array of dictionairies, one dict per score entry.

← Older revision		Revision as of 14:32, 3 May 2013
Line 38:		Line 38:

	Requesting [http://skeezix.wallednetworks.com:13001/json_1/bublbobl /json_1/(gamename)] will return you scoreboard details		Requesting [http://skeezix.wallednetworks.com:13001/json_1/bublbobl /json_1/(gamename)] will return you scoreboard details
		+
		+	[code]
		+	- You can also pull a simple HTML (ASCII) dump: skeezix.wallednetworks.com:13001/scoreboard_1/mspacman/
		+	- Getting previous months can use backdating for both JSON and ASCII pulls; for example: skeezix.wallednetworks.com:13001/scoreboard_1/mspacman/201304/
		+	[/code]

	The scoreboard is an array of dictionairies, one dict per score entry.		The scoreboard is an array of dictionairies, one dict per score entry.

← Older revision		Revision as of 14:27, 3 May 2013
Line 39:		Line 39:
	Requesting [http://skeezix.wallednetworks.com:13001/json_1/bublbobl /json_1/(gamename)] will return you scoreboard details		Requesting [http://skeezix.wallednetworks.com:13001/json_1/bublbobl /json_1/(gamename)] will return you scoreboard details

		+	The scoreboard is an array of dictionairies, one dict per score entry.

		+	The dictionairies will include at least:
		+	- shortname -> the player's shortname (initials)
		+	- longname -> the player's long name (display name)
		+	- hi -> the actual score number (for single-score style of games); TBD for time-attack, and other kinds of games
		+	- time -> the epoch time the event occured

	== Game Developer ==		== Game Developer ==

← Older revision		Revision as of 14:22, 3 May 2013
Line 14:		Line 14:
	Sending a HTTP GET request to [http://skeezix.wallednetworks.com:13001/curgamelist_1 /curgamelist_1] will return you a list of games, and details of those games		Sending a HTTP GET request to [http://skeezix.wallednetworks.com:13001/curgamelist_1 /curgamelist_1] will return you a list of games, and details of those games

		+	The JSON response will be an array of dictionairies (one dictionairy per game.)
		+
		+	The dictionaries will include at least the following fields for each game:
		+	- gamename -> the 'short name' of the game; for MAME, it is the driver name ('dkong') and not generally for display; it is a unique-id (unique within C4A)
		+	- longname -> the readable display name ('Donkey Kong')
		+	- status -> current status options include:
		+	- available -> show in frontends, available for scoring etc
		+	- active -> show in frontends (and highlight or in their own tab?), is actively in the ROT tournament or highlight right now (but is otherwise same as available)
		+	- wip -> do not show in frontend; available for scoring and functionality identical to 'active', but for developers to test their code prior to finalization
		+	- genre -> the 'type' of game (at a high level); current values are..
		+	- platform
		+	- maze
		+	- runngun
		+	- shmup
		+	- strategy
		+	- ... we can add more - to be determined
		+	- field -> the 'kind' of game it is, the platform; current values are
		+	- arcade -> implies c4a-mame will be used
		+	- indie -> means standalone; it will contact c4a, but not be part of c4a-mame
		+	- TBD

	=== Getting the Score Board ===		=== Getting the Score Board ===