Language Selection

English French German Italian Portuguese Spanish

Login

Enter your Tux Machines username.
Enter the password that accompanies your username.

More in Tux Machines

Programming: GAction, Research on Developers, JavaBeans and Python

  • Sébastien Wilmet: Providing GActions in a library

    GAction represents an action that the user can do in an application, it’s usually present in a menu item or a button. It’s not just a function to launch, it’s a little more involved than that. Overall, providing GActions in a library can be done quite naturally, once the library provides a framework for the application. TeplApplication and TeplApplicationWindow both provide GActions in their public API. They are namespaced with the "tepl-" prefix, to avoid conflicts with other libraries or the application; so the full name of the GActions are "app.tepl-something" or "win.tepl-something". And all the GActions are documented in the class description. Note that TeplApplication and TeplApplicationWindow are not subclasses of GtkApplication and GtkApplicationWindow, because several libraries might want to extend those GTK classes and an application needs to be able to use all those extensions at the same time. A nice solution that doesn’t require to hold a new object in the application: use this design pattern that I’ve already described on my blog.

  • Research: Developers are trusted by the business but the alignment is not felt evenly across different generations

    Welcome to the first in a series of in-depth articles looking at the developer’s role in the modern organisation. In this first post: a new generation has arrived. As organisations shift to becoming technology-focused, developers’ roles have evolved so that they are now playing a crucial role in decision making across their businesses. However, all this newfound alignment isn’t so keenly felt across the whole developer workforce…

  • Jakarta EE: Creating an Enterprise JavaBeans timer

    Enterprise JavaBeans (EJB) has many interesting and useful features, some of which I will be highlighting in this and upcoming articles. In this article, I’ll show you how to create an EJB timer programmatically and with annotation. Let’s go! The EJB timer feature allows us to schedule tasks to be executed according a calendar configuration. It is very useful because we can execute scheduled tasks using the power of Jakarta context. When we run tasks based on a timer, we need to answer some questions about concurrency, which node the task was scheduled on (in case of an application in a cluster), what is the action if the task does not execute, and others. When we use the EJB timer we can delegate many of these concerns to Jakarta context and care more about business logic. It is interesting, isn’t it?

  • Python Dictionary Comprehension

    In this tutorial, we will learn about Python dictionary comprehension and how to use it with the help of examples.

Mozilla and Curl Leftovers

  • Ending QA community events, for now

    QMO events have been around for several years now, with many loyal Mozilla contributors engaged in various types of manual testing activities– some centered around verification of bug fixes, others on trying out exciting new features or significant changes made to the browser’s core ones. The feedback we received through them, during the Nightly and Beta phases, helped us ship polished products with each iteration, and it’s something that we’re very grateful for. We also feel that we could do more with the Testday and Bugday events. Their format has remained unchanged since we introduced them and the lack of a fresh new take on these events is now more noticeable than ever, as the overall interest in them has been dialing down for the past couple of years. We think it’s time to take a step back, review things and think about new ways to engage the community going forward.

  • Tips to improve your Ring camera security

    We cannot stress this enough. Weak and reused passwords are a serious vulnerability to your personal security and privacy. The software that the Nulled crew is using to tap into Ring feeds can be used to take over other things like, say, a Disney+ account. Or your bank account.

  • The Mozilla Blog: Petitioning for rehearing in Mozilla v. FCC

    Today, Mozilla continues the fight to preserve net neutrality protection as a fundamental digital right. Alongside other petitioners in our FCC challenge, Mozilla, Etsy, INCOMPAS, Vimeo and the Ad Hoc Telecom Users Committee filed a petition for rehearing and rehearing en banc in response to the D.C. Circuit decision upholding the FCC’s 2018 Order, which repealed safeguards for net neutrality. Our petition asks the original panel of judges or alternatively the full complement of D.C. Circuit judges to reconsider the decision both because it conflicts with D.C. Circuit or Supreme Court precedent and because it involves questions of exceptional importance.

  • Daniel Stenberg: Reporting documentation bugs in curl got easier

    After I watched a talk by Marcus Olsson about docs as code (at foss-sthlm on December 12 2019), I got inspired to provide links on the curl web site to make it easier for users to report bugs on documentation. Starting today, there are two new links on the top right side of all libcurl API function call documentation pages. File a bug about this page – takes the user directly to a new issue in the github issue tracker with the title filled in with the name of the function call, and the label preset to ‘documentation’. All there’s left is for the user to actually provide a description of the problem and pressing submit (and yeah, a github account is also required).

