FDM/FFF (3D printing) documentation #177

Activity

1. machinekoder

   self-assigned this

   on Jun 24, 2016
2. luminize commented on Jun 24, 2016

   

   luminize

   on Jun 24, 2016 via email

   Contributor

   More actions

   That would only make sense imo if the configurations are "stock" machinekit.
3. the-snowwhite commented on Jun 24, 2016

   

   the-snowwhite

   on Jun 24, 2016

   Contributor

   More actions

   I Agree with you both. For mere 3d printing is not just a "toy" I have seen
   3d Glass printing and 3d Bridge building with robot welders.

   But this is not My Call as I was not part of the deciding around the
   externalisation of the qt stuff.
   On 24 Jun 2016 5:12 p.m., "Bas de Bruijn" notifications@github.com wrote:

   That would only make sense imo if the configurations are "stock"
   machinekit.

   —
   You are receiving this because you are subscribed to this thread.
   Reply to this email directly, view it on GitHub
   #177 (comment),
   or mute the thread
   https://github.com/notifications/unsubscribe/AKifnGrvmC4dvt03zwWu8bX9VgKF_OgEks5qO_PBgaJpZM4I9zZY
   .
4. luminize commented on Jun 24, 2016

   

   luminize

   on Jun 24, 2016

   Contributor

   More actions

   On 24 Jun 2016, at 19:13, Michael Brown notifications@github.com wrote:

   But this is not My Call as I was not part of the deciding around the
   externalisation of the qt stuff.

   I'm sorry, I don't see the connection. Qt has nothing to do with configurations or HAL
5. cdsteinkuehler commented on Jun 24, 2016

   

   cdsteinkuehler

   on Jun 24, 2016

   Contributor

   More actions

   On 6/24/2016 10:12 AM, Bas de Bruijn wrote:

   That would only make sense imo if the configurations are "stock" machinekit.

   I think Alexander's standards for FDM setups and his example
   configurations should migrate into the machinekit repo and become part
   of the standard release. IMHO, the existing FDM examples should also
   migrate to using the FDM standards and possibly the python HAL setup.

   Charles Steinkuehler
   charles@steinkuehler.net
6. the-snowwhite commented on Jul 15, 2016

   

   the-snowwhite

   on Jul 15, 2016

   Contributor

   More actions

   What i remember the issue was about not adding more gui stuff at that time, because of the build system being very strained.

   I tried to add some qvcp configs

   On 24 Jun 2016, at 20:23, Bas de Bruijn notifications@github.com wrote:

   On 24 Jun 2016, at 19:13, Michael Brown notifications@github.com wrote:

   But this is not My Call as I was not part of the deciding around the
   externalisation of the qt stuff.

   I'm sorry, I don't see the connection. Qt has nothing to do with configurations or HAL
   —
   You are receiving this because you commented.
   Reply to this email directly, view it on GitHub #177 (comment), or mute the thread https://github.com/notifications/unsubscribe/AKifnEBxAI49r3Eopu08kuZuCbBWEBYqks5qPCCygaJpZM4I9zZY.
7. machinekoder commented on Jul 16, 2016

   

   machinekoder

   on Jul 16, 2016

   MemberAuthor

   More actions

   To clarify: The config itself is not UI specific, I See no problem in adding additional configs to the Machinekit repo.
8. cdsteinkuehler commented on Jul 16, 2016

   

   cdsteinkuehler

   on Jul 16, 2016

   Contributor

   More actions

   I agree with adding 3DP content to the docs as well as adding some stock configurations that use the FDM-Standard and/or migrating the existing 3DP configs to use the FDM-Standard.