Changeset View
Standalone View
binaries/data/mods/mod/gui/modmod/modio.xml
- This file was added.
<?xml version="1.0" encoding="utf-8"?> | |||||
Itms: I'd personally see that page as a pop-up on top of the mod selector, especially if it's one way… | |||||
Done Inline ActionsOr a button/checkbox/whatever to enable integration, and adding the entries to the available list, or a tab where one can toggle between the available mods (locally and remotely). As said the only purpose of the current gui is to show that it works, not to be pretty or nice or good looking. leper: Or a button/checkbox/whatever to enable integration, and adding the entries to the available… | |||||
<objects> | |||||
<script file="gui/modmod/modio.js"/> | |||||
Done Inline Actionssee comment at modmod.xml inclusion, refs D619 elexis: see comment at `modmod.xml` inclusion, refs D619 | |||||
Not Done Inline ActionsSee comment below. No, not that one, the other one. leper: See comment below. No, not that one, the other one. | |||||
<object type="image" sprite="ModernFade" z="0"/> | |||||
<object name="modmod" type="image" style="ModernDialog" size="10% 10% 90% 90%"> | |||||
<!-- Page Title --> | |||||
<object style="ModernLabelText" type="text" size="50%-128 -18 50%+128 14"> | |||||
<translatableAttribute id="caption">mod.io mods</translatableAttribute> | |||||
</object> | |||||
<!-- Available Mods Wrapper --> | |||||
<object name="modsAvailable" size="16 20 100%-16 100%-70" style="ModmodScrollbar"> | |||||
<object style="ModernLabelText" type="text" size="0 5 100% 25"> | |||||
<translatableAttribute id="caption">Available Mods</translatableAttribute> | |||||
</object> | |||||
<object name="modsAvailableList" | |||||
style="ModernList" | |||||
type="olist" | |||||
size="0 25 100%-2 100%" | |||||
font="sans-stroke-13" | |||||
> | |||||
<action on="SelectionChange">showModDescription();</action> | |||||
<!-- List headers --> | |||||
<column id="modname_id" color="255 255 255" width="20%"> | |||||
Not Done Inline Actionsdoubleclick action example rP20550 elexis: doubleclick action example rP20550 | |||||
<translatableAttribute id="heading">Name</translatableAttribute> | |||||
</column> | |||||
<column id="modVersion" color="255 255 255" width="10%"> | |||||
<translatableAttribute id="heading">Version</translatableAttribute> | |||||
</column> | |||||
<column id="name" color="255 255 255" width="20%"> | |||||
<translatableAttribute id="heading">Mod Label</translatableAttribute> | |||||
</column> | |||||
<column id="modfilesize" color="255 255 255" width="15%"> | |||||
<translatableAttribute id="heading">File Size</translatableAttribute> | |||||
</column> | |||||
<column id="dependencies" color="255 255 255" width="25%"> | |||||
Done Inline ActionsThe three names here should be human-readable (well only capital letters are missing) Itms: The three names here should be human-readable (well only capital letters are missing) | |||||
<translatableAttribute id="heading">Dependencies</translatableAttribute> | |||||
</column> | |||||
</object> | |||||
<object name="modDescription" type="text" style="ModmodScrollbar" size="0 100% 100%-16 100%+28" /> | |||||
</object> | |||||
<!-- BUTTONS --> | |||||
<object type="button" style="ModernButtonRed" size="16 100%-44 200 100%-16"> | |||||
<translatableAttribute id="caption">Back</translatableAttribute> | |||||
<action on="Press">Engine.SwitchGuiPage("page_modmod.xml");</action> | |||||
</object> | |||||
<object type="button" style="ModernButtonRed" size="100%-200 100%-44 100%-16 100%-16"> | |||||
Not Done Inline Actionscolor attribute elexis: color attribute | |||||
Not Done Inline ActionsSee GUI comment in the description. leper: See GUI comment in the description. | |||||
<translatableAttribute id="caption">Download</translatableAttribute> | |||||
<action on="Press">downloadMod();</action> | |||||
</object> | |||||
</object> | |||||
</objects> | |||||
Done Inline Actions(Reminder for later that we need the security warning message box) elexis: (Reminder for later that we need the security warning message box) | |||||
Done Inline ActionsTODO overhaul the buttons here. We should decide what the user can do at that point (do we need an extra manual step for installing the mod with the pyromod stuff? can we enable mods from here or should we go back to the selection screen?) Itms: TODO overhaul the buttons here. We should decide what the user can do at that point (do we need… | |||||
Done Inline ActionsBrowse mods, download one; then the behaviour is the same as with locally installed mods (so the same as right now without this patch). There is nothing else the user can do. Why those buttons are here, well to test things, and because copying the mod.xml seemed easier than writing it from scratch. .pyromod files are installed without actually starting the game (well, as visible to the user). You open a pyromod file with the engine, it does its thing, then you can start the game and enable it as usually. I guess displaying some progress or whatever when installing in case that takes ages (think different filesystems, so moving things takes a while) would be useful. leper: Browse mods, download one; then the behaviour is the same as with locally installed mods (so… |
I'd personally see that page as a pop-up on top of the mod selector, especially if it's one way among others to install mods.