FLOSS Project Planets

Andrew Cater: BBQ Cambridge 2017 - post 3

Planet Debian - Sun, 2017-08-27 07:24
One set of gazebos put up: kilos of mushrooms eaten, bacon, mushrooms and all the trimmings barbequed and consumed by the hordes. Now laptops are sprouting in the garden under the gazebos as the temperature is soaring,

Some folk are quiet in the house under fans typing and cooling off.

Masses of washing up is being done - as ever, it's how many people you can fit into a kitchen.

Now it will all go quiet for a bit as everyone lets the breakfast go down :)

Superb hospitality - we're _SO_ lucky to have Steve and Jo do this so readily.
Categories: FLOSS Project Planets

Hideki Yamane: Let's send patches to debian-policy (rst file is your friend :-)

Planet Debian - Sun, 2017-08-27 06:26
As I posted before, now debian-policy package uses Sphinx. It means, you can edit and send patches for Debian Policy easier than ever. Get source (install devscripts package and exec 'debcheck debian-policy')  and dig into policy directory. There are several rst files for each chapter.

Open it with your favorite editor and edit (Perhaps most of editors support reStructuredText, and if not, check its extension).

rst file is more friendly than old policy.xml file :-)

Then, commit and create patches with 'git format-patch'. Not much complicated, right?
Categories: FLOSS Project Planets

GSoC – Port of R to QProcess

Planet KDE - Sun, 2017-08-27 06:23

Hello, this post will be about what all targets I completed , what’s left and what I did during the last month.

During the first two months I had ported 2 back ends to QProcess, which includes Lua and Qalculate. For the last month I was left with 2 more backends , which were  R and Python .  Due to time constraint I decided that I will be working on just one of the two. Python’s code base was a bit large because of the two versions of Python(2.7 and 3), hence I decided to work on R.

Cantor’s R backend was broken, so my job to was to get it in a working state and make use of QProcess for all the communication.

R’s backend architecture was a bit different from the rest of the backends. It was divided into 2 parts

1.  RServer:
This is a separate application, that uses the R-API to run commands,
and exposes it’s functionality over DBUS

2. R backend
This implements the Cantor interfaces, and starts the RServer. It delivers
the commands to the server over DBUS, and connects to it’s signals to get
the result.

Due to such an architecture the code of R backend was quite complicated. To remove such complications we used R’s command line interface and made use of QProcess to connect to it. Instead of the multi step communication(rbackend->rserver->R API), we now have a simple one step communication(Rbackend->QProcess).

Previously R back end supported:
* Plotting graphs
* Tab completion
* Syntax completion(incomplete state)

Current Status:
* User can still plot graphs but the graphs are not integrated in the worksheet

* Tab completion- Not working. This used to make use of Rserver for getting the completions, but since we have disabled the Rserver tab completion is not working.

* Syntax higlighter – Same state as before. It just highlights the keywords(if,else etc) and not the built-in functions/variables of R

Overall, R back end is in a better state than before. We have more or less most of the functionalities working. The only thing that’s not working is tab completion. Hopefully in future we will able to make use of  R’s command line interface for tab completion. R back end also does not have support for variable management but it should ideally support this since R(language)  supports it.

With this most of what I planned to do during GSoC has been completed and the only back end left to be ported is Python’s.

The last 3 months have been great and a bit hectic for me, but nonetheless I enjoyed working on the  project. I plan to keep working on my project, complete what’s left and continue contributing to KDE.

I want to thank my mentor Filipe Saraiva  for being such a cool mentor that he is and for all the support he provided during the last three months

Lastly I want to thank KDE for giving me and others this opportunity.

Thanks and Happy Hacking


Categories: FLOSS Project Planets

Andrew Cater: BBQ Cambridge 2017 - post 2

Planet Debian - Sun, 2017-08-27 05:50
We were all up until about 0100 :) House full of folk talking about all sorts, a game of Mao. Garden full of people clustered round the barbeque or sitting chatting - I had a long chat about Debian, what it means and how it's often an easier world to deal with and move in than the world of work, office politics or whatever - being here is being at home.

Arguments in the kitchen over how far coffee "just happens" with the magic bean to cup machine, some folk are in the garden preparing for breakfast at noon.

I missed the significance of this week's  date - the 26th anniversary of Linus' original announcement of Linux in 1991 fell on Friday. Probably the first user of Linux who installed it from scratch was Lars Wirzenius - who was here yesterday.

