Another approach to assembly solver (A2plus)

triplus · Post by **triplus** » Sat Jun 23, 2018 12:55 pm

This is a Python based FreeCAD module. Therefore creating an AppImage for testing purposes would be an overkill. Just download and install the module by extracting it in the Mod folder.

https://freecadweb.org/wiki/How_to_inst ... orkbenches

Post by **Kunda1** » Sat Jun 23, 2018 1:22 pm

Good point, what about adding it to the addon repo labeled 'Experimental' to make it more widely available for testing?

triplus · Post by **triplus** » Sat Jun 23, 2018 1:41 pm

Code needs to be hosted somewhere first. Currently addon manager only supports GitHub. Therefore if the module would be hosted on GitHub a request can be made to add it here:

https://github.com/FreeCAD/FreeCAD-addons/issues

P.S. Due to Microsoft buying GitHub it could happen potential future FreeCAD module developers won't join GitHub anymore. As easily as in the past. Therefore likely alternative git repository service provider support will be needed.

Post by **Kunda1** » Sat Jun 23, 2018 1:47 pm

triplus wrote: ↑Sat Jun 23, 2018 1:41 pm P.S. Due to Microsoft buying GitHub it could happen potential future FreeCAD module developers won't join GitHub anymore. As easily as in the past. Therefore likely alternative git repository service provider support will be needed.

Another good point, I think there is an issue for that also open in the Github freecad-addon repo as well. (there wasn't so I added issue#80)

@kbwbe do you mind using GitHub for now and submitting an issue to the freecad-addon repo for your a2+ workbench and the push changes that way so people could download it seamlessly via the FC addon-manager?

kbwbe · Post by **kbwbe** » Sat Jun 23, 2018 2:17 pm

Kunda1 wrote: ↑Sat Jun 23, 2018 1:47 pm
triplus wrote: ↑Sat Jun 23, 2018 1:41 pm P.S. Due to Microsoft buying GitHub it could happen potential future FreeCAD module developers won't join GitHub anymore. As easily as in the past. Therefore likely alternative git repository service provider support will be needed.
Another good point, I think there is an issue for that also open in the Github freecad-addon repo as well. (there wasn't so I added issue#80)

@kbwbe do you mind using GitHub for now and submitting an issue to the freecad-addon repo for your a2+ workbench and the push changes that way so people could download it seamlessly via the FC addon-manager?

@Kunda1, @triplus
I do not have a real problem using GitHub at moment. Hope that Microsoft is doing no things which i would not like (special trackers, etc)

But i think, time is not right do move to GitHub. My new workbench is really not ready. There are still a lot of mistakes in code.
Some absolutely necessary features are missing.

I prefer tests from the interested and very competent people in this thread at moment, because most other users would be frustrated to use my WB now.

When most things are working, it would be very good to use GitHub and the addons-manager.

triplus · Post by **triplus** » Sat Jun 23, 2018 2:27 pm

If you eventually plan to move your code to GitHub i would suggest to do that rather sooner than latter. Your module being in alpha development stage isn't a problem in my opinion. End users are made aware of that. Things like development and testing would be made much more streamlined.

Post by **Kunda1** » Sat Jun 23, 2018 2:36 pm

triplus wrote: ↑Sat Jun 23, 2018 2:27 pm If you eventually plan to move your code to GitHub i would suggest to do that rather sooner than latter. Your module being in alpha development stage isn't a problem in my opinion. End users are made aware of that. Things like development and testing would be made much more streamlined.

I agree with @triplus on this. The add-on manager description can clearly state that the WB is in alpha and what known issues it still has + a link to this forum thread for feedback. Of course no pressure, it's your effort @kbwbe so you dictate the pace

Thanks for all your work so far.

kbwbe · Post by **kbwbe** » Sat Jun 23, 2018 7:40 pm

Just one more new version as ZIP. (I think one of the last ones before migrating to GitHub)
ZIP attached...

Whats new ?:

- Constraints clearly grouped under both involved imported parts
- fixed objectName/labelName mismatch during imports
- removed + downsized codeparts
- added new Constraint "sphereCenterIdent"
- fixed unwanted resizing of documentWindows.
.
Seems to work fine. Rough tested with fc0.16, fc0.17, fc0.18
.
See "sphereCenterIdent" in action:
.

: triaeder.png (265.99 KiB) Viewed 1607 times

.
FOR TESTING DO ALWAYS A FRESH ASSEMBLY. DATASTRUCTURE IS CHANGING MUCH. ASSEMBLIES DONE WITH VERSIONS BEFORE WILL SHOW ERRORS AND WILL NOT OPEN CORRECTLY.

kbwbe

triplus · Post by **triplus** » Sat Jun 23, 2018 9:14 pm

Nice. I guess if there will be Assembly 2 (alike) successor under active development and maintenance. After achieving feature parity and going beyond. That by itself is a good thing.

P.S. Yellow icons somehow don't do justice.

jbe · Post by **jbe** » Sun Jun 24, 2018 12:23 pm

Hello,
With the last version, I don't arrive to assembly part !
We can duplicate, you can import a part, but not assembly ...
I don't understand ?

Another approach to assembly solver (A2plus)

Re: Another approach to assembly solver (assembly2relaunch)

Re: Another approach to assembly solver (assembly2relaunch)

Re: Another approach to assembly solver (assembly2relaunch)

Re: Another approach to assembly solver (assembly2relaunch)

Re: Another approach to assembly solver (assembly2relaunch)

Re: Another approach to assembly solver (assembly2relaunch)

Re: Another approach to assembly solver (assembly2relaunch)

Re: Another approach to assembly solver (assembly2relaunch)

Re: Another approach to assembly solver (assembly2relaunch)

Re: Another approach to assembly solver (assembly2relaunch)