Embracing stability and security of our projects

Our projects always show their high quality and stability, because they’re battle tested with different conditions under consideration. Our applications currently use our libraries as part of…

Aptivi

Why do some of our projects get more updates than others?

Our release cadence involves setting up a set of rules that every release of every project must follow. Nitrocid follows a ten-year release support window for long-term support releases, while short-term releases get 9 months of updates. So, the question here is why do some of our projects, such as Terminaux and Nitrocid, get more releases that focus on improvements and bug fixes than other projects, such as Textify and Magico?

Projects’ release cadence and methods vary from project to project, and goals are set for each project. Some of our projects require constant maintenance as part of following the best practices of testing our projects. Some projects, such as Terminaux, are more complex both in features and in source code, and require constant maintenance to give you the best experience possible, while others like Textify don’t require this much maintenance.

For example, Terminaux gets more and more updates as bugs are spotted and improvements are planned to ensure better application experience for everyone. As part of our commitment into high quality projects, just week, we’ve set a release cadence for future Terminaux releases as we have introduced long-term support versions as its API reached maturity thanks to the latest improvements done in both 7.0 and 8.0.

On the other hand, Textify, Nettify, and other libraries have already maintained static API and didn’t need as much maintenance. Last year, Textify received just fourteen releases to make mild modifications to the library according to the requirements of frequently-updated projects like Terminaux. Update frequency to such projects are often low, and updates are made based on what features are needed.

This is not only the factor that caused this update frequency variation, but project goals, scopes, features, and other factors have also affected the frequency for various projects.

Terminaux, given the goal of the project (which is to provide a console app framework for interactive textual user interface applications and advanced CLI applications), needs to be able to reliably provide various advanced console-related features, such as console resizing in TUIs, mouse support in TUIs, and true color console writing facility with more than 16 million colors (16,777,216 colors). Not only that, but Terminaux needs to be able to provide interactive CLI applications an ability to read a line with some of the advanced features, such as syntax highlighting (reminiscent to that of PowerShell), history system (similar to Bash and ZSH), positional reading for text boxes, and, most importantly, Chinese-Japanese-Korean (CJK) and Emoji support.

Nitrocid provides an operating system simulator, despite its branding as a kernel simulator, because it is a console application that provides simulated components, such as the kernel (when it comes to hardware recognition, booting up), the log-in system, and the shell. Because of its aim to be configurable and flexible, features like the configuration manager and the kernel driver manager were introduced to the simulated environment. Nitrocid, alone, relies on Terminaux and other dependencies to perform basic operations, and, without those dependencies, wouldn’t have been possible. Nitrocid started as a standalone application in 2018 before having some of its code branched out to new libraries, such as Textify and Terminaux.

However, projects like Textify only focus on one goal. For example, Textify focuses on providing text extensions, while also provides some of the addons, such as providing a set of words and names. This is very simple, predictable, and doesn’t require constant maintenance, but we run continuous tests from time to time, and release updates as necessary.

For this reason, you’ll see that some of our projects rely on frequent updates to integrate stability improvements and bug fixes, while others get their updates slowly and when required. Some of the major updates, especially those on Nitrocid, take multiple months to plan blueprints, add features, and fix bugs. Nitrocid 0.1.0 took more than 18 months to finally materialize, given that the release was a foundational release that went through 9 milestones, 3 betas, and a release candidate, because of how complex the plan was. Our mission was to get it out of the “alpha” stage that stayed for six years.

To summarize, complexity in frequently-updated projects often require updates to address issues that may have cropped up during our testing. Of course, user reports also help us in eliminating bugs in our projects.

#bassboom #news #nitrocid #Tech #Technology #terminaux #update

The new branding curtains will be opened any minute from now! Get ready for the new era of modern design!

#Aptivi #Nitrocid #Terminaux #BassBoom #Blogging #Branding #Website #Logos #Logo #TechNews #TechUpdates

Making native library builds more consistent with GitHub Actions

When we first started building C# libraries that relied on native libraries to do their function, we tried to make this goal stand still: maintaining cross platform support across all popular archi…

Aptivi

BassBoom v0.2.13 released with .NET 10 support!