Debian's 24th birthday  was just about ten days ago on 16th August, making it the second oldest distribution and I reckon I've been using it for twenty one of those years - I wouldn't change it for the world.
Categories: FLOSS Project Planets

GSoC- Port of Lua to QProcess

Planet KDE - Sun, 2017-08-27 05:26

Hi, it has been a bit long since I last wrote a blog about the status of my GSoC project. This has been majorly because I got a job and it has kept me busy ever since. Anyway, I managed to complete my second month target , mostly by working on weekends. Here’s a quick update on what I did during the 2nd month

I worked on porting Lua backend to QProcess. Lua backend was dependent on Lua’s C api for all the communication. By default Lua had spport for:
* Syntax highlighting
* Tab completion

Lua backend now makes use of Lua’s command line interface, which we connect to using QProcess. Most of the mathematical functionalities of Lua are offered through the math library. Here are some screen shots showing the output to different commands

Usage of math library


String manipulation/Os functionalities/arrays 


Current Design of Lua

* we make use of Lua’s command line interface for all the mathematical calculations or any other functionality offered by Lua’s  CLI

* Tab completion is still dependent on Lua’s C API. This should eventually be ported to make use of the command line interface as well.

All of the functionalities offered by Lua have been ported safely and nothing has been broken. As of now Lua does not have support for Variable management. I would love to work on it in future.

That’s it for this blog.

Happy hacking


Categories: FLOSS Project Planets

Django Weekly: DjangoWeekly 53 - Celery Workflow, Transaction Hooks, Django Rest API

Planet Python - Sun, 2017-08-27 03:00
Worthy Read
Factory Boy can help you during testing Django AppsWith Django Factory Boy I can create a shadow object during the testing phase without needing to create objects from the queryset that make it so simple.
How to Setup Amazon S3 in a Django ProjectIn this tutorial you will learn how to use the Amazon S3 service to handle static assets and the user uploaded files, that is, the media assets.
Embed docs directly on your website with a few lines of code.eSignature API Integration. HelloSign eSign API. Test the API for free.
Posting JSON data to the Django REST Framework with AJAXThis article will explore the challenges I faced recently while trying to make POST requests with JSON data to the Django REST Framework using jQuery’s AJAX function. After tracing down all of the error messages into the documentation for Django, Django REST Framework, jQuery and JavaScript and many Stack Overflow questions, I was finally able to see my “It worked!” alert pop up from the success callback.
ajax, jquery
Django, GraphQL & React - part 2Setting up GraphQL with Django.
How to Install Jupyter Notebook in a Dockerized Django ProjectHaving shell with full access to the project files and database is crucial to its development and testing.
Django-Axes tool review and project detailsDjango-axes is a reusable app for Django to limit the brute force login attempts for your web application.
Executing time-consuming tasks asynchronously with Django and Celerycelery
How Uploadcare Built a Stack That Handles 350M File APIscalability

django-sspanel - 50 Stars, 33 Fork
django-docker-template - 11 Stars, 3 ForkA Django project template for a RESTful Application using Docker.
django_rest_example - 3 Stars, 0 ForkDjango/DRF rest application example.
django_graphql - 2 Stars, 0 ForkDjango/GraphQL api
django-aws-xray: - 0 Stars, 0 ForkUnofficial Django app for AWS X-Ray. The AWS X-Ray daemon is a software application that listens for traffic on UDP port 2000, gathers raw segment data, and relays it to the AWS X-Ray API. The daemon works in conjunction with the AWS X-Ray SDKs and must be running so that data sent by the SDKs can reach the X-Ray service.
Categories: FLOSS Project Planets

[UPDATE] Warning: NVIDIA driver 384.69 seems to be broken with QtQuick

Planet KDE - Sun, 2017-08-27 02:31

Just a short warning to KDE Plasma users with NVIDIA drivers. Lately we have seen many crash reports from NVIDIA users who updated to version 384.xx. Affected is at least KWin and KScreenLocker, which means one cannot unlock the session any more. The crash happens in the NVIDIA driver triggered from somewhere in QtQuick, so completely outside of our code. A typical backtrace looks like that:

