2 This directory contains the Bacula Admin Tool (bat).
4 At the current time, the contents of this directory are under
5 development. If you want to help, please contact Kern directly.
6 If you want to build it, you need Qt4 loaded and setup as your
7 default Qt or with the appropriate Qt Environment variables set.
10 There is now one dependency, it is qwt. It compiles just fine with
11 either qwt-5.0.2 or qwt-5.0.1. You can either install the qwt package
12 yourself or if your distro does not have it, we have included the source
13 in depkgs-qt, which you can download from the Bacula Source Forge
16 Building and running bat is done much like bconsole. You add the appropriate
17 options to your ./configure, then simply do a make. Please see the
18 Installation chapter of the manual for more details.
21 Win32 mingw infos for QT4 :
23 - http://doc.qtfr.org/post/2007/04/10/Cross-Compilation-Native-dapplication-Qt-depuis-Linux
25 Development status as of 05/06/07
27 Items not implemented:
28 - Nothing on the brestore page
31 - All translatable strings should be written as tr("string") ...
32 - To extract the strings for translation run:
36 - To translate the strings, do:
40 where xx is the country code (e.g. fr or de)
42 - To "compile" the translated strings do:
46 The necessary binary files will be in ts/bat_xx.qm
47 As far as I can tell, these files must be on your path or
48 in the same directory as bat for them to be used, otherwise
49 it reverts to English. Selecting the translation is based on
50 how your system is setup or the LANG environment variable.
53 - If possible all code for a particular component will be kept in
54 an appropriate subdirectory.
55 - All private class variables are named "m_xxx" this makes it very
56 clear if one is referencing a class variable or a local.
57 - All signal/slots are connected by explicit code (most all are
58 done in the MainWin constructor), rather than using designer.
59 - Each page has a separate designer .ui file in a subdirectory.
60 - All windows are created with designer and have
61 a name such as xxxForm i.e. the main window is MainForm and kept
65 - Implement other restore interfaces such as brestore ...
66 - Implement a database browser
67 - Implement a resource (conf file) browser
68 - Implement a reports page -- e.g. something similar to bweb
69 - Implement Qt plugins to add new functionality to bat
70 - Implement a GUI configuration file editor (something like JBacula).
74 ===========================
75 - Implement graphical commands that allow updating most aspects of
76 the database (i.e. commands for label, update Volume, ...)
77 still need to be able to edit a pool object
79 - None of the menu items except About, Select Font, and Quit.
80 Print and save don't do anything, does save need to??
82 ============================
83 Design/implementation considerations:
84 - Need icons in front of the Director.
85 - The console page should be in a DockWidget so it can be removed
86 from the main window. It is currently in a dock window, but it
87 does not remove properly -- more research needed.
88 - Need to figure out a good implementation of adding pages and even
89 having plugins that load as pages. Currently the page mechanism
92 - We need to have multiple Directors
93 - Each Director should have its own console
94 - The Console class needs to be a list or be attached to the
95 currently active Director.
96 - Will automatically connect to the first Director in the
97 conf file. Doesn't know about multiple Directors.
99 - The Label menu bar item, prints on the shell window what you entered.
100 - The Run menu bar item, prints on the console window what you entered.
101 - The Restore menu bar item, brings up dialog, then when OK is
102 clicked, it goes on to the next dialog, which is meant to be
103 a tree view, but for the moment does nothing ... It is a bit
104 ugly. Canceling it should get you back to the normal command prompt.
106 - Implement a restore page that does a directory tree restore selection.
109 - The left selection window and the right window (where the console
110 is) are dockable windows so should be movable once they are properly
111 clicked. Well, they sort of move, but then get stuck. I haven't figured
112 out what is going on, so for the current time, I am implementing most
113 stuff through dialogs.