pros and cons knowledge fusion vs. nxopen
pros and cons knowledge fusion vs. nxopen
(OP)
What are the pros and cons of knowledge fusion versus nxopen?
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS Come Join Us!Are you an
Engineering professional? Join Eng-Tips Forums!
*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting GuidelinesJobs |
pros and cons knowledge fusion vs. nxopen
|
RE: pros and cons knowledge fusion vs. nxopen
Tightly integrated into NX. Connected to expressions, update, and object behaviour.
Needed to write CheckMate checkers (unless you're clever)
Cons of KF
Proprietary language, so harder to get help/support
Useless outside of NX
Strange syntax
Hard to connect to other existing software
Pros of NX/Open
Standard languages (C/C++, VB, Java, Python, etc, etc.)
Good free development tools
Easy to access vast numbers of other libraries (e.g. .NET tools, SciPy, etc.)
Easy way to get started (SNAP)
Cons of NX/Open
Harder to add new associative objects to NX (UDOs are complicated)
A bit harder to write CheckMate checkers
RE: pros and cons knowledge fusion vs. nxopen
Pro of NX/Open
Ability to generate code by journaling (recording steps in interactive NX)
RE: pros and cons knowledge fusion vs. nxopen
One of the biggest disadvantages of kf is it slow performance since its more of a demand driven language it first has to figure out the demand order if its child (objects) before creating any geometry. This was a major problem in the early stages of kf back in V17. Kf classes would need demandOrder.