{ "version": "https://jsonfeed.org/version/1", "title": "EXTechs OSS Blog", "home_page_url": "https://your-docusaurus-site.example.com/blog", "description": "EXTechs OSS Blog", "items": [ { "id": "https://your-docusaurus-site.example.com/blog/2026-08-13-bahfo_blog_1", "content_html": "

On our main goal of making user experience inside DreamStudio the best. Threaded design is always a pattern to consider. Especially when dealing with large codebases. In this blog, we explain how Ironica. The DreamStudio code editor. Is now threaded, which is a feature to expect in next major update.

\n
\n

Threaded Design Implementation​

\n

The main idea of threaded design in Ironica is to move analysis off the main thread. That helps in faster typing, less UI freezing, and less blocking on the main thread. Especially when it comes to large files with thousands of files. DreamStudio does not lack the ability to handle large codebases since it is powered by a powerful engine. However, analysis features require careful threading implementation for better experience.

\n

How it is Implemented​

\n

The threaded design is language agnostic. Doesn't rely on a language plugin or how fast its analysis speed is. When a feature is requested from the main code editor API, like folding, syntax highlighting, etc. The engine creates a separated thread, and moves computation there, this ensures that users are free to type without lagging or freezing UI.

\n

Problems and Fixes​

\n

even with analysis threaded, IronicaLexer.styleText — which QScintilla calls synchronously on the UI thread for every keystroke — copied the whole document and rebuilt the bracket-depth stack from byte 0 each time. On a 467KB file that was 77ms per keystroke (63ms was the O(cursor-position) rescan).

\n
The fix is by applying the following​
\n
    \n
  1. Bracket-depth cache: styleText now caches [position, depth_stack]. Since Scintilla restyles from the edit point, normal typing re-scans only the small segment between the cache and the new start instead of the whole prefix. Edits before the cache point correctly fall back to a full rebuild.
    2. \n
  2. Regex-based scan: replaced the per-char Python loop with a C-compiled _BRACKET_REGEX over bracket characters only (~6× faster, identical output).
    3. \n
\n

Releasing​

\n

The new threaded design is going to be release with the next major studio update. Soon.

", "url": "https://your-docusaurus-site.example.com/blog/2026-08-13-bahfo_blog_1", "title": "Threaded DreamStudio Design", "summary": "On our main goal of making user experience inside DreamStudio the best. Threaded design is always a pattern to consider. Especially when dealing with large codebases. In this blog, we explain how Ironica. The DreamStudio code editor. Is now threaded, which is a feature to expect in next major update.", "date_modified": "2026-08-13T00:00:00.000Z", "author": { "name": "Bahaa Nofal" }, "tags": [ "updates", "news" ] }, { "id": "https://your-docusaurus-site.example.com/blog/2026-08-05-bahfo_blog_1", "content_html": "

Our latest experiments with the B-Sharp Programming Language are over. We are announcing now moving to next step of the development: Features implementation. In this blog, we talk more about how B-Sharp is going to be shaped in the future. What we are trying to implement and our goals of development.

\n
\n

B-Sharp: Familiarity and Differences​

\n

There are many reasons why B-Sharp exists in the first place. It goes back to six months from now when we needed a Terminal User Interface (TUI) that is easy to use, fast, rich in features, but isn't steepy to learn and master. Unfortunately for us, Python did not serve good here. We tried to use Prompt Toolkit in addition to rich (which are both Python TUI modules) but that failed. Other languages have good options like Rust does or Go. But who is going to spend a huge time fighting the compiler for a small error when our TUI app is just one window-service? In addition, we use C/C++ and D in low-level tasks and adopting to Rust quickly is not something we might consider.

\n

In addition, networking toolkits with other languages did not feel native. Of course, each programming langauge comes with a socket module implementation. But we are talking about advanced network implementations such as packets sniffing. You might suggest using a module in Python or C++. That would help.

\n

However, it doesn't help when it comes to building. We wanted a language that is built easy to be executable. D might seem a good option here, but neither Python or C++ would help immediately. CMake would help, but after nighty hours of debugging or using an LLM that we don't want to rely heavily on for these kinds of tasks.

\n

We wanted a language that isn't too hard to use, familiar and optionally typed (which we will talk about later). In the same time, it supports building easily and natively, in addition to having builtin TUI and Networking modules. That was the time were we considered making a simple programming language that serves these goals.

\n

At first, its name was SASL (Simple Abstracted Syntax Language). But the name did not sound very explaining and it was kinda less intuitive to use. We then considered naming it B-Sharp (B#) in hall of (C#) my first programming language to use and learn, in addition to continuing the legacy naming of programming languages by alphabatical letters.

\n

We also considered naming it B++ (B Plus Plus) but that sounds a more modern implementation of the B Programming Language, but our language was firstly interpreted, and has very different syntax than B and rules, so we cancelled that idea.

\n

So we finally arrived at (B#). We want to discuss the language a bit in more details next and what we are aiming to build with it.

\n

Language Syntax​

\n

The first thing that comes to mind is how the syntax is going to be? Well, B-Sharp syntax is not so different from other languages' syntax. Imaging mixing Python, JavaScript, and BASIC syntax together, you get B-Sharp.

\n

B# inherits from Python the optional typing rule. It also inherits from JS some syntax keywords. Here is how you can define a variable in B#:

\n
var myFirstBSharpVariable = 12
\n

And you can also declare a variable's type as following:

\n
var myFirstBSharpVariable : Number = 12
\n

B# Holds all int, float and double types in one data type called Number which is similar to how JavaScript works. It also has the same type declaration feature format as Python.

\n

as to BASIC. If you programmed in it before, you may recognize familiarity here:

\n
if x == 12 then
my_val_function()
\n

B# implements also some syntax from BASIC (like then, do, etc.) keywords.

\n

That doesn't mean B# doesn't have its own syntax rules. Look at how a B# file for implementing a simple guessing game goes:

\n
module : simple_guessing_game
#SPECIAL_DATA_FORMATS false

import std.random

random_number : Number = RandInt() // from the imported std.random module
user_guess : String = input(\"Please guess the number: \")

if user_guess > random_number {
    print(\"Bigger than number\")
} elif user_guess < randome_number {
    print(\"Smaller than number\")
} else {
    print(\"You guessed it right!\")
}
\n

Might seem familiar and not different but has its own flavor. That is how B# is wanted to be, familiar but with an additional unique flavor.

\n

Modules​

\n

Standard Library​

\n

B# Standard Library (std) contains the following modules:

\n
    \n
  1. std.math for math functions.
    2. \n
  2. std.net for networking support.
    3. \n
  3. std.regex for regular expressions engine.
    4. \n
  4. std.builtins for more built-in functions and custom types.
    5. \n
  5. std.tui for building modern TUI apps.
    6. \n
  6. std.threads for handling threading.
    7. \n
  7. std.io for standard file I/O operations.
    8. \n
  8. std.system for system functions and utilities for controlling the OS.
    9. \n
\n

Core Library​

\n

Another library that comes with B# is core library containing the following modules

\n
    \n
  1. core.gui the standard B# GUI module.
    2. \n
  2. core.gpu GPU support for B#.
    3. \n
  3. core.cpu CPU support for B#.
    4. \n
  4. core.additional additional core utilities bundeled within the library.
    5. \n
\n

Software Development Kit​

\n

To make building B-Sharp easy and fast, we considered two pillars:

\n
    \n
  1. Using Poly system to build B# projects.
    2. \n
  2. Adding a Software Development Kit (SDK) for B# to simplify installing libraries from external sources, building, and testing.
    3. \n
\n

These two simplified using B# a lot. You can now run B# inside the interpreter or compile it to a native executable program that runs standalone.

\n

That is exactly how we wanted B#, familiar, easy to use, and supported. There are other mentions here that we want to make:

\n

Blossom and Begasus​

\n

Two other additional libraries are Blossom (for building more advanced TUI applications) and Begasus (a set of external tools and features that help B# threading and multitasking). These two libraries expand B# more and more.

\n

B-Sharp Butterfly​

\n

Butterfly is another library that is built to introduce easy integration between B# and Python. This module aims to make B# functions executable in Python and vise-versa. Although the idea seems weird, it is applicable.

\n

At the End​

\n

These are first impressions after developing B# and experimenting with it a bit. The language is still in pre-alpha release, so it contains bugs and unexpected behaviors, please use in caution.

\n

Happy Coding!

", "url": "https://your-docusaurus-site.example.com/blog/2026-08-05-bahfo_blog_1", "title": "Our Experiments with B-Sharp Programming Language", "summary": "Our latest experiments with the B-Sharp Programming Language are over. We are announcing now moving to next step of the development: Features implementation. In this blog, we talk more about how B-Sharp is going to be shaped in the future. What we are trying to implement and our goals of development.", "date_modified": "2026-08-05T00:00:00.000Z", "author": { "name": "Bahaa Nofal" }, "tags": [ "updates", "news" ] }, { "id": "https://your-docusaurus-site.example.com/blog/2026-08-05-dreamstudio_version_1dot1", "content_html": "

Explore the Latest Features in DS-1.1.0. Our powerful integrated development environment (IDE). DreamStudio got a huge update moving from version 1.0.0 to 1.1.0 expanding its functionality and adding more stability to the studio.

\n
\n

Explore the Latest Features in this Version​

\n

What's New?​

\n\n

Explore in Details​

\n

The UI Refactoring​

\n

DreamStudio got in version 1.1.0 a huge UI refactoring. The UI backend stayed the same. However, we changed how the structure is implemented. Previously, we relied heavily on two things:

\n\n

which made continuous development and integrating more features harder. Now, we changed that system completely:

\n
    \n
  1. UI elements now sourced inside .json files, complete with their properties, icons, and functionalities. This makes adding more features in future less intuitive and opens up more UI restyling opportunities.
    2. \n
  2. Retheming now takes source from standard static .qss files. This enables adding more themes easily. It also eliminates static retheming functions which took too much space in the codebase.
    3. \n
\n

Bootstrapping​

\n

Bootstrapping is a fundamental step in loading the IDE. DreamStudio supports now stable bootstrapping bundled with the following features:

\n
    \n
  1. Logging steps one by one.
    2. \n
  2. Error-proof system by adding a recovery window whenever a fatal error occurs. This prevents most of bootstrapping errors and ensures the IDE loads up successfully.
    3. \n
  3. Initialization by deterministic steps.
    4. \n
\n

Ironica Rewriting​

\n

Ironica is the name we will call DreamStudio's texteditor! This code editor is based on QScintilla texteditor. We supported it with syntax highlighting, autocompletion utilities, minimap, a suitable tabs manager and a complete API module for supporting plugin systems.

\n

Ironica's source code will be available as a standalone repository since it is, as a successful project, will power all our texteditors and projects.

\n

Utilities​

\n

1. Solution Explorer​

\n

Solution Explorer now consists of two main widgets:

\n
    \n
  1. File Explorer Treeview Utility.
    2. \n
  2. Packages Explorer.
    3. \n
\n

The Packages Explorer is a new utility to explore installed Python packages in the current solution.

\n

2. Source Control​

\n

Controlling Git became easier by adding more version control actions:

\n
    \n
  1. View source changes in a table format, or a graph format.
    2. \n
  2. Switch between branches easily.
    3. \n
  3. Commit your chagnes faster and push to the current remote branch.
    4. \n
\n

3. Properties Explorer​

\n

Controls the properties of the currently opened solution.

\n

Additional Bug Fixes​

\n
    \n
  1. Fixed bugs related to syntax highlighting in Ironica.
    2. \n
  2. Fixed an issue related to folding where folding buttons did not position correctly.
    3. \n
  3. Added two additional methods for later usage: Ghost Text addition and Errors Underlining method.
    4. \n
\n

Happy Coding!

\n

The DreamStudio Team

", "url": "https://your-docusaurus-site.example.com/blog/2026-08-05-dreamstudio_version_1dot1", "title": "DreamStudio 1.1.0 is Here!", "summary": "Explore the Latest Features in DS-1.1.0. Our powerful integrated development environment (IDE). DreamStudio got a huge update moving from version 1.0.0 to 1.1.0 expanding its functionality and adding more stability to the studio.", "date_modified": "2026-08-05T00:00:00.000Z", "author": { "name": "EXTechs Team" }, "tags": [ "updates", "news" ] }, { "id": "https://your-docusaurus-site.example.com/blog/2026/01/01/welcome", "content_html": "

Welcome to EXcellent TechStacks Blog!

\n

Here, we share our thoughts, latest updates, ideas and future updates. Contribution here is welcomed! Visit contributing to blog to find out all rules and standards.

", "url": "https://your-docusaurus-site.example.com/blog/2026/01/01/welcome", "title": "Welcome", "summary": "Welcome to EXcellent TechStacks Blog!", "date_modified": "2026-01-01T00:00:00.000Z", "tags": [] } ] }