Linked by Thom Holwerda on Tue 18th Jan 2011 22:18 UTC, submitted by alinandrei
Thread beginning with comment 459039
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[8]: De kogel is door de kerk
by saynte on Wed 19th Jan 2011 10:30
in reply to "RE[7]: De kogel is door de kerk"
But only Qt applications which were re-written to explicitly call those bindings (probably making them a dependency, and also therefore bringing in dconf as a dependency) would be able to work.
However, modifying dconf to also provide a replacement QSettings class and a replacement qtconfig would provide the desired mechanisms for Qt applications running under Ubuntu's GNOME to use the dconf database WITHOUT having to modify said Qt applications!
Better for everybody!
This would be a bad software design. dconf has a very dedicated purpose, you do not want to complicate it with unnecessary functionality.
RE[9]: De kogel is door de kerk
by lemur2 on Wed 19th Jan 2011 10:37
in reply to "RE[8]: De kogel is door de kerk"
"
But only Qt applications which were re-written to explicitly call those bindings (probably making them a dependency, and also therefore bringing in dconf as a dependency) would be able to work.
However, modifying dconf to also provide a replacement QSettings class and a replacement qtconfig would provide the desired mechanisms for Qt applications running under Ubuntu's GNOME to use the dconf database WITHOUT having to modify said Qt applications!
Better for everybody!
But only Qt applications which were re-written to explicitly call those bindings (probably making them a dependency, and also therefore bringing in dconf as a dependency) would be able to work.
However, modifying dconf to also provide a replacement QSettings class and a replacement qtconfig would provide the desired mechanisms for Qt applications running under Ubuntu's GNOME to use the dconf database WITHOUT having to modify said Qt applications!
Better for everybody!
This would be a bad software design. dconf has a very dedicated purpose, you do not want to complicate it with unnecessary functionality. "
Extra functionality (integration of an environment for Qt applications under GNOME) ... that Mr Shuttleworth has said he wants for his GNOME desktop ... functionality that already involves dconf ... why not just do it within the dconf package and be done with it?
Better for everybody.
Edited 2011-01-19 10:42 UTC





Member since:
2007-02-17
Having the author of dconf write bindings for Qt, so there is the choice of using it, is a good thing!
But only Qt applications which were re-written to explicitly call those bindings (probably making them a dependency, and also therefore bringing in dconf as a dependency) would be able to work.
However, modifying dconf to also provide a replacement QSettings class and a replacement qtconfig would provide the desired mechanisms for Qt applications running under Ubuntu's GNOME to use the dconf database WITHOUT having to modify said Qt applications!
Better for everybody!