vanuan wrote: ↑Wed Sep 16, 2020 10:46 pm
I'd say the main benefit of introducing a well known technology is attracting more developers rather than trying to mimic a workflow of existing developers. With custom html template engine and custom protocol I'd say you limit developer participation even further without any clear benefit.
- Most freecad developers are not web developers.
- Have you seen the code?, the templates are many orders of magnitude simpler that any React project. I Love reactjs, but the use case does not require another build framework. I tried to keep javascript at minimun and python at maximum. It is just my approach, maybe I am wrong about that.
vanuan wrote: ↑Wed Sep 16, 2020 10:46 pm
Do you have any intention on upstreaming QWebEngine-based MDI window into the main FreeCAD repository?
Yes the whole project was created with the intention to replace the old Addon Manager. But going from proposal to mainstream will take some time. There are running discussions about extensions standardization...
mnesarco wrote: ↑Wed Sep 16, 2020 11:01 pm
Yes the whole project was created with the intention to replace the old Addon Manager. But going from proposal to mainstream will take some time. There are running discussions about extensions standardization...
Lets start this. The idea was to make a formal FreeCAD Enhacement Proposal (FEP) of what the standard would look like. Do you feel like taking point on that ?
Kunda1 wrote: ↑Wed Sep 16, 2020 11:06 pm
Lets start this. The idea was to make a formal FreeCAD Enhacement Proposal (FEP) of what the standard would look like. Do you feel like taking point on that ?
Sure, I was one of the main proponents. I was working on this few months ago, but then I was in a health situation that convined with the pandemic outage put me in a situation with very low time availability. I am restarting myself slowly, I am very interested in this topic.
It is not hardcoded, it is externalized to a json file. The idea is to get that file from a trusted source (ideally from the FreeCAD-addons) but I have no commit permissions there and this ExtMan is still not official thing. So I saved it locally and it can be trivally relocated.
mnesarco wrote: ↑Thu Sep 17, 2020 7:25 pm
It is not hardcoded, ...
Please read this Addon Manager sustainability issues. I'd like your opinion of a self-updating addon manager, or another solution for that problem.
Basically, it's the problem of what to do if the online repository for addons changes and we cannot parse it any more using the current Addon Manager. This seems to be the case with v0.18; we updated the Addon Manager in v0.19, but in v0.18 the code is static and no longer works with the GitHub page.
If in the life of a stable release our online repository changes, how can we provide an updated Addon Manager to take into account those changes? Fortunately, workbenches can always be installed manually (How_to_install_additional_workbenches) but this isn't very user friendly.
It is not hardcoded, it is externalized to a json file. The idea is to get that file from a trusted source (ideally from the FreeCAD-addons) but I have no commit permissions there and this ExtMan is still not official thing. So I saved it locally and it can be trivally relocated.
mnesarco wrote: ↑Thu Sep 17, 2020 7:25 pm
It is not hardcoded, ...
Please read this Addon Manager sustainability issues. I'd like your opinion of a self-updating addon manager, or another solution for that problem.
Basically, it's the problem of what to do if the online repository for addons changes and we cannot parse it any more using the current Addon Manager. This seems to be the case with v0.18; we updated the Addon Manager in v0.19, but in v0.18 the code is static and no longer works with the GitHub page.
If in the life of a stable release our online repository changes, how can we provide an updated Addon Manager to take into account those changes? Fortunately, workbenches can always be installed manually (How_to_install_additional_workbenches) but this isn't very user friendly.
In the case of ExtMan, it is an external workbench, it is very easy to self-update it, I will add an option.
It is not hardcoded, it is externalized to a json file. The idea is to get that file from a trusted source (ideally from the FreeCAD-addons) but I have no commit permissions there and this ExtMan is still not official thing. So I saved it locally and it can be trivally relocated.
I have not commit access to https://github.com/FreeCAD/FreeCAD-addons, if you have, feel free to copy these files there and I will update ExtMan to download them from there.
