January 26, 2020, 04:41:29 AM
Welcome, Guest. Please login or register
News: Stay up to date with everything that's happening at http://plus.digitalsignage.com

MediaSignage support forum



Author Topic: API Monster Signage Development Kit and SDK , Examples  (Read 4046 times)

paulie

  • Newbie
  • *
  • Posts: 36
  • Karma: +0/-0
    • View Profile
API Monster Signage Development Kit and SDK , Examples
« on: August 19, 2013, 04:38:22 PM »
Does anyone have working examples on what can be actually done with the API Monster Signage Development Kit and SDK?

I'm just trying to see if anybody has successfully achieved using it to assist with there business model.
Does DS have any clients that will be happy to show what can be achieved with it?
We have a few ideas on how we would like to use it in the future and may need to source developers that already used it.

criley

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 598
  • Karma: +15/-0
    • View Profile
Re: API Monster Signage Development Kit and SDK , Examples
« Reply #1 on: August 19, 2013, 05:32:48 PM »
The problem is that we are not sure what changes if any will be made as it is a new system that is being designed.

admin

  • Administrator
  • Hero Member
  • *****
  • Posts: 5032
  • Karma: +35/-8
    • View Profile
Re: API Monster Signage Development Kit and SDK , Examples
« Reply #2 on: October 06, 2013, 08:46:26 AM »
A new API is 100% complete and we are finalizing interfaces in HTML5 / JS for late November public release.
It exposes 100% of the Studio capabilities.
And, we will release an open source ultra easy to use SignageStudio called StudioLite which is powered by that API.

Some great stuff coming...

mediaboy

  • Newbie
  • *
  • Posts: 38
  • Karma: +3/-0
    • View Profile
Re: API Monster Signage Development Kit and SDK , Examples
« Reply #3 on: October 28, 2013, 08:45:42 AM »
@admin – looking forward to this exciting development opportunity, as I'm sure many other Enterprise customers are out there. Any chance you could publish some of the API documentation in advance so we get a heads up of the API scope? If we have an idea of the API endpoints/authentication methods/granularity of the system it may help us ascertain how much development time/internal resource us Enterprise users will need to allocate to build a custom solution. We're already allocating internal resource for December projects, so having to wait until the end of November to review how much work this requires would mean we'd probably not start until the end of January at best.

 

Carbonate design by Bloc
variant: carbon
SMF 2.0.12 | SMF © 2016, Simple Machines