We have released a hotfix version, BassBoom v0.2.13.1, to fix issues related to loading the mpg123 library on Windows systems.

We are so excited to announce the availability of BassBoom v0.2.13 for Windows, macOS, and Linux systems. This music player app has now become more fresh with the crucial upgrades that were needed for a long time, and we’ve made the music player more attractive, with the help of Terminaux 8.0.

This is going to be the last version of BassBoom v0.2.x before moving on to v1.0.0, with huge improvements that will be made to the music player. We will also focus on the Basolia library to make sure that it’s ready to be used with both the system wide mpg123 installation and the bundled mpg123 installation, and to make improvements to the internal structure to reduce errors and to introduce new features without any friction.

This version of BassBoom includes the following changes:

  • Updated mpg123 to 1.33.3: We have updated the native C library for the MPG123 library, which is already bundled with BassBoom.Native, to version 1.33.3 from the previous version, 1.32.9. We have also changed the way we build mpg123, and we have eliminated inconsistencies between libraries by moving the library build workflow to GitHub Actions for all supported platforms. Now, our method of building the MPG123 library is no longer “dirty.”
  • Updated Terminaux to 8.0: By updating Terminaux to version 8.0, we’ve enhanced the design of BassBoom by making it more attractive. We’ve also changed how we display the duration and the lyrics from the old design as a result of the progress bar style changing to make it more modern.
  • Updated .NET to 10.0: We have updated the .NET framework from 8.0 to 10.0 to benefit from improved performance resulting in changes made between 8.0 and 10.0. We are making sure that the music player stays fast, and we’ll use the latest version of both libraries and frameworks.

General improvements and bug fixes were also made, including changes to how we render the duration indicator and the lyrics (if the song has a valid srt file). We have also fixed disappearing elements in some situations, as well as the resize handler refreshing the screen properly, as needed.

You can get this version of BassBoom via this download link.

Download v0.2.13

You can also download BassBoom on Ubuntu systems with the official Launchpad PPA, and on Arch Linux systems using the AUR.

Photo by RDNE Stock project

#bassboom #C #dotnet #music #musicPlayer #news #Tech #Technology #update

BassBoom v0.2.13 released with .NET 10 support!

We are so excited to announce the availability of BassBoom v0.2.13 for Windows, macOS, and Linux systems. This music player app has now become more fresh with the crucial upgrades that were needed …

Aptivi
December 2025 – The Month of Excitement

After eleven months of continuous development and blogging for everything related to technology and Aptivi-related projects, such as Nitrocid, Terminaux, and others, we’re excited to announce…

Aptivi
Addressing plans for BassBoom and MediaBoom v1.0

Since BassBoom was released, it went through several iterations of improvements, including library updates and new features, such as the radio station playback support. Over time, we needed to exte…

Aptivi

Addressing plans for BassBoom and MediaBoom v1.0

Since BassBoom was released, it went through several iterations of improvements, including library updates and new features, such as the radio station playback support. Over time, we needed to extend support for more music extensions other than the MPEG ones, such as Advanced Audio Codec (AAC) files and wave files (WAV), so we were plotting a plan to create a separate experimental branch of BassBoom before we eventually called it MediaBoom, finally separated as a separate app.

The two versions, BassBoom v1.0 and MediaBoom v1.0, are currently being worked on as we focus on the more essential things to make sure that we provide you with the best BassBoom and MediaBoom releases. We will conduct thorough checks for every single line of code written in both projects. Currently, MediaBoom’s repository didn’t see any sign that the real development had started, beyond just experimental code that wrapped around libmpv.

Of course, all this planning and execution takes time, but when we take time, we do our due diligence to ensure that BassBoom v1.0 and MediaBoom v1.0 get released as soon as they’re ready.

Currently, there is no ETA as to when those two launches actually happen, but we will be more transparent about those two projects as soon as we start development on them.

Photo by Catherine Kalmykova on Unsplash

#Net #bassboom #C_ #csharp #dotnet #MediaBoom #news #Tech #Technology #update

Transparency in our projects has started

When we work in projects, we rely on our plans to make our projects go the way we expect them to be. Because of this, we underwent through several improvements, such as the build system improvement…

Aptivi