Difference between revisions of "Talk:Wish List"
Jump to navigation
Jump to search
Moved Discussions
imported>MegaBurn |
imported>MegaBurn (Moved Discussions) |
||
| Line 74: | Line 74: | ||
:Justed finished with my edits. Not sure I can get it any shorter without moving comments to other people's requests. I'm really not sure if thats an issue or not, normally when stuff is signed its like saying "mine, don't touch". Someone really needs to do something with the Longer MAX_SCRIPT_SIZE! request, thats gotten way out of hand. Maybe signing these at all was a bad idea. If people can't clean up their own requests, own comments, and comments on their requests then, yeah, split it up into more topics. Or just wholesale move all discussion to this page.--[[User:MegaBurn|MegaBurn]] 19:58, 27 April 2006 (EDT) | :Justed finished with my edits. Not sure I can get it any shorter without moving comments to other people's requests. I'm really not sure if thats an issue or not, normally when stuff is signed its like saying "mine, don't touch". Someone really needs to do something with the Longer MAX_SCRIPT_SIZE! request, thats gotten way out of hand. Maybe signing these at all was a bad idea. If people can't clean up their own requests, own comments, and comments on their requests then, yeah, split it up into more topics. Or just wholesale move all discussion to this page.--[[User:MegaBurn|MegaBurn]] 19:58, 27 April 2006 (EDT) | ||
== Moved Discussions == | |||
I suggest people move discussion content to this section to help reduce the overall Wish List size. The top of the Wish List clearly states that we are to keep the discussion on the discussion page. Please use subsections for each request discussion added to this section. | |||
===Add UI Option Elements Discussion Snips=== | |||
I'm moving this discussion to help clean up the Wish List. | |||
'''Moved reply to Callie on Add UI Option Elements:''' | |||
:Or being able to create new UI windows/menus with the CS, just like creating new cells. Thats about the only major thing still missing from the CS, by adding that you could finally call the CS a full blown IDE. --[[User:MegaBurn|MegaBurn]] 03:28, 13 April 2006 (EDT) | |||
'''Moved replies to Maian on Add UI Option Elements:''' | |||
:Dropping the external XML files so everything is in the ESM/ESP would be better. Its certainly workable since it doesn't really matter where that data is stored. The strings could be moved to a global list (e.g. under Settings in the Gameplay menu) or added to the Settings as another string data list section. If they really want to get creative it could be turned into a full GUI IDE, something akin to VB. The result of that would be very cool, I can easily see someone doing a desktop mod, where if sit at a desk you get a dynamic OS style desktop (e.g. if the desk contains a quill, ink well, and parchment a UI button for scroll writing pops up, or an alchemy button if the desk contains all the required alchemy equipment). Not sure if thats possible now with on-activate/message box menu scripts, might be. --[[User:MegaBurn|MegaBurn]] 01:21, 15 April 2006 (EDT) | |||
::I bet that's very unlikely to happen. They've already invested plenty into creating their menu XML dialect and interpreter. In any case, the XML format is actually pretty ideal for describing UIs, since many people are familiar with it, including web developers (like me). Not everything should go into an esp file. External resources should be put into bsa files, and the esp should somehow be able to get the game to import that bsa file. --[[User:Maian|Maian]] 06:49, 20 April 2006 (EDT) | |||
:This really should be moved into the talk page, but... Its not unlikely at all and would be a vast improvement. If you think I mean dropping the XML format then you misunderstood, again, I'm saying just move the UI XML data into the ESM/ESP files. Technically it should makes no different if the XML data is stored in a BSA or a ESM/ESP. Adapting the CS to include an XML editor similar to the script editor should be fairly simple, it would make the XML data more accessible to modders and forgo having to even mess with the BSA files (assuming some of the other items on this list are implemented). Generating the XML data for UI windows created in an UI editor should be fairly simple too. I'm not sure if the CS includes an XML parser or not, I'd assume it does but if not, porting the parser from the game engine over to the CS would, again, be a fairly simple task. --[[User:MegaBurn|MegaBurn]] 08:42, 20 April 2006 (EDT) | |||