Cross-Platform Qt-Based Implementation of Low Level GUI Layer of ROOT. V.Fine BNL, Upton. Why ROOT is multi-platform ?. Just to be healthy ! Just because there are plenty of Windows users around. ROOT for different platforms http://root.cern.ch/root/images/ftpstats.gif.
It does what it promises !
Myself have been confused no time with Qt documentation and functionality
But it is not my (ROOT user) business to make the ROOT team life more easy.
The plain implementation of TVirtualX that doesn’t bring any new feature can not justify the efforts to introduce a new extra layer and external dependency of the ROOT package
0.5 day to implement
1 day to implement !
2 days to implement
There are enough evidences the present approach allows the ROOT developers as well as ROOT users to work with code that has no X11/WIN32 graphics subsystem dependencies and at the same time opens unrestricted access to a rich set of ready-to-use commercial and free GUI Qt-based widgets. The Qt-based version was tested on Unix and Windows.
0. Long lasting application Layer of ROOT
1. Very wide used on Linux system (KDE)
2. Shipped with the source code and installation script
(no technical to take over but legal issue).
1. What is accepted level:
1. one pixel was that reliable level
2. dialog window is a mandatory attibute of any system
ROOT is designed like we 20 years ago
2. Qt - quality
library of Widget
weel-though separation of the automaically generated GUI and
user-provided custom actions. (Tha tallow to share GUI across applications)
3. Functionality: They treat MS a GUI standard
3. What ROOT may end up with. The best scenario we will ned up with somethin
Qt alike but in many years.
1. Free for non-commercial applcation on X11 platform
2. True cross platform (code designed and debugged on with free UNIX will
work in Windows
3. This allow to minimiz the number of Windows license
4. Windows license is really cheap anyway (acad. price $700/developer)
our experiecne did prove this worth to buy. It is much faster and better
to create GUI with Qt rather struggle with TG<classes>
4.1. Lack of documentation
4.2. Lack of functionality
Qt 2. restrictive
Qt 3. can be accepted