Re: [Qt-creator] Syntax highlighting of PHP files
Hi, I resubmitted a change that was lost during a feature freeze (https://codereview.qt-project.org/#/c/88138/) You can check if the new syntax file works by simply replacing your html.xml syntax file with the new web.xml from the patch under creator path/share/qtcreator/generic-highlighter. BR, David On 6/23/2014 11:21 PM, Jochen Becher wrote: Am Montag, den 23.06.2014, 08:33 + schrieb Hunger Tobias: On 20.06.2014 20:10, Jochen Becher wrote: I would like to use QtCreator for some small PHP/HTML5/CSS/Javascript projects I am currently working on. Creator might not be the best tool for this job. Surely not the best but I don't want to use another IDE just because I want to edit some php files and jQuery code. I already started to create some file wizards for Web projects, PHP and HTML files. Any idea what's going wrong? Unfortunately I do not, but then the editors are not really my area of expertise. I do not have Kate installed on my system but gedit from Gnome 3. It highlights these files correctly but I am not sure if gedit also uses the Kate definitions. AFAIK gedit is using a completely different highlighter. So that gedit works is not really a sign that creator should also work. Creator will most likely also have trouble with PHP embedded in HTML. AFAIK (not my area of expertise, see above) Creator has one generic highlighter, so you will get either PHP or HTML. I found this http://comments.gmane.org/gmane.comp.lib.qt.general/42686 If I understand it right QtCreator should already be able to handle embedded highlighting. But for now I would be happy to know why PHP highlighting isn't working. Embedded HTML is the next step. Regards, Jochen Best Regards, Tobias ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] Ugly font rendering?
23.06.2014, 16:33, Nikos Chantziaras rea...@gmail.com: I was using Qt Creator 2.8.1 and decided to try 3.1.1. So I installed it using the official Linux installer. The fonts look washed out and lack blackness, making them tiring to read. Here's how fonts look in Creator 2.8.1: http://s15.postimg.org/es4jn3xdn/qt4.png and here's how they look in 3.1.1: http://s28.postimg.org/lic77ee25/qt5.png Is there anything I can do about this? As for me, it would look quite nice if full hinting was enabled. -- Regards, Konstantin ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] Refactoring the CMake plugin
1) Registering new cmake instances / tools The idea is to provide a way for plugins to register their own cmake installation and I introduced a class called CMakeManager that will own all registered installations. Every registered cmake will be represented by a CMakeTool instance, that abstracts away how a specific cmake is invoked. To register them I can see 2 ways: a) using factories: Personally I like factories more, maybe the approach used by the toolchains would fit here too (QListCMakeTool* Factory::autoDetect()). That would also require a UI in the settings dialog where the user can manage the available cmake tools and manually register them. b) provide a function called registerCMakeTool() in the I'd like to see more than just a ubuntu sdk specific use case for this. As is, I don't see much value in that. CMakeManager that can be called by plugins. 2) Associating a cmake tool with a build Now that there is a way to have more than one possible cmake, there needs to be a way to control which cmake is used when building/creating the project files. a) By linking it to a Kit - provide a CMakeKitInformation so the user can control which Kit uses which cmake tool b) By linking it to a build configuration - a CMakeBuildConfiguration would either need to return a Core::Id specifying the cmake tool it wants to use, or the CMakeTool instance itself, so the IDE can use it to create the build files. The build configurations config widget then can provide a way for the user to switch between the cmake installations available. Like Tobias said, definitely in the kit. 3) Automatically running cmake in the background (Get rid of the Run cmake dialog) It would be nice if the user was not required to handle the cmake dialog every time he wants to change the build settings, cmake arguments or wants to switch between different build configurations. In my MR, a cmake run is automatically started every time the build settings are changed and when opening a unconfigured project the project configuration page is used. At first sight this is very similar to how qmake behaves and makes it easily possible to switch between multiple build configurations without the need for running the cmake dialog every time. But the difference of course is that there are files created when running cmake and the user does probably not know about that. -- A possible solution to this would be to open a dialog to change the build settings, but to run cmake automatically when switching between build configurations. This would make the user more aware of what is happening. Right, that would work. daniel ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
