19,344
edits
User talk:Geyser: Difference between revisions
Oy.
No edit summary |
(Oy.) |
||
| Line 175: | Line 175: | ||
::::::::::3. Making a GUI for editing every single part of Oni is also a technical hurdle. :) | ::::::::::3. Making a GUI for editing every single part of Oni is also a technical hurdle. :) | ||
::::::::::3.5 See point 2. Unless the same guy who makes the underlying program makes the GUI (not true here), the GUI's features will not mirror the program's features. And at some point, the program will have more features than will properly fit on a GUI. See point 1. This will either lead to a messy\unfriendly GUI (bad), or a GUI with features removed (also bad). [[User:Gumby|Gumby]] 22:45, 25 August 2008 (CEST) | ::::::::::3.5 See point 2. Unless the same guy who makes the underlying program makes the GUI (not true here), the GUI's features will not mirror the program's features. And at some point, the program will have more features than will properly fit on a GUI. See point 1. This will either lead to a messy\unfriendly GUI (bad), or a GUI with features removed (also bad). [[User:Gumby|Gumby]] 22:45, 25 August 2008 (CEST) | ||
:::::::::::0. The modder <u>is</u> the end-user of the mod-making process, just not the mod-''using'' process. And modding ''should'' be available for the lazy. I demand a retraction of your statement :-) Seriously, though, just because someone wants to "mod", that term could mean anything from changing one parameter of one TRAM, to making a whole new scenario. So is it worth it to learn all these technicalities when you just want to mod small-time stuff? Arguably not, with the way things are right now. But here's the point I want you to remember: I agree with the stetement "If you are making a mod, you should know what you are doing." But only if you define "what you are doing" as "how to make quality modifications to the game", not your apparent definition of "what the changes you make are doing at the hex level". My definition focuses on the creative skill of the modder, yours focuses on the ability of the modder to learn nerdy geek stuff; I still maintain that those are almost opposite skills. Once again, this is the whole point of the GUI; to <u>not</u> know what you are doing at the lower level of the OS as long as it produces reliable results at the upper level. Many OS X users couldn't care less about the Unix layer of the OS, and the beautiful thing is, they don't have to. | |||
:::::::::::1. Well, maybe I will *sticks out lower lip poutily*. But as I indicated, that's gotta come after the trailer and the HD models. I think that if I find a compelling way to present a total Oni-modding package as a GUI, you'll come around to my way of thinking soon enough and want a Windows version :-) | |||
:::::::::::2. If I knew what you meant by "fine tune", I would respond to this, but I don't, so I won't. :-p But whatever you mean, I probably don't agree. :-P x 2 | |||
:::::::::::3. Yes, quite true. But it's only a hurdle for one or two people who have to make the tool, as opposed to every single person who comes along wanting to mod that has to learn hex and endians. If you question the act of programming an interface because it's "hard", you call into question millions of dollars of software that's sold every year and decades of common practice. I'm sure that's not what you intend to say. | |||
:::::::::::P.S.: I genuinely want to apologize for spamming geyser's page with this stuff; it all started with an innocent question about OniMenu and just snowballed from there. The basic problem I have is that I keep thinking for some dumb reason that if I suggest something, others might actually agree with me and do the work I described. Instead it looks like I can only see something done that I think should be done if I do it myself. Talking about it beforehand only makes unnecessary arguments. I'm starting to see that now. --[[User:Iritscen|Iritscen]] 23:32, 25 August 2008 (CEST) | |||