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

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.

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.]]

:http://carnage.bungie.org/oniforum/oni.forum.pl?read=19468 ([[User:Paradox-01/quotes_chef_1]])

* [[Talk:Restless_Souls/Reconstruction/Gapfilling#Where went all the details.3F]] (contains Hardy's talk)

::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>

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)

: Check this out: <nowiki>https://dl.dropbox.com/u/139715/temp/ssg_overviews_wikified.txt</nowiki> (dead link)

::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?

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)

| [[Image:Chart turn right.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart fork right.gif]]

| [[Image:Chart descend.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart descend.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart descend.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart fork right.gif]]

| [[Image:Chart descend.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart turn right.gif]]

: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)

:: 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%;"'')

::: 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).

| [[Image:Chart turn right.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart fork right.gif]]

| [[Image:Chart descend.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart descend.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart descend.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart fork right.gif]]

| [[Image:Chart descend.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart turn right.gif]]

| [[Image:Chart turn right.gif]]

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)

: 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)