#0 0x00007fffdedffc02 in ?? () from /usr/lib/nvidia-384/libnvidia-glcore.so.384.69 #1 0x00007fffdf0ca9ba in ?? () from /usr/lib/nvidia-384/libnvidia-glcore.so.384.69 #2 0x00007fffdef953da in ?? () from /usr/lib/nvidia-384/libnvidia-glcore.so.384.69 #3 0x00007fffdefab2d4 in ?? () from /usr/lib/nvidia-384/libnvidia-glcore.so.384.69 #4 0x00007fffdef99bce in ?? () from /usr/lib/nvidia-384/libnvidia-glcore.so.384.69 #5 0x00007ffff5f0b681 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x00007ffff5f0bf8d in QSGBatchRenderer::Renderer::renderBatches() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x00007ffff5f11909 in QSGBatchRenderer::Renderer::render() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x00007ffff5f0209f in QSGRenderer::renderScene(QSGBindable const&) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x00007ffff5f0257b in QSGRenderer::renderScene(unsigned int) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x00007ffff5f3dd2e in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x00007ffff5f97b04 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x00007ffff5f4715e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x00007ffff5f4b8dc in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x00007ffff4e28989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007ffff39966ba in start_thread (arg=0x7fffd4d5a700) at pthread_create.c:333 #16 0x00007ffff47353dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

I would recommend to not update to that driver and if you are affected to downgrade again.


Together with NVIDIA we figured out the root problem causing the crash. The sandbox of the lockscreen introduced in Plasma 5.10 is too restrictive for the NVIDIA driver. We have now worked around the issue by removing parts of the sandbox when running on NVIDIA and released a Plasma release. This should be shipped to distributions shortly. We will look into a way to make the sandbox work again also for NVIDIA users with Plasma 5.11.

Categories: FLOSS Project Planets

Codementor: Building a desktop notification tool using python

Planet Python - Sun, 2017-08-27 02:02
A simple post on how to build desktop notifiers using python.
Categories: FLOSS Project Planets

Python Data: Forecasting Time Series data with Prophet – Jupyter Notebook

Planet Python - Sat, 2017-08-26 20:01

In previous posts, I described how I use Prophet to forecast time series data.  There were some questions in the comments about the code not working, so I wanted to publish a new post with a link to a Jupyter Notebook that will hopefully provide a full, correct working example.

The original posts are:

The Jupyter notebook can be found here:


The post Forecasting Time Series data with Prophet – Jupyter Notebook appeared first on Python Data.

Categories: FLOSS Project Planets

Python Insider: Python 2.7.14 release candidate 1 available

Planet Python - Sat, 2017-08-26 18:41
The first release candidate for Python 2.7.14 is now available for download. A final release is expected in 3 weeks.
Categories: FLOSS Project Planets

Zato Blog: Zato 2.0.8 released

Planet Python - Sat, 2017-08-26 17:00

Zato 2.0.8 has just been released - check here for installation instructions under Ubuntu, RHEL/CentOS, Debian, Docker and more.

This is primarily a regular patch release that closes GitHub tickets opened since 2.0.7 was published.

But there is more - several performance improvements have been backported from the upcoming 3.0 release and now your API servers will be up to 30% faster merely by upgrading from 2.0.7 to 2.0.8.

Zato is an open-source Python-based integration platform for ESB, SOA, REST, APIs and Cloud Integrations. Zato focuses on APIs, middleware and backend systems exclusively.

If you're thinking of building distributed systems with Python and need to handle business scenarios or processes of any complexity, from simple to large, Zato is the platform to choose.

Here are some screenshots to whet your appetite - head over to the documentation index for more!

Categories: FLOSS Project Planets

Last week in Kube

Planet KDE - Sat, 2017-08-26 14:14

“Kube is a modern communication and collaboration client built with QtQuick on top of a high performance, low resource usage core. It provides online and offline access to all your mail, contacts, calendars, notes, todo’s and more. With a strong focus on usability, the team works with designers and UX experts from the ground up, to build a product that is not only visually appealing but also a joy to use.”

