Re: [Interest] CLion to replace QtCreator?

2016-04-04 Thread Nikos Chantziaras
It only works with the old, Qt4 string/macro-based syntax (using the SLOT and SIGNAL macros.) Which is totally unsafe and I don't use it anymore (I wouldn't even recommend it to anyone.) The new syntax, which is statically checked (compile time) and thus type-safe, even though it's the

Re: [Interest] CLion to replace QtCreator?

2016-04-04 Thread Diego Iastrubni
On Sun, Apr 3, 2016 at 10:00 PM, Thiago Macieira wrote: > > But I have to say I don't feel any unpleasantness. Qt Creator is the best > IDE > I've ever used. There are some things I'd do differently, but that's all. I > also expect that's how most Qt developers and

Re: [Interest] CLion to replace QtCreator?

2016-04-04 Thread Emre Besirik
Sorry forgot to mention this was meant for Alexey Rusakov :) Regards, Emre Beşirik nome...@gmail.com > On 04 Apr 2016, at 13:59, Emre Besirik wrote: > > BTW I think you are replying to the person instead of list address. > list can not see your replies if you dont send it

Re: [Interest] CLion to replace QtCreator?

2016-04-04 Thread Emre Besirik
> XML tags completion for known tags. This can be done for *.UI files, and > maybe some part of *.QS. Basic XML structure is already know - so even for > unknown XML variants - the IDE knows what tag to close. > Class implementations - for example, I derive from an interface and pressing >

Re: [Interest] CLion to replace QtCreator?

2016-04-04 Thread ekke
Am 04.04.16 um 10:12 schrieb Nikos Chantziaras: > On 03/04/16 22:00, Thiago Macieira wrote: >> On domingo, 3 de abril de 2016 21:07:00 PDT Emre Besirik wrote: >>> Do you also find it a littlebit unpleasent to code in QtCreator like >>> me? >>> Does Qt plan to do something about this? >> >> It

Re: [Interest] CLion to replace QtCreator?

2016-04-04 Thread Emre Besirik
BTW I think you are replying to the person instead of list address. list can not see your replies if you dont send it to the list. Regards, Emre Beşirik nome...@gmail.com > On 04 Apr 2016, at 13:47, Nikos Chantziaras wrote: > > On 04/04/16 13:29, Alexey Rusakov wrote: >> I

Re: [Interest] CLion to replace QtCreator?

2016-04-04 Thread André Hartmann
Hi all, 1. XML tags completion for known tags. This can be done for *.UI files, and maybe some part of *.QS. Basic XML structure is already know - so even for unknown XML variants - the IDE knows what tag to close. That would indeed be very cool. 2. Class implementations - for

Re: [Interest] CLion to replace QtCreator?

2016-04-04 Thread Nikos Chantziaras
On 04/04/16 13:29, Alexey Rusakov wrote: I don't know what I'm doing wrong but the new compile-time-checked syntax is auto-completed by my Qt Creator (that came with Qt 5.5.1) as well :) With the clang code model? (Which is the only even remotely useful choice for modern C++.) and you're

Re: [Interest] CLion to replace QtCreator?

2016-04-04 Thread Konstantin Tokarev
04.04.2016, 15:40, "Sean Harmer" : > On Monday 04 April 2016 15:13:01 Emre Besirik wrote: > >>  tabs — the current working type of open documents are really annoying. if >>  you have split view open, first you need to select the view you intend to >>  change open document.

[Interest] Available versions to QML import in older Qt releases?

2016-04-04 Thread Elvis Stansvik
Hi all, I'm working on a product based on Ubuntu 15.10, where Qt 5.4.1 is the packaged version (I know a more recent Ubuntu is soon to be released, and an LTS at that, but we're on this version for now). Is there an online way to find out which versions of packages I can import from the QtQuick

Re: [Interest] CLion to replace QtCreator?

2016-04-04 Thread Emre Besirik
> On 04 Apr 2016, at 15:18, Konstantin Tokarev wrote: > > > > 04.04.2016, 15:13, "Emre Besirik" : >>> * XML tags completion for known tags. This can be done for *.UI files, and >>> maybe some part of *.QS. Basic XML structure is already know - so even

Re: [Interest] CLion to replace QtCreator?

2016-04-04 Thread Konstantin Tokarev
04.04.2016, 15:13, "Emre Besirik" : >> * XML tags completion for known tags. This can be done for *.UI files, and >> maybe some part of *.QS.  Basic XML structure is already know - so even for >> unknown XML variants - the IDE knows what tag to close. >> * Class