Talk:Resources - Revision history

Erorr404 at 09:06, 11 June 2007

2007-06-11T09:06:45Z

← Older revision		Revision as of 09:06, 11 June 2007
Line 2:		Line 2:
	: Thats a good idea. I'll add it to the page. [[User:EAi\|eAi]] 06:41, 27 December 2006 (CST)		: Thats a good idea. I'll add it to the page. [[User:EAi\|eAi]] 06:41, 27 December 2006 (CST)

	I don't know if this has been addressed before, but is there a good way for add-on resources to get information from game mode resources? Currently you can call the add-on's exported functions, but that is not practical for most end-users. Having the data stored in a config seems like the ideal solution, but how can add-on scripts know which config to read from? It would be nice to have some standardized way of doing this. --[[User:Erorr404\|Erorr404]] 04:06, 11 June 2007 (CDT)		I don't know if this has been addressed before, but is there a good way for add-on resources to get information from game mode resources (information such as respawn time, blip color, etc.)? Currently you can call the add-on's exported functions, but that is not practical for most end-users. Having the data stored in a config seems like the ideal solution, but how can add-on scripts know which config to read from? It would be nice to have some standardized way of doing this. --[[User:Erorr404\|Erorr404]] 04:06, 11 June 2007 (CDT)

	== About resources ==		== About resources ==

Erorr404 at 09:06, 11 June 2007

2007-06-11T09:06:00Z

← Older revision		Revision as of 09:06, 11 June 2007
Line 1:		Line 1:
	I have an even better suggestion: rename it from .zip to something unique (whilst keeping it still compressed as a zip) and have it open with MTA:SA. MTA can then automatically copy everything to the right directories without the user having to specify. MTA:SA has a lot of folders, so this would ease any confusion as to where to put things. - [[User:JonChappell\|JonChappell]] 15:37, 26 December 2006 (CST)		I have an even better suggestion: rename it from .zip to something unique (whilst keeping it still compressed as a zip) and have it open with MTA:SA. MTA can then automatically copy everything to the right directories without the user having to specify. MTA:SA has a lot of folders, so this would ease any confusion as to where to put things. - [[User:JonChappell\|JonChappell]] 15:37, 26 December 2006 (CST)
	: Thats a good idea. I'll add it to the page. [[User:EAi\|eAi]] 06:41, 27 December 2006 (CST)		: Thats a good idea. I'll add it to the page. [[User:EAi\|eAi]] 06:41, 27 December 2006 (CST)

			I don't know if this has been addressed before, but is there a good way for add-on resources to get information from game mode resources? Currently you can call the add-on's exported functions, but that is not practical for most end-users. Having the data stored in a config seems like the ideal solution, but how can add-on scripts know which config to read from? It would be nice to have some standardized way of doing this. --[[User:Erorr404\|Erorr404]] 04:06, 11 June 2007 (CDT)

	== About resources ==		== About resources ==

Jbeta at 10:06, 4 March 2007

2007-03-04T10:06:24Z

← Older revision		Revision as of 10:06, 4 March 2007
Line 1:		Line 1:
	I have an even better suggestion: rename it from .zip to something unique (whilst keeping it still compressed as a zip) and have it open with MTA:SA. MTA can then automatically copy everything to the right directories without the user having to specify. MTA:SA has a lot of folders, so this would ease any confusion as to where to put things. - [[User:JonChappell\|JonChappell]] 15:37, 26 December 2006 (CST)		I have an even better suggestion: rename it from .zip to something unique (whilst keeping it still compressed as a zip) and have it open with MTA:SA. MTA can then automatically copy everything to the right directories without the user having to specify. MTA:SA has a lot of folders, so this would ease any confusion as to where to put things. - [[User:JonChappell\|JonChappell]] 15:37, 26 December 2006 (CST)
	: Thats a good idea. I'll add it to the page. [[User:EAi\|eAi]] 06:41, 27 December 2006 (CST)		: Thats a good idea. I'll add it to the page. [[User:EAi\|eAi]] 06:41, 27 December 2006 (CST)

	~~The "new" specification isn't functional AFAIK, which is why we are using the first one. Could anyone clarify? --[[User:Jbeta\|jbeta]] 13:45, 1 February 2007 (CST)~~

	== About resources ==		== About resources ==
Line 17:		Line 15:
	</syntaxhighlight>		</syntaxhighlight>
	would make more sense now, maybe with getRootElement() taking an optional argument to return the root element, a resource's root element, or a map's.		would make more sense now, maybe with getRootElement() taking an optional argument to return the root element, a resource's root element, or a map's.

			* What is going to be the final specification? We're using the old spec from this page, because the new one is not functional.

	* Shouldn't included resources know what resource included them? There seems to be a getIncludedResources(), but we still lack something like getParentResource().		* Shouldn't included resources know what resource included them? There seems to be a getIncludedResources(), but we still lack something like getParentResource().

Jbeta: About resources

2007-03-04T10:04:07Z

About resources