For more info, head over to: kube.kde.org

  • WebEngineProfile no longer blocks kube on exit. It looks like some webengine code ends up in a deadlock when installing a QWebEngineUrlRequestInterceptoron the default profile from the main thread. It was solved by creating a custom WebEngineProfile as custom QML element.
  • Fixed scrolling issue where a slow loading mail would result in the positioning code interfering with user scrolling. This fixes email positioning in the conversation view.
  • Made scrollbars always visible. This is to help people that use the mouse to grab the scrollbar handle for scrolling.
  • Fixed some account config corner cases and improved user feedback when saving changes.
  • Large CMake cleanup to remove duplication and to clarify what settings we set.
  • Made sure all tests pass again, cleaned up testsuite.
  • Fixed encoding issue when replying to mail that would mangle some utf-8 chars.
  • Fixed font sizes so the same size is applied throughout the application. This resolves some scaling issues we had on some devices.
  • Changed connected/disconnected detection so resources that have no known status yet turn up as disconnected.

Kube Commits, Sink Commits

Previous updates

The 0.4 release seems within reach now =)

Categories: FLOSS Project Planets

PKI is needed for micro-services

Planet KDE - Sat, 2017-08-26 11:30


Today I want to explain why I think that for a proper micro-service software a PKI is needed.

First the problem: when you have a network application you need a way to authenticate one service to another and verify a service to another.

One way to do this is with usernames and passwords or tokens. This solution works well but there is an issue about where to store the secret data, how to deploy the secret data to all nodes in a secure way and how to revoke access to only one node.

When you are using only usernames/passwords or tokens, it is kind of a mess and you have to write everything to a config file. Revocation is not easy and needs good orchestration to avoid downtime.

PKI is a strong and standard way to have mutual authentication between two endpoints.

Managing a CA is not an easy task but the effort pays off if you care about security and you want to avoid a big spaghetti-style security approach.

Someone would say: but we can trust the source IP!
The short answer to this is: no.

The long answer is: no! no! no! no! no! no! no! no! no!

An IP address is not secure by design, the network can be manipulated quite easily with an L2 access (like one server compromised).

Also, the IP layer is not encrypted by default, so if you have to use some kind of encryption on top in your application, what’s the point of encrypting everything with a pre shared key when you can use an asymmetric layout?

I hope I’ve made my point and that you will use PKI for your next micro-service application.


Categories: FLOSS Project Planets

Andrew Cater: OMGWTFBBQ Cambridge 2017

Planet Debian - Sat, 2017-08-26 10:16
Funny this - I only blog when I'm in Cambridge :) I'm sure there's a blog back in the day from a BBQ a good few years ago. This is almost deja vu - a room full of Debian types - the crazy family - Thinkpads on a lot of laps and lots of chat around the room.

Colin showing round an amateur radio project in a tobacco tin, coding happening at the back of the room. Pepper the dog sitting on my foot - everything pretty well normal.
Categories: FLOSS Project Planets

My experiences with Summer of Code 2017

Planet KDE - Sat, 2017-08-26 10:08

How quickly the summer ran away, in a wild mix of fun, frustration, development, and success! It seems like just yesterday that I received news of working with Marble in the summer, yet now September quickly approaches, and it’s time to look back on all our experiences this summer.This year hasn’t been my first foray into contributing open-source projects, I’ve had the pleasure of working with Marble under last year as well. However this year has come with it’s own set of challenges and I’m proud to have taken part in such a great experience, built up by fantastic mentors and a lovely community who helped me along the way. But let’s get to the recap, this year's tale, from beginning to end, how the summer went!This years project was focused on Marbles Android version, Marble Maps, and my task was redesigning the UI, adding features and making sure it's all up to Material Design standards! The summer began with my work on Marbles historical map viewing app, Behaim Globe. 
The original Behaim Globe app featuring bottom tab bar navigation.
The redesigned Behaim app features a Kirigami based sidebar for settings, and separate drawers for the information menus.As readers may know redesigning that using the Kirigami framework was one of my firstly tasks, introducing me to the challenges I had to be aware of. It also taught me valuable lessons on communication with mentors, as ironing out each change was a great example of how to handle discuss required changes well. In the end we’ve a new and redesigned Behaim Globe for our efforts, and a great platform to browse historical maps! 
A view of Ghillany (1853) map variant inside the redesigned Behaim app.As readers may know, one of the first design decisions that involved Marble Maps was the decisions to use the Kirigami framework in our app. Kirigami is a QtQuick based components set, that offers a wide-variety of components and solutions to your user-interface needs. Through the summer I used Kirigami to aid in redesigning Marble Maps, simplifying my tasks of redesigning the different drawers and menus to fit Material Design standards. My summer tasks were a long list of changes to the Marble Maps app, that slowly added up to the current state. Below I will present a series of comparisons of the original and of the new version, that evolved, explaining the different changes and features on each image.
The original to the left, and the redesigned app on the right; the overall layout changes.
The sidebar was deemed an important area to update. It went through several stages, the current one using a Kirigami Global Drawer component as it’s base. The theming also took an update to match Material standards more.
The Placemark and Routing information panel was also redesigned, using a bottom menu bar that features context-sensitive buttons. Beforehand the bottom circular button was responsible for “Adding to Route”.
The “Part of Routes” menu was also changed to fit Material standards, and now can be closed with a gesture, or tapping outside it’s container, instead of using the hard to tap “OK” button.
Phone numbers OSM tags are now supported, and can be called from the app.
The original About menu got replaced with a separate page containing all the About information.
Layer Options were previously difficult to find, as opening them required tapping specifically on the icon of Public Transportation and Outdoor Activities in the sidebar. They were moved to a new page dedicated to them, which can, like all other page-based menus, be closed by pressing the back button.
Bookmark management has also been added, with gesture based controls. Swiping is now supported and it now removes bookmarks.
In closingThis year's Summer of Code was an invaluable experience to me. I am honestly grateful for the opportunity to work in this environment, learn about open-source development and be led all the way by such inspirational people. First hand experience with current practices and insight into the workings of projects of this scale is something people rarely get to experience before entering the workforce, but is something that will be a great part of our skill set. It’s been a great adventure and a fantastic learning opportunity, which I am very thankful for and hope I can take part in again!I wish you great fun on your contributions to open-source!Happy browsing both historical maps, and current ones!And again, thanks for reading!

