Re: [Qt-creator] It's time to fix double redundant quotes
On 09/03/16 00:10, Jason H wrote:
A while back, I started a discussion about Creator's quoting policy. There was
a lot of support, and a few people were concerned about changing the behavior
that has been there since the beginning.
However, I'm again tired of fighting with creator inserting "" when I type " and deleting
both when I backspace over one. This behavior only occurs in QtCreator, and no other editor _ever_, and
it needs to go. It is a "clever trick" that costs more than it is clever. At least for me,
YMMV.
Yes, there is a checkbox, but that applies to brackets and braces as well.
Fundamentally, I want to changes to the behavior:
1. If the character after the cursor is not whitespace, do NOT double quote ("")
2. If backspacing over a double quote, do not remove both double quotes.
For the love of all that is binary!!!
Wait, it's not a bug? They actually want that behavior?
lol :-P
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
[Qt-creator] Linguist
Hi, is there any good reason why linguist is not configured as a standard external tool? I'd like to add it. Regards, Jochen ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] It's time to fix double redundant quotes
I support Jason, it's annoying, but somehow i got used to the pattern of
post-quote elimination which is suboptimal to say the least.
Ariel
On Tue, Mar 8, 2016 at 4:10 PM, Jason H wrote:
> A while back, I started a discussion about Creator's quoting policy.
> There was a lot of support, and a few people were concerned about changing
> the behavior that has been there since the beginning.
>
> However, I'm again tired of fighting with creator inserting "" when I type
> " and deleting both when I backspace over one. This behavior only occurs in
> QtCreator, and no other editor _ever_, and it needs to go. It is a "clever
> trick" that costs more than it is clever. At least for me, YMMV.
>
> Yes, there is a checkbox, but that applies to brackets and braces as well.
>
> Fundamentally, I want to changes to the behavior:
> 1. If the character after the cursor is not whitespace, do NOT double
> quote ("")
> 2. If backspacing over a double quote, do not remove both double quotes.
>
> For the love of all that is binary!!!
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
>
--
Ariel Molina R.
Oficina: +52 (222) 3723196
Movil: +521 2226 758874
http://edis.mx
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
[Qt-creator] It's time to fix double redundant quotes
A while back, I started a discussion about Creator's quoting policy. There was
a lot of support, and a few people were concerned about changing the behavior
that has been there since the beginning.
However, I'm again tired of fighting with creator inserting "" when I type "
and deleting both when I backspace over one. This behavior only occurs in
QtCreator, and no other editor _ever_, and it needs to go. It is a "clever
trick" that costs more than it is clever. At least for me, YMMV.
Yes, there is a checkbox, but that applies to brackets and braces as well.
Fundamentally, I want to changes to the behavior:
1. If the character after the cursor is not whitespace, do NOT double quote ("")
2. If backspacing over a double quote, do not remove both double quotes.
For the love of all that is binary!!!
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] QtCreator 4.0: Where did my color icons go
> Yes, implementing Diana's theme for 4.0 is the goal. At least the darker > variant, and the light one afterwards. Nice! I've already started to play with the variable in the theme since I like the flat buttons on the right :) Thanks for implementing it. Lorenz ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] Sug: Refactor text
> On Mo, 2016-03-07 at 20:44 +0100, Jason H wrote:
> > It would be cool if we could right click on a string "this" and refactor:
> > translate or refactor:translate plural, where in it gets changed from "this"
> > to:
> > qsTr("this") or
> > qsTr("this", "", n)
> > Respectively.
> >
> > Alternative "refactorings" could be: All uppercase, Title Case, or all lower
> > case.
>
> Please report suggestions, feature requests and bug reports at
> https://bugreport
> s.qt.io/
>
> Reports stay around in the bug tracker forever... here they get lost as soon
> as
> enough mails have arrived to push your suggestions down far enough to require
> scrolling;-)
That's fine. Sometimes I like to post here first to get comments, ranging from:
1. It's there, you just aren't using it correctly.
2. That's brilliant! :-)
3. That's stupid. :-(
4. Me too.
(In no particular order)
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] QtCreator 4.0: Where did my color icons go
Hi, Yes, implementing Diana's theme for 4.0 is the goal. At least the darker variant, and the light one afterwards. The original theme with gradients and colored mode icons as-well as the "dark" theme are supposed to stay. Best Regards, Alessandro From: Qt-creator on behalf of Ariel Molina Please do it, that's a nice theme! On Mon, Mar 7, 2016 at 10:42 AM, Lorenz Haas mailto:lyk...@gmail.com>> wrote: Hi Alessandro, are you going to implement the entire flat style UI Diana proposed here http://blog.qt.io/blog/2015/02/09/qt-creator-flat-style-ui-design-new-light-theme for 4.0? Cheers, Lorenz ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] CMake in QtC 4.0 [ex Qt Creator 4.0 soft-branched]
On 03/08/2016 03:48 PM, Alexander Drozdov wrote: I think, that compilers for the langs, supported by the QtC should be detected too. Otherwise: we can create C project via wizard but can't point C compiler. Not a good (is it problem solved for Qbs, qmake and how?). It's an unsolved problem. Basically Qt Creator assumes single-language projects. Christian ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] CMake in QtC 4.0 [ex Qt Creator 4.0 soft-branched]
2016-03-08 20:01 GMT+10:00 Hunger Tobias : > Hi Alexander, > Hi again! [skip] > > > > > I know and understand. In my solution I simple predict C compiler based > on > > some info: g++ -> gcc, clang++ -> clang, cl.exe -> cl.exe :-) with same > > prefixes and suffixes > > Look (core removed after dialog reworks): > > > https://github.com/h4tr3d/cmakeprojectmanager2/commit/268b1cb93ea3fb40c7bdcaea > > d51452c764dc95bb#diff-8809e7f792412acf4605265b6ad2c20fR790 > > I would prefer to keep this as is: It is pretty straight forward for the > users > (or an admin/packager) to provide custom cmake config flags to be set by a > kit. > So this problem can be addressed at that level (till Qt Creator starts to > manage > several toolchains per kit at some point -- if we ever go there). > I think, that compilers for the langs, supported by the QtC should be detected too. Otherwise: we can create C project via wizard but can't point C compiler. Not a good (is it problem solved for Qbs, qmake and how?). But this question must be discussed ouside of the CMake-only context. It more deeply. > > > > > No. Toolchain file in simple way look like settings. But in some complex > > cases it can call CMake functions, search complilers via find_program() > and > > so so. > > > > To somplify: Toolchain file is a file that preloaded by the cmake before > > CMakeLists.txt. > > I would argue that they still are just a bunch of settings... at least > after > they are executed. Since kits are host specific, I still think we can get > away > with the current approach: Just put whatever concrete information you need > into > the Kit's settings and you are done. Yes, that fails to detect compilers > and > stuff for you, but you know where those are anyway. > > > If that is the case: Can the CMake Configuration in the Kits cover that? > > > > Not in all cases. Also, in some cases you can want simple builds current > > project with current Kit but with suggested Toolchain. Toolchain can be > > specific for single project. Create Kits for every toolchains not a good > > idea. IMHO. > > IMHO it is:-) How else would you switch between different configurations > easily? > Heh, two compilers (gcc 4.8, gcc 5.3) and two Qt versions (4.8, 5.5) requires to create four Kit configurations. Adding clang increases possible Kit configurations up to six. Increasing Kit settings increases possible Kit configurations dramatically. CMake toolchain can use same compiler but provide some other presets. In general Toolchain file can be used not only for cross-building. In common: it can be interpreted as a per-build project configuration. Complex and power configuration, not only VARIABLE=value pairs. [skip] > > > I understand. I try to parse cmake (adopt tokenizer to build with plugin) > > but it to complex to process CMakeLists.txt and in sub-CMakeLists.txt. > > I am not brave enough to go there:-) > I too :-) Simply tried. But KDevelop and CLion guys more-less solve this problem. > > > 4. In handlers of the given signals I ask BuildDirManager to do > > forceReparse() > > > > This scenarion works very well for FILE GLOBBING and AUX SOURCE DIR. And > > yes, this scenarion requires addition CMake execution when files > described > > in CMakeLists.txt without globbing. > > Yes, I see that it will work there. But that is not good enough for me, > simply > because I will get tons of bug reports about "Add file" not working from > lots of > people that do not use such a setup. There are just too many cmake users > out > there for me to risk that:-) > Hmm. On file adding cmake reparsing forces. We can checks that added files not goes to the any target and output notice to the top of the editor (like in past notice to re-run cmake outputs). Like: "File added but not assigned to any target, please edit CMakeLists.txt manually". Yes only source-code files should be filtered :-) [skip] > > Not in a straight forward way... The tree is pretty static as is the > transformation from the full tree to the simplified tree. > Ok, thanks. > > > Look: > > * > > > https://github.com/h4tr3d/cmakeprojectmanager2/commit/61df428d14c7bb785b50f26a > > 90517aecb701a9eb > > - reading source tree > > Could you consider to push the scanning logic upstream? > No problem. Simple give me some amount of time :-) Also, could you please provide Best Qt-friedly way to scan directory tree? If recursion can be omited - it will be good. My current solution uses QDir::entryInfoList() + recursion. [skip] > > > A combobox to select between a set of different options is not going to > > > happen, > > > simply because cmake has no way (that I found) to tell Qt Creator > about the > > > allowed values. > > > > Ok. Not a problem. But, I found that it is impossible to add some custom > > value: there is Edit button but there is no Add button. It works as > planed? > > I wanted to implement adding and unsetting values, but then I thought that > this > will probably not be necessary: CMake
Re: [Qt-creator] CMake in QtC 4.0 [ex Qt Creator 4.0 soft-branched]
Hi Alexander, On Mo, 2016-03-07 at 23:44 +1000, Alexander Drozdov wrote: > 2016-02-29 19:31 GMT+10:00 Hunger Tobias : > Hi Tobias, sorry for delay No worry:-) > > Currently I > > > see, that two of the four features that I support at the > > > CMakeProjectManager2 (fork on github) already implemented: > > > 1) Handling Kit compiler. But only C++, not C or other. But it simple > > > configurable at the Kit configuration page now. > > QtCreator does only know one toolchain for each Kit and assumes that to be > > a C++ > > one. So there simply is not enough information to set up the C compiler > > with the > > information available. We will need to manage toolchains and programming > > languages they support for that and I currently have no plans to go that > > far, > > even though that information is also useful for other build systems. > > > > You can add any cmake settings you need to the Kit's cmake configuration > > though > > and those settings will then be applied automatically everywhere that kit > > is > > used. > > > I know and understand. In my solution I simple predict C compiler based on > some info: g++ -> gcc, clang++ -> clang, cl.exe -> cl.exe :-) with same > prefixes and suffixes > Look (core removed after dialog reworks): > https://github.com/h4tr3d/cmakeprojectmanager2/commit/268b1cb93ea3fb40c7bdcaea > d51452c764dc95bb#diff-8809e7f792412acf4605265b6ad2c20fR790 I would prefer to keep this as is: It is pretty straight forward for the users (or an admin/packager) to provide custom cmake config flags to be set by a kit. So this problem can be addressed at that level (till Qt Creator starts to manage several toolchains per kit at some point -- if we ever go there). > No. Toolchain file in simple way look like settings. But in some complex > cases it can call CMake functions, search complilers via find_program() and > so so. > > To somplify: Toolchain file is a file that preloaded by the cmake before > CMakeLists.txt. I would argue that they still are just a bunch of settings... at least after they are executed. Since kits are host specific, I still think we can get away with the current approach: Just put whatever concrete information you need into the Kit's settings and you are done. Yes, that fails to detect compilers and stuff for you, but you know where those are anyway. > If that is the case: Can the CMake Configuration in the Kits cover that? > > Not in all cases. Also, in some cases you can want simple builds current > project with current Kit but with suggested Toolchain. Toolchain can be > specific for single project. Create Kits for every toolchains not a good > idea. IMHO. IMHO it is:-) How else would you switch between different configurations easily? > Maybe we could add an "import from toolchain file" to the CMake > > > > Configuration dialog? > > > Not a good idea. See above. OK. > 2) Adding files via context menu and show all files in source Tree: it > > > allows to add new file to the target directory, see it and after simple > > add > > > > > > to the needed target at the CMakeLists.txt > > The only chance I ever see that happening is for cmake-daemon ( > > https://steveire > > .wordpress.com/2016/01/24/cmake-daemon-for-user-tools/ ) to get accepted > > upstream. > > > I understand. I try to parse cmake (adopt tokenizer to build with plugin) > but it to complex to process CMakeLists.txt and in sub-CMakeLists.txt. I am not brave enough to go there:-) > So currently I use next scenario: > 1. For code module I use files provided by the CbpParser > 2. For source tree I display all files. Yes, it displayes files like > README, LICENSE and some sources that skipped from the compilation (and > from the Model). But it simplify navigation and adding/removing/renaming I have been thinking on doing that, too. I hate the idea of just scanning the file system, but I think it is the best that cmake will let us do. > 3. Enable items Add/Rename/Remove file I don't plan on that yet. > 4. In handlers of the given signals I ask BuildDirManager to do > forceReparse() > > This scenarion works very well for FILE GLOBBING and AUX SOURCE DIR. And > yes, this scenarion requires addition CMake execution when files described > in CMakeLists.txt without globbing. Yes, I see that it will work there. But that is not good enough for me, simply because I will get tons of bug reports about "Add file" not working from lots of people that do not use such a setup. There are just too many cmake users out there for me to risk that:-) > And yes, this algorithm requires additional work: > 1. Scan sources tree > 2. Sorts tree and cmake tree > 3. Search for added files (ProjectExplorer::compareSortedLists) > 4. Substract and clear source dir tree (qDeleteAll + > ProjectExplorer::subtractSortedList) > 5. Add it to the cmake tree > 6. Pass new cmake tree list to the buildTree() > > Also, this behaviour same to the KDevelop, CLion. But it can be done > optional in simple way. > > One questi
Re: [Qt-creator] Sug: Refactor text
On Mo, 2016-03-07 at 20:44 +0100, Jason H wrote:
> It would be cool if we could right click on a string "this" and refactor:
> translate or refactor:translate plural, where in it gets changed from "this"
> to:
> qsTr("this") or
> qsTr("this", "", n)
> Respectively.
>
> Alternative "refactorings" could be: All uppercase, Title Case, or all lower
> case.
Please report suggestions, feature requests and bug reports at https://bugreport
s.qt.io/
Reports stay around in the bug tracker forever... here they get lost as soon as
enough mails have arrived to push your suggestions down far enough to require
scrolling;-)
Best Regards,
Tobias
--
Tobias Hunger, Senior Software Engineer | The Qt Company
The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der Gesellschaft:
Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