← Older revision		Revision as of 10:04, 4 March 2007
Line 3:		Line 3:

	The "new" specification isn't functional AFAIK, which is why we are using the first one. Could anyone clarify? --[[User:Jbeta\|jbeta]] 13:45, 1 February 2007 (CST)		The "new" specification isn't functional AFAIK, which is why we are using the first one. Could anyone clarify? --[[User:Jbeta\|jbeta]] 13:45, 1 February 2007 (CST)

			== About resources ==

			There are some still unanswered questions:
			* How does the serverside element tree look like with multiple maps from multiple resources? If all elements are simply getting merged into one parent map tag, scripters can't know what resource does a certain element belong to. Maybe something like
			<syntaxhighlight lang="xml">
			<root>
			<resource name="myresource">
			<map name="map1">...</map>
			<map name="map2">...</map>
			</resource>
			</root>
			</syntaxhighlight>
			would make more sense now, maybe with getRootElement() taking an optional argument to return the root element, a resource's root element, or a map's.

			* Shouldn't included resources know what resource included them? There seems to be a getIncludedResources(), but we still lack something like getParentResource().

			* What map functions are deprecated? Most were made when only one map could be loaded at the same time, and are probably useless now.

			Also, all resource function pages need syntax.

			--[[User:Jbeta\|jbeta]] 04:04, 4 March 2007 (CST)

Jbeta: forgot to sign

2007-02-01T19:45:22Z

forgot to sign

← Older revision		Revision as of 19:45, 1 February 2007
Line 2:		Line 2:
	: Thats a good idea. I'll add it to the page. [[User:EAi\|eAi]] 06:41, 27 December 2006 (CST)		: Thats a good idea. I'll add it to the page. [[User:EAi\|eAi]] 06:41, 27 December 2006 (CST)

	The "new" specification isn't functional AFAIK, which is why we are using the first one. Could anyone clarify?		The "new" specification isn't functional AFAIK, which is why we are using the first one. Could anyone clarify? --[[User:Jbeta\|jbeta]] 13:45, 1 February 2007 (CST)

Jbeta at 19:42, 1 February 2007

2007-02-01T19:42:06Z

← Older revision		Revision as of 19:42, 1 February 2007
Line 1:		Line 1:
	I have an even better suggestion: rename it from .zip to something unique (whilst keeping it still compressed as a zip) and have it open with MTA:SA. MTA can then automatically copy everything to the right directories without the user having to specify. MTA:SA has a lot of folders, so this would ease any confusion as to where to put things. - [[User:JonChappell\|JonChappell]] 15:37, 26 December 2006 (CST)		I have an even better suggestion: rename it from .zip to something unique (whilst keeping it still compressed as a zip) and have it open with MTA:SA. MTA can then automatically copy everything to the right directories without the user having to specify. MTA:SA has a lot of folders, so this would ease any confusion as to where to put things. - [[User:JonChappell\|JonChappell]] 15:37, 26 December 2006 (CST)
	: Thats a good idea. I'll add it to the page. [[User:EAi\|eAi]] 06:41, 27 December 2006 (CST)		: Thats a good idea. I'll add it to the page. [[User:EAi\|eAi]] 06:41, 27 December 2006 (CST)

			The "new" specification isn't functional AFAIK, which is why we are using the first one. Could anyone clarify?

EAi at 12:41, 27 December 2006

2006-12-27T12:41:05Z

← Older revision		Revision as of 12:41, 27 December 2006
Line 1:		Line 1:
	I have an even better suggestion: rename it from .zip to something unique (whilst keeping it still compressed as a zip) and have it open with MTA:SA. MTA can then automatically copy everything to the right directories without the user having to specify. MTA:SA has a lot of folders, so this would ease any confusion as to where to put things. - [[User:JonChappell\|JonChappell]] 15:37, 26 December 2006 (CST)		I have an even better suggestion: rename it from .zip to something unique (whilst keeping it still compressed as a zip) and have it open with MTA:SA. MTA can then automatically copy everything to the right directories without the user having to specify. MTA:SA has a lot of folders, so this would ease any confusion as to where to put things. - [[User:JonChappell\|JonChappell]] 15:37, 26 December 2006 (CST)
			: Thats a good idea. I'll add it to the page. [[User:EAi\|eAi]] 06:41, 27 December 2006 (CST)

JonChappell at 02:03, 27 December 2006

2006-12-27T02:03:49Z

← Older revision		Revision as of 02:03, 27 December 2006
Line 1:		Line 1:
	I have an even better suggestion: rename it from .zip to something unique (whilst keeping it still compressed as a zip) and have it open with MTA:SA. ~~The program that opens it~~ can then automatically copy everything to the right directories without the user having to specify. MTA:SA has a lot of folders, so this would ease any confusion as to where to put things. - [[User:JonChappell\|JonChappell]] 15:37, 26 December 2006 (CST)		I have an even better suggestion: rename it from .zip to something unique (whilst keeping it still compressed as a zip) and have it open with MTA:SA. MTA can then automatically copy everything to the right directories without the user having to specify. MTA:SA has a lot of folders, so this would ease any confusion as to where to put things. - [[User:JonChappell\|JonChappell]] 15:37, 26 December 2006 (CST)

JonChappell at 21:37, 26 December 2006

2006-12-26T21:37:49Z

New page

I have an even better suggestion: rename it from .zip to something unique (whilst keeping it still compressed as a zip) and have it open with MTA:SA. The program that opens it can then automatically copy everything to the right directories without the user having to specify. MTA:SA has a lot of folders, so this would ease any confusion as to where to put things. - [[User:JonChappell|JonChappell]] 15:37, 26 December 2006 (CST)