Page 26 of 29 First 222425262728 Last
Results 376 to 390 of 428

Click here to go to the first staff post in this thread.
Thread: Open Letter to Frontier Developments

  1. #376
    As a follow up to the PM from last Wednesday I did sent to Zac. He stated that the ppl like Michael Brookes and co (my words the decision makers) where on holiday and would be back next year - this week I assume. I just sent him a new PM and asked him if perhaps some new information has become available - been able to contact MB etc, decision made, meeting(s) scheduled etc... Fingers crossed. I will keep you updated.

  2. #377
    To all that are whining saying this is cheating give me a break. Did we somehow invent spaceships but lose basic computer/internet functionality between 2016 and 3302. I can go on google and compare prices on items from across the world now, did we somehow lose this technology when we went into space? Put the API's back, people can choose to use them if they like.

  3. #378
    Commanders. We are all passionate about ED, otherwise we would not play the game and be here in the forums. We all have a right to voice our opinion - pro or against the open letter. A plea to you all. Can we please act in a civil manner and discuss the open letter in such a way that this thread is meaningful. The tone makes the music. The OP requested the same, lets try to abide/honour his wishes.

  4. This is the last staff post in this thread. #379
    Hey guys,

    As promised we've discussed the topic for you all, sorry for the delay in replys but today was the first available opportunity to review the thread.

    People are free to continue use of the existing companion app API, though please be aware this is something we hope to expand and improve on the future. Since we donít yet have a date for that, use of the existing one is fine, but we ask that you do so in a careful and considered manner Ė for example not polling it continuously. We will bring in guidelines and an approval process over time too, but for now please be aware that we will stop apps that are not well behaved.

    We are passionate about the development of community created content and very much see the value in the tools that are being created which is why we are happy for this API to be continued. As we have mentioned before, we would like to create a new API which allows tool developers support to create their own tools but this will not be a short term implementation and is instead something we are considering for future development.

    Thanks for your patience, we will keep you informed as and when we have more information to share.

  5. #380
    Originally Posted by Zac Antonaci View Post (Source)
    Hey guys,

    As promised we've discussed the topic for you all, sorry for the delay in replys but today was the first available opportunity to review the thread.

    People are free to continue use of the existing companion app API, though please be aware this is something we hope to expand and improve on the future. Since we don’t yet have a date for that, use of the existing one is fine, but we ask that you do so in a careful and considered manner – for example not polling it continuously. We will bring in guidelines and an approval process over time too, but for now please be aware that we will stop apps that are not well behaved.

    We are passionate about the development of community created content and very much see the value in the tools that are being created which is why we are happy for this API to be continued. As we have mentioned before, we would like to create a new API which allows tool developers support to create their own tools but this will not be a short term implementation and is instead something we are considering for future development.

    Thanks for your patience, we will keep you informed as and when we have more information to share.
    There you go, you can continue using what you've been using, they'll get around to making it better at some future point but until then, keep on using it, but do so responsibly, no constant polling, etc.

  6. #381
    Originally Posted by Zac Antonaci View Post (Source)
    Hey guys,

    As promised we've discussed the topic for you all, sorry for the delay in replys but today was the first available opportunity to review the thread.

    People are free to continue use of the existing companion app API, though please be aware this is something we hope to expand and improve on the future. Since we don’t yet have a date for that, use of the existing one is fine, but we ask that you do so in a careful and considered manner – for example not polling it continuously. We will bring in guidelines and an approval process over time too, but for now please be aware that we will stop apps that are not well behaved.

    We are passionate about the development of community created content and very much see the value in the tools that are being created which is why we are happy for this API to be continued. As we have mentioned before, we would like to create a new API which allows tool developers support to create their own tools but this will not be a short term implementation and is instead something we are considering for future development.

    Thanks for your patience, we will keep you informed as and when we have more information to share.
    Hi Zac,
    Thanks for your reply, we really appreciate that our thread was review.

    Be assured that we are not polling it too much, we always added in the client (EDCE then EDMC) some time out (Actually one minute) to prevent that.
    I cannot guarantee that it is the case for other clients I'm not aware of, but I'm not sure they are much there.
    EDMC is also open source so we can assure that they are no stollen informations for the player.

    It is easier for us to concentrate on one client republishing the informations to EDDN, those every third party developer is able to grab the informations, and your API is not pulled too much.

    As usual, if you need private intel about how we use it and what should be corrected in the API, feel free to contact us in private.

    Thanks

  7. #382
    Good news, thanks Zac.

  8. #383
    Originally Posted by Zac Antonaci View Post (Source)

    People are free to continue use of the existing companion app API, though please be aware this is something we hope to expand and improve on the future.
    Thanks for this!

  9. #384
    I know it is probably a squishy number, but is there any guideline as to what would be considered too much polling?

    Without a defined, even if loosely, limit app devs will be playing a guessing game when trying to apply this kind of non-functional requirement to their applications.

    Would hate for someone who, in all earnest was trying to put a limit on polling but didn't quite get it right, have their application summarily blocked/banned/whatever.

  10. #385
    Originally Posted by Zac Antonaci View Post (Source)
    Hey guys,

    As promised we've discussed the topic for you all, sorry for the delay in replys but today was the first available opportunity to review the thread.

    People are free to continue use of the existing companion app API, though please be aware this is something we hope to expand and improve on the future. Since we don’t yet have a date for that, use of the existing one is fine, but we ask that you do so in a careful and considered manner – for example not polling it continuously. We will bring in guidelines and an approval process over time too, but for now please be aware that we will stop apps that are not well behaved.

    We are passionate about the development of community created content and very much see the value in the tools that are being created which is why we are happy for this API to be continued. As we have mentioned before, we would like to create a new API which allows tool developers support to create their own tools but this will not be a short term implementation and is instead something we are considering for future development.

    Thanks for your patience, we will keep you informed as and when we have more information to share.
    THIS IS ABSOLUTELY BRILLIANT NEWS. Thanks for the fast response by PM AND creating a post here. Totally appreciated. I was in the car so I missed the PM/post but I'm exited. I do have a few additional questions but that can wait. Because I'm gonna open a bottle of very good wine perhaps even champagne to celebrate this. Don't drink and drive is a very good principle, don't drink and write is another one;-) Again thanks for the cooperation and its absolutely positively good news!!!

    I also would like to thank Anthornet who didn't give up after many other similar threads failed. I personally didn't think the outcome would be different then in the other cases but I've been proven wrong. CHEERS my friend!!! Currently drinking a glass of the good stuff and a toast to you !!!

    Also in this thread commanders have expressed there personal opinion about this API. Also (personal) statements have been made about whether or not FD would allow the usage of the iphone API and the natural/logical data sharing aspect involved with it - if commanders choose to do so. I think its important that now that we have an official statement by FD about the usage of the existing iPhone api that is water down the bridge and that we look forward - not backwards!!!


    Update: I forgot to mention the person who made the current situation a reality. Its commander Andargor as he created the first publicly available api based tool. "EDCE: Elite Dangerous Companion Emulator". The intention afaik was to make a proof of concept that could be used as a base by commanders. Eggplant! and Otis B. picked up the gauntlet and have updated their programs so that they kept working after every update like Horizons. Eggplant! created "EDAPI: Elite Dangerous API Tool" which integrates brilliantly with Trade Dangerous as he created a plugin for TD which is distributed with it. Otis B. created "Elite: Dangerous Market Connector (EDMC)" a tool now more or less a synonym for the api based tools. GREAT works guys, all three of you ;-)

    Added comment by Andargor from a later post.
    For the record, I was not the first to create an app that used the mobile API. In fact, there were a couple of people during and after the beta (summer to autumn 2014) that posted about tools they developed, but their posts were removed. Although they did not explain how the API worked at the time, which is why I did my research and published EDCE to show how it's done and help people develop great tools.

    It feels GREAT that we are now allowed - I'm assuming - to openly talk about these tools, link to them and promote them!!! All tools can be found on EDCodex

  11. #386
    Thank you for answer, Zac!

  12. #387
    Hey Zac ! Many Thanks for your anwsers ^^

  13. #388
    Thanks Zac, I'm glad this grey area has finally been cleared up!

  14. #389
    +100 to the Devs, Frontier and ...ofc... Zec!

  15. #390
    I'm in agreement. Either add these quality of life enhancing tools to the game or allow 3rd parties to run their own tools easily. They are all optional and no one has to use them if they think it will break their immersion.