Categories: FLOSS Project Planets

The enclosure post

Planet KDE - Sat, 2017-08-26 08:04

I would like a enclosure for my printer for a couple of reasons. I Print In ABS a lot and I would like to negate effects of the enviroment on my prints. I looked around a lot to see what others have done and many people use Ikea’s Lack table to create an enclosure. They are inexpensive and work well for making a box frame. I must have looked at 3 dozen different enclousers and one printer all made from these tables while looking around for what I wanted. The one that came closest to what I wanted to do was this one https://www.thingiverse.com/thing:1685857. I was planning to make real plans and a full tutorial for what I was about to make but one day my friend dave was over we decided to just build it we went to the local hardware place and got some MDF and a plastic panel for the door, some metal hinges and 90deg brackets. Unfortuantely my printer is too tall to fit inside with the tables just stacked on top of each other. I was going to print something to extend the tableleg but since I had found enough wood to make four legs I made legs at 19″. The legs were very carefully drilled out in center and the Ikea provided double screw could then be used to secure it to the table just like the lacks real legs.

The first leg

Next the walls were mesured, cut and screwed onto the outside. I want to keep the build as modular as possible this way the panels can come off if needed.

Painted and ready.

 Every thing was painted a flat black and after drying it was time to start assembling the enclosure.  I first put the lack table down and placed the printer on top of it and cut a small slot for the cabling to sit between the top table and the bottom one. Since the cabling was now recessed enough to place the top on I installed the 3d printer and secured the control box to the bottom of the lower table. Some of the final things like the hole for the filiment feed had to be done after the printer was installed so I could see where things lined up. Then a hole was drilled and a filiment guide installed and finally the top table attached to the bottom one.

It was then time to work on making a the door assembly.Cuttng the  plastic is difficult and I would recommend not only having the proper tool but also someone to help you keep it from moving as you score it.(thanks again dave)  Drilling thru the plastic very carefully we made holes for the hinges, door latch and handle in the plastic. Put it all together and its looks and works pretty good.

There are some things planned for the future on this such as getting my lighting properly wired into the control box for power instead of on a seperate power source. An Exhaust is needed still and there are currently no cameras in this enclosure. I need to re install my extruder cam as well as a PI  (w/camera) for enclosure control. For this I plan to make a fake walls on the sides and hide all the electronics and filters in that space . i will have a 1x24x24 space on each side to hide this all . This will help to keep the clean look it currently has with little change to the inside.

Categories: FLOSS Project Planets

Angle and Windows Ink – a new test version of Krita for Windows

Planet KDE - Sat, 2017-08-26 04:34

