Hello Fellow Developer, Friend,
TRQL Radio… it's computer code. Above all, computer code!
Therefore, we are going to make it as easy as possible for you to interact with TRQL Radio and the data that has been gathered over the past 8 years.
All we need from you is a little bit of patience so that we can create something fantastic, simple and effective. Not like the anti-covid vaccines! Something safe and effective, you know?
What keeps us busy now is our Vae Soli! Player (where you can listen to a multitude of radios and tracks) and our API (which you will be able to use to interact with us).
Stay tuned and plan a visit here in a few days!
Bonjour chers développeurs, chers amis,
TRQL Radio... c'est du code informatique. Avant tout, du code informatique !
C'est pourquoi nous allons faire en sorte que vous puissiez interagir le plus facilement possible avec TRQL Radio et les données qui ont été recueillies au cours des 8 dernières années.
Tout ce dont nous avons besoin, c'est d'un peu de patience pour créer quelque chose de fantastique, de simple et d'efficace. Pas comme les vaccins anti-covidés ! Quelque chose de sûr et d'efficace, vous voyez ?
Ce qui nous occupe pour l'instant, c'est notre lecteur Vae Soli ! (où vous pouvez écouter une multitude de radios et de morceaux) et notre API (que vous pourrez utiliser pour interagir avec nous).
Restez à l'écoute et prévoyez une visite ici dans quelques jours !
Immediate Release
This code is NOT our latest code (open source) but at least it can help you start with something useful as it covers everything we will still document in our generic concepts (still a lot of things to do here!):
- GitHub Repository: https://github.com/patboens/TRQL-Labs
GitHub has some limitations in terms of number of entries. We are working on that constraint by re-organizing our code (there are more than 1000 classes/files)
The Ancestor of Vae Soli! is … Vae Soli!
All this work started in 1996, when we developed the core architectural concepts needed for the automation of a new extension of the Upjohn facility in Puurs. The mission was clear: we needed to have a facility that would be fully automated, which required to interface software with many different physical devices such as packaging machines, weighing scales, automatic forklifts, …
At that time, we wanted to have the possibility of exchanging information between machines located on the production lines all throughout the new facility. That's the reason why we worked hard together with Oracle to create a messaging mechanism whose central message repository was an Oracle DB.
Then, based on what Siemens suggested, we have switched to IBM's MQSeries and we abandoned the work with Oracle to concentrate on MQ that already had many of the features we were actually searching for.
Later on, in 2001, I had the honor of creating an EAI: I baptized this EAI "Vae Soli!", which literally means Woe to the ones standing alone. All the sources of this EAI were written in ANCI C and was mostly based on what I remembered our code for Upjohn was. I still plan to put this in the Open Source community some day.
Then, in 2005, I founded Lato Sensu Management. This company was focused on delivering consulting services to large and medium companies, many of them which were turning to web consulting.
That is the moment, I created the other arm of Vae Soli!: the web framework, a rebuild of some previous work I started with ColdFusion, which I then turned to Ephemere, a framework built in a language that was pretty close to Visual FoxPro, and finally the PHP version of Vae Soli! as we know it today (09/02/2022 14:14:46, when I first wrote these lines, but still the case on 07/02/2024 08:58:03).
The promise of Vae Soli! was to be STRICTLY compatible from version to version. It happens to be a reality since 2005, a total of 20 years of stability and strict compatibility.
The latest modifications I ran on Vae Soli! are dated of today! Sources are still compatible, which is an incredible achievement (20 years)! In the meantime, all code was transformed to form yet another framework: the one I build web sites with today, made of more than 1000 PHP classes, mostly built with standardized et of properties inherited from schema.org and wikidata.
Articles
- Service Catalog : c'est quoi un catalogue de services ?
- Service Catalog (Extended) : la suite (avec un véritable catalogue et avec des paramètres) ?
- HTTP : l'utilisation du protocole HTTP dans les services REST
- YAML : YAML comme base de documentation des services
- OpenAPI 3.0 — Partie 1 : écrire services et microservices en OpenAPI 3.0
- OpenAPI 3.0 — Partie 2 : utiliser Swagger
- OpenAPI 3.0 — Partie 3 : finalisation de notre API à 3 services
- OpenAPI 3.0 — Partie 4 : ajout d'un service nécessitant un passage de paramètre
- OpenAPI 3.0 — Partie 5 : plus de détails
- UML : Diagramme de classe — Les relations — Partie 1
- UML : Diagramme de classe — Les autres symboles — Partie 2
- Project Management, Program Management, Portfolio Management
- Schema.org, Wikidata & Co: Leveraging Open Repositories
- Procurement Management
Resources
Here you will find some useful resources:
