On Dec 12, 12:59*am, Max Kellermann wrote:
Westbender wrote:
I haven't gotten that far yet. I don't think there's any reason why
the source code can't be released, although I don't know why that
would be important.

For people who don't run 32 bit Windows on an Intel CPU.

For people who don't to run "untrusted" closed-source software.

Practical example: I want to download and verify the flight from the
Cambridge with my Streak running Android. *The Streak has an ARM CPU,
so even if I wanted and even if Windows would run on it, there would
be no chance to use your DLL. *None of my computers runs Windows,
anyway.

The majority of devices sold currently have an Intel CPU, and the
majority of devices sold currently don't run Windows.

If you're not convinced that disclosing and freeing the source code is
important, I can elaborate more.

Max

Downloading a flight from a Cambridge 10/20/25 has nothing to do with
this effort. I am not proposing that, nor am I trying to solution
that. If you're talking about the cai 2 igc conversion process, that
is being done by leveraging the existing vali-cam and conv-cam
utilities from Cambridge. They are currently limited as to what OS
they will run on. I also am not trying to solution any alternatives
for that. I am only trying to provide a solution for 10/20/25 owners
to be able to continue posting their flights on the OLC....period! If
that means it's bound by the same OS limitations that has been in
place up to today for these loggers, then so be it. A limited means is
better than no means. Let's not try to make a mountain out of a mole
hill.