XML:TxtC: Difference between revisions

1,837 bytes removed ,  18 January 2009
m
fixing a confusion + removing talk; @ "digest wisdom" : a new structure will take some time to develope ...
(my "digest" notes from the old talk page)
m (fixing a confusion + removing talk; @ "digest wisdom" : a new structure will take some time to develope ...)
Line 1: Line 1:
==Notes on tutorial(s) from Iritscen==
Well, geyser and I decided to move the page here, as you can see. Having the tutorials out there as separate pages means individually linking to each one from the related OBD page as well as the (not-yet-created) overview page, whereas having it here makes it easy to say "All tutorials are on the talk pages for their related file types", plain and simple. Naming is also a no-brainer now :-).
Also, this might not be its permanent place, but for now it seems appropriate to put all tutorials into Talk pages like so. If they develop into broader articles than simply elaborating on the OBD file type as this article does, we might at least make those articles stand-alone. Anyway, thanks to paradox for all your work on this, especially this one, where the basic OBD page is sorely lacking any explanation of how the type actually works.
A couple things I wanted to preserve from the old Talk page that was attached to this article before the article itself became a Talk page:
"If you develop on the structure of an instance in its OBD talk page, some of the "digest" [I think he means "summarized"] wisdom can be copied/moved to the OBD article" -- geyser
Also, I had said:
"have you considered writing the tutorials from a goal-oriented perspective" --Iritscen
And you replied:
"TRAM has a taste of it (with "adding impact flash", "adding colorful trails" and the hidden "adding motion blur" (mechanism seems buggy). I think this should be decided from case to case. ONCC, ONGS, ONIE and PART will need similar for sure but not TxtC, TRMA, and most of object collections (the goal there is obvious)." --Paradox-01
That is very true, and I clearly should have read your WIP page more closely. Thanks again for your hard work! --[[User:Iritscen|iritscen]] 20:57, 9 November 2008 (CET)
==[[TxtC]]: text console (page)==
==[[TxtC]]: text console (page)==
===general notes===
===general notes===
* See [[XML basic tutorial|HERE]] if you don't know how to convert an oni file into XML and vice versa.
* See [[XML basic tutorial|HERE]] if you don't know how to convert an oni file into XML and vice versa.
* Console text pages can be called via BSL command "text_console". In fact they don't need a console, you can call up a page in any function you like.
* Console text pages can be called via BSL command "text_console". In fact they don't need a console, you can call up a page in any function you like.
* TxtC's are normally level specific, but could be made global.
* TxtC's are normally level specific, but could be made global.


Line 86: Line 65:
===XML tags and options===
===XML tags and options===
'''TxtC instance tags'''
'''TxtC instance tags'''
: <Pages> (defines the number of pages)
: <Pages> (link to IGPA instance)


'''IGPA instance tags'''
'''IGPA instance tags'''
: <Pages>
: <Pages> (every link represents a page)
:: <Link> (links to an IGPG instance)
:: <Link> (links to an IGPG instance)


Line 205: Line 184:
         <Text>And that's a white, smaller text.</Text>
         <Text>And that's a white, smaller text.</Text>
     </Instance>
     </Instance>
[[Category:Tutorials]]
8,018

edits