RFC: Improving Qt4 designer support in kdevelop3.4

[Andreas Pakulat]

On 19.07.06 19:47:02, Andreas Pakulat wrote:
> Hi,
> 
> I started to look at how the designer support for kdevelop3.4 could be
> improved. Working my way through the FAQ I stumbled upon:
> 
> http://www.kdevelop.org/mediawiki/index.php/FAQ#How_can_I_develop_with_Qt4_and_KDevelop-3.3.x.3F
> 
> which says that kdevelop starts designer through kdeinit. So before I
> start to dig into kdevelop's code, I'd like to ask if you guys want to
> keep it that way or if it would be Ok to specify the path to the
> designer within kdevelop and kdevelop just runs that.
> 
> The drawback of the kdeinit option is that if no desktop file for either
> qt3 designer or qt4 designer is installed in the system the user needs
> to create one (this is the case currently for qt4 on debian). Also the
> second option would allow kdevelop to run the "proper" version of other
> Qt tools, such as qmake, automagically without fiddeling around with
> PATH.

Should've looked at the source first, before trusting a (possibly
outdated) FAQ entry. KDevelop uses KRun::run with a QString, which
doesn't invoke kdeinit. So I'm definetly going with the 2nd option,
specifying the qtdir.

Andreas

-- 
Ships are safe in harbor, but they were never meant to stay there.