Language Selection

English French German Italian Portuguese Spanish

Qt Creator 4.8 Beta released

Filed under
KDE

In Qt Creator 4.8 we’ll introduce experimental support for the language server protocol. For many programming languages there is a “language server” available, which provides IDEs with a whole lot of information about the code, as long as they support communicating via the protocol.

This means that by providing a client for the language server protocol, Qt Creator gets (some) support for many programming languages “for free”. Currently Qt Creator supports code completion, highlighting of the symbol under cursor, and jumping to the symbol definition, as well as integrates diagnostics from the language server. Highlighting and indentation are still provided by our generic highlighter, since they are not provided via the language server protocol.

Read more

Also: Qt Creator 4.8 Rolls Into Beta With C++ Improvements, Language Server Protocol Support

Qt Company: Introducing the Distance Field Generator

  • Introducing the Distance Field Generator

    At least from the perspective of rendering, text is often the most complex part of a traditional two-dimensional user interface. In such an interface, the two main components are rectangular images and text. The rectangular images are often quite static, and can be represented by two triangles and four indexes into a texture atlas that is uploaded to graphics memory once and then retained. This is something that has low complexity and which the graphics hardware has been optimized to handle quickly.

    Text starts as a series of indexes into an international database of writing systems (Unicode). It is then, based on some selection algorithm, combined with one or more fonts, which is in principle a collection of shapes and some lookup tables and executable programs that convert said indexes into shapes and relative positions. These shapes, basically filled paths made out of bezier curves, then have to be rasterized at a specified size, and this can range from simple and neat outlines to complex ones with lots of detail. (By rasterization, I mean finding out how much of each target pixel, or subpixel in some cases, is covered by the shape.)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Audiocasts/Shows: Linux Action News, Problematic Privileges, Open Source Security Podcast and GNU World Order

  • Linux Action News 115

    We're pleasantly surprised by a new Linux distro, EvilGnome malware spies on Gnome Shell users, and more good news for MacBook Linux users. Plus why RetroArch coming to Steam is a bit controversial, ubuntu-wsl is a cold drink for Windows users, and gpodder needs a new maintainer.

  • Problematic Privileges | TechSNAP 407b

    Wes takes a quick look at a container escape proof-of-concept and reviews Docker security best practices.

  • Open Source Security Podcast: Episode 155 - Stealing cars and ransomware

    Josh and Kurt talk about a new way to steal cars because a service didn't do proper background checks. We also discuss how this relates to working with criminals, such as ransomware, and what it means for the future of the ransomware industry.

  • gnu World Order 13x30

KDE: Plasma Mobile at Plasma Sprint Valencia and GSoC Work

  • Plasma Mobile at Plasma Sprint Valencia

    In June month we gathered in Slimbook’s offices to work on Plasma. Along with Plasma developers, we were also joined by KDE Usability and Productivity team. During the sprint I mostly worked to create up-to-date image for Plasma Mobile, as from last few weeks Plasma Mobile image was quite out-of-date and needed update.

  • Somewhat Usable

    Adding a feature by yourself is a lot satisfying than requesting someone to add that for you, cause now you are both the producer and the consumer. But to be honest, I never thought I would be the one implementing the Magnetic Lasso for Krita when I requested it 4 years back, leave the fact that I even getting paid for doing so. So here are the first tests being done on it.

  • View and Examples

    This week I began learning about QML to try to fix the View that show the graphs and tools for manipulating graphs.

  • Month 2 in making the Titler – GSoC ’19

    From my understanding so far (forgive me for any mistakes that I might make – it’s a different codebase and different concepts – I wholeheartedly welcome corrections and suggestions) the whole producer boils down to two parts – the actual producer code (which is in C and which is the thing which does the ‘producer stuff’) and the wrapper code (which ‘wraps’, supplements and does the actual rendering part of the QML frames). The wrapper files are responsible for mainly rendering the QML templates that are passed to it and make it available for the actual producer to use. And consequently, most of the work is to be done in the wrapper files, as the producer in itself doesn’t change much as it will still do the same things like the existing XML producer (producer_kdenlivetitle.c) – such as loading a file, generating a frame, calling rendering methods from the wrapper files.

System administrator responsibilities: 9 critical tasks

System administrators are critical to the reliable and successful operation of an organization and its network operations center and data center. A sysadmin must have expertise with the system's underlying platform (i.e., Windows, Linux) as well as be familiar with multiple areas including networking, backup, data restoration, IT security, database operations, middleware basics, load balancing, and more. Sysadmin tasks are not limited to server management, maintenance, and repair, but also any functions that support a smoothly running production environment with minimal (or no) complaints from customers and end users. Although sysadmins have a seemingly endless list of responsibilities, some are more critical than others. If you work in a sysadmin role (or hope to one day), make sure you are ready to follow these best practices. Read more

Fedora, CNCF and IBM-Paid Puff Pieces

  • Changing how we work

    As those of you who read the https://communityblog.fedoraproject.org/state-of-the-community-platform-engineering-team/ blog know, we are looking at changing workflows and organization around in the Community Platform Engineering team (of which, I am a member). So, I thought I would share a few thoughts from my perspective and hopefully enlighten the community more on why we are changing things and what that might look like.

  • Kubernetes policy project takes enterprise IT by storm

    An open source compliance as code project has gained a groundswell of popularity over the last six months among enterprise IT pros, who say it simplifies and standardizes Kubernetes policy management. The Open Policy Agent (OPA), an open source compliance as code project founded by former VMware employees, was used at Netflix as early as 2017 and accepted into the Cloud Native Computing Foundation (CNCF) as a sandbox project in March 2018. Netflix gave an OPA demonstration at KubeCon in December 2017, and Intuit and Capital One followed at KubeCon in December 2018. After the project advanced to the CNCF's incubating stage in April 2019, and was demonstrated a third time at KubeCon EU in May 2019, it began to generate mainstream buzz. [...] As Kubernetes environments grow to encompass Istio service mesh and Knative event-based orchestration in what Google calls the open cloud stack, the fact that OPA lends itself to Kubernetes policy enforcement but can expand to include those adjacent utilities boosts its appeal.

  • The Who, What, Where, When, and Why for Mainframe Security [Ed: IBM pays Ponemon for puff pieces]

    For most people, security is a bit of a nuisance. No-one likes having to keep updating their password and then needing to remember the new one. And then there’s all the different passwords that need to be remembered for different things. It all just seems like an administrative nightmare. It just makes getting a day’s work done harder. That’s what most users think right up until the moment there’s a breach. And suddenly the mood has changed. Now everyone wants to know exactly what’s happened. They want to know who has done what, where they’ve done it, when it occurred, how they got in, and a million other questions. Your phone is ringing off the hook. Your e-mail is filling up faster than usual. What can you do? Where can you access the information you need? How do you respond to the incident?