2014-06-01 22:49:53 +00:00
|
|
|
<?xml version="1.0" encoding="UTF-8"?>
|
|
|
|
|
<ui version="4.0">
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<class>ExternalResourcesPage</class>
|
|
|
|
|
<widget class="QMainWindow" name="ExternalResourcesPage">
|
2014-06-01 22:49:53 +00:00
|
|
|
<property name="geometry">
|
|
|
|
|
<rect>
|
|
|
|
|
<x>0</x>
|
|
|
|
|
<y>0</y>
|
2019-07-15 23:30:53 +00:00
|
|
|
<width>1042</width>
|
|
|
|
|
<height>501</height>
|
2014-06-01 22:49:53 +00:00
|
|
|
</rect>
|
|
|
|
|
</property>
|
2019-07-15 23:30:53 +00:00
|
|
|
<widget class="QWidget" name="centralwidget">
|
|
|
|
|
<layout class="QGridLayout" name="gridLayout">
|
|
|
|
|
<property name="leftMargin">
|
|
|
|
|
<number>0</number>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="topMargin">
|
|
|
|
|
<number>0</number>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="rightMargin">
|
|
|
|
|
<number>0</number>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="bottomMargin">
|
|
|
|
|
<number>0</number>
|
|
|
|
|
</property>
|
|
|
|
|
<item row="4" column="1" colspan="3">
|
|
|
|
|
<layout class="QGridLayout" name="gridLayout_2">
|
|
|
|
|
<item row="0" column="1">
|
|
|
|
|
<widget class="QLineEdit" name="filterEdit">
|
|
|
|
|
<property name="clearButtonEnabled">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
</property>
|
|
|
|
|
</widget>
|
|
|
|
|
</item>
|
|
|
|
|
<item row="0" column="0">
|
|
|
|
|
<widget class="QLabel" name="filterLabel">
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string>Filter:</string>
|
|
|
|
|
</property>
|
|
|
|
|
</widget>
|
|
|
|
|
</item>
|
|
|
|
|
</layout>
|
|
|
|
|
</item>
|
|
|
|
|
<item row="2" column="1" colspan="3">
|
|
|
|
|
<widget class="MCModInfoFrame" name="frame">
|
|
|
|
|
<property name="sizePolicy">
|
|
|
|
|
<sizepolicy hsizetype="Preferred" vsizetype="Minimum">
|
|
|
|
|
<horstretch>0</horstretch>
|
|
|
|
|
<verstretch>0</verstretch>
|
|
|
|
|
</sizepolicy>
|
|
|
|
|
</property>
|
|
|
|
|
</widget>
|
|
|
|
|
</item>
|
|
|
|
|
<item row="1" column="1" colspan="3">
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<widget class="ModListView" name="treeView">
|
2016-08-04 19:54:25 +00:00
|
|
|
<property name="sizePolicy">
|
2019-07-15 23:30:53 +00:00
|
|
|
<sizepolicy hsizetype="Expanding" vsizetype="Expanding">
|
2016-08-04 19:54:25 +00:00
|
|
|
<horstretch>0</horstretch>
|
|
|
|
|
<verstretch>0</verstretch>
|
|
|
|
|
</sizepolicy>
|
|
|
|
|
</property>
|
2019-07-15 23:30:53 +00:00
|
|
|
<property name="acceptDrops">
|
|
|
|
|
<bool>true</bool>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="dragDropMode">
|
|
|
|
|
<enum>QAbstractItemView::DropOnly</enum>
|
|
|
|
|
</property>
|
2014-07-20 22:10:13 +00:00
|
|
|
</widget>
|
2019-07-15 23:30:53 +00:00
|
|
|
</item>
|
|
|
|
|
</layout>
|
|
|
|
|
</widget>
|
2019-07-22 22:48:14 +00:00
|
|
|
<widget class="WideBar" name="actionsToolbar">
|
2019-07-15 23:30:53 +00:00
|
|
|
<property name="windowTitle">
|
|
|
|
|
<string>Actions</string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="toolButtonStyle">
|
|
|
|
|
<enum>Qt::ToolButtonTextOnly</enum>
|
|
|
|
|
</property>
|
|
|
|
|
<attribute name="toolBarArea">
|
|
|
|
|
<enum>RightToolBarArea</enum>
|
|
|
|
|
</attribute>
|
|
|
|
|
<attribute name="toolBarBreak">
|
|
|
|
|
<bool>false</bool>
|
|
|
|
|
</attribute>
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<addaction name="actionAddItem"/>
|
2019-08-04 22:44:56 +00:00
|
|
|
<addaction name="separator"/>
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<addaction name="actionRemoveItem"/>
|
|
|
|
|
<addaction name="actionEnableItem"/>
|
|
|
|
|
<addaction name="actionDisableItem"/>
|
|
|
|
|
<addaction name="actionViewConfigs"/>
|
|
|
|
|
<addaction name="actionViewFolder"/>
|
2019-07-15 23:30:53 +00:00
|
|
|
</widget>
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<action name="actionAddItem">
|
2019-07-15 23:30:53 +00:00
|
|
|
<property name="text">
|
2019-08-04 22:44:56 +00:00
|
|
|
<string>&Add</string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="toolTip">
|
2022-03-03 12:51:46 +00:00
|
|
|
<string>Add</string>
|
2022-03-03 04:10:10 +00:00
|
|
|
</property>
|
|
|
|
|
</action>
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<action name="actionRemoveItem">
|
2019-07-15 23:30:53 +00:00
|
|
|
<property name="text">
|
2019-08-04 22:44:56 +00:00
|
|
|
<string>&Remove</string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="toolTip">
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<string>Remove selected item</string>
|
2019-07-15 23:30:53 +00:00
|
|
|
</property>
|
|
|
|
|
</action>
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<action name="actionEnableItem">
|
2019-07-15 23:30:53 +00:00
|
|
|
<property name="text">
|
2019-08-04 22:44:56 +00:00
|
|
|
<string>&Enable</string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="toolTip">
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<string>Enable selected item</string>
|
2019-07-15 23:30:53 +00:00
|
|
|
</property>
|
|
|
|
|
</action>
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<action name="actionDisableItem">
|
2019-07-15 23:30:53 +00:00
|
|
|
<property name="text">
|
2019-08-04 22:44:56 +00:00
|
|
|
<string>&Disable</string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="toolTip">
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<string>Disable selected item</string>
|
2019-07-15 23:30:53 +00:00
|
|
|
</property>
|
|
|
|
|
</action>
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<action name="actionViewConfigs">
|
2019-07-15 23:30:53 +00:00
|
|
|
<property name="text">
|
2019-08-04 22:44:56 +00:00
|
|
|
<string>View &Configs</string>
|
2019-07-15 23:30:53 +00:00
|
|
|
</property>
|
|
|
|
|
<property name="toolTip">
|
|
|
|
|
<string>Open the 'config' folder in the system file manager.</string>
|
|
|
|
|
</property>
|
|
|
|
|
</action>
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<action name="actionViewFolder">
|
2019-07-15 23:30:53 +00:00
|
|
|
<property name="text">
|
2019-08-04 22:44:56 +00:00
|
|
|
<string>View &Folder</string>
|
2019-07-15 23:30:53 +00:00
|
|
|
</property>
|
|
|
|
|
</action>
|
2022-05-30 14:36:30 +00:00
|
|
|
<action name="actionDownloadItem">
|
|
|
|
|
<property name="enabled">
|
|
|
|
|
<bool>false</bool>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string>&Download</string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="toolTip">
|
|
|
|
|
<string>Download a new resource</string>
|
|
|
|
|
</property>
|
|
|
|
|
</action>
|
2022-06-05 00:18:51 +00:00
|
|
|
<action name="actionUpdateItem">
|
|
|
|
|
<property name="enabled">
|
|
|
|
|
<bool>false</bool>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="text">
|
|
|
|
|
<string>Check for &Updates</string>
|
|
|
|
|
</property>
|
|
|
|
|
<property name="toolTip">
|
2022-07-19 16:03:45 +00:00
|
|
|
<string>Try to check or update all selected resources (all resources if none are selected)</string>
|
2022-06-05 00:18:51 +00:00
|
|
|
</property>
|
|
|
|
|
</action>
|
2014-06-01 22:49:53 +00:00
|
|
|
</widget>
|
|
|
|
|
<customwidgets>
|
|
|
|
|
<customwidget>
|
|
|
|
|
<class>ModListView</class>
|
|
|
|
|
<extends>QTreeView</extends>
|
2021-11-22 02:55:16 +00:00
|
|
|
<header>ui/widgets/ModListView.h</header>
|
2014-06-01 22:49:53 +00:00
|
|
|
</customwidget>
|
|
|
|
|
<customwidget>
|
|
|
|
|
<class>MCModInfoFrame</class>
|
|
|
|
|
<extends>QFrame</extends>
|
2021-11-22 02:55:16 +00:00
|
|
|
<header>ui/widgets/MCModInfoFrame.h</header>
|
2014-06-01 22:49:53 +00:00
|
|
|
<container>1</container>
|
|
|
|
|
</customwidget>
|
2019-07-22 22:48:14 +00:00
|
|
|
<customwidget>
|
|
|
|
|
<class>WideBar</class>
|
|
|
|
|
<extends>QToolBar</extends>
|
2021-11-22 02:55:16 +00:00
|
|
|
<header>ui/widgets/WideBar.h</header>
|
2019-07-22 22:48:14 +00:00
|
|
|
</customwidget>
|
2014-06-01 22:49:53 +00:00
|
|
|
</customwidgets>
|
2019-08-04 22:44:56 +00:00
|
|
|
<tabstops>
|
refactor: Create a more clear hierarchy for some instance pages
Previously, the Shaders, Texture packs and Resource packs tabs had as
parent the ModFolderPage, making it so that making changes only to the
Mods page would require checking the id of the page for the correct one.
This was hackish and error-prone.
Now, those pages all inherit from a single class, ExternalResourcesPage,
that handles the basic behaviour of all of them, while allowing for
individual modification in code.
This is still not a clear separation, since internally, all those
resources are derived from Mods, so for now there's still some awkward
common code :/
2022-03-11 21:03:21 +00:00
|
|
|
<tabstop>treeView</tabstop>
|
2019-08-04 22:44:56 +00:00
|
|
|
<tabstop>filterEdit</tabstop>
|
|
|
|
|
</tabstops>
|
2014-06-01 22:49:53 +00:00
|
|
|
<resources/>
|
|
|
|
|
<connections/>
|
|
|
|
|
</ui>
|
