The documentation will be easier to navigate

The GitBook documentation for our projects will be easier to navigate than before. We have made earlier statements about how we’ll schedule changes made to the GitBook docs for all our projec…

Aptivi

Terminaux 8.1 is globally available!

Terminaux 8.0 was released last October to provide long term support releases for the first time in the lifetime of this library since the first version was released on August 2023. Since then, we have added more improvements and new features on top of this version to make it stronger!

Now, we are so excited to release this version of Terminaux, which is version 8.1! This version provides mouse improvements that were made in the selection-related TUIs and prompts, such as the selection infobox and the choice selector TUI. By binding double clicks for all items to act like the Enter key, you can now use your mouse to select a choice and perform the action based on it.

Terminaux 8.1 also provides more improvements, such as the preparation of the Color class for movement to Colorimetry library, which is already done there. The complete movement will be done in the next Terminaux 8.x release expected to release on March 19th. Also, we’ve done the migration of the calendar-related code to Calendrier, which is a bold move as we clean things up from old residual code that may not have received bug fixes.

This version also provides screen overlays, making a rather laborious task of having to maintain screen overlays easier by providing two types of overlays: global overlays, which get rendered regardless of the screen, and screen-specific overlays, which get rendered depending on the screen used. This is useful for gauges and other overlaid display. Also, we’ve have synchronized the list of terminal emulators and their Terminfo specifications with NCurses 6.6.

The upgrade path from 8.0 to 8.1 requires that you follow the list of breaking changes made in the GitBook documentation.

Terminaux 8.1 is now available for free on NuGet!

NuGet package Release page GitBook docs API Reference

#Net #C #Console #csharp #dotnet #news #Tech #Technology #terminal #terminaux #Terminaux8 #Terminaux81 #update

Terminaux 8.1 is now globally available!

Get ready for the biggest milestone on February 12th!

#Terminaux #csharp #programming #TechNews #TechUpdates #dotnet

https://officialaptivi.wordpress.com/2026/01/22/terminaux-8-1-is-globally-available/

Terminaux 8.1 is globally available!

Terminaux 8.0 was released last October to provide long term support releases for the first time in the lifetime of this library since the first version was released on August 2023. Since then, we …

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

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 shor…

Aptivi

Terminaux 8.1 will be released tomorrow at 9:00 AM GMT! Stay tuned for the latest updates of Nitrocid 0.2.0!

#Nitrocid #NitrocidKS #KernelSimulator #Terminaux #TechNews #TechUpdates #csharp #programming #dotnet

Terminaux 8.2 will include QR code renderer!

While implementing the two-factor authentication (2FA) feature on Nitrocid KS, we thought it would be wise to include a QR code setup so that people who are using their phones to authenticate to their Nitrocid user will be able to quickly add the authentication information for them to get the 6-digit code they need to enter to be able to log in. However, we were faced with an implementation challenge when it comes to actually printing the QR code. Do we print the QR code to the console? Or do we generate an image and open it using the image viewer found in a computer? The answer was the former.

We have chosen to print the QR code to the console, because we have several of the block characters that we can use to render a graphic, just like what we’re currently doing with the image renderer in Terminaux.Images. Using the QR code matrix map, why not use it to print it to the console, knowing that the size is not adjustable without data loss?

Terminaux 8.2 will include both the standard QR code renderer and the Micro QR code renderer using the simple renderer class. This simplification ensures that the QR code is printable to the console in both the CLI mode, which involves scrolling lines, and in TUI mode, which requires that the console window be larger than the QR code itself. Right now, the code sits in Nitrocid KS, with this commit adding the QR code renderer, which the 2FA feature uses.

While Terminaux 8.1 is yet to be released until tomorrow, we are looking forward to adding new interesting features to the library as we go on through the support cycle.

#news #Tech #Technology #terminaux #Terminaux80 #Terminaux82 #update

Terminaux 8.2 will include QR code renderer!

While implementing the two-factor authentication (2FA) feature on Nitrocid KS, we thought it would be wise to include a QR code setup so that people who are using their phones to authenticate to th…

Aptivi
Maintaining stable documentations for Terminaux point releases

We have earlier outlined our plan for Terminaux long-term support versions and the release cadence that we’ll be following beginning January 22nd of this year to integrate a small pool of new…

Aptivi

Maintaining stable documentations for Terminaux point releases

We have earlier outlined our plan for Terminaux long-term support versions and the release cadence that we’ll be following beginning January 22nd of this year to integrate a small pool of new features while providing bug fixes and general improvements, and, in some cases, breaking changes. However, the documentation of the library currently branches out only when a new major version of the library appears. As the former plan goes into effect on January 22nd, we’ll have problems maintaining stable docs for older point releases, as some of the point releases may either introduce breaking changes, behavioral changes, or new feature additions.

So, we’ve decided to solve this problem by introducing separate branches for the Terminaux docs. We’ll be using branches from a single Terminaux docs found in the stable docs organization to ensure that we don’t have to maintain the docs twice (one stable and one rolling) and to tag the older point release’s docs as “stable.”

The main rolling Terminaux documentation won’t be affected, but the stable docs entry will be made so that we can finally follow our plan. This means that Terminaux 8.1’s docs will be moved to the stable Terminaux docs repository in another organization, alongside Terminaux 8.0, before we start working on the docs for 8.2. This ensures easier checkout and contribution, while maintaining the docs for all branched releases. To simplify this, a new major release means a new stable docs repository, while a new point release means a new branch in the series’ docs repository.

We’ll start working on this as soon as possible after the release of Terminaux 8.1.

#news #Tech #Technology #terminaux #Terminaux81 #update