18,700
edits
User talk:Paradox-01/Archive1: Difference between revisions
m
one link fix, many dead Dropbox links
m (link fix) |
m (one link fix, many dead Dropbox links) |
||
| Line 10: | Line 10: | ||
==OniSplit source code== | ==OniSplit source code== | ||
The source code (<nowiki>https://dl.dropboxusercontent.com/u/139715/OniGalore/OniSplit/OniSplit_source_code_v0.9.99.0.zip</nowiki>, dead link) can be retrieved by decompiling OniSplit.exe with [https://www.telerik.com/download-trial-file/v2/justdecompile "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.]] | 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.]] | ||
| Line 20: | Line 20: | ||
Oni.Func<Vector3, float> cSu0024u003cu003e9_CachedAnonymousMethodDelegate3 = RoomBuilder.CS$<>9__CachedAnonymousMethodDelegate3; | Oni.Func<Vector3, float> cSu0024u003cu003e9_CachedAnonymousMethodDelegate3 = RoomBuilder.CS$<>9__CachedAnonymousMethodDelegate3; | ||
JustDecompile screenshot (<nowiki>https://dl.dropboxusercontent.com/u/139715/OniGalore/OniSplit/JustDecompile.png</nowiki>, dead link), VS errors (<nowiki>https://dl.dropboxusercontent.com/u/139715/OniGalore/OniSplit/VisualStudioCommunity.png</nowiki>, dead link) | |||
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) | 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) | ||
| Line 134: | Line 134: | ||
: I changed my mind: colored table cells could show embedded instances of files, so ssg's style should be better. | : 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 | : 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) | : 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:H|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? | ::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:H|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? | ||
| Line 252: | Line 252: | ||
:'''"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) | :'''"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) | :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 [http://www.mwusers.com/forums/showthread.php?18647-onclick-in-wikitext | :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) | 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) | ||
| Line 262: | Line 262: | ||
: 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. | : 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 | :: 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 | ::: 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). | :: 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? | ::: 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? | ||