shaba/virt-manager
1
0
Fork 0
mirror of https://github.com/virt-manager/virt-manager.git synced 2024-12-22 13:34:07 +03:00
Code Issues Projects Releases Wiki Activity
720ea801bc
virt-manager/ui/snapshots.ui

784 lines
40 KiB
Plaintext
Raw Normal View History

Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<?xml version="1.0" encoding="UTF-8"?>
ui: Fix minor issues, and resave all files with f21 glade
2014-09-06 23:01:12 +04:00
<!-- Generated with glade 3.18.3 -->
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<interface>
Bump gtk and pygobject deps to 3.14 We need to bump the gtk dep to at least 3.10 for GtkRevealer usage, and I want to bump the pygobject higher to drop some bug workarounds. But since the oldest thing I have that meets those requirements is RHEL/Centos 7.3 which is at 3.14 for both, set those as the minimum versions since that's what I'll be testing against. They are still 1.5 years old and only a bit over a year newer than the previous versions, so it's not a huge change.
2016-05-18 00:07:48 +03:00
<requires lib="gtk+" version="3.14"/>
snapshots: Desensitize 'finish' if no name entered
2013-10-01 00:04:11 +04:00
<object class="GtkImage" id="image3">
ui: Set non-stock button images in glade, not explicitly in code
2013-09-22 20:18:49 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-new</property>
</object>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<object class="GtkWindow" id="snapshot-new">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="can_focus">False</property>
<property name="title" translatable="yes">Create snapshot</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<property name="resizable">False</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="type_hint">dialog</property>
<signal name="delete-event" handler="on_snapshot_new_delete_event" swapped="no"/>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<child>
<object class="GtkBox" id="box1">
<property name="visible">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<property name="spacing">6</property>
<child>
<object class="GtkViewport" id="header">
<property name="visible">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="can_focus">False</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<property name="resize_mode">queue</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<child>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<object class="GtkBox" id="hbox77">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<property name="can_focus">False</property>
<property name="border_width">6</property>
<property name="spacing">10</property>
<child>
<object class="GtkImage" id="image4">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-new</property>
<property name="icon_size">6</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkBox" id="hbox2">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<object class="GtkLabel" id="label2">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">&lt;span size='large' color='white'&gt;Create snapshot&lt;/span&gt;</property>
<property name="use_markup">True</property>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<object class="GtkBox" id="box3">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<property name="border_width">12</property>
<property name="orientation">vertical</property>
<property name="spacing">18</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<child>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<object class="GtkGrid" id="box4">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkLabel" id="label1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
snapshots: Desensitize 'finish' if no name entered
2013-10-01 00:04:11 +04:00
<property name="label" translatable="yes">_Name:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">snapshot-new-name</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkEntry" id="snapshot-new-name">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
snapshots: new: Grab name focus, make activate create the snapshot
2013-10-05 22:47:10 +04:00
<signal name="activate" handler="on_snapshot_new_name_activate" swapped="no"/>
snapshots: Desensitize 'finish' if no name entered
2013-10-01 00:04:11 +04:00
<signal name="changed" handler="on_snapshot_new_name_changed" swapped="no"/>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label3">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="yalign">0</property>
snapshots: Desensitize 'finish' if no name entered
2013-10-01 00:04:11 +04:00
<property name="label" translatable="yes">_Description:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">snapshot-new-description</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
</object>
<packing>
<property name="left_attach">0</property>
snapshots: List VM status in 'new snapshot' window
2013-10-01 01:40:01 +04:00
<property name="top_attach">2</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
</packing>
</child>
<child>
<object class="GtkScrolledWindow" id="scrolledwindow1">
<property name="width_request">300</property>
<property name="height_request">125</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="shadow_type">in</property>
<child>
<object class="GtkTextView" id="snapshot-new-description">
<property name="visible">True</property>
<property name="can_focus">True</property>
</object>
</child>
</object>
snapshots: List VM status in 'new snapshot' window
2013-10-01 01:40:01 +04:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label4">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">Status:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkBox" id="hbox1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">3</property>
<child>
<object class="GtkImage" id="snapshot-new-status-icon">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-cancel</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="snapshot-new-status-text">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">Shut down</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 05:41:10 +04:00
<child>
<object class="GtkLabel" id="label6">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
snapshots: Fix showing async dialogs for revert/delete
2013-10-05 18:03:56 +04:00
<property name="yalign">0</property>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 05:41:10 +04:00
<property name="label" translatable="yes">Screenshot:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkImage" id="snapshot-new-screenshot">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="stock">gtk-missing-image</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
</packing>
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<object class="GtkButtonBox" id="buttonbox2">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<property name="can_focus">False</property>
<property name="spacing">6</property>
<property name="layout_style">end</property>
<child>
<object class="GtkButton" id="snapshot-new-cancel">
<property name="label">gtk-cancel</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="use_stock">True</property>
<signal name="clicked" handler="on_snapshot_new_cancel_clicked" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkButton" id="snapshot-new-ok">
snapshots: Desensitize 'finish' if no name entered
2013-10-01 00:04:11 +04:00
<property name="label" translatable="yes">_Finish</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
snapshots: Desensitize 'finish' if no name entered
2013-10-01 00:04:11 +04:00
<property name="image">image3</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<property name="use_underline">True</property>
<signal name="clicked" handler="on_snapshot_new_ok_clicked" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
</child>
</object>
<object class="GtkWindow" id="snapshot-top-window">
snapshots: Add a right click menu for start/stop
2013-10-05 22:57:58 +04:00
<property name="width_request">600</property>
<property name="height_request">400</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="can_focus">False</property>
<child>
<object class="GtkBox" id="snapshot-top-box">
<property name="visible">True</property>
<property name="can_focus">False</property>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<property name="hexpand">True</property>
<property name="vexpand">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="border_width">12</property>
<property name="orientation">vertical</property>
<property name="spacing">6</property>
<child>
<object class="GtkPaned" id="spaned1">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="position">200</property>
<property name="position_set">True</property>
<child>
<object class="GtkScrolledWindow" id="scrolledwindow7">
<property name="visible">True</property>
<property name="can_focus">True</property>
snapshots: Make sure 'current' icon is always visible (bz 1065074)
2014-02-14 19:20:37 +04:00
<property name="hscrollbar_policy">never</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="shadow_type">in</property>
<child>
<object class="GtkTreeView" id="snapshot-list">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="headers_visible">False</property>
snapshots: Add a right click menu for start/stop
2013-10-05 22:57:58 +04:00
<signal name="button-press-event" handler="on_snapshot_list_button_press_event" swapped="no"/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<child internal-child="selection">
Set list selection signals in glade, not code
2013-09-23 00:29:58 +04:00
<object class="GtkTreeSelection" id="treeview-selection">
<signal name="changed" handler="on_snapshot_list_changed" swapped="no"/>
</object>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</child>
</object>
</child>
</object>
<packing>
<property name="resize">False</property>
snapshots: Make sure 'current' icon is always visible (bz 1065074)
2014-02-14 19:20:37 +04:00
<property name="shrink">False</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</packing>
</child>
<child>
ui: Fix minor issues, and resave all files with f21 glade
2014-09-06 23:01:12 +04:00
<object class="GtkAlignment" id="alignment1">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
ui: Fix minor issues, and resave all files with f21 glade
2014-09-06 23:01:12 +04:00
<property name="can_focus">False</property>
<property name="left_padding">12</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<child>
ui: Fix minor issues, and resave all files with f21 glade
2014-09-06 23:01:12 +04:00
<object class="GtkNotebook" id="snapshot-notebook">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
ui: Fix minor issues, and resave all files with f21 glade
2014-09-06 23:01:12 +04:00
<property name="can_focus">True</property>
<property name="show_border">False</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<child>
ui: Fix minor issues, and resave all files with f21 glade
2014-09-06 23:01:12 +04:00
<object class="GtkBox" id="sbox3">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
ui: Fix minor issues, and resave all files with f21 glade
2014-09-06 23:01:12 +04:00
<property name="orientation">vertical</property>
<property name="spacing">12</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<child>
<object class="GtkGrid" id="sgrid1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkLabel" id="slabel94">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="yalign">0</property>
<property name="label" translatable="yes">Description:</property>
</object>
<packing>
<property name="left_attach">0</property>
snapshots: Show indication of the 'current' snapshot (bz 1017385)
2014-02-01 20:25:35 +04:00
<property name="top_attach">5</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkScrolledWindow" id="scrolledwindow8">
<property name="height_request">80</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="hexpand">True</property>
<property name="shadow_type">in</property>
<child>
<object class="GtkTextView" id="snapshot-description">
<property name="visible">True</property>
<property name="can_focus">True</property>
ui: Add margins to 'description' text fields
2014-02-14 19:21:21 +04:00
<property name="left_margin">2</property>
<property name="right_margin">2</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</object>
</child>
</object>
<packing>
<property name="left_attach">1</property>
snapshots: Show indication of the 'current' snapshot (bz 1017385)
2014-02-01 20:25:35 +04:00
<property name="top_attach">5</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="label92">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
snapshots: s/State/VM State/ (bz 1016604)
2013-11-10 03:00:00 +04:00
<property name="label" translatable="yes">VM State:</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</object>
<packing>
<property name="left_attach">0</property>
snapshots: Show indication of the 'current' snapshot (bz 1017385)
2014-02-01 20:25:35 +04:00
<property name="top_attach">3</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</packing>
</child>
<child>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<object class="GtkBox" id="hbox3">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">3</property>
<child>
<object class="GtkImage" id="snapshot-status-icon">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-cancel</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="snapshot-status-text">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">Shut down</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="left_attach">1</property>
snapshots: Show indication of the 'current' snapshot (bz 1017385)
2014-02-01 20:25:35 +04:00
<property name="top_attach">3</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="label93">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">Timestamp:</property>
</object>
<packing>
<property name="left_attach">0</property>
snapshots: Show indication of the 'current' snapshot (bz 1017385)
2014-02-01 20:25:35 +04:00
<property name="top_attach">2</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="snapshot-timestamp">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">label</property>
</object>
<packing>
<property name="left_attach">1</property>
snapshots: Show indication of the 'current' snapshot (bz 1017385)
2014-02-01 20:25:35 +04:00
<property name="top_attach">2</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="snapshot-title">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
snapshots: Desensitize 'finish' if no name entered
2013-10-01 00:04:11 +04:00
<property name="label">&lt;b&gt;snapshot 'foo'&lt;/b&gt;</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="use_markup">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">2</property>
</packing>
</child>
snapshots: Add some specific UI for external snapshots We sort them separately in the snapshot list, explicitly mention that they are 'external', and add a UI field listing the memory/disk details. In general mixing internal and external snapshots is a recipe for confusion and disaster, so I think the best thing to do is at least acknowledge their presence in the UI but not make any attempt to predict what will or will not work.
2013-10-01 01:53:55 +04:00
<child>
<object class="GtkLabel" id="label5">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">Snapshot Mode:</property>
</object>
<packing>
<property name="left_attach">0</property>
snapshots: Show indication of the 'current' snapshot (bz 1017385)
2014-02-01 20:25:35 +04:00
<property name="top_attach">4</property>
snapshots: Add some specific UI for external snapshots We sort them separately in the snapshot list, explicitly mention that they are 'external', and add a UI field listing the memory/disk details. In general mixing internal and external snapshots is a recipe for confusion and disaster, so I think the best thing to do is at least acknowledge their presence in the UI but not make any attempt to predict what will or will not work.
2013-10-01 01:53:55 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="snapshot-mode">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">label</property>
</object>
<packing>
<property name="left_attach">1</property>
snapshots: Show indication of the 'current' snapshot (bz 1017385)
2014-02-01 20:25:35 +04:00
<property name="top_attach">4</property>
snapshots: Add some specific UI for external snapshots We sort them separately in the snapshot list, explicitly mention that they are 'external', and add a UI field listing the memory/disk details. In general mixing internal and external snapshots is a recipe for confusion and disaster, so I think the best thing to do is at least acknowledge their presence in the UI but not make any attempt to predict what will or will not work.
2013-10-01 01:53:55 +04:00
</packing>
</child>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 05:41:10 +04:00
<child>
<object class="GtkLabel" id="label7">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="yalign">0</property>
<property name="label" translatable="yes">Screenshot:</property>
</object>
<packing>
<property name="left_attach">0</property>
snapshots: Show indication of the 'current' snapshot (bz 1017385)
2014-02-01 20:25:35 +04:00
<property name="top_attach">6</property>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 05:41:10 +04:00
</packing>
</child>
<child>
<object class="GtkBox" id="box5">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<object class="GtkImage" id="snapshot-screenshot">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-missing-image</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="snapshot-screenshot-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">No screenshot available</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="left_attach">1</property>
snapshots: Show indication of the 'current' snapshot (bz 1017385)
2014-02-01 20:25:35 +04:00
<property name="top_attach">6</property>
snapshots: Add screenshot support Show a screenshot in the 'new snapshot' wizard. If we successfully create that snapshot, save the screenshot in ~/.cache/virt-manager/$connuri/$vmuuid/snap-screenshot-$snapname.$ext And show it in the snapshot details overview. We don't do any reaping on snapshot delete, vm delete, etc, but that could be added later.
2013-10-01 05:41:10 +04:00
</packing>
</child>
snapshots: Show indication of the 'current' snapshot (bz 1017385)
2014-02-01 20:25:35 +04:00
<child>
<object class="GtkBox" id="snapshot-is-current">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">3</property>
<child>
<object class="GtkImage" id="image2">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-info</property>
<property name="icon_size">2</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label652">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">&lt;small&gt;&lt;i&gt;This was the most recently applied snapshot.&lt;/i&gt;&lt;/small&gt;</property>
<property name="use_markup">True</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">2</property>
</packing>
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</object>
ui: Fix minor issues, and resave all files with f21 glade
2014-09-06 23:01:12 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</child>
</object>
ui: Fix minor issues, and resave all files with f21 glade
2014-09-06 23:01:12 +04:00
</child>
<child type="tab">
<object class="GtkLabel" id="label89">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">details</property>
</object>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<packing>
ui: Fix minor issues, and resave all files with f21 glade
2014-09-06 23:01:12 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="snapshot-error-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">error label</property>
</object>
<packing>
<property name="position">1</property>
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label90">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">empty</property>
</object>
<packing>
<property name="position">1</property>
<property name="tab_fill">False</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</packing>
</child>
</object>
</child>
</object>
<packing>
<property name="resize">True</property>
<property name="shrink">True</property>
</packing>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkBox" id="box2">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">6</property>
<child>
snapshots: Pretty up the 'new snapshot' dialog
2013-09-30 22:28:43 +04:00
<object class="GtkBox" id="hbox10">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
snapshots: add button to force snapshots list refresh Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-07-31 15:26:56 +04:00
<child>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<object class="GtkButton" id="snapshot-add">
snapshots: add button to force snapshots list refresh Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-07-31 15:26:56 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<property name="has_tooltip">True</property>
<property name="tooltip_markup" translatable="yes">Create new snapshot</property>
<property name="tooltip_text" translatable="yes">Create new snapshot</property>
<signal name="clicked" handler="on_snapshot_add_clicked" swapped="no"/>
snapshots: add button to force snapshots list refresh Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-07-31 15:26:56 +04:00
<child>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<object class="GtkImage" id="image1">
snapshots: add button to force snapshots list refresh Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-07-31 15:26:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<property name="stock">gtk-add</property>
snapshots: add button to force snapshots list refresh Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-07-31 15:26:56 +04:00
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<property name="fill">False</property>
snapshots: add button to force snapshots list refresh Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-07-31 15:26:56 +04:00
<property name="position">0</property>
</packing>
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<child>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<object class="GtkButton" id="snapshot-start">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<property name="tooltip_markup" translatable="yes">Run selected snapshot</property>
<signal name="clicked" handler="on_snapshot_start_clicked" swapped="no"/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<child>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<object class="GtkImage" id="someicon">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<property name="stock">gtk-media-play</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
snapshots: add button to force snapshots list refresh Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-07-31 15:26:56 +04:00
<property name="position">1</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</packing>
</child>
<child>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<object class="GtkButton" id="snapshot-refresh">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<signal name="clicked" handler="on_snapshot_refresh_clicked" swapped="no"/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<child>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<object class="GtkImage" id="image5">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<property name="stock">gtk-refresh</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
snapshots: Use consistent button layout with host dialog Except 'refresh' is in place of 'stop'
2014-09-21 19:44:01 +04:00
<property name="fill">True</property>
snapshots: add button to force snapshots list refresh Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-07-31 15:26:56 +04:00
<property name="position">2</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkButton" id="snapshot-delete">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="has_tooltip">True</property>
<property name="tooltip_markup" translatable="yes">Delete selected snapshot</property>
<property name="tooltip_text" translatable="yes">Delete selected snapshot</property>
<signal name="clicked" handler="on_snapshot_delete_clicked" swapped="no"/>
<child>
<object class="GtkImage" id="image11">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-delete</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
snapshots: add button to force snapshots list refresh Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2014-07-31 15:26:56 +04:00
<property name="position">3</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</packing>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkButtonBox" id="buttonbox1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">6</property>
<property name="layout_style">end</property>
<child>
<object class="GtkButton" id="snapshot-apply">
<property name="label">gtk-apply</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="has_tooltip">True</property>
<property name="tooltip_markup" translatable="yes">Save updated snapshot metadata</property>
<property name="tooltip_text" translatable="yes">Save updated snapshot metadata</property>
<property name="use_stock">True</property>
<signal name="clicked" handler="on_snapshot_apply_clicked" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
</child>
</object>
</interface>
Reference in New Issue Copy Permalink