FreeCAD Legacy Migration: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
Line 22: Line 22:


=Costs of Not Using the Latest FreeCAD Version=
=Costs of Not Using the Latest FreeCAD Version=
* You'll copy and paste snippets from Googling help online and they won't work for you because they're only available in a later version of FreeCAD
** '''Real Example:''' <code>firstVertex</code> and <code>lastVertex</code> methods don't exist in FreeCAD 16. Had to use alternative. See [https://forum.freecadweb.org/viewtopic.php?t=22500 the following thread for details]
* Less help on the FreeCAD forums
* Less help on the FreeCAD forums
** According to the [https://forum.freecadweb.org/viewtopic.php?f=3&t=2264 FreeCAD Forum Rules], you must "Make sure your FreeCAD version is up to date" before posting.
** According to the [https://forum.freecadweb.org/viewtopic.php?f=3&t=2264 FreeCAD Forum Rules], you must "Make sure your FreeCAD version is up to date" before posting.

Revision as of 02:04, 4 May 2020

Introduction

This page is meant to document the motivation of why OSE should migrate away from FreeCAD 16 or FreeCAD Legacy.

Motivation

The is motivation for migrating away from FreeCAD Legacy.

FreeCAD 17 Features

  • Addon Manager - Vastly simplifies installing additional workbenches and macros
  • Part: Attachment - Links, or attaches objects parameterically which means that if the attached-to object's placement changes, then the attached object will update it's position automatically.

FreeCAD 18 Features

FreeCAD 19 Features

Python 3 Features

Costs of Not Using the Latest FreeCAD Version

  • You'll copy and paste snippets from Googling help online and they won't work for you because they're only available in a later version of FreeCAD
  • Less help on the FreeCAD forums
    • According to the FreeCAD Forum Rules, you must "Make sure your FreeCAD version is up to date" before posting.
    • I was told on my first post for help on the forums that my versions were "obsolete" and I should be using the latest. See the following post and reply.
  • Additional overhead of writing Python 2 and Python 3 compatible code

Python 2 Is No Longer Supported!!!

Python 2 was sun-setted on January 1, 2020. That means the Python Software Foundation will not improve it anymore after that day, even if someone finds a security problem in it. You should upgrade to Python 3 as soon as you can.

See Also: https://www.python.org/doc/sunset-python-2/