API Change Notification

  • 3
  • Idea
  • Updated 3 years ago
If not already implemented, it may be worthwhile for Flex to publish contemplated API changes (and some non-API  components) in advance of any SSDR release as part of its FlexADP partnership program.  This would give 3rd-party application developers advance notice of any upcoming SSDR change(s) that will impact the performance their programs.  In doing so, a developer is constructively placed on notice of a future change, allowing him or her to modify their application rather than discover a compatibility issue on the day of a new SSDR release.  Flex need not contact these developers; the onus is placed on the developer to check a designated area on the Flex website concerning upcoming changes.  If this is already part of the FlexADP program, that's great and please ignore this request.  Many thanks.

Paul, W9AC
Photo of Paul Christensen, W9AC

Paul Christensen, W9AC, Elmer

  • 319 Posts
  • 135 Reply Likes

Posted 3 years ago

  • 3
Photo of Mark - WS7M

Mark - WS7M

  • 1026 Posts
  • 364 Reply Likes
I was hoping to see an updated API and Wiki too.  The Wiki needs serious work as many pages are completely missing.
Photo of k3Tim

k3Tim

  • 849 Posts
  • 166 Reply Likes
Photo of Mark - WS7M

Mark - WS7M

  • 1026 Posts
  • 364 Reply Likes
Ok that was NOT there when I checked yesterday...  Thanks Tim!
Photo of k3Tim

k3Tim

  • 849 Posts
  • 166 Reply Likes
Hi Mark,

There seems to be no indication on the download lists this is available. I found it by using the next / previous in the download page.

k3Tim
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9152 Posts
  • 3478 Reply Likes
You can find all 1.6.17 related software by searching on the version number.
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 718 Posts
  • 211 Reply Likes
Good idea about notification of API changes.  While we don't send anything out like this today, we do avoid breaking backwards compatibility if we do have to change an API.  This is definitely an area where we could improve our communication.  I'll run this back to the team and we will try to come up with the best way to do this.  Thanks for the idea.  #2875
Photo of Steve - N5AC

Steve - N5AC, VP Engineering / CTO

  • 1031 Posts
  • 1002 Reply Likes
Paul, this is a completely valid request.  I think some of what you're seeing is growing pains.  We are working with several of the active developers to get them advance information, but we've not been as good at keeping the wiki updated.  We've pulled some developers into the Alpha program almost as self-defense (so they get information as quickly as we have it and can test against the apps).  Unfortunately, there is a cost to having too many people on the Alpha team and we've resisted adding every developer to the team.  There is no "hurdle" to becoming a developer on our platform since there is no cost, the API is open, etc.  We could easily end up in the same situation other companies have where people join the developer program simply to have early access to code and then become a support burden.  So I'mm spend some time thinking about how we can do this better.  I do want to continue to increase our support for developers, especially if I can do it without a huge additional load on our team.
Photo of Johan Schepers

Johan Schepers

  • 13 Posts
  • 3 Reply Likes
When I my own app's recompiled with the new DLL”s, there where different
problems.

I have via “Try and Error” my app's rewritten.

A list of changes would be nice...


Johan PA3AIN

Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 718 Posts
  • 211 Reply Likes
Johan,

If you are using the FlexLib library, the source is available on the download page.  You could certainly download versions and run a diff across them to see any relevant changes to the DLL source if that would help.

Again -- we hear you loud and clear that an API change document upon release would be nice.  Thanks for chiming in and for using the API.
Photo of Robbie - KI4TTZ

Robbie - KI4TTZ

  • 480 Posts
  • 77 Reply Likes
I use git to see the differences.  Just commit the prior version to a new local repo, then overwrite with the new files and use a gui GIT app like Sourcetree (it's free) to see what has changed.

Then the next time a new flexlib is released, commit the changes from the prior release, and repeat.
Photo of Mark - WS7M

Mark - WS7M

  • 1026 Posts
  • 364 Reply Likes
Hi Eric,

Thanks for chiming in on this thread.

Is there a particular reason that when the API is downloaded there is no master solution to group the projects for a build?

I realize you can copy the individual projects over to your project and reference them but it is still nice to know the primary API builds.  I've created my own solution for this but just wonder why that is the case?

Also the lib references ionic.zip which is not supplied with the lib.  Novice API users might not know where to get that.  I would also suggest as part of the API change document perhaps a section on preparation to build and what you need to get and where.

Thanks again for a wonderful product.  Lots of fun to work with.