2 ====================================================
3 See if there is a solution to images fun with designer other than:
4 %s/<iconset>[\.\/]*:images/<iconset>images/g
5 %s/<iconset>images/<iconset>..\/images/g
7 Allow for selecting multiple jobs to restore from in joblist. Right click
8 restore from job works, but not with multiple selected jobs.
10 Test left pane of restore with 2 windows drives in one backup job.
12 Resolve issue of connection during restore selection. Could go with preempt of
15 User preferences. With log to stdout options.
16 Have settings for defaults of limits on joblist
18 Add numerous are you sure dialog boxes. Like are you sure you want to
19 delete/purge that volume. Show a little of the documentation about what
20 the consequences of delete or purging are.
22 Add context sensitive options for most commands
23 status dir on page select director item
24 All items with jobid= that I thought could work from joblist are done.
29 preempt all connections to console with
30 if (!is_connectedGui())
31 or some other mechanism. Partially done.
33 Create documentation for any other developers interested in creating
34 new classes to add more pages. Explain how to use the pages class
35 and about not populating until the tree widget is clicked etc...
39 User configuration dialog. Include options for debugging output to stdout.
41 Is there a way to query the director/database for whether a storage is currently
42 mounted so I am not presenting both mount and unmount to the user??
44 Is there a way to identify a slot as having a cleaning tape???
45 (Kern says more work needs to be done in bacula with autochangers)
47 Get rid of "Warning: name layoutWidget is already used" when make uic's restore.ui
50 MainWin::setContextMenuDockText
51 MainWin::setTreeWidgetItemDockColor
54 Think about good ways to clean up the Console creation part of the
56 ========================================================
59 A window showing a list of jobs and defaults. Defaults can be gotten in manner
60 similar to what the first restore window does.
62 A window showing a list of schedule resources.
64 Kern discussed windows showing statistics like web based interfaces.
65 ========================================================
68 The ablility to modify configuration files to create jobs, schedules, filesets
69 and any other director resources.
71 The ablility to modify configuration files to create storage resources.
73 Add a status dir graphical interface. It would auto update every ?? seconds
74 and have a list of scheduled jobs, and in the que to run jobs that could be
75 cancelled graphically.
77 Add a status client window. Keep updating showing what file is being
80 A Tree widget context sensitive menu option and class to jump from known job
81 to surf the filestructure on the job.
83 bRestore add code to get working.
85 ===========================================================
87 ===========================================================
89 I'm not sure about this one?? Things seem to work and I did not do a
90 thing to make it happen: the "dir" is a member of Console
92 - We also must somehow make the low level I/O routines know which
93 director/console to use. Currently they always use the single
94 global one defined in the mainWin class (if I remember right).
96 ============================================================
98 ============================================================
99 Create the ability to start a restore from joblist. Right click, select
100 "restore from Jobid=xx" create an instance of restore defaulting in the jobid
101 or a list of selected jobs.
103 Update README describe bat.conf.example to bat.conf
105 Test restore and get anything not working, working.
106 Add inteligence to prerestore.
108 Color code Media Red->Error Append->green Full/Used->Yellow
110 Get restore into stack.
111 Should the jobs dialog be turned into a page as well??
112 Possilbe: Turn run and label into docked pages. (remove button bar buttons??)
114 Where and bootstrap are confused in runjobs of restore.
115 This was just the labels.
117 Create list of what does not work.
118 From what I can tell, just the restore window on the left.
120 Add option to LIMIT the number of jobs shown in all jobs page for users with
121 multiple hundreds to thousands of jobs.
123 Play with includes to Make these compiles shorter.
124 moved includes of of includes and into files only console.h should be long
126 relabel storage=DDS3 oldvolume=ddsvol003 volume=dds3vol003 slot=3 pool=dds3_hope
127 in label slot spinner, limit the upper to the value of slots for that storage.
129 Fix bug in myth box not working with .sql query="" command.
130 This was a fix in mysql
132 Figure out how to get tables like Joblist to do the equivalent of double clicking
133 on the separating lines between each of the headings.
134 Tried the hard way first. Oops.
136 If the console command line entry docked widget gets the focus, make
137 m_currentConsole the top widget by setting the treewidgetitem selected.
138 Did this in MainWin::input_line almost better to let the person see
139 whatever they want until they hit enter.
141 Set Window titles to reflect what director it is.
143 Must:: get page selector to follow undocked windows. Otherwise
144 current console won't be current.
146 Re-add class for storage, I accidentally reverted because I left
147 it on my laptop. This is why I like committing often.
149 Add class for FileSets
151 Another idea for what you have implemented:
152 - I think that the dynamic pages that you create on the fly
153 should be nested under the item that creates them more like a
156 For example: Jobs on Volume xxx, probably should be shown under
157 "All Jobs" (or Media if that is what created it) and "Jobs of
158 Client Rufus" probably should be shown under "Clients". I base
159 this on looking at the Select page list after I have brought up 3
160 or 4 dynamic pages. Once there are a good number, I get a bit
161 confused where they came from. This would also permit selecting
162 multipe Volumes then displaying multiple pages, one for each
163 Volume selected. If they are nested, then that nested level can
164 be expanded or collapsed, which would be pretty cool at keeping
165 information, but getting it out of the way, sort of like what
166 happens for a directory tree.
169 My original concept was to put these in a tabbed widget. Your Idea may
170 make for a cleaner user experience. I like it. It could save the
171 effort of getting a tabbed widget to work.
174 - I think we need to make the current Director more explicit, by
175 perhaps highlighting it in the page selector when it is current
176 and unhighlighting it when it is not (we could use color as we do
177 for the console, though some color blind people may have
180 - When any director is clicked, we need to set it as the current
181 director and set the current console as well.
183 Remove DoubleClicking, From pages class not needed any more.
185 Broken with multiple directors:
186 - If you click on the second director, it will probably open, but
187 none of the pages that are defined below it will be able to talk
188 to it. They will most likely talk to the first director.
190 - When any console is clicked we need to set it as the current
191 console (m_console) and also set its director as the current
192 director (m_topItem). These are in the mainwin class.
194 - When any page is selected, we must set both the current
195 director (m_topItem) and current console (m_console) that this
196 page is connected to.
199 m_topItem has been changed to Console::directorTreeItem()
200 m_currentConsole->directorTreeItem(); returns disired treeWidgetItem
202 - We also need a concept of a "local" director/console for each
203 page, so the page knows who it is talking to -- this doesn't
204 currently exist, so I think we must pass the director and console
205 to each page widget constructor.
208 m_currentConsole is saved in each page subclass's m_console. This value
209 is set by all but the console class calling Pages::pgInitialie() in it's
213 In short, there is a lot of work to be done to make multiple
214 simultaneous directors work.
219 If the above prooves to be too much, we might consider to only
220 have a single director at a time, and simply let the user select
221 which director he wants to connect to (one at a time, but
222 dynamically). In the end, this may be the best thing to do, so
223 any user who wishes to connect to multiple directors would run
224 two instances of bat. I am a bit unsure now, but the above list
225 of things to do is much bigger than I thought it was going to be.