Developer branch

Developer branch is up to date.
https://github.com/emanuel4you/LibreCAD/tree/developer

Do you think it's stable enough for merging?

emanuel wrote

Developer branch is up to date.
https://github.com/emanuel4you/LibreCAD/tree/developer

hm... I suppose the content there requires some additional review and refactoring...

all actions go well

so far I can't even build that branch that I've just pull from Git.

First, I've tried to build it with CMake.

Ok, I've managed to install swig and set proper variables in CMakeLists.txt (yet that's not good that they are not there by default in CMakeLists.txt, I suppose).

But later, when building the project, the build process is failed with message:

[735/766] Linking CXX static library librecad_lib.lib
[736/766] Swig compile librecad/src/python.i for python
FAILED: [code=1] CMakeFiles/librepython.dir/pythonPYTHON_wrap.cxx librecad.py D:/Local/LibreCAD_Developer/cmake-build-debug/CMakeFiles/librepython.dir/pythonPYTHON_wrap.cxx D:/Local/LibreCAD_Developer/cmake-build-debug/librecad.py
CMakeFiles\pythonPYTHON_wrap.cxx-f79fbc4.bat 976b77978b0cec99
Language subdirectory: python
Search paths:
......
......
......
Preprocessing...
(999999) : Error: Unable to find 'swig.swg'
(2) : Error: Unable to find 'python.swg'
D:\Local\LibreCAD_Developer\librecad\src\python.i(16) : Error: Unable to find 'std_string.i'
Batch file failed at line 4 with errorcode 1

So after that I've switched to QtCreator and opened the project there.

In QtCreator project:
1) src/slide_records_visitor_qt_drawer.hpp file seems to be missing (referred by libslide.pro)

Probably I'll manage to correct QtCreator project to get some buildable state, but try to check this later.

Also, I'm not sure that some samples (both for python and lisp), tests or docs are included into this branch.

So far I didn't review the code - yet it I'll have more time, I'll be happy to drop a couple of notes.

Hello everyone,

I have recently installed and compiled LibreCAD 2.2.2-alpha6. I noticed a significant difference in size: the final build exceeds 3 GB, whereas alpha5 was under 840 MB. I would like to ask if this is expected for the current development state or if it might be due to specific debug configurations or new dependencies included in this build.

Given the magnitude of the changes in this stage, I believe it would be beneficial to clearly define the Roadmap for the next major release to ensure a smooth transition for the community. In my opinion:

Stability: The current stable branch (2.2.1.x) should remain focused exclusively on critical bug fixes and stability.

Versioning: The current alpha branch could be renamed to LibreCAD 2.2.90 alpha, eventually leading to a formal 2.3.0 release.

Incremental Releases: I suggest moving toward smaller, incremental updates. Introducing such radical changes without updated documentation can create confusion among users and significantly prolong the stabilization process.

Regarding my testing of alpha6, I would like to report two specific issues:

UI Bug: The “Show all tools in a widget” option does not seem to work in this build.

Usability & Contrast: The default dark theme could use some usability improvements. At the moment, many toolbar icons have low contrast against the background, which makes several tools difficult to identify quickly. Improving the icon visibility and overall visual hierarchy would greatly enhance the user experience, especially for new users.

Finally, I want to thank the active developers for all the hard work being done. LibreCAD is a great project and a highly valuable asset for the community.

Best regards,

Usuario

ideally, we should have:

1. current stable: 2.2.1.x;
2. next stable: 2.2.3-alpha;
3. experimental: 2.2.90-sid.

The practical issue, we do not have enough development power to keep tracking two development branches(2 & 3).

At certain point, 2.2.1.x will reach acceptable stability and not a burden to developers. Then, 2.2.3 can be branched to a feach frozen Release candidate, and developers will be still tracking mostly the development branch.

usuario wrote

Hello everyone,

I have recently installed and compiled LibreCAD 2.2.2-alpha6. I noticed a significant difference in size: the final build exceeds 3 GB, whereas alpha5 was under 840 MB. I would like to ask if this is expected for the current development state or if it might be due to specific debug configurations or new dependencies included in this build.

Given the magnitude of the changes in this stage, I believe it would be beneficial to clearly define the Roadmap for the next major release to ensure a smooth transition for the community. In my opinion:

Stability: The current stable branch (2.2.1.x) should remain focused exclusively on critical bug fixes and stability.

Versioning: The current alpha branch could be renamed to LibreCAD 2.2.90 alpha, eventually leading to a formal 2.3.0 release.

Incremental Releases: I suggest moving toward smaller, incremental updates. Introducing such radical changes without updated documentation can create confusion among users and significantly prolong the stabilization process.

Regarding my testing of alpha6, I would like to report two specific issues:

UI Bug: The “Show all tools in a widget” option does not seem to work in this build.

Usability & Contrast: The default dark theme could use some usability improvements. At the moment, many toolbar icons have low contrast against the background, which makes several tools difficult to identify quickly. Improving the icon visibility and overall visual hierarchy would greatly enhance the user experience, especially for new users.

Finally, I want to thank the active developers for all the hard work being done. LibreCAD is a great project and a highly valuable asset for the community.

Best regards,

Usuario