--
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
Unsubscribe: harbour-user...@googlegroups.com
Web: https://groups.google.com/group/harbour-users
---
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/harbour-users/aaf07572-6c60-4d7d-b5d9-379312b4ebe4n%40googlegroups.com.
Sorry, but which gui do you use ?
--
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
Unsubscribe: harbour-user...@googlegroups.com
Web: https://groups.google.com/group/harbour-users
---
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/harbour-users/610161f0-34fb-499a-93df-921cbcee903cn%40googlegroups.com.
While Harbour evolved into a multi-OS compiler, it never acquired an official GUI library. Although various open-source GUI libraries appeared, the absence of a native Windows library specifically designed to ease the migration from Clipper was a significant gap.
Add IMGUI... 7....And add at least a couple of projects to use html ...And at least another project to use WASM...We don't even have a central repository for listing projects and repositories... :-)
--
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
Unsubscribe: harbour-user...@googlegroups.com
Web: https://groups.google.com/group/harbour-users
---
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/harbour-users/222f62b3-187e-4055-8370-6e4e4b9c2462n%40googlegroups.com.
How to do as much as possible with down to the point program code and very little external dependecies? Otherwise what's wrong with hbQT?I'd say it got everything you could wish.
// @ 00, 01 SAY 'Employee Details'
@ 00, 01 LABEL 'Employee Details' FONT HeadFont()
Add IMGUI... 7....
WVWCLIP library depends on GTWVW, and was witten to modernize a large business application written using Clipper in the early 80s. This application is still being used today.Source code is avilable.
Harbour is not used for programming like other languages because there are no complete projects or frameworks that enable efficient development.
For example, it lacks:
A framework like PHP’s Laravel.
An ORM to easily connect to different databases (from DBF/CDX to MySQL, MariaDB, PostgreSQL, Oracle, etc.). SqlRDD allows connections to multiple databases, but it’s not an ORM like Eloquent (https://laravel.com/docs/4.2/eloquent).
Unit Testing support.
Libraries or frameworks for web development.
mod Harbour exists, but few people know about or use it.
mod Harbour V2 (https://github.com/mod-harbour) is an open-source Apache module that lets you run Harbour programs on the web.
Libraries or frameworks for smartphone development.
Native functionality to handle APIs and integrate with JavaScript libraries like Angular, React, or Vue.
A complete open-source program (like ODOO https://github.com/odoo/odoo ) to showcase Harbour’s potential.
No easy way to use AI API.
There are some usage examples, but they lack visibility. For instance:
New Class TKimi for KIMI AI:
https://groups.google.com/g/harbour-users/c/OPy-EsphSnU
These are some of the features Harbour currently lacks.
Hi,
Putting aside the Harbour repository and a possible redefinition of the roadmap, i think nowadays, having a centralized package manager—something like Packagist, npm, etc.—would really help popularize the platform among developers. It would standardize how everyone uses libraries, making it easier to manage different versions and dependencies. Basically, a site with a centralized index of all these libraries, while the actual packages stay in their authors' own repos.
A simple publishing system and a standardized approach would speed things up. I don’t know if anyone’s already working on this, but I’m sure we could quickly gather hundreds of contributions this way.
Right now, many of us use Git or others..., but we should take the next step—unifying everything and figuring out the best approach.
Every developer contributes their own "package."
Every developer can use any "package."
Any thoughts on this topic I would love to hear :-)