Jump to content

Pedro Rodrigues 1377186

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

1 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. To be clear on the safety of this project. It is nothing more than the exact same files the official source provides in an msi install able format. You should always check any and all downloaded files for viruses no matter the source. In the interest of full disclosure. The process of generating the installation file is 100% automated and open source. It uses features available in GitHub and Travis CI. I'm notified of any changes made to the upstream or official project. At that point I apply 3 patches to the project and push them to my fork on GitHub. From there on, no huma
  2. The installer files are generated automatically by GitHub. The code that does so can be peer reviewed at https://github.com/pedro2555/vatspy-data-project/blob/installer/.travis.yml
  3. Alex. Seriously, you are in a war of your own where everyone is losing. This was proposed in a pull request you rejected. https://github.com/vatsimnetwork/vatspy-data-project/pull/15 The source tree is exactly yours and advertised as such. Anyone with a little knowledge of git can verify it is the exact files you provide. You had all the chance to guarantee accuracy by choosing to accept a perfectly fine pull request (which ads no additional considerations to the current team). Yet. You rejected it. For no good reason. 'Out of project scope' you say. This was proposed in https:
  4. Just to advertise one click installs for VatSpy data files. Data is sourced from the official vatspy-data-update project and is regularly updated. Download the latest msi installer package from https://github.com/pedro2555/vatspy-data-project/releases install it and restart VatSpy. I may also provide help for those unsure how to have their updates pushed upstream. This was proposed to the upstream project, but was rejected. https://github.com/vatsimnetwork/vatspy-data-project/pull
  5. I'm providing a one click install to update the data files. Check it at https://github.com/pedro2555/vatspy-data-project. * Download it from https://github.com/pedro2555/vatspy-data-project/releases/download/0.0.2/win-installer.msi * Close VATSpy * Double Click the installer * Open VATSpy Enjoy!
  6. I'm providing a one click install to update the data files. Check it at https://github.com/pedro2555/vatspy-data-project. * Download it from https://github.com/pedro2555/vatspy-data-project/releases/download/0.0.2/win-installer.msi * Close VATSpy * Double Click the installer * Open VATSpy Enjoy!
  7. Easy there. All I meant to say was "someone has already done it, it works, it's open source, so why don't you look there before deciding to do all the work yourself?" There may be valid reasons for making your own from-scratch implementation, but you haven't stated any, and when talk about "reimplementing the wheel", I really mean that it's a good idea to either use what's already there, or be confident about your reasons not to. Thanks, I'm very glad you took it with right amount of salt. Yes. what ever is done already, providing the licenses are permissible enough to allow m
  8. I don't think I can adequately show my appreciation to the effort I see you put in. Thanks. You are correct, I haven't seen the NDA or have I been a member of the dev team. Nor do I want to read it or be a member of said team. With all due respect for their efforts. I appreciate the invite, and this is a discussion I had with a board member before, but I just want to send some patches.
  9. Thanks Nestor. NDAs and closed source, NO. But you can always change that. Couldn't you?
  10. Their source code is available in https://dev.swift-project.org/source/pilotclient/
  11. That is correct. Before AFV I could control on Linux. Since AFV I cannot get a solid setup. Mostly due to AFV current implementation.
  12. Thank you. Yes, it is a very valid implementation. It is in C++ which I'm not very familiar with. I'm sorry to pick you, but you started it. Since the invention of the wheel, we have engineered all kinds of wheels. Cart wheels, artillery wheels, flywheels, wire wheels, train wheels, just to name a few. Perhaps most notably, gears. There are many kinds of wheels, none of which is a replacement for the other. Inventing and engineering are not synonymous. None of the engineers that design the various types of wheels we have today, have invented the wheel or have tried to do so, yet
  13. I'm currently considering implementing AFV my self to control under Linux. Way out of my league at the moment so would highly appreciate someone joining in. Anyone interested in such attempt?
  14. Is there someone having success in running AFV under wine. I just don't seem to be able to get all dependencies right in the wine bottle.
×
×
  • Create New...