Skip to main content
D
DavidBigelow17-Peridot
17-Peridot
June 2, 2017
Question

JSON Interface to CREO - Intro

  • June 2, 2017
  • 5 replies
  • 5939 views

Just as an update.

The creoson.com site is now up for the introduction of what CREOSON is and how it basically works.

CREOSON - OpenSource Automation Interface for PTC's CREO Parametric!

We are looking forward to your feedback.  The example shown on the site is a prototype interface for Node.js Applications to demonstrate the core principles of remotely manipulating CREO Parametric. The same principles apply to any language (or scripting environment) you want to use.

NOTE: This has NOTHING to do with PTC.  It is an OpenSource project using code we have developed and shipped over the last 10+ years.  So please don't call PTC for support on this, they will not help you.

If you want to help this project move forward, there is a list of things we would like input on... Fill out the Google Form at the base of the site page.  The site will be eventually replaced with something more worthy of handing development / documentation / education in the future.

Thanks in advance!

Dave

    5 replies

    S
    sjuraj15-Moonstone
    15-Moonstone
    June 2, 2017

    Where can I find source ?

    D
    DavidBigelow17-PeridotAuthor
    17-Peridot
    June 2, 2017

    We are currently working through the details of "how" to properly OpenSource this... if you have any suggestions please throw them out.  We "may" release a Node.js module also to play with at the same time (depends on our workload).  But Javascript and Node.js are VERY popular these days - very flexible.  But that stack has its own issues and learning curve.  Other languages (e.g. php, Ruby, Python, etc...) may be easier for people to use and learn.  <--- THIS is what I am specifically excited about, I think people are going to come up with some amazing things using other languages and integrations that we have not thought about.

    We think that GitHub would be the primary way to go - but it does not have the best "control mechanisms" as far as we can tell to manage things to the resolutions we would like to see.  It is important that no other code get into the distribution that is not tested and/or also OpenSource. Specifically - we are NOT permitted to distribute any PTC Code... so we have to protect/manage that.  Still talking about this internally.  ANY SUGGESTIONS?

    The generic JSON microserver and application framework for CREOSON is already developed and we are testing that currently.  The stuff that is missing is purely on our side - churning all the high-level interfaces to take the last 10+ years and make it available via this new JSON interface. We are trying to schedule the work around a commercial release we are behind on (the latest release of Nitro-CELL).

    More to come.... Stay tuned. 

    Thanks for your interest!

    Y
    YaroslavSin17-Peridot
    17-Peridot
    June 2, 2017

    Looks interesting. New, fresh, OPEN SOURCE! But, I have mixed feelings. Maybe it is a little easier then using PTC API, but not very for end users. Hope I'm wrong. In any way it is very good initiative. Good luck!!!

    ps: Yes, how to try?

    D
    DavidBigelow17-PeridotAuthor
    17-Peridot
    June 2, 2017

    Stay tuned...  We will be pushing forward on this soon... I hope we can get something out there initially within the next few weeks if possible.

    We have a LOT of functionality that we have built up over the years... So we may start with the obvious things and then dig deeper into more functions later.

    T
    TomasLoun1-Visitor
    1-Visitor
    June 2, 2017

    Nice, but what was the reason you did not choose Pro/Toolkit or Object Toolkit?

    T
    23-Emerald IV
    TomU23-Emerald IV
    23-Emerald IV
    June 2, 2017

    Both of these toolkits are very expensive and most small companies cannot afford them.  J-Link is included out of the box and requires no extra cost.

      J
      James621-Visitor
      1-Visitor
      June 2, 2017

      Nice. Really interested to try it out.

        D
        DavidBigelow17-PeridotAuthor
        17-Peridot
        June 13, 2017

        CREOSON Update...


        Documentation is one of those critical things that we have always struggled with delivering cleanly and efficiently.  The biggest problem has always been delivering documentation that is easy to find and use - and accurate to what you want to do.


        After a bit of thought, and since CREOSON uses a HTTP (Web) Server locally for the JSON Interface to CREO Parametric, we are doing to deliver the documentation via the same HTTP Server.  The documentation will include pretty much everything required to get going and use the JSON API - for the specific version you would download and use.


        We thought about hosting the documentation somewhere on the web, but that just seemed like a pain for users in the long run.  Specifically, as new functionality gets added, older distributions may be confused when things don't work properly -- because the user found the latest doc via Google and the current version on their machine is NOT that.  I know, that sounds like "duh" -- but it happens more than you can think.  This is an even bigger problem when inputs/outputs change within an API over time -- something we are striving to avoid.


        Here is the current plan:


            Application Services : http://localhost:8000/creoson

            Documentation: http://localhost:8000/doc

        This is not final yet, but we are working on it over the next two weeks.  We hope to have an initial beta out soon.  If anyone is interested in being on that short list -- please reach out.

        Dave

        Terms & ConditionsAccessibility statement