On Tue, 2010-03-16 at 15:34 +0100, Attila Csipa wrote:
> On Tuesday 16 March 2010 14:47:58 Bernd Stramm wrote:
> > Another point of view is that the excellent portability provided by Qt
> > comes from the libraries. Tying this to any particular IDE is really
> > bad. It generates programming styles and project build structures that
> > have nothing to to with the Qt libraries or the application problem.
> > This is not a good thing, regardless of how fine a product Qt Creator
> > is.
> 
> >From what I understand, MADDE is something quite separate from Qt Creator. 
> >Qt 
> Creator is fairly modular, and in this case, is extended to handle MADDE. 
> This does imply loosing the ability of calling MADDE with the appropriate 
> paramers yourself should you not like Qt Creator for some reason, and I hope 
> the MADDE team keeps the CLI mode in the future, too. As for styles and 
> project build structures... well, from my experience Qt creator is fairly 
> agnostic in that regard, especially if you use qmake and .pro files. From all 
> the all-in-one development enviroments I have used, Qt Creator is definitely 
> in the less-intrusive group.
> 

Yes creator is nice in that regard. What I had in mind is, for example
that Qt Creator, like most IDEs, works best when the project has one
single build target. Multiple build targets are really inconvenient.

This causes people to pack all functionality into a single program.
Other development environments produce lots of small programs for a
related purpose, like for example git. This is easy to do with make.

I'm not saying that one approach is better than the other, it depends on
the application. I'm saying that the structure is often an artifact of
the development environment, not a result of what is best for the
application. That is the part that's bad. That is why it is better to
have alternatives to Qt Creator.

Bernd


> 
> Regards,
> Attila
> _______________________________________________
> MeeGo-dev mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-dev


_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to