OpenTabletDriver VS cyclonedx-maven-plugin

First follow the installation guide on https://opentabletdriver.net/

I don't have a huge amount of experience with Krita's Wayland performance because the situation on Wayland is still sub-optimal for art in general. Tablet support has gotten much better, but configuration per-app or tied to the desktop environment still seems to be a big issue. The idea that my tablet configuration might stop working if I switch off of a desktop environment is kind of a non-starter to me. It stinks because I really want to use Wayland, but even as recently as a month ago I tried to see if I could make the switch and couldn't.

Truthfully, if someone has a lot of money to dump around, devoting a few full-time developers or dropping cash on https://github.com/OpenTabletDriver/OpenTabletDriver would probably go a long way towards encouraging Wayland adoption from artists.

As far as I can tell the issue is not that Wayland can't do tablet control on the same level as X11, it's that the tools built around those capabilities still seem immature. OpenTabletDriver looks very promising but seems to have limited device support, limited in no small part by what tablets the devs have access to (my Cintiq 32 is unlikely to get added any time soon because it is no longer being sold and was expensive and uncommon when it was on the market).

The NVIDIA situation is also a problem, but there's nothing anyone can do about that other than yell at NVIDIA more.

----

> The text tool is a joke.

The text tool should see considerable improvement soon; the entire text engine got rewritten in the last release, the devs just only had time to get it to feature parity with the existing tools.

I believe Wacom is a first class citizen in Linux. They have it in the kernel (https://linuxwacom.github.io/). There is also https://opentabletdriver.net/ that is multi-platform.

If the Wacom driver is no longer compatible with your system, you might want to consider using a third party driver like OTD (https://opentabletdriver.net/)

Use OpenTabletDriver, you might have better luck.

One of these programs is called OpenTabletDriver and can be found here

You might give OpenTabletDriver a try, it seems like it supports that particular tablet according to their list of supported tablets.

- DIGImend and OpenTabletDriver look pretty similar in github activity(?)

You can try OpenTabletDriver, a 3rd party open source tablet driver, with support for your tablet. It has many different smoothing algoritms and filters and much more customisability than Wacom drivers, as well as pressure support.

The CD is for driver installation, however you don't need it. Drivers used to come on CDs. For Linux, you have two options, both third party: OpenTabletDriver or linuxwacom. For Windows, you might be able to find an older driver version in the archives on Wacom's website, since newer drivers dropped support for it (thanks, Wacom) or you can once again use OpenTabletDriver. Personally, I recommend using OpenTabletDriver for both operating systems. It's much more customisable, gives you higher hover height, allows for more pen compatibility and more.

As others have already commented:

The US government has added SBOMs to a proposed rule to update the Federal Acquisition Regulation. So if you want to sell to the US Government you'll have to provide SBOMs: https://www.federalregister.gov/documents/2023/10/03/2023-21...

Lots of large companies require SBOMs from their supplier.

In the EU we will get the Cyber Resilience Act which will make them mandatory as well in certain cases: https://data.consilium.europa.eu/doc/document/ST-12536-2023-...

And yes, there's bascially two technical standards to provide them: SPDX and CycloneDX: https://cyclonedx.org/

Usually there is a requirement through a risk in the risk register, new project etc. appsec engineers perform an analysis of what is available in the market paid and/or open source and match it against the list of requirements and come up with an proposal to be signed off by relevant stakeholders. Usually (there may be exceptions) security engineers take care of the implementation. Which snyk product are talking about? SCA? If so have a look in https://cyclonedx.org/ open source or jfrog (paid) but it will depend much on your current processes mainly around CI/CD tools

We use https://cyclonedx.org/ to auto generate them.

The recent govulncheck effort made me think of the possibility of having the go tool create an SBOM (Software Bill of Materials) in a standard format like CycloneDX that could be consumed by existing tools like DependencyTrack. Somewhat similar to the recent docker sbom feature.

Alternative it would be nice, if there is way to get an SBOM (Software Bill of Materials). Microsoft created an Open Source Tool to get an SBOM for many programming languages, but pascal is not one of this. With a SBOM file, it should be possible to run it against a tool like CycloneDX.

A Software-Bill-of-Materials (SBOM) lists all the software components included in an image. Buildpacks support SBOMs in CycloneDX, Syft and SPDX formats.

CycloneDX is OWASP's lightweight SBOM standard for application security and software composite analysis. It comes with multiple tools for all environments. Its maven plugin generates SBOM featuring all types of dependencies in your projects.

There is a CylconeDX plugin available on Maven central and Github that appears to be well-maintained and commonly used.

This sample project is using Maven build system for generating artifacts. cyclonedx-maven-plugin is used for generating CycloneDX SBom file.