HMGforum.com

Hi everyone:
Today, after a very long time, Workspace is moving from being a sample to a trial version, removing elements that served merely as a bridge.
I have already added the services for Workspace; there are several of them, and they are described in the documentation.

Context:

Those services are interconnected and need to be tested in a real-world scenario; in my case, I was working on a PC application project for the HopeWay IP camera. It doesn't expose the camera via ONVIF—a feature found in many IP cameras—and since I was never able to resolve the errors, I put the project on hold.

...so the need for real projects with compilation errors came at just the right time for me.

I already have the compilation service... it's called WBS; it runs from the command line or is launched via Windows Explorer, and it replaces HMG's Build.bat.

WBS (Workspace Build System) uses a library called WES (Workspace Engine System), which is responsible for assembling the entire project for hbmk2.

When HBMK2 executes that build, it calls Harbour, then the G++ compiler, and finally the linker.
All of this generates trace logs.
Ultimately, if the compilation is successful, it generates a simple log file named `build.log`.

But if there was an error, the IDE sometimes wouldn't give us the summary. That’s why I now have a compilation diagnostic service that generates a human-readable log—a more detailed and precise diagnostic.

This document is saved in the xx.ws file, which is readable by Scintilla; however, the Navigator does not provide precise details regarding the location of the error. You simply need to select the warning, error, or info item with the mouse, and it takes you to the document where the issue occurs.
I still need to make a few adjustments to the Workspace setup—similar to what I was doing before—so you can test it in your projects, identify any errors, and get them fixed.

I think being able to test it would really help me finish it up. Just a reminder that I work on this in my spare time; programming isn't my full-time job anymore—I moved on from that after doing it for years and years. My work now is as a piercer—something that used to be a hobby—much like being a lathe operator (which remains an unfinished project of mine because I lack the tools to build a small lathe just for fun).

Español

Hola a todos: mientras desayuno estoy revisando y corrigiendo la documentacion de Workspace. casi nadie las lee pero debe estar sincronizada con todas las modificaciones y actualizaciones del entorno de desarrollo.
Workspace nacio despues de ver que estaba luchando mucho con el manejo de los controles al estar trabajando con el diseñador de formularios para IDEunicode.
asi que de pasar a diseñar el IDE pase a rediseñar la GUI no modificando todo lo construido para que haya compatibilidad.
Esa compatibiidad ahora se bifurca con un simple
ahi está la separacion de GUI ("#include 'gui.ch' ) y HMG("#include 'mingui.ch')

como vi que algunos controles debian ser modernizados por ejemplo TextBox, este debe ser acompañado por un Label en algunos casos, entonces TextBox Modern tiene un Label incluido que puede estar arriba, abajo, a la izquierda o derecha, con un PlaceHolder que se borra al comezar a escribir dentro de el control.
asi como otros controles mas tienen Modern.

desde hoy comenzaré a leer y comprender el funcionamiento del Editor de Formularios, y quien lo haya estudiado puede ayudarme mucho, si usted ya miro las entrañas de diseñador puede buscarme en Telegram con mi nombre de usuario que es DaNiElMaXiMiLiAnO
y comentarme sobre el.. gracias!

PD: las imagenes de Workspace compilando con WES me permitio encontrar errores que IDE no me decia. ese ejemplo generaba .exe (clase tONVIF para camera9.hbp)
hoy WES con el codigo corregido pudo generarme el .exe

Ingles

Hello everyone: while having breakfast, I'm reviewing and correcting the Workspace documentation. Almost no one reads it, but it needs to be synchronized with all the modifications and updates to the development environment.
Workspace was born after I realized I was struggling a lot with handling controls while working with the form designer for IDEunicode.

So, instead of designing the IDE, I moved on to redesigning the GUI, without modifying everything that had been built, to ensure compatibility.
That compatibility is now forked with a simple
That's where the separation between GUI ("#include 'gui.ch'") and HMG ("#include 'mingui.ch'") is located.

Since I saw that some controls needed to be modernized, for example, TextBox, which should be accompanied by a Label in some cases, TextBox Modern includes a Label that can be positioned above, below, to the left, or to the right, with a PlaceHolder that is cleared when typing begins within the control.

as well as other controls that have Modern.

Starting today, I will begin to read and understand how the Forms Editor works, and anyone who has studied it can help me a lot. If you have already looked into the inner workings of the designer, you can find me on Telegram with my username, DaNiElMaXiMiLiAnO, and tell me about it. Thanks!

PS: The Workspace images compiling with WES allowed me to find errors that the IDE didn't tell me about. That example was generating an .exe (tONVIF class for camera9.hbp). Today, WES, with the corrected code, was able to generate the .exe.

History:

Hola a todos , por ahora les dejo un video del desarrollo de Workspace en YT

https://youtu.be/U-RleTTagXo

Thanks !

Gracias!

Gracias Daniel.

Hola a todos, : cree un Grupo en mí telegram para poder Compartir Workspace para que lo prueben. Cómo WhatsApp tiene limitaciones para compartir archivos grandes cree el grupo
Les dejo el link: https://t.me/HMGWorkspace

Si quiere enviar mensaje personal recuerden que mí nombre para encontrarme sin saber mí número de celular es : DaNiElMaXiMiLiAnO

descomprimir y leer :

Hola a todos: el entorno de desarrollo Workspace ya tiene implementado en forma local y remoto GitService, un servicio dentro de Workspace y en host consola (CMD) , si quiere respaldar su codigo fuente dentro de GITHUB o en forma local .
forma de uso en CMD
los invito a probarlo, desde mi grupo en telegram estaré subiendo la nueva version que incluye esta y otras caracteristicas implementada estos dias.

enlace de Invitacion : https://t.me/HMGWorkspace

Hola a Todos : nueva implementacion en Workspace, la posibilidad de navegar en funciones C dentro de un .prg
Navigator reconoce funciones y punteros encerrados dentro de #pragma BEGINDUMP / #pragma ENDDUMP
asi como el proyecto puede contener archivos .c y .cpp

Proyecto
app.hbp
source\main.prg
source\window.prg
source\native_winapi.c
source\editor_bridge.cpp

La diferencia práctica es esta:
gcc:
Compila y enlaza C. Si le pasás .c, trabaja como C. Puede compilar .cpp si se lo forzás, pero al enlazar no siempre arrastra automáticamente la librería estándar C++.
g++:
Compila y enlaza C++. También puede compilar .c, pero puede tratar el flujo como C++ según opciones/extensión. Al enlazar, agrega automáticamente el runtime C++: libstdc++, soporte de excepciones, constructores globales, etc.

hoy Workspace trabaja con :

Harbour 3.2.1dev (r2607071005)

gcc (x86_64-posix-seh-rev1, Built by MinGW-Builds project) 16.1.0

g++ (x86_64-posix-seh-rev1, Built by MinGW-Builds project) 16.1.0

este proyecto : Proyecto.hbp contiene Code.c