Talk:Resources: Difference between revisions
m (forgot to sign) |
(About resources) |
||
| 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) | |||
Revision as of 10:04, 4 March 2007
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. - JonChappell 15:37, 26 December 2006 (CST)
- Thats a good idea. I'll add it to the page. 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? --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
<root>
<resource name="myresource">
<map name="map1">...</map>
<map name="map2">...</map>
</resource>
</root>
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.
--jbeta 04:04, 4 March 2007 (CST)