Welcome to the Atlas toolkit web site
Albeit relying on web technologies, the Atlas toolkit is not for building web applications, nor desktop applications. With the Atlas toolkit, you obtain hybrid programs. Like desktop applications, the same code can handle both front and back ends, and, like web applications, the programs will be reachable from all over the internet.
Programs based on the Atlas toolkit, when launched on any computer which has access to internet (no need to be accessible from internet), can be used through a modern web browser on every device with an access to internet. You have nothing to configure, or to upload on a remote server. Simply launch your program on a computer connected to internet, and it will be accessible from everywhere on internet.
Even a program which was originally designed to have only a command line interface (CLI] or a text-based user interface (TUI) can easily be modified to have a GUI, thanks to Atlas toolkit. The GUI can then cohabit with the other interface, giving the user the choice of the interface s/he wants to use.
The Atlas toolkit is very lightweight, so it can be used on devices such a Raspberry Pi (even the Zero model), opening new horizons to electronics or robotics enthusiasts. The Atlas toolkit can also be used on Android devices, by using Termux.
The Atlas toolkit is currently available for Java, Node.js, PHP, Python and Ruby. Works are in progress for the toolkit to be available for other languages, and if you wish to discuss about those perspectives, you are welcome to do so in this forum.
Let's take the Raspberry Pi as example. This nanocomputer was developed to provide an affordable device with which you can learn programming. And with the GPIO ports available on the Raspberry Pi, you can write programs to control electronic circuits and even robots.
The Atlas toolkit makes things even more fun. With te Atlas toolkit, you can easily modify your programs to add GUI, with which you and control your circuits and robots directly from your smartphone.
Of course, you don't need a Raspberry Pi (or such kind of devices) to use the Atlas toolkit. You can use it for whatever program you want as long it is developed in one of the available language.
There are some programs which were developed especially fot the Raspberry Pi and other similar devices (like ODROIDs), and you will find more about them at this page.
The development of a web application is something which requires special computing skills and plenty of time, and therefore costs a lot of money. Before launching such a development, you better have a very good idea of what the result should be, and be sure that the developers exactly know what you want.
As the Atlas toolkit is available for the most popular languages and requires only basic programming skills, it's an affordable and fast way to develop a prototype of your web application, which can easily be shown to discuss about, and used to test the functionalities and refine them.
Once the prototype is validated, it can be used as a model for the development of the final application. You will so be sure that this application will be exactly what you want. And you can use the prototype to easily test and validate new functionalities before including them in the final application.
Here is a preview of the famous "Hello, World!" program made with the Atlas toolkit:
Click on above animation to get an overview of the global structure of a program using the Atlas toolkit, with the source code of the Hello, World! program for all languages in which the Atlas toolkit is available. s
For comparison, the application from the TodoMVC project has been developed using the Atlas toolkit. This is what it looks like:
The programs will be stopped after a few tens of seconds, due to a RunKit timeout. By going back, you have then access to the editor containing the source code. Depending of the browser used, the above described dialog box will pop-up again.
RunKit relies on NPM. When a new package is published on NPM, it's not always immediately available on RunKit. When old and new version of the packages are not compatible which each others, the live demonstration do not work until RunKit is updated, and they are therefore disabled.
List of the available live demonstrations:
On the launching of the program, or to update broad parts of the interface, the needed HTML code is sent directly to the browser; this is very similar to a CGI based application. Otherwise, only the needed part of the DOM is updated, like a single-page application. With the Atlas toolkit, you have the best of both worlds.
The HTML code can be generated using XSLT, manually, or by using the template engine of your choice.
Here are where you will find the source code of the library, with examples of use:
Web applications usually need to be installed on a server which have to be accessible from internet. And, in addition of the application itself, there is also the need of a web server, standalone or embedded in the application, which handles the user's web browser requests.
By using the Atlas toolkit, you only have to launch your program on your computer, and you can give access to your program to whoever is on internet. As you don't have to deploy your pogram on a remote computer, each modification you make to your program is instantly available. That's why the Atlas toolkit is particularly suitable for prototyping.
To achieve this, the Atlas toolkit connects to a free public server, which also handles the connections from the user's web browser. The URL corresponding to your program is displayed in the console from which you launched your program, and by simply giving this URL to someone on internet, you grant this person the access to your program.
The sources of the software on the remote server can be found here:
If you want to deploy this software on your own server, retrieve both above repositories and compile them.
If you are under Windows, use the
.vcxproj files. For other systems, launch
make in the root of each repository. Then launch
<path-to>/xdhwebqcli/xdhwebq <path-to>/xdhq/xdhqxdh (without the
You also need a web server, in which you install the content of the
htdocs directory from the xdhwebq-cli repository.
You have also to modify the needed environment variables accordingly to http://q37.info/s/pkhrq3px.
He developed C++ libraries to handle desktop user interfaces using XULRunner. As XULRunner were discontinued, he switched to the newly standardized HTML5, along with the Chromium Embedded Framework. The libraries were then improved to also handle web user interfaces. Finally, Electron replaced the Chromium Embedded Framework.
As most of the popular languages are interpreted ones, he also specialized in improving the performances of this languages, by developing binding libraries simplifying the use of the more efficient C++ native code with this languages.