We’ve created a special version of Krita 4.0 pre-alpha for Windows users to test. This version contains two big new features that should solve the biggest problems Krita has on the Windows platform:

  • Support for ANGLE. This is really technical, but basically, ANGLE is a technology that presents an OpenGL API but lets Direct3D do the work. On Windows, many OpenGL drivers are very buggy, and that could lead to crashes, black or blank screens. It’s the most-hated issue we have, and it is not even a bug in Krita! If you’re a Windows user and had to disable OpenGL in the Configure Krita dialog, then you should test this build!
  • Support for Windows Ink/Windows 8 Pointer Events. That’s to say, native support for the n-trig pen technology in Microsoft’s Surface line of products — also used by Asus, Dell and HP in their convertibles that can use a pen.

Note: that this is a build from our development branch. It has got all kinds of nifty, but highly unstable features, like scripting, saving in the background, svg graphics… If you load a Krita 3.x file with vector layers and save it with this version of Krita, you will NOT be able to open it in your regular, stable Krita. This build is purely experimental! Do NOT use it for real work. DO help us with testing!

Test Instructions for Angle
  • Open the survey in your browser: https://goo.gl/forms/vYxPMbqGyVhPCc2q2
  • Download the test build and debug symbols
  • Open the first zipfile in Windows Explorer, and drag the krita_4.0-prealpha_angle_ink-1-x64 folder to your desktop
  • Open the second zipfile in Windows Explorer and drag the bin, lib and share folders into the krita_4.0-prealpha_angle_ink-1-x64 folder on your desktop.
  • With Windows Explorer, navigate into the krita_4.0-prealpha_angle_ink-1-x64 folder on your desktop
  • Start Krita by double-clicking on the krita link or on the bin\krita.exe file
  • You will now be given a choice:
  • Please first choose Test Desktop OpenGL. Create a new image and try to draw for a bit. Fill in the results in the survey: whether you experienced a crash or not.
  • Next, restart Krita and choose Test ANGLE. Create a new image and draw for a bit. Fill in the results in the survey.

NOTE: You won’t be able to enable/disable OpenGL/Angle in Krita’s Settings/Configure Krita/Display settings dialog; it will be forced enabled for this test.

Test Instructions for Windows Ink/Windows Pointer API

This is only relevant for Windows 8 and 10: Windows 7 does not support this API (and Krita does not support Windows 95, 98, XP or Vista). You should be using a Surface Pro with a pen or another convertible that uses Microsoft’s n-trig pen technology. It does not matter whether you have the wintab driver installed.

  • Open the survey in your browser: https://goo.gl/forms/N5Exyx8aKSOeAUmu2
  • If you haven’t performed the previous test for Angle, download the test build and debug symbols
  • Open the first zipfile in Windows Explorer, and drag the krita_4.0-prealpha_angle_ink-1-x64 folder to your desktop
  • Open the second zipfile in Windows Explorer and drag the bin, lib and share folders into the krita_4.0-prealpha_angle_ink-1-x64 folder on your desktop.
  • With Windows Explorer, navigate into the krita_4.0-prealpha_angle_ink-1-x64 folder on your desktop
  • Start Krita by double-clicking on the krita link or on the bin\krita.exe file
  • Press either Test Desktop OpenGL or Test ANGLE when you see the dialog discussed above: this does not matter
  • Go to Settings/Configure Krita/Tablet and check the experimental pointer api/windows ink support checkbox:
  • Close Krita and start Krita again
  • Create a new document and draw with the default brush. Check whether pressure gives a variation in size and opacity. Note your findings in the survey: https://goo.gl/forms/5TSCWNZvvjN5SVoq1

Thanks for helping to test this important new features.

Categories: FLOSS Project Planets

Final Blog Gsoc 2017

Planet KDE - Sat, 2017-08-26 02:00

Hello, this is the final GSOC blog. Over the past three months, I’ve been working on a telemetry project for the graphic editor Krita. I achieved almost all the goals. A working prototype was created, you can help in its testing by downloading a test version of the Krita with...

Categories: FLOSS Project Planets

Chapter Three: How to Alter Entity Autocomplete Results in Drupal 8

Planet Drupal - Fri, 2017-08-25 23:38

Sometimes you might want to display additional data in the autocomplete results, for instance add content language next to the title, or display entity type or any other related data. In this blog post I will demonstrate how to alter suggestions in autocomplete fields in Drupal 8. The project is available for download from github, see the link at the bottom of the page.

Here is the module structure I will be using:

Categories: FLOSS Project Planets
Syndicate content