User talk:Paradox-01/Archive1: Difference between revisions

From OniGalore
Jump to navigation Jump to search
m (Reverted edits by Hua220 (Talk) to last revision by Iritscen)
m (link fix)
 
(109 intermediate revisions by 4 users not shown)
Line 1: Line 1:
===New art by Guido===
==Contact==
I would suggest you to have a look at my oni2.net section. I am pretty sure you have missed something ^ ^ ([[User:Guido]])
<s>Only email or talk page.</s> Got laptop back.
: --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 22:16, 4 March 2017 (CET)


:Oh man! You are always good in surprises! I'm going to add this. Let me know when you make more of it. I'm addicted to your art. xD
==Image categorization==
:[[User:Paradox-01|Paradox-01]] 15:31, 19 January 2008 (CET)
I really appreciate you helping out with categorizing the images by class. I was hesitant to make a category for Konoko because she's in almost every image on the wiki, so it's a big task if we're going to be thorough. But I guess we can chip away at it. My main concern is that, if we only categorize *some* of each character's/class' images, then how do we ever know if we're done? That's why I was looking through all wiki images for each class that I categorized. That way I could know that I had truly found every image for that class, and cross it off the to-do list. Just something to think about in terms of how we keep track of our remaining work. Also, I wanted to mention that underscores don't matter in category (or any page) names. MediaWiki treats them as space characters, so we usually just use spaces instead. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 22:06, 19 May 2017 (CEST)