today's howtos

Fedora, Red Hat and IBM: Flatpak 1.5.2, Cockpit 209, OpenShift, Java and More

  • Flatpak 1.5.2 Continues Work On Authentication Support In Push To Handling Paid Apps

    Introduced last month was the Flatpak 1.5.1 development build that provided initial support for protected/authenticated downloads of Flatpaks as the fundamental infrastructure work towards allowing paid or donation-based applications within Flathub or other Flatpak-based "app stores" on Linux.  Flatpak 1.5.2 is out this Friday morning and it has continued work on this focus for authenticated/protected downloads. There has been new API coverage around the authentication code, an OCI authenticator is now bundled, a simple user/password authentication-driven option similar to HTTP-based authentication, and related work towards opening up new use-cases for Flatpak. 

  • Cockpit 209

    Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 209. A new design for the Overview page The landing page has been completely redesigned. Information is grouped into easier to understand panels, health information is much more prominent, the resource graphs have been moved to their own page, and the hardware information page should now be easier to find.

  • We’re headed for edge computing

    Every week seems to bring a new report on how edge computing is going to take over the world. This crescendo has been building for the past few years, so it’s no surprise that edge computing sits near the peak on the Gartner hype cycle for emerging technologies. But the question remains—will the edge computing phenomenon take over the world as predicted and, if so, how can businesses benefit from it? In this and future articles, we’ll demystify edge computing, examine its motivations, and explore best practices in creating scalable edge deployments and the role of open source at the edge. We’ll also look at 5G and its impact to the telco industry, remote office/branch office, IoT, and other use cases.

  • Persistent data implications for apps and microservices

    Speed and agility are the name of the game, whether you are running track in a triathlon, racing to find cures to the world’s most nefarious diseases, or developing new applications that are changing the way society interacts. Application development teams can have a profound effect, not only on their organizations’ ability to differentiate themselves, but also the world we live in. [...] While just a few years ago, some organizations were still concerned with the viability of running production workloads in containers, the benefits of capitalizing on faster development cycles has garnered favor among developers. And, with enterprise-class enhancements delivered by platforms such as Red Hat OpenShift Container Platform, containers have grown from nifty developer projects, to scalable, more manageable infrastructure environments that enable DevOps for the hybrid cloud.

  • Cloud Pak for Applications supports IBM Z

    The latest version of Cloud Pak for Applications, Version 4.0, extends support for Red Hat OpenShift Container Platform 4.2 onto the IBM Z platform. Now users can extend their hybrid cloud deployments to include Red Hat OpenShift clusters on IBM Z hardware, taking advantage of the container orchestration platform and tools to bring a consistent experience for development of cloud-native workloads. Support for OpenShift on IBM Z in this release of IBM Cloud Pak for Applications is limited to the container platform only. IBM runtimes continue to provide support for IBM Z, including container deployments where appropriate.

  • Exploring OpenShift 4.x Cluster

    In this video we will explore the cluster installed during the last video, log into the cluster, configure an authentication provider. We will understand the structure of the cluster and the architecture overview of HA installation. We will get deep understanding of what runs on the master node vs worker node, how the load balancers are setup. We will also look at the cloud provider to see all the infrastructure components that got created by the installer.

  • Celebrating 20 years of enterprise Java: Milestones

    As we celebrate the last 20 years of enterprise Java, it is important to look back at the platform's history to better understand where it came from and how we arrived where we are today. Enterprise Java emerged during a pivotal time in the history of enterprise computing. When Java 2 Platform, Enterprise Edition (J2EE) 1.2 was introduced in December 1999, it not only marked the birth of enterprise Java, but also signaled an important shift in how organizations were thinking about the web. Roughly five years earlier, in May 1995, the Java programming language had been publicly released. The language was originally developed to address obstacles faced by a stealth innovation team at Sun Microsystems building the Star7, an interactive handheld home entertainment controller; however, after a tepid response from the television industry, the team instead set its sights on the internet. Web browsers were making the web more accessible to users, and when the Java language was first announced by Sun, it came with a crucial endorsement: Netscape, one of the leaders in the nascent Web browser market at the time, announced in 1995 that it would include support for Java in its namesake browser.