Archive:Drive Mapping - Revision history

Ned Scott: moved Drive Mapping to Archive:Drive Mapping

2012-04-10T00:22:39Z

moved Drive Mapping to Archive:Drive Mapping

← Older revision		Revision as of 00:22, 10 April 2012
(No difference)

Ned Scott: Blanked the page

2012-04-10T00:22:12Z

Blanked the page

← Older revision		Revision as of 00:22, 10 April 2012
Line 1:		Line 1:
	~~Proposed drive mappings<br />~~
	~~<br />~~
	~~Currently:<br />~~
	~~U = Used in place of Q for skins/scripts/plugins/vis (and anything else in the root of Q) - currently we check U and then Q for these things manually.<br />~~
	~~Q = System (should not be writable)<br />~~
	~~P = Profile<br />~~
	~~Z = Temporary<br />~~
	~~T = UserData - the "masterusers" profile, normally Q:\userdata, but can be mapped elsewhere (on xbox at least) via Q:\system\profiles.xml<br />~~
	~~<br />~~
	~~Proposal:<br />~~
	~~Q = system<br />~~
	~~This is where we install stuff, it never changes (except on update), it's not writable<br /><br />~~
	~~Z = Temporary<br />~~
	~~This is where we store file temporarily. It's not shared between users/instances/runs. Very volatile.<br /><br />~~
	~~U = No idea what to call this<br />~~
	~~Store mutable data here which doesn't belong to any user. Is there anything we need besides profiles.xml? Should this be writable by scripts or only xbmc itself?<br /><br />~~
	~~P = profiles<br />~~
	~~Give some default profile to begin with, can create more profiles. If some file doesn't exist in here, read from Q. On write, copy from Q and make changes.<br /><br />~~

	~~New names<br />~~
	Currently we support Windows like drive mappings. This is only because of the xbox, and moving forward we would like to change this to a protocol string (system://) or an environment variable (ENV[system]). Proposed names:<br />
	~~Q -> system://<br />~~
	~~Z -> temp://<br />~~
	~~P -> profile:// or user://<br />~~
	~~U -> global://? Do we really need this? It should only be writable by the app itself.<br />~~

	~~Another possible naming: xbmc://system@path~~

	~~More suggestions:<br />~~
	We should perhaps have "drives" for plugins, scripts, skins, themes, sounds (since those are subjects to install) and also we need a user (for userdata/scriptdata) and one userdata/scriptdata (globally for all users)<br />
	~~<br />~~
	~~Have no real idea what to name these.~~

	~~[[Category:Miscellaneous notes]]~~

Ned Scott at 00:27, 1 October 2011

2011-10-01T00:27:41Z

← Older revision		Revision as of 00:27, 1 October 2011
Line 31:		Line 31:
	<br />		<br />
	Have no real idea what to name these.		Have no real idea what to name these.

			[[Category:Miscellaneous notes]]

>NedBot: Robot: Cosmetic changes

2011-09-07T16:09:01Z

Robot: Cosmetic changes

← Older revision		Revision as of 16:09, 7 September 2011
Line 1:		Line 1:
	Proposed drive mappings<br/>		Proposed drive mappings<br />
	<br/>		<br />
	Currently:<br/>		Currently:<br />
	U = Used in place of Q for skins/scripts/plugins/vis (and anything else in the root of Q) - currently we check U and then Q for these things manually.<br/>		U = Used in place of Q for skins/scripts/plugins/vis (and anything else in the root of Q) - currently we check U and then Q for these things manually.<br />
	Q = System (should not be writable)<br/>		Q = System (should not be writable)<br />
	P = Profile<br/>		P = Profile<br />
	Z = Temporary<br/>		Z = Temporary<br />
	T = UserData - the "masterusers" profile, normally Q:\userdata, but can be mapped elsewhere (on xbox at least) via Q:\system\profiles.xml<br/>		T = UserData - the "masterusers" profile, normally Q:\userdata, but can be mapped elsewhere (on xbox at least) via Q:\system\profiles.xml<br />
	<br/>		<br />
	Proposal:<br/>		Proposal:<br />
	Q = system<br/>		Q = system<br />
	This is where we install stuff, it never changes (except on update), it's not writable<br/><br/>		This is where we install stuff, it never changes (except on update), it's not writable<br /><br />
	Z = Temporary<br/>		Z = Temporary<br />
	This is where we store file temporarily. It's not shared between users/instances/runs. Very volatile.<br/><br/>		This is where we store file temporarily. It's not shared between users/instances/runs. Very volatile.<br /><br />
	U = No idea what to call this<br/>		U = No idea what to call this<br />
	Store mutable data here which doesn't belong to any user. Is there anything we need besides profiles.xml? Should this be writable by scripts or only xbmc itself?<br/><br/>		Store mutable data here which doesn't belong to any user. Is there anything we need besides profiles.xml? Should this be writable by scripts or only xbmc itself?<br /><br />
	P = profiles<br/>		P = profiles<br />
	Give some default profile to begin with, can create more profiles. If some file doesn't exist in here, read from Q. On write, copy from Q and make changes.<br/><br/>		Give some default profile to begin with, can create more profiles. If some file doesn't exist in here, read from Q. On write, copy from Q and make changes.<br /><br />

	New names<br/>		New names<br />
	Currently we support Windows like drive mappings. This is only because of the xbox, and moving forward we would like to change this to a protocol string (system://) or an environment variable (ENV[system]). Proposed names:<br/>		Currently we support Windows like drive mappings. This is only because of the xbox, and moving forward we would like to change this to a protocol string (system://) or an environment variable (ENV[system]). Proposed names:<br />
	Q -> system://<br/>		Q -> system://<br />
	Z -> temp://<br/>		Z -> temp://<br />
	P -> profile:// or user://<br/>		P -> profile:// or user://<br />
	U -> global://? Do we really need this? It should only be writable by the app itself.<br/>		U -> global://? Do we really need this? It should only be writable by the app itself.<br />

	Another possible naming: xbmc://system@path		Another possible naming: xbmc://system@path

	More suggestions:<br/>		More suggestions:<br />
	We should perhaps have "drives" for plugins, scripts, skins, themes, sounds (since those are subjects to install) and also we need a user (for userdata/scriptdata) and one userdata/scriptdata (globally for all users)<br/>		We should perhaps have "drives" for plugins, scripts, skins, themes, sounds (since those are subjects to install) and also we need a user (for userdata/scriptdata) and one userdata/scriptdata (globally for all users)<br />
	<br/>		<br />
	Have no real idea what to name these.		Have no real idea what to name these.

>Malloc at 19:52, 11 July 2008

2008-07-11T19:52:58Z

← Older revision		Revision as of 19:52, 11 July 2008
Line 24:		Line 24:
	P -> profile:// or user://<br/>		P -> profile:// or user://<br/>
	U -> global://? Do we really need this? It should only be writable by the app itself.<br/>		U -> global://? Do we really need this? It should only be writable by the app itself.<br/>

			Another possible naming: xbmc://system@path

	More suggestions:<br/>		More suggestions:<br/>

>Blittan at 17:25, 11 July 2008

2008-07-11T17:25:52Z

← Older revision		Revision as of 17:25, 11 July 2008
Line 25:		Line 25:
	U -> global://? Do we really need this? It should only be writable by the app itself.<br/>		U -> global://? Do we really need this? It should only be writable by the app itself.<br/>

	More suggestions:		More suggestions:<br/>
	We should perhaps have "drives" for plugins, scripts, skins, themes, sounds (since those are subjects to install) and also we need a user (for userdata/scriptdata) and one userdata/scriptdata (globally for all users)		We should perhaps have "drives" for plugins, scripts, skins, themes, sounds (since those are subjects to install) and also we need a user (for userdata/scriptdata) and one userdata/scriptdata (globally for all users)<br/>
			<br/>
	Have no real idea what to name these :)		Have no real idea what to name these.

>Blittan at 17:25, 11 July 2008

2008-07-11T17:25:13Z

← Older revision		Revision as of 17:25, 11 July 2008
Line 24:		Line 24:
	P -> profile:// or user://<br/>		P -> profile:// or user://<br/>
	U -> global://? Do we really need this? It should only be writable by the app itself.<br/>		U -> global://? Do we really need this? It should only be writable by the app itself.<br/>

			More suggestions:
			We should perhaps have "drives" for plugins, scripts, skins, themes, sounds (since those are subjects to install) and also we need a user (for userdata/scriptdata) and one userdata/scriptdata (globally for all users)

			Have no real idea what to name these :)

>Jmarshall at 22:36, 2 July 2008

2008-07-02T22:36:36Z

← Older revision		Revision as of 22:36, 2 July 2008
Line 2:		Line 2:
	<br/>		<br/>
	Currently:<br/>		Currently:<br/>
	U = ~~UserData~~<br/>		U = Used in place of Q for skins/scripts/plugins/vis (and anything else in the root of Q) - currently we check U and then Q for these things manually.<br/>
	Q = System (should not be writable)<br/>		Q = System (should not be writable)<br/>
	P = Profile<br/>		P = Profile<br/>
	Z = Temporary<br/>		Z = Temporary<br/>
	T = ?<br/>		T = UserData - the "masterusers" profile, normally Q:\userdata, but can be mapped elsewhere (on xbox at least) via Q:\system\profiles.xml<br/>
	<br/>		<br/>
	Proposal:<br/>		Proposal:<br/>

>Malloc at 22:34, 2 July 2008

2008-07-02T22:34:55Z

← Older revision		Revision as of 22:34, 2 July 2008
Line 20:		Line 20:
	New names<br/>		New names<br/>
	Currently we support Windows like drive mappings. This is only because of the xbox, and moving forward we would like to change this to a protocol string (system://) or an environment variable (ENV[system]). Proposed names:<br/>		Currently we support Windows like drive mappings. This is only because of the xbox, and moving forward we would like to change this to a protocol string (system://) or an environment variable (ENV[system]). Proposed names:<br/>
	Q -> system://		Q -> system://<br/>
	Z -> temp://		Z -> temp://<br/>
	P -> profile:// or user://		P -> profile:// or user://<br/>
	U -> global://? Do we really need this? It should only be writable by the app itself.		U -> global://? Do we really need this? It should only be writable by the app itself.<br/>

>Malloc at 22:34, 2 July 2008

2008-07-02T22:34:33Z

← Older revision		Revision as of 22:34, 2 July 2008
Line 14:		Line 14:
	This is where we store file temporarily. It's not shared between users/instances/runs. Very volatile.<br/><br/>		This is where we store file temporarily. It's not shared between users/instances/runs. Very volatile.<br/><br/>
	U = No idea what to call this<br/>		U = No idea what to call this<br/>
	Store mutable data here which doesn't belong to any user. Is there anything we need besides profiles.xml?<br/><br/>		Store mutable data here which doesn't belong to any user. Is there anything we need besides profiles.xml? Should this be writable by scripts or only xbmc itself?<br/><br/>
	P = profiles<br/>		P = profiles<br/>
	Give some default profile to begin with, can create more profiles. If some file doesn't exist in here, read from Q. On write, copy from Q and make changes.<br/><br/>		Give some default profile to begin with, can create more profiles. If some file doesn't exist in here, read from Q. On write, copy from Q and make changes.<br/><br/>

			New names<br/>
			Currently we support Windows like drive mappings. This is only because of the xbox, and moving forward we would like to change this to a protocol string (system://) or an environment variable (ENV[system]). Proposed names:<br/>
			Q -> system://
			Z -> temp://
			P -> profile:// or user://
			U -> global://? Do we really need this? It should only be writable by the app itself.