----
----
===Translations issues===
Just a reminder to add categories to your images (in the Summary field) when uploading them. See my edits of today for examples of where things should go. Thanks. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 21:48, 27 December 2017 (CET)
Hi Paradox! Been a little while since we talked. I have images from Harry to upload (Fan art), but I have to see if they're new or if any are already up on the wiki somewhere. A project for next week, I think. Anyway, here's my question: I see you have a lot of writing in the Restless Souls section. Some of it is in English, but a lot of the material is ''sprachen en sie Deutsche''! This much foreign language frightens my narrow American brain. Anyway, it would be nice for English speakers (who don't know German) to be able to read it (like me!), but it's a lot of text and I don't want to ask you to rewrite it. May I run it through Babelfish (and clean it up, since Babelfish is far from perfect) and then post it somewhere like Restless Souls/TechnologyEN (for the English version of the Technology page)? The translation won't be great, but it will work. Also, I see you have an orphaned page called "Gapfilling" with some interesting material in English -- emails between Harry and someone at Bungie. Where is that from? It would be nice to incorporate those emails into the wiki somewhere.


P.S.: Is "ikimas" the same Japanese word I'm thinking of? As in, Amuro Ray? --[[User:Iritscen|Iritscen]] 20:52, 15 February 2008 (CET)
==OniSplit source code==
:I watched only Gundam SEED and Gundam SEED Destiny where Kira Yamato says "ikimas" alot. According to wikipedia articles I think it's more or less a remake of various gundam series, so Kira could be influenced by the character of Amuro Ray...
The source code can be retrieved by decompiling OniSplit.exe with [https://www.telerik.com/products/decompiler.aspx "JustDecompile"]. After dragging and dropping the OniSplit into the decompiler you can already browse the code.
:[[User:Paradox-01|Paradox-01]] 00:24, 16 February 2008 (CET)


This should work with any version. This gives us the opportunity to compare them and fix bugs such as the recently discovered [[XML_talk:TRAM#Problem_with_exporting_a_textured_character_with_non-native_TRAC_animation|character dae export bug.]]


@ Fan Art: so Harry gave you them (finally). I have wonder some time but wasn't in mood to ask... However, it's good you can complete  the section; cheers.
If you want to save the code as files, you go to Tools > Create Project.


@ RS: The reasons why RS isn't translated yet: it was a spontaneous porting from my old site (much stuff), the material is still "work in progress" and I am still a bad translator. - After a talk with geyser a little age ago: The plan was to translate little sections while improving them (working more out, improves concepts/theories) and write the stuff onto original pages. (For example: putting the RS SLD section in "add value" or "speculation" of the original SLD page. No need for for extra pages like "TechnologieEN".) But we all had other priorities. - Now: well .. or damn it  .. I've less free time these days but I want ''to do something about the nightmare''. Tell me a section of your interest and I will try to improve it and maybe even translate. For a bigger number of sections you will need Babelfish, hm right. In this case more English speaking wiki user can jump by, read and discussing the stuff; and this might be good .. in the spirit of a wiki ..
After loading the project file into Microsoft Visual Studio Community 2015 Update 3 it looks all good at first sight. But in attempt to build a new exe quite a number of errors per file are shown. In total it's about 1100 whereby multiple errors are found in the same expression.


@ quotes: Ahm.. there's not much material.
Oni.Func<Vector3, float> cSu0024u003cu003e9_CachedAnonymousMethodDelegate3 = RoomBuilder.CS$<>9__CachedAnonymousMethodDelegate3;


:http://carnage.bungie.org/oniforum/oni.forum.pl?read=19468 (http://wiki.oni2.net/User:Paradox-01/quotes_chef_1)
You can find the Main function in Program.cs --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 16:47, 23 August 2016 (CEST)
 
:Honestly, your time would be better spent just writing to Neo asking for a more recent release of the source. We've always known decompilation was a possibility, but then you lose comments and at least some symbol names, which makes the code unnecessarily difficult to work with. Neo has been holding out on releasing the source again until he reaches v1.0 or ports it to .NET Core, but he can probably be convinced to release it or at least fix bugs if you ask nicely. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 18:55, 23 August 2016 (CEST)
 
What makes you think Neo will rewrite OniSplit for .Net Core (released 2016)? -- Anyway, I just found the decompiler by accident and thought it would be a nice addition to .. nothing. I don't have his email address anymore and he doesn't appear on yahoo. Our last chat dates back to 2015 September. Version 0.99 was and is the latest. He said he didn't changes the code for a long time. --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 11:56, 24 August 2016 (CEST)
 
:I said that he might rewrite OniSplit for .NET Core because he told me so :-) I think I have contact info for him, so I'll ask him about the state of OniSplit and a possible source release. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 22:18, 24 August 2016 (CEST)
 
::Sadly, since I have been unable to contact Neo, decompilation is looking like a more relevant option lately. I will write details about this in a more central location in the future, but I am thinking of porting OniSplit's features to C. The conversion code in OniSplit (-create/-extract) is what's really valuable -- the splitting part (-import/-export) should be trivial to re-create -- so for the really technical parts of Neo's code that none of us understand at the moment, we may need to start just dumping in functions composed of OniSplit's decompiled C#, ported to C or C++, and then make sense of those chunks of code in the future, pecking away at them over time. Initially, at least, we won't need to understand them as long as they produce the right results, and over time we can add comments and apply better symbol names if the originals get lost in the process. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 17:00, 4 May 2017 (CEST)
 
==Translations issues==
* An English translation for RS related stuff was requested. Dunno if I really want to translate ''brainstorming'' stuff or if I distillate some parts and wreck the other.
* It has been suggested to put some stuff at Added value sections.
* Keeping track of quotes:
:http://carnage.bungie.org/oniforum/oni.forum.pl?read=19468 ([[User:Paradox-01/quotes_chef_1]])
:http://forums.bungie.org/oni/archive.pl?read=15104
:http://forums.bungie.org/oni/archive.pl?read=15104


Line 30: Line 44:


two more pages (with undocumented sources, cannot find them again):
two more pages (with undocumented sources, cannot find them again):
:http://wiki.oni2.net/User:Paradox-01/quotes_clearfy
:[[User:Paradox-01/quotes_clearfy]]
:http://wiki.oni2.net/User:Paradox-01/quotes_old_questions
:[[User:Paradox-01/quotes_old_questions]]
 
 
==List of (now) unused sections==
While translating I noticed two misplaced sections. "Where went all the details?" was actually part of "Griffin in a Syndicate helicopter?" but off-topic.
* [[Talk:Restless_Souls/Reconstruction/Gapfilling#Where went all the details.3F]] (contains Hardy's talk)
* [[Talk:Restless_Souls/Reconstruction/Gapfilling#Jamie]] (random thoughts)
::Paradox, you do know about this page, right? -- <nowiki>[[Restless_Souls/Reconstruction/Summary_of_2032]]</nowiki>. It is orphaned, so I just wanted to make sure you didn't forget about it. --[[User:Iritscen|Iritscen]] 20:13, 28 February 2008 (CET)
:::^_^ Nah, it's not orphaned but '''part''' of <nowiki>[[Restless_Souls/Reconstruction/Story_factors]]</nowiki> '''as''' <nowiki>"{{:Restless_Souls/Reconstruction/Summary_of_2032}}"</nowiki>
:::I had split material bigger than 32kb and put it into separate pages.
:::But thanks for keeping an eye onto redlinks and such.
:::--[[User:Paradox-01|Paradox-01]] 21:19, 28 February 2008 (CET)
::::Ah, good. Just checking. I never took the time to try to understand the structure of your Restless Souls pages. It's like you have your own little site as part of the wiki :) --[[User:Iritscen|Iritscen]] 21:54, 28 February 2008 (CET)
 
==RS pages structure chart==
 
Restless_Souls
|
+--> various links<br><br>
Restless_Souls/Reconstruction
                | | |
                | | |
                | | +--> <nowiki>{{:Restless_Souls/Reconstruction/Gapfilling}}</nowiki>
                | +----> <nowiki>{{:Restless_Souls/Reconstruction/Global_development}}</nowiki>
                +------> <nowiki>{{:Restless_Souls/Reconstruction/Story_factors}}</nowiki>
 
==XML Project==
Question: "How should I *not* move pages?" Answer: "By using transclusion." :-P  Normally you should use the Move tool, but since the OBD talk pages have had some actual "talk" on them, we probably want to selectively copy and paste the XML content to the new XML: pages. We can discuss this more later, I just wanted to let you know before you made any more "moves" :-)  --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 02:48, 3 November 2012 (CET)
 
: "Answer: By using transclusion"
: By using <nowiki>{{:}}</nowiki>, like I did in XML:AISA ? When I switched off the PC I realized that it wasn't such a good idea (although there was no talk on that page).
: XML:AISA doesn't appear in the search because there's no real content on it. So I agree with you to copy-paste the content. -- [[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 11:15, 3 November 2012 (CET)
 
:Solved. --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 21:16, 6 November 2012 (CET)
 
 
===Broken Links===
Okay, I moved the pages that we agreed did not have notable history or extant discussion that needed to stay in the OBD namespace (sorry it took so long). Note that there are now red links on pages that referred to the moved pages. You could try going [[Special:WantedPages|here]] and searching for "talk". Also, if you search there for "XML"... I assume those are just types that you haven't gotten to document yet? Just curious. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 19:54, 6 November 2012 (CET)
 
: "sorry it took so long" -- I don't mind. Thanks for your assistance. :)
: Yes, there are two file types that still need documentation (and others for sake of completeness). Modding the combat behavior was never my favorite and SABD had not much attention so I used my time on different things. The others will be redirects, either because Oni don't use it (AITR) or because the XML for that instance simply exist as file type ([http://ssg.oni2.net/oni_fi_l.htm AGQR, now part of AKEV]).
: There are one or two things I would like you to pick up: ONLV and maybe TRBS (see list for reason).
 
: things that need care
::XML:AITR replace with better link: redirect to TRGV (I was blindly following analogy to OBD template)
::XML:AGQR replace with better link: redirect to ONLV (^)
::XML:BINA/SABD todo: documentation
::XML:BINA/OBJC/CMBT todo: documentation
::XML:HPge todo: documentation (for sake of completeness)
::''possibly one or two other types that aren't of much use'' --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 21:16, 6 November 2012 (CET)
 
::Okay, I moved ONLV, but what did you want me to do with TRBS? It looks like you already cut-and-pasted it to XML:. But let me know what else I can do to help. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 23:08, 6 November 2012 (CET)
 
lol You are right, I guess my cold makes me dizzy. --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 09:33, 7 November 2012 (CET)
 
Iritscen, when you see this please move another one: <nowiki>http://wiki.oni2.net/OBD_talk:TRGE</nowiki> --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 19:57, 7 November 2012 (CET)
 
 
===Category===
You might want to consider using a category-macro template like [[Template:OBD]] instead of manually entering the category name on each XML page. You can then simply drop a little "<nowiki>{{XML}}</nowiki>" at the bottom of each page, and later on the whole category can be "renamed" if we change our minds. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 14:36, 8 November 2012 (CET)
 
: For the records: 'scen, that worked fine.
 
:: I don't longer remember what this is, can I delete it? [[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 21:14, 2 July 2017 (CEST)
 
 
===Overview===
# Do we have a main XML: page like OBD: has [[OBD:Oni Binary Data]]?  Would it be "XML_basic_tutorial"?
# Is [http://ssg.oni2.net/oni_fi_l.htm SSG's overview] anywhere on the wiki? --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 20:42, 7 November 2012 (CET)
 
:# Not name-wise. I don't wanted to create a new XML:??? page because that would have been pretty much XML_basic_tutorial as you already guessed. Should it be moved to - lets say - XML:basics ?
:# Afaik, ssg's overview isn't on this wiki yet. It would be nice to have a port of it. Maybe following style will be sufficient enough. (There are more overviews, just in case you didn't noticed: [http://ssg.oni2.net/oni_fi_c.htm character files], [http://ssg.oni2.net/oni_fi_m.htm message files], [http://ssg.oni2.net/oni_fi_0.htm level 0 files].)
 
AAAA
  |
  +-- BBBB
  +-- CCCC
  |    |
  |    +-- DDDD
  |
  +-- EEEE
 
 
: I changed my mind: colored table cells could show embedded instances of files, so ssg's style should be better.
: Check this out: <nowiki>https://dl.dropbox.com/u/139715/temp/ssg_overviews_wikified.txt</nowiki> (dead link)
: Now we've to find a good place for it. Any ideas? --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 20:08, 11 November 2012 (CET)
::Ooh, I like! The question of where to put it is a good one, as I would love to find a way to merge that hierarchical information with the acronym expansions given on the [[OBD:File types|File types]] page, and, even better, to also have a small summary of each type ("AKEV (Akira Environment) is ___"). Short of using [[Template:Hover|hover text]], which I don't think is ideal, I don't have any ideas yet as to how to fit everything into one display. It just seems wasteful to use a whole page just for showing relationships, with no explanation of each type; also, the File types page is now somewhat wasteful of space too, since investigation of the file types is essentially done and we no longer need a page to track its progress with smileys. At least, that's my opinion; what do you think?
::P.S.: One small tip -- I'm generally against the use of images external to the wiki. I would suggest uploading SSG's arrow pics to the wiki and then invoking them as shown below. The blank link field makes them non-clickable: <pre>[[File:Wiki.png|link=]]</pre> --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 21:02, 11 November 2012 (CET)
 
 
SSG's arrow pics: before we upload them let's be sure we will use them. (If it's going to be a html from an oni2 user account then we wouldn't upload them.)
 
Proposal of that new page (recycling OBD:file_types). (For Neo's sake, let's keep the ^_^ ? Or another symbol that makes them as done.)
* With a narrow table the content (types + hierarchy + explanation) should fit on one page.
* By default the hierarchy tables and explanations are hidden. Clicking a file type from the list at the left makes the corresponding table + explanation visible.
 
Problem
* If we can't pull this off we might consider writing a html page although a wiki page would be more appropriated.
* I don't know if we can show a table and at same time hide the previous table on click event. At least <nowiki><div></nowiki> demonstrates that some hiding/showing can be done on the wiki.
{{divhide|inspiration}}
Can you reuse the template source code at some point?
{{divhide|end}}
 
PS: [[User:Iritscen/vector.js]] - That's some customization but how do you store/call actual java script functions? --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 15:56, 12 November 2012 (CET)
 
{|class="wikitable" width="100%"
|width="100"|
 
;file types
*<a href="#AISA" id="table_1">AISA</a>
*<a href="#TXMP" id="table_2">TXMP</a>
*<a href="#ONCC" id="table_3">ONCC</a>
 
|width="420"|
{|class="wikitable" width="400" style="text-align:center"
|style="background-color:#DDDDDD;"| TxtC
|width="16.66%"|
|width="16.66%"|
|width="16.66%"|
|width="16.66%"|
|width="16.66%"|
|-
| [[Image:Chart turn right.gif]]
|style="background-color:#DDDDDD; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);"| IGPA
|
|
|
|
|-
|
| [[Image:Chart turn right.gif]]
| style="background-color:#DDDDDD; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);"| IGPG
|
|
|
|-
|
|
| [[Image:Chart fork right.gif]]
|style="background-color:#CCCCFF;"| TSFF
|
|
|-
|
|
| [[Image:Chart descend.gif]]
| [[Image:Chart turn right.gif]]
|style="background-color:#CCCCFF; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);"| TSFL
|
|-
|
|
| [[Image:Chart descend.gif]]
| [[Image:Chart turn right.gif]]
|style="background-color:#CCCCFF; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);"| TSFT
|
|-
|
|
| [[Image:Chart descend.gif]]
|
| [[Image:Chart turn right.gif]]
|style="background-color:#CCCCFF; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);"| TSGA
|-
|
|
| [[Image:Chart fork right.gif]]
| PSpc
|
|
|-
|
|
| [[Image:Chart descend.gif]]
| [[Image:Chart turn right.gif]]
| TXMP
|
|-
|
|
| [[Image:Chart turn right.gif]]
|style="background-color:#DDDDDD; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);"| IGSA
|
|
|-
|
|
|
| [[Image:Chart turn right.gif]]
|style="background-color:#DDDDDD; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);"| IGSt
|
|}
 
|
;explanation of clicked file type
* .......
|}
 
:Cool, I like the diagonal striping; I didn't even know that was possible. I also really like how you fit everything onto the page in three columns. I don't have the time this minute to do much work on this myself, but I can at least answer a couple of your questions.
:'''"For Neo's sake, let's keep the ^_^ ?"''' -- If he still uses them, we should definitely keep them. I guess I was under the impression that Neo isn't really using those anymore. We should ask him.
:'''"I don't know if we can show a table and at same time hide the previous table on click event [...] That's some customization but how do you store/call actual java script functions"''' -- I would direct your attention to [[MediaWiki:Common.js]] (also, note that all the JS pages are linked to on my user page). Towards the top of Common.js is code that imports additional scripts, such as [[MediaWiki:Common.js/edit.js]], based on the type or name of the page. E.g., anyone performing an edit will have edit.js loaded for them, which does things like adding buttons to the toolbar (at least, it will when I fix it!). Does that help? --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 19:39, 12 November 2012 (CET)
:Just a quick note, the repeating-linear-gradient property does not work for WebKit browsers. Chrome/Safari apparently need "-webkit-repeating-linear-gradient" instead. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 03:31, 13 November 2012 (CET)
:Another quick note, we would probably want to mimic the JS that enables the divhide template, as you already suggested and in line with [https://web.archive.org/web/20121031134317/http://www.mwusers.com/forums/showthread.php?18647-onclick-in-wikitext this forum post], which means that we probably want to create a new table class (e.g. "click-table") that responds to 'onclick' events by modifying the text in a column in the table (e.g. "click-table-descrip"). But I can't figure out where the file type description text would come from. We don't really want all the description texts lodged inside the Javascript, but rather somewhere we can edit them freely. One possibility is to figure out how to copy/transclude text from a subpage, similar to the way [[Quotes/Consoles]] works, where each console quote is on a separate, editable page. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 14:38, 13 November 2012 (CET)
 
I tried get myself more familiar with the different codes and their mixing, but I would just ending to make hundreds of edits just to learn how to do this or that. So I can't be a great help here. :/ [[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 22:09, 13 November 2012 (CET)
:That's okay, I have played around with JS before. I'll spend some time on this soon. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 00:42, 14 November 2012 (CET)
 
Okay, I wrote some quick and dirty code and put it in Common.js. Go to my test space's file type table and you should get descriptions when you hover over each type. This could easily be adjusted to require a click instead of a hover but I liked the idea of a no-click interface. I'm going to step aside now and give you the chance to work with this table type as you see fit. I had to simplify the markup for testing purposes, and you might have some better ideas as to how to arrange the table.
 
As you'll see, the basic idea is that you attach the class "hovertable" to a wikitable, then you place multiple spans in one large cell of class "hovertable_descrip". Each span is "display:none" and contains the description for one type, which is given as that span's id. Then you declare other cells in the hovertable as class "hovercell" with ids that match the ones in the descrip cell. The JS I wrote attaches event handlers to all hovercells which display their corresponding span in the hovertable_descrip cell when the hovercell receives 'mouseover', and hide the span upon 'mouseout'. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 20:22, 16 November 2012 (CET)
 
: I checked your test space. It looks awesome, I didn't expected to see so fast results on this. However, there are 2 things I would like you to think about.
:: 1) SSG's "Level files" table (<nowiki>https://dl.dropbox.com/u/139715/temp/ssg_overviews_wikified.txt</nowiki>, dead link) (ONLV) is ''too big'' for an ''absolute location'' of the explanation: if the user hovers the CRSA table cell he would see nothing because the explanation is out of view.
::: The solution to this problem might be to fix the explanation area to the screen. Here's an example made of CSS (<nowiki>https://dl.dropbox.com/u/139715/temp/explanation_fixed_to_screen.htm</nowiki>, dead link). (basically ''style="position: fixed; top: 50%; left: 50%;"'')
:: 2) We talked about merging those hierarchies and the general file type overview. In my last draft the types were vertical listed but I think it will look less odd if  they are horizontal (because the tables differ in their number of rows).
::: At the moment the chasing explanation makes a strange impression but that's due to the other content here. With nothing else then the content under the gray line should look ... not "super" ... but good enough. Or we make a step back and use H template?
:: 2a) If we agree on the merging then the file types should be click-able: if user clicks TxtC type then of course the TxtC table should appear.
::: I think you can reuse the mechanism here you just created. Not sure about IGPG: it appears in TxtC but also in others (DPge, WPge, Opge, ...)
:: '''2b)''' Facing this problem we might choose an easier path than hiding all tables by default.
::: If we put all table under each other we could create "AAAA-using types" sections at the end of all tables: If the user clicked IGPG then the browser jumps to that section and there the user reads IGPG being used by this, this and that type. From there he can jump again (by clicking [<nowiki>[#ABCD|ABCD]]</nowiki>) and reaches his final choice (TxtC/DPge/WPge/... table).
 
 
-----
 
 
 
 
 
 
{| width="100%" style="text-align:center; font-weight:bold;"
| ABNA
| AGQC
| AGQG
| AGQR
| AISA
| AKAA
| AKBA
| AKBP
| AKEV
| AKOT
| AKVA
| BINA
| CBPI
| CBPM
| CONS
| CRSA
| DOOR
| DPge
| ENVP
| FILM
| HPge
| IDXA
| IGHH
|-
| IGPA
| [[#IGPG-using types|IGPG]]
| IGSA
| IGSt
| Impt
| IPge
| KeyI
| M3GA
| M3GM
| Mtrl
| OBAN
| OBOA
| OFGA
| ONCC
| ONCP
| ONCV
| ONGS
| ONIA
| ONLD
| ONLV
| ONOA
| ONSK
| ONVL
|-
| ONWC
| OPge
| OSBD
| OTIT
| OTLF
| PLEA
| PNTA
| PSpc
| PSpL
| PSUI
| QTNA
| SNDD
| SUBT
| TRAC
| TRAM
| TRAS
| TRBS
| TRCM
| TRGA
| TRGE
| TRIA
| TRIG
| TRMA
|-
| TRSC
| TRTA
| TSFF
| TSFL
| TSFT
| TSGA
| TURR
| TXAN
| TXCA
| TXMA
| TXMB
| TXMP
| [[#TxtC|TxtC]]
| VCRA
| WMCL
| WMDD
| WMM
| WMMB
| WPge
|}


:[[User:Paradox-01|Paradox-01]] 00:24, 16 February 2008 (CET)
Based on OBD:file_types. Maybe we should list BINA subtypes too (object collections like [[XML:BINA/OBJC/CHAR|CHAR]], CONS, DOOR, ...) ?


Interesting. Thanks for the links. Sorry for such a long delay in responding, but it's hard to say what should be translated first, since I can't read any of it... maybe the sections where you comment on the quotes of the emails. There's at least one page where you have those emails in English, but your commentary is in German; it would be nice to be able to read that part.


Perhaps I can run your pages through Babelfish, and we'll see if the translation is even slightly acceptable. Then you can simply alter the wording a little if it's not correct. It could save you a lot of typing if you can start from there. I don't want to mess with your pages, so I will post the translation somewhere nearby. --[[User:Iritscen|Iritscen]] 15:55, 21 February 2008 (CET)
====TxtC====
{|width="100%"
|width="200" valign="top"|  


:Okay, I just can't do it. Check this out:
{|class="wikitable hovertable" width="400" style="text-align:center; font-weight:bold;"
::<font color="red">Herkunft und Alter von Barabas, so wie bei vielen anderen Charakteren, zu bestimmen, gleicht Kaffeesätze zu lesen - dies wird nochmals durch sein Mutanten-Dasein erschwert... Das Beste wird wohl sein einfach ein paar Sachen festzulegen, die der gewählten Zeitlinie zumindest nicht widersprechen. Von dem was der Name hergibt, wurde im OniGalore eine nette Theorie aufgestellt mit der man Barabas' Hintergrund flicken könnte. Und ganau das habe ich nun mit einem selbstgewähltem Szenario vor darstellen. (Ein grundsätzlich freien Hintergrund stelle ich jedoch auch zur Verfügung falls die erste Variante auf zu viel Kritik stößt, die man gegebenfalls nicht mehr anpassen kann.)</font>
|style="background-color:#DDDDDD;" class="hovercell" id="txtc"| [[TxtC]]
|width="16.66%"|
|width="16.66%"|
|width="16.66%"|
|width="16.66%"|
|width="16.66%"|
|-
| [[Image:Chart turn right.gif]]
|style="background-color:#DDDDDD; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);" class="hovercell" id="igpa"| [[IGPA]]
|
|
|
|
|-
|
| [[Image:Chart turn right.gif]]
| style="background-color:#DDDDDD; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);" class="hovercell" id="igpg"| [[IGPG]]
|
|
|
|-
|
|
| [[Image:Chart fork right.gif]]
|style="background-color:#CCCCFF;" class="hovercell" id="tsff"| [[TSFF]]
|
|
|-
|
|
| [[Image:Chart descend.gif]]
| [[Image:Chart turn right.gif]]
|style="background-color:#CCCCFF; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);" class="hovercell" id="tsfl"| [[TSFL]]
|
|-
|
|
| [[Image:Chart descend.gif]]
| [[Image:Chart turn right.gif]]
|style="background-color:#CCCCFF; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);" class="hovercell" id="tsft"| [[TSFT]]
|
|-
|
|
| [[Image:Chart descend.gif]]
|
| [[Image:Chart turn right.gif]]
|style="background-color:#CCCCFF; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);" class="hovercell" id="tsga"| [[TSGA]]
|-
|
|
| [[Image:Chart fork right.gif]]
|class="hovercell" id="pspc"| [[PSpc]]
|
|
|-
|
|
| [[Image:Chart descend.gif]]
| [[Image:Chart turn right.gif]]
|class="hovercell" id="txmp"| [[TXMP]]
|
|-
|
|
| [[Image:Chart turn right.gif]]
|style="background-color:#DDDDDD; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);" class="hovercell" id="igsa"| [[IGSA]]
|
|
|-
|
|
|
| [[Image:Chart turn right.gif]]
|style="background-color:#DDDDDD; background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(255,255,255,.5) 10px, rgba(255,255,255,.5) 20px);" class="hovercell" id="igst"| [[IGSt]]
|}


becomes
|valign="top"|


::<font color="blue">Origin and age of Barabas, as with many other characters to determine resemble coffee-corrode to read - this again by to be Mutanten existence difficult more difficult... The best will probably be simply a few things to specify, which do not contradict the selected zeitlinie at least. From which the name gives, became in the OniGalore a nice theory set up with which one to Barabas ' background repair could. And ganau I have that now with a self-chosen scenario forwards to explain. (in principle a free background make available I however also if the first variant too much criticism encounters, which one cannot adapt no more to if necessary.)</font>
{|style="position: fixed; top: 30%"
|class="hovertable_descrip" valign="top"|
<span style="display:none; background-color:#EEEEEE; border-color:#DDDDDD; border-width:1px; border-style:solid; padding:10px;" id="txtc">'''TxtC''': This is console text.</span>
<span style="display:none; background-color:#EEEEEE; border-color:#DDDDDD; border-width:1px; border-style:solid; padding:10px;" id="igpa">'''IGPA''': In-Game User Interface Page Array.</span>
<span style="display:none; background-color:#EEEEEE; border-color:#DDDDDD; border-width:1px; border-style:solid; padding:10px;" id="igpg">'''IGPG''': In-Game User Interface Page.</span>
<span style="display:none; background-color:#EEEEEE; border-color:#DDDDDD; border-width:1px; border-style:solid; padding:10px;" id="tsff">'''TSFF''': A font family.</span>
<span style="display:none; background-color:#EEEEEE; border-color:#DDDDDD; border-width:1px; border-style:solid; padding:10px;" id="tsfl">'''TSFL''': A font language.</span>
<span style="display:none; background-color:#EEEEEE; border-color:#DDDDDD; border-width:1px; border-style:solid; padding:10px;" id="tsft">'''TSFT''': Actual font bitmaps.</span>
<span style="display:none; background-color:#EEEEEE; border-color:#DDDDDD; border-width:1px; border-style:solid; padding:10px;" id="tsga">'''TSGA''': A glyph array linking 256 possible symbols to their bitmaps (TSFTs).</span>
<span style="display:none; background-color:#EEEEEE; border-color:#DDDDDD; border-width:1px; border-style:solid; padding:10px;" id="pspc">'''PSpc''': Part Specification (coordinates for finding a UI symbol in a bitmap collection of UI elements.</span>
<span style="display:none; background-color:#EEEEEE; border-color:#DDDDDD; border-width:1px; border-style:solid; padding:10px;" id="txmp">'''TXMP''': A texture map!</span>
<span style="display:none; background-color:#EEEEEE; border-color:#DDDDDD; border-width:1px; border-style:solid; padding:10px;" id="igsa">'''IGSA''': In-Game user interface String Array.</span>
<span style="display:none; background-color:#EEEEEE; border-color:#DDDDDD; border-width:1px; border-style:solid; padding:10px;" id="igst">'''IGSt''': In-Game user interface STring.</span>
|}


I think that it would be harder for you to fix that mess than to just translate your own German. Well, whenever you have time, maybe you can do a little at a time. Just so others can benefit from your ideas. I see that you wrote a LOT of material, though, so it would take a lot of time to translate. I was hoping that Babelfish would give you a headstart, but if you read what it gives me for your pages, you wouldn't even recognize it as something you wrote :-\ --[[User:Iritscen|Iritscen]] 16:39, 21 February 2008 (CET)
|}


:Nice chaos. ^_^ In German you can move around various parts of a sentence without making it non-understandable. And babelfish seems to lack this skill.
: > Well, whenever you have time, maybe you can do a little at a time.
:Will do that. --[[User:Paradox-01|Paradox-01]] 19:20, 21 February 2008 (CET)


Babelfish is actually used for laughs sometimes because it's so bad, but I guess I was naive in thinking that it could even give you a starting point. It would take longer to fix each mistake than to write every word from scratch.
[ other tables ]


Speaking of laughs:


:<font color="red">Aus dem achten und neunten Band des Manga Battle Angel Alita, Last Order. (Nur um das klarzustellen: der Text handelt von Vampir-Werdung...)</font>


becomes


:<font color="blue">From the respected and ninth volume of the Manga Battle fishing rod Alita, load order. to get straight (only around: the text acts of Vampir becoming...)</font>


Fear the deadly fishing rod Alita! --[[User:Iritscen|Iritscen]] 19:37, 21 February 2008 (CET)
====IGPG-using types====
:All I can say : rofl.--[[User:Paradox-01|Paradox-01]] 16:00, 23 February 2008 (CET)
* [[#TxtC|TxtC]]
* OPge
* IPge
* WPge


----
===List of translated pages / sections===
* [[Restless_Souls/Ikimas]]
* [[Restless_Souls/Reconstruction/Gapfilling]]


----
----
===List of (now) unused sections===
Ah, the fixed-position box is interesting, that could be the answer. I think we will need to have a chat before I can fully understand what we are trying to document, though, in terms of what/how hierarchies are to be shown. I'll look for you online this weekend. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 03:41, 17 November 2012 (CET)
While translating I noticed two misplaced sections. "Where went all the details?" was actually part of "Griffin in a Syndicate helicopter?" but off-topic.
* [[Talk:Restless_Souls/Reconstruction/Gapfilling#Where went all the details.F3]] (contains Hardy's talk)
* [[Talk:Restless_Souls/Reconstruction/Gapfilling#Jamie]] (random thoughts)
::Paradox, you do know about this page, right? -- [[Restless_Souls/Reconstruction/Summary_of_2032]]. It is orphaned, so I just wanted to make sure you didn't forget about it. --[[User:Iritscen|Iritscen]] 20:13, 28 February 2008 (CET)
:::^_^ Nah, it's not orphaned but '''part''' of [[Restless_Souls/Reconstruction/Story_factors]] '''as''' <nowiki>"{{:Restless_Souls/Reconstruction/Summary_of_2032}}"</nowiki>
:::I had split material bigger than 32kb and put it into separate pages.
:::But thanks for keeping an eye onto redlinks and such.
:::--[[User:Paradox-01|Paradox-01]] 21:19, 28 February 2008 (CET)
::::Ah, good. Just checking. I never took the time to try to understand the structure of your Restless Souls pages. It's like you have your own little site as part of the wiki :) --[[User:Iritscen|Iritscen]] 21:54, 28 February 2008 (CET)


----
Just a note on where I left off -- I fixed the classes so that the cells are being styled correctly. However, I seem to have accidentally changed the stripe style; I didn't mean to create a stripe with a gradient in it; I just want to make the blue and background colors evenly spaced at 10px or 15px. Also, the "position:fixed" on the descrip cell was somehow shifting the location of the next cell (TxtC), so for now I have removed that property. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 23:56, 17 November 2012 (CET)


===RS pages structure chart===
:If you look closely there are 3 px value in the gradient code: for clean stripes let the last value be the sum of the others.
: background-image: -webkit-repeating-linear-gradient(-45deg, transparent, transparent '''10px''', rgba(0, 0, 255, 0.2) '''10px''', rgba(0, 0, 255, 0.2) '''20px'''); --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 11:29, 18 November 2012 (CET)


Restless_Souls
: The table in your [[User:Iritscen/TestSpace|test space]] will look okay if you enable the position fixed in Common.css again. That code piece rips the cell out of the table. I added some columns to fix it. --13:12, 18 November 2012 (CET)
|
+--> various links<br><br>
Restless_Souls/Reconstruction
                | | |
                | | |
                | | +--> <nowiki>{{:Restless_Souls/Reconstruction/Gapfilling}}</nowiki>
                | +----> <nowiki>{{:Restless_Souls/Reconstruction/Global_development}}</nowiki>
                +------> <nowiki>{{:Restless_Souls/Reconstruction/Story_factors}}</nowiki>
                                                          |
                                                          +--> '''<nowiki>{{:Restless_Souls/Reconstruction/Summary_of_2032}}</nowiki>'''


----
Sorry, 'dox, I didn't think it would take very long, but after I had written some of the JavaScript, I could see how complicated it would be. Then I got sidetracked by real life for a while. Normally I would just keep at it until it's done, but seeing as I am trying to get back to my main Oni project ASAP, I'm afraid I have to cut short my work on this. Maybe it's more complicated than it needs to be. If you want to "retreat" back to a simpler solution, then let me know how I can help with that. Otherwise I might have time to finish this at a later date. I just don't want to spend hours on it when it's keeping me from my other work. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 20:57, 17 December 2012 (CET)


===Deleted teaser===
===New overview===
:Maybe you shouldn't be deleting parts of your pages like that just because they don't seem to fit right now.
Just wanted to say, I still feel this is an important thing to add to the wiki. But I made it too complex the first time around. Rather than a dynamically generated table, we should probably stick to something that is set up manually. Although my more complex code was never finished, we do still have the hovertable class available, as used above (and I can easily change it to display info on a click instead of a mouse-hover if that's better). Let me know if you have any new ideas on how to present the info, or if you want to stick with the format we had before.
:Of course they're kept in the history, but maybe you could use talk pages as a temporary dump for such stuff.
::[[User:Geyser|geyser]] 21:06, 20 February 2008 (CET)


::What did he delete? --[[User:Iritscen|Iritscen]] 15:55, 21 February 2008 (CET)
The fact is, looking at this with a fresh perspective, I'm not 100% convinced that the arrow-based table is the best use of space or the easiest thing to read, or that we need fancy JS either. What about the simple text-based approach I suggested [[Special:Permalink/21714#Organizing_the_modding_side_of_the_wiki|here]], combined with your anchor-based TOC serving as an alphabetical index at the beginning? --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 00:03, 18 April 2013 (CEST)


::: .. draft of a (sucking) "message" article / teaser. [http://wiki.oni2.net/w/index.php?title=Restless_Souls/Ikimas&curid=2450&diff=8173&oldid=8068 link.] I recently felt annoyed about it. --[[User:Paradox-01|Paradox-01]] 16:17, 21 February 2008 (CET)
: About that thing at [[Special:Permalink/21714#Organizing_the_modding_side_of_the_wiki|Current_events]]. Sounds like you want a simple page with sections and links. So if you don't want to hierarchal information then you could take [[XML:File_types]] and extend it. In that case I wouldn't use '''<nowiki>===</nowiki>''' but '''<nowiki>{{Anchor|some_anchor_name}}</nowiki>'''. This prevents the page to be ripped in sections. By that the user can follow links and the page will still look nice. --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 12:56, 18 April 2013 (CEST)


----
::Basically, yes. I like that "File types" page, I just would like the descriptions to be a bit longer and to list what types they have under them, or what types can contain them, and maybe group them by type. I think I'll make a separate WIP table in my userspace so I don't mess up yours, because I'm not 100% clear on what I want it to look like. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 13:59, 18 April 2013 (CEST)
===Double images===
::Okay, it can use some nicer formatting, but if you look at my [[User:Iritscen/TestSpace|TestSpace]], you'll see what I had in mind. It's similar to your XML File types page, just organized by category, and with "parent" and "child" anchor links to the related types on the same page. Probably it can also contain your colored documentation dots and the types can link to their XML: pages instead of OBD:, at least if this replaces your File types page. Any suggestions? --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 22:07, 19 April 2013 (CEST)
> OK, why the blam did you name it "TCTF Cracked"? (edit: quote from [http://wiki.oni2.net/w/index.php?title=Image:Ian_McConville_Desktop_1600.jpg&action=history HERE])


Well, there's another thing you don't know yet. .. ahm .. ^_^"
Caution, the header template on pages like [[XML:BINA/OBJC/CHAR]] link to "other BINA" and "other OBJC" ([[XML:File_types]]) in analogy to [[OBD:BINA/OBJC]] and [[OBD:BINA]].
http://wiki.oni2.net/Image:TFTC_screen_smash_1600.jpg      (14. Jan 2008) by Paradox-01
http://wiki.oni2.net/Image:TCTF_Cracked.jpg  (1280 x 1024) (16. Jan 2008) by Iritscen
  http://wiki.oni2.net/Image:Ian_McConville_Desktop_1600.jpg (21. Feb 2008) by Geyser


:Now let's all say "Oops" in unison. Well, geyser and I, at least. Apparently I didn't see it in the Gallery (although it could have been there, I just didn't see it) and voila, wasted bandwidth. Who knows what Geyser's excuse is :)
I like how you structure the descriptions, I'm just a bit unhappy with the index thing because of the mentioned template header.
:I don't know where the quote came from about "why the blam" is it named "TCTF Cracked", but as an answer, I don't think I provided that name; it came from somewhere else.
As a compromise perhaps make 3 type indices so that the template can still link to those.
:I'm positive there are more duplicate images out there, but I am not looking for them until I am done with the image uploading I'll be doing in the next week. --[[User:Iritscen|Iritscen]] 19:33, 21 February 2008 (CET)
:Type index: BINA
:* [...]
:Type index: CJBO
:* [...]
:Type index: other files
:* [...]


----
:Add color dots and links and I totally agree with replacing current file types page with this second version. :) --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 22:43, 19 April 2013 (CEST)
===Lorraine Art and Tutorial===
::Sorry, I don't understand the point you're making. I'm not 100% fluent in where all Oni's data is stored (particularly what is in .sep vs. .raw), but my idea was that this wasn't an important distinction to make for the beginner who just wants to know what these kinds of data do. After all, we no longer have to know which file to look in with a hex editor to mod something, we just ask OniSplit to export the data :-) But please let me know what you meant if there's a reason the reader has to think in terms of BINA vs. CBJO vs. everything else. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 23:17, 19 April 2013 (CEST)
Where oh where did you get those high-res images of Jamie and Hasegawa? That's really cool.


Also, and nice job carrying over the Tutorial from HTML. I just saw it for the first time. --[[User:Iritscen|Iritscen]] 16:08, 12 March 2008 (CET)
I just want the user to be aware of what types belong to object collections (for instance so he does chose the door collection and not the door class) and that searches can be easily be done by BINA*/BINAOBJC*. --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 14:19, 20 April 2013 (CEST)


:Yea, it might be one of the last big Oni secrets out there... I searched like crazy on the net but didn't found the source again. Probable not even [http://www.archive.org/web/web.php wayback] have them anymore. The images here are from a very old and incomplete back-up. ~sigh~
[[Category:Userspace]]
::[[User:Paradox-01|Paradox-01]] 22:00, 12 March 2008 (CET)
:The official Oni page on bungie.net used to have a collection of in-game art.
::(That's where the hi-res splashscreens and Hasegawa drawings are from)
:They were removed for some reason when bungie.net was redesigned.
::[[User:Geyser|geyser]] 22:37, 12 March 2008 (CET)
:Muhahahahar, I get sick. They still have them on the server but unlinked. I toyed with the URLs and viola.
:<del>Will upload them later, time runs out again. - Or you do it. They differ only in the numbers... ~sigh~</del> Done.
::[[User:Paradox-01|Paradox-01]] 23:10, 12 March 2008 (CET)
:::That is ''awesome'', Paradox, ''great'' discovery. You don't have to u/l them all right now, but have you d/led all the mission start/end/whatever screens and the "dream" images to your computer? As long as you have them d/led, I can stop worrying that the Bungie webmaster will be like, "Hey, what are these unused files doing here? *delete*". --[[User:Iritscen|Iritscen]] 17:09, 13 March 2008 (CET)
::::"Aw, c'm'on..." I've had them all backed up for ''years'', guys... [[User:Geyser|geyser]] 17:13, 13 March 2008 (CET)
::Ok, you did not upload them here but you did not even told us that you have them. Do you so much enjoyed our tremble? =P --[[User:Paradox-01|Paradox-01]] 17:23, 13 March 2008 (CET)
----
===Random discovers===
How the Oni music CD looks like:
http://www.bysmitty.com/Soundtracks/Oni/Oni.htm
:Yeah, I had to look up the cover art myself just last week to apply to the Oni tracks in iTunes. I just wish that ugly Best Buy label wasn't part of the cover. (I could probably 'shop it out, but I'm too lazy.)
Oni icons for mac:
http://amarsagoo.info/design/icons/index.shtml (Cannot open it. Someone, please check it. Maybe it's useful.)
:I will check them out. They could be very useful for the Mac version of the Edition. How interesting that he produced only a few sets of icons, and he picked Oni as his only game to design icons for. --[[User:Iritscen|Iritscen]] 17:13, 13 March 2008 (CET)
I wondered what hits google would give me for "HapeMask". Didn't found a picture of it but a fan of the game, somehow funny. http://web.archive.org/web/20050413113423/www.hapemask.com/whatisthehape.php
:I didn't even recognize "HapeMask" when you said it, and then it came back to me when I followed the link. But I remember immediately thinking of post-apocalyptic Pokémon when I first saw the poster. "Meowth says, 'Don't forget to wear your mask, kiddies! That air'll kill ya!'" Something like Hapémask would ''definitely'' have to appear in an Oni sequel. :-) --[[User:Iritscen|Iritscen]] 19:42, 18 March 2008 (CET)
----
===Thanks for Silly World write-up===
I really appreciate you taking the time to document geyser's mod.  I know it will be useful at some point... possibly in BGI... oh, and you'll be hearing from me soon about that.  P.S.: Don't be a stranger, visit us on YIM once in a while! --[[User:Iritscen|Iritscen]] 13:30, 7 February 2010 (UTC)

Latest revision as of 17:35, 24 December 2023

Contact

Only email or talk page. Got laptop back.

--paradox-01 (talk) 22:16, 4 March 2017 (CET)

Image categorization

I really appreciate you helping out with categorizing the images by class. I was hesitant to make a category for Konoko because she's in almost every image on the wiki, so it's a big task if we're going to be thorough. But I guess we can chip away at it. My main concern is that, if we only categorize *some* of each character's/class' images, then how do we ever know if we're done? That's why I was looking through all wiki images for each class that I categorized. That way I could know that I had truly found every image for that class, and cross it off the to-do list. Just something to think about in terms of how we keep track of our remaining work. Also, I wanted to mention that underscores don't matter in category (or any page) names. MediaWiki treats them as space characters, so we usually just use spaces instead. --Iritscen (talk) 22:06, 19 May 2017 (CEST)


Just a reminder to add categories to your images (in the Summary field) when uploading them. See my edits of today for examples of where things should go. Thanks. --Iritscen (talk) 21:48, 27 December 2017 (CET)

OniSplit source code

The source code can be retrieved by decompiling OniSplit.exe with "JustDecompile". After dragging and dropping the OniSplit into the decompiler you can already browse the code.

This should work with any version. This gives us the opportunity to compare them and fix bugs such as the recently discovered character dae export bug.

If you want to save the code as files, you go to Tools > Create Project.

After loading the project file into Microsoft Visual Studio Community 2015 Update 3 it looks all good at first sight. But in attempt to build a new exe quite a number of errors per file are shown. In total it's about 1100 whereby multiple errors are found in the same expression.

Oni.Func<Vector3, float> cSu0024u003cu003e9_CachedAnonymousMethodDelegate3 = RoomBuilder.CS$<>9__CachedAnonymousMethodDelegate3;

You can find the Main function in Program.cs --paradox-01 (talk) 16:47, 23 August 2016 (CEST)

Honestly, your time would be better spent just writing to Neo asking for a more recent release of the source. We've always known decompilation was a possibility, but then you lose comments and at least some symbol names, which makes the code unnecessarily difficult to work with. Neo has been holding out on releasing the source again until he reaches v1.0 or ports it to .NET Core, but he can probably be convinced to release it or at least fix bugs if you ask nicely. --Iritscen (talk) 18:55, 23 August 2016 (CEST)

What makes you think Neo will rewrite OniSplit for .Net Core (released 2016)? -- Anyway, I just found the decompiler by accident and thought it would be a nice addition to .. nothing. I don't have his email address anymore and he doesn't appear on yahoo. Our last chat dates back to 2015 September. Version 0.99 was and is the latest. He said he didn't changes the code for a long time. --paradox-01 (talk) 11:56, 24 August 2016 (CEST)

I said that he might rewrite OniSplit for .NET Core because he told me so :-) I think I have contact info for him, so I'll ask him about the state of OniSplit and a possible source release. --Iritscen (talk) 22:18, 24 August 2016 (CEST)
Sadly, since I have been unable to contact Neo, decompilation is looking like a more relevant option lately. I will write details about this in a more central location in the future, but I am thinking of porting OniSplit's features to C. The conversion code in OniSplit (-create/-extract) is what's really valuable -- the splitting part (-import/-export) should be trivial to re-create -- so for the really technical parts of Neo's code that none of us understand at the moment, we may need to start just dumping in functions composed of OniSplit's decompiled C#, ported to C or C++, and then make sense of those chunks of code in the future, pecking away at them over time. Initially, at least, we won't need to understand them as long as they produce the right results, and over time we can add comments and apply better symbol names if the originals get lost in the process. --Iritscen (talk) 17:00, 4 May 2017 (CEST)

Translations issues

  • An English translation for RS related stuff was requested. Dunno if I really want to translate brainstorming stuff or if I distillate some parts and wreck the other.
  • It has been suggested to put some stuff at Added value sections.
  • Keeping track of quotes:
http://carnage.bungie.org/oniforum/oni.forum.pl?read=19468 (User:Paradox-01/quotes_chef_1)
http://forums.bungie.org/oni/archive.pl?read=15104

note about influences:

http://forums.bungie.org/oni/archive.pl?read=4618

search page (somehow defunct):

http://forums.bungie.org/oni/archive.pl?

two more pages (with undocumented sources, cannot find them again):

User:Paradox-01/quotes_clearfy
User:Paradox-01/quotes_old_questions


List of (now) unused sections

While translating I noticed two misplaced sections. "Where went all the details?" was actually part of "Griffin in a Syndicate helicopter?" but off-topic.

Paradox, you do know about this page, right? -- [[Restless_Souls/Reconstruction/Summary_of_2032]]. It is orphaned, so I just wanted to make sure you didn't forget about it. --Iritscen 20:13, 28 February 2008 (CET)
^_^ Nah, it's not orphaned but part of [[Restless_Souls/Reconstruction/Story_factors]] as "{{:Restless_Souls/Reconstruction/Summary_of_2032}}"
I had split material bigger than 32kb and put it into separate pages.
But thanks for keeping an eye onto redlinks and such.
--Paradox-01 21:19, 28 February 2008 (CET)
Ah, good. Just checking. I never took the time to try to understand the structure of your Restless Souls pages. It's like you have your own little site as part of the wiki :) --Iritscen 21:54, 28 February 2008 (CET)

RS pages structure chart

Restless_Souls
|
+--> various links

Restless_Souls/Reconstruction | | | | | | | | +--> {{:Restless_Souls/Reconstruction/Gapfilling}} | +----> {{:Restless_Souls/Reconstruction/Global_development}} +------> {{:Restless_Souls/Reconstruction/Story_factors}}

XML Project

Question: "How should I *not* move pages?" Answer: "By using transclusion." :-P Normally you should use the Move tool, but since the OBD talk pages have had some actual "talk" on them, we probably want to selectively copy and paste the XML content to the new XML: pages. We can discuss this more later, I just wanted to let you know before you made any more "moves" :-) --Iritscen (talk) 02:48, 3 November 2012 (CET)

"Answer: By using transclusion"
By using {{:}}, like I did in XML:AISA ? When I switched off the PC I realized that it wasn't such a good idea (although there was no talk on that page).
XML:AISA doesn't appear in the search because there's no real content on it. So I agree with you to copy-paste the content. -- paradox-01 (talk) 11:15, 3 November 2012 (CET)
Solved. --paradox-01 (talk) 21:16, 6 November 2012 (CET)


Broken Links

Okay, I moved the pages that we agreed did not have notable history or extant discussion that needed to stay in the OBD namespace (sorry it took so long). Note that there are now red links on pages that referred to the moved pages. You could try going here and searching for "talk". Also, if you search there for "XML"... I assume those are just types that you haven't gotten to document yet? Just curious. --Iritscen (talk) 19:54, 6 November 2012 (CET)

"sorry it took so long" -- I don't mind. Thanks for your assistance. :)
Yes, there are two file types that still need documentation (and others for sake of completeness). Modding the combat behavior was never my favorite and SABD had not much attention so I used my time on different things. The others will be redirects, either because Oni don't use it (AITR) or because the XML for that instance simply exist as file type (AGQR, now part of AKEV).
There are one or two things I would like you to pick up: ONLV and maybe TRBS (see list for reason).
things that need care
XML:AITR replace with better link: redirect to TRGV (I was blindly following analogy to OBD template)
XML:AGQR replace with better link: redirect to ONLV (^)
XML:BINA/SABD todo: documentation
XML:BINA/OBJC/CMBT todo: documentation
XML:HPge todo: documentation (for sake of completeness)
possibly one or two other types that aren't of much use --paradox-01 (talk) 21:16, 6 November 2012 (CET)
Okay, I moved ONLV, but what did you want me to do with TRBS? It looks like you already cut-and-pasted it to XML:. But let me know what else I can do to help. --Iritscen (talk) 23:08, 6 November 2012 (CET)

lol You are right, I guess my cold makes me dizzy. --paradox-01 (talk) 09:33, 7 November 2012 (CET)

Iritscen, when you see this please move another one: http://wiki.oni2.net/OBD_talk:TRGE --paradox-01 (talk) 19:57, 7 November 2012 (CET)


Category

You might want to consider using a category-macro template like Template:OBD instead of manually entering the category name on each XML page. You can then simply drop a little "{{XML}}" at the bottom of each page, and later on the whole category can be "renamed" if we change our minds. --Iritscen (talk) 14:36, 8 November 2012 (CET)

For the records: 'scen, that worked fine.
I don't longer remember what this is, can I delete it? paradox-01 (talk) 21:14, 2 July 2017 (CEST)


Overview

  1. Do we have a main XML: page like OBD: has OBD:Oni Binary Data? Would it be "XML_basic_tutorial"?
  2. Is SSG's overview anywhere on the wiki? --Iritscen (talk) 20:42, 7 November 2012 (CET)
  1. Not name-wise. I don't wanted to create a new XML:??? page because that would have been pretty much XML_basic_tutorial as you already guessed. Should it be moved to - lets say - XML:basics ?
  2. Afaik, ssg's overview isn't on this wiki yet. It would be nice to have a port of it. Maybe following style will be sufficient enough. (There are more overviews, just in case you didn't noticed: character files, message files, level 0 files.)
AAAA
 |
 +-- BBBB
 +-- CCCC
 |    |
 |    +-- DDDD
 |
 +-- EEEE


I changed my mind: colored table cells could show embedded instances of files, so ssg's style should be better.
Check this out: https://dl.dropbox.com/u/139715/temp/ssg_overviews_wikified.txt (dead link)
Now we've to find a good place for it. Any ideas? --paradox-01 (talk) 20:08, 11 November 2012 (CET)
Ooh, I like! The question of where to put it is a good one, as I would love to find a way to merge that hierarchical information with the acronym expansions given on the File types page, and, even better, to also have a small summary of each type ("AKEV (Akira Environment) is ___"). Short of using hover text, which I don't think is ideal, I don't have any ideas yet as to how to fit everything into one display. It just seems wasteful to use a whole page just for showing relationships, with no explanation of each type; also, the File types page is now somewhat wasteful of space too, since investigation of the file types is essentially done and we no longer need a page to track its progress with smileys. At least, that's my opinion; what do you think?
P.S.: One small tip -- I'm generally against the use of images external to the wiki. I would suggest uploading SSG's arrow pics to the wiki and then invoking them as shown below. The blank link field makes them non-clickable:
[[File:Wiki.png|link=]]
--Iritscen (talk) 21:02, 11 November 2012 (CET)


SSG's arrow pics: before we upload them let's be sure we will use them. (If it's going to be a html from an oni2 user account then we wouldn't upload them.)

Proposal of that new page (recycling OBD:file_types). (For Neo's sake, let's keep the ^_^ ? Or another symbol that makes them as done.)

  • With a narrow table the content (types + hierarchy + explanation) should fit on one page.
  • By default the hierarchy tables and explanations are hidden. Clicking a file type from the list at the left makes the corresponding table + explanation visible.

Problem

  • If we can't pull this off we might consider writing a html page although a wiki page would be more appropriated.
  • I don't know if we can show a table and at same time hide the previous table on click event. At least <div> demonstrates that some hiding/showing can be done on the wiki.

PS: User:Iritscen/vector.js - That's some customization but how do you store/call actual java script functions? --paradox-01 (talk) 15:56, 12 November 2012 (CET)

file types
  • <a href="#AISA" id="table_1">AISA</a>
  • <a href="#TXMP" id="table_2">TXMP</a>
  • <a href="#ONCC" id="table_3">ONCC</a>
TxtC
Chart turn right.gif IGPA
Chart turn right.gif IGPG
Chart fork right.gif TSFF
Chart descend.gif Chart turn right.gif TSFL
Chart descend.gif Chart turn right.gif TSFT
Chart descend.gif Chart turn right.gif TSGA
Chart fork right.gif PSpc
Chart descend.gif Chart turn right.gif TXMP
Chart turn right.gif IGSA
Chart turn right.gif IGSt
explanation of clicked file type
  • .......
Cool, I like the diagonal striping; I didn't even know that was possible. I also really like how you fit everything onto the page in three columns. I don't have the time this minute to do much work on this myself, but I can at least answer a couple of your questions.
"For Neo's sake, let's keep the ^_^ ?" -- If he still uses them, we should definitely keep them. I guess I was under the impression that Neo isn't really using those anymore. We should ask him.
"I don't know if we can show a table and at same time hide the previous table on click event [...] That's some customization but how do you store/call actual java script functions" -- I would direct your attention to MediaWiki:Common.js (also, note that all the JS pages are linked to on my user page). Towards the top of Common.js is code that imports additional scripts, such as MediaWiki:Common.js/edit.js, based on the type or name of the page. E.g., anyone performing an edit will have edit.js loaded for them, which does things like adding buttons to the toolbar (at least, it will when I fix it!). Does that help? --Iritscen (talk) 19:39, 12 November 2012 (CET)
Just a quick note, the repeating-linear-gradient property does not work for WebKit browsers. Chrome/Safari apparently need "-webkit-repeating-linear-gradient" instead. --Iritscen (talk) 03:31, 13 November 2012 (CET)
Another quick note, we would probably want to mimic the JS that enables the divhide template, as you already suggested and in line with this forum post, which means that we probably want to create a new table class (e.g. "click-table") that responds to 'onclick' events by modifying the text in a column in the table (e.g. "click-table-descrip"). But I can't figure out where the file type description text would come from. We don't really want all the description texts lodged inside the Javascript, but rather somewhere we can edit them freely. One possibility is to figure out how to copy/transclude text from a subpage, similar to the way Quotes/Consoles works, where each console quote is on a separate, editable page. --Iritscen (talk) 14:38, 13 November 2012 (CET)

I tried get myself more familiar with the different codes and their mixing, but I would just ending to make hundreds of edits just to learn how to do this or that. So I can't be a great help here. :/ paradox-01 (talk) 22:09, 13 November 2012 (CET)

That's okay, I have played around with JS before. I'll spend some time on this soon. --Iritscen (talk) 00:42, 14 November 2012 (CET)

Okay, I wrote some quick and dirty code and put it in Common.js. Go to my test space's file type table and you should get descriptions when you hover over each type. This could easily be adjusted to require a click instead of a hover but I liked the idea of a no-click interface. I'm going to step aside now and give you the chance to work with this table type as you see fit. I had to simplify the markup for testing purposes, and you might have some better ideas as to how to arrange the table.

As you'll see, the basic idea is that you attach the class "hovertable" to a wikitable, then you place multiple spans in one large cell of class "hovertable_descrip". Each span is "display:none" and contains the description for one type, which is given as that span's id. Then you declare other cells in the hovertable as class "hovercell" with ids that match the ones in the descrip cell. The JS I wrote attaches event handlers to all hovercells which display their corresponding span in the hovertable_descrip cell when the hovercell receives 'mouseover', and hide the span upon 'mouseout'. --Iritscen (talk) 20:22, 16 November 2012 (CET)

I checked your test space. It looks awesome, I didn't expected to see so fast results on this. However, there are 2 things I would like you to think about.
1) SSG's "Level files" table (https://dl.dropbox.com/u/139715/temp/ssg_overviews_wikified.txt, dead link) (ONLV) is too big for an absolute location of the explanation: if the user hovers the CRSA table cell he would see nothing because the explanation is out of view.
The solution to this problem might be to fix the explanation area to the screen. Here's an example made of CSS (https://dl.dropbox.com/u/139715/temp/explanation_fixed_to_screen.htm, dead link). (basically style="position: fixed; top: 50%; left: 50%;")
2) We talked about merging those hierarchies and the general file type overview. In my last draft the types were vertical listed but I think it will look less odd if they are horizontal (because the tables differ in their number of rows).
At the moment the chasing explanation makes a strange impression but that's due to the other content here. With nothing else then the content under the gray line should look ... not "super" ... but good enough. Or we make a step back and use H template?
2a) If we agree on the merging then the file types should be click-able: if user clicks TxtC type then of course the TxtC table should appear.
I think you can reuse the mechanism here you just created. Not sure about IGPG: it appears in TxtC but also in others (DPge, WPge, Opge, ...)
2b) Facing this problem we might choose an easier path than hiding all tables by default.
If we put all table under each other we could create "AAAA-using types" sections at the end of all tables: If the user clicked IGPG then the browser jumps to that section and there the user reads IGPG being used by this, this and that type. From there he can jump again (by clicking [[#ABCD|ABCD]]) and reaches his final choice (TxtC/DPge/WPge/... table).






ABNA AGQC AGQG AGQR AISA AKAA AKBA AKBP AKEV AKOT AKVA BINA CBPI CBPM CONS CRSA DOOR DPge ENVP FILM HPge IDXA IGHH
IGPA IGPG IGSA IGSt Impt IPge KeyI M3GA M3GM Mtrl OBAN OBOA OFGA ONCC ONCP ONCV ONGS ONIA ONLD ONLV ONOA ONSK ONVL
ONWC OPge OSBD OTIT OTLF PLEA PNTA PSpc PSpL PSUI QTNA SNDD SUBT TRAC TRAM TRAS TRBS TRCM TRGA TRGE TRIA TRIG TRMA
TRSC TRTA TSFF TSFL TSFT TSGA TURR TXAN TXCA TXMA TXMB TXMP TxtC VCRA WMCL WMDD WMM WMMB WPge

Based on OBD:file_types. Maybe we should list BINA subtypes too (object collections like CHAR, CONS, DOOR, ...) ?


TxtC

TxtC
Chart turn right.gif IGPA
Chart turn right.gif IGPG
Chart fork right.gif TSFF
Chart descend.gif Chart turn right.gif TSFL
Chart descend.gif Chart turn right.gif TSFT
Chart descend.gif Chart turn right.gif TSGA
Chart fork right.gif PSpc
Chart descend.gif Chart turn right.gif TXMP
Chart turn right.gif IGSA
Chart turn right.gif IGSt


[ other tables ]



IGPG-using types



Ah, the fixed-position box is interesting, that could be the answer. I think we will need to have a chat before I can fully understand what we are trying to document, though, in terms of what/how hierarchies are to be shown. I'll look for you online this weekend. --Iritscen (talk) 03:41, 17 November 2012 (CET)

Just a note on where I left off -- I fixed the classes so that the cells are being styled correctly. However, I seem to have accidentally changed the stripe style; I didn't mean to create a stripe with a gradient in it; I just want to make the blue and background colors evenly spaced at 10px or 15px. Also, the "position:fixed" on the descrip cell was somehow shifting the location of the next cell (TxtC), so for now I have removed that property. --Iritscen (talk) 23:56, 17 November 2012 (CET)

If you look closely there are 3 px value in the gradient code: for clean stripes let the last value be the sum of the others.
background-image: -webkit-repeating-linear-gradient(-45deg, transparent, transparent 10px, rgba(0, 0, 255, 0.2) 10px, rgba(0, 0, 255, 0.2) 20px); --paradox-01 (talk) 11:29, 18 November 2012 (CET)
The table in your test space will look okay if you enable the position fixed in Common.css again. That code piece rips the cell out of the table. I added some columns to fix it. --13:12, 18 November 2012 (CET)

Sorry, 'dox, I didn't think it would take very long, but after I had written some of the JavaScript, I could see how complicated it would be. Then I got sidetracked by real life for a while. Normally I would just keep at it until it's done, but seeing as I am trying to get back to my main Oni project ASAP, I'm afraid I have to cut short my work on this. Maybe it's more complicated than it needs to be. If you want to "retreat" back to a simpler solution, then let me know how I can help with that. Otherwise I might have time to finish this at a later date. I just don't want to spend hours on it when it's keeping me from my other work. --Iritscen (talk) 20:57, 17 December 2012 (CET)

New overview

Just wanted to say, I still feel this is an important thing to add to the wiki. But I made it too complex the first time around. Rather than a dynamically generated table, we should probably stick to something that is set up manually. Although my more complex code was never finished, we do still have the hovertable class available, as used above (and I can easily change it to display info on a click instead of a mouse-hover if that's better). Let me know if you have any new ideas on how to present the info, or if you want to stick with the format we had before.

The fact is, looking at this with a fresh perspective, I'm not 100% convinced that the arrow-based table is the best use of space or the easiest thing to read, or that we need fancy JS either. What about the simple text-based approach I suggested here, combined with your anchor-based TOC serving as an alphabetical index at the beginning? --Iritscen (talk) 00:03, 18 April 2013 (CEST)

About that thing at Current_events. Sounds like you want a simple page with sections and links. So if you don't want to hierarchal information then you could take XML:File_types and extend it. In that case I wouldn't use === but {{Anchor|some_anchor_name}}. This prevents the page to be ripped in sections. By that the user can follow links and the page will still look nice. --paradox-01 (talk) 12:56, 18 April 2013 (CEST)
Basically, yes. I like that "File types" page, I just would like the descriptions to be a bit longer and to list what types they have under them, or what types can contain them, and maybe group them by type. I think I'll make a separate WIP table in my userspace so I don't mess up yours, because I'm not 100% clear on what I want it to look like. --Iritscen (talk) 13:59, 18 April 2013 (CEST)
Okay, it can use some nicer formatting, but if you look at my TestSpace, you'll see what I had in mind. It's similar to your XML File types page, just organized by category, and with "parent" and "child" anchor links to the related types on the same page. Probably it can also contain your colored documentation dots and the types can link to their XML: pages instead of OBD:, at least if this replaces your File types page. Any suggestions? --Iritscen (talk) 22:07, 19 April 2013 (CEST)

Caution, the header template on pages like XML:BINA/OBJC/CHAR link to "other BINA" and "other OBJC" (XML:File_types) in analogy to OBD:BINA/OBJC and OBD:BINA.

I like how you structure the descriptions, I'm just a bit unhappy with the index thing because of the mentioned template header. As a compromise perhaps make 3 type indices so that the template can still link to those.

Type index: BINA
  • [...]
Type index: CJBO
  • [...]
Type index: other files
  • [...]
Add color dots and links and I totally agree with replacing current file types page with this second version. :) --paradox-01 (talk) 22:43, 19 April 2013 (CEST)
Sorry, I don't understand the point you're making. I'm not 100% fluent in where all Oni's data is stored (particularly what is in .sep vs. .raw), but my idea was that this wasn't an important distinction to make for the beginner who just wants to know what these kinds of data do. After all, we no longer have to know which file to look in with a hex editor to mod something, we just ask OniSplit to export the data :-) But please let me know what you meant if there's a reason the reader has to think in terms of BINA vs. CBJO vs. everything else. --Iritscen (talk) 23:17, 19 April 2013 (CEST)

I just want the user to be aware of what types belong to object collections (for instance so he does chose the door collection and not the door class) and that searches can be easily be done by BINA*/BINAOBJC*. --paradox-01 (talk) 14:19, 20 April 2013 (CEST)