Table of Missing Features
Posted: Fri Jul 23, 2021 7:51 am
This may sound like someone denigrating LC, but that's not my intention.
Considering that as a cross-platform app LC has 7 different "runtimes" (if we include Raspberry Pi) and not all features work on all runtimes (though it may be as high as 95% do work on all runtimes), wouldn't it be an idea to maintain a list of those edge cases where this is not so? My reasoning behind this is that someone might only discover one of the edge cases some 100s of hours into development. If the edge cases were known in advance, then one could design an app differently up front.
For example, for 7 years "system date" doesn't work on Android. https://quality.livecode.com/show_bug.cgi?id=11726
There are ways around this, but it might be better that someone starts off using that workaround early on rather than late in the day. Obviously many/most of these edge cases may be noted in the documentation somewhere, but with 1000s of pages of documentation, any one of us might not stumble upon that note until the hours of development are gone.
Moreover, the table of exceptions might help LC Ltd focus on some of those exceptions. I'm not suggesting that the years of something not working be highlighted in the table, just the fact of where it doesn't work.
Considering that as a cross-platform app LC has 7 different "runtimes" (if we include Raspberry Pi) and not all features work on all runtimes (though it may be as high as 95% do work on all runtimes), wouldn't it be an idea to maintain a list of those edge cases where this is not so? My reasoning behind this is that someone might only discover one of the edge cases some 100s of hours into development. If the edge cases were known in advance, then one could design an app differently up front.
For example, for 7 years "system date" doesn't work on Android. https://quality.livecode.com/show_bug.cgi?id=11726
There are ways around this, but it might be better that someone starts off using that workaround early on rather than late in the day. Obviously many/most of these edge cases may be noted in the documentation somewhere, but with 1000s of pages of documentation, any one of us might not stumble upon that note until the hours of development are gone.
Moreover, the table of exceptions might help LC Ltd focus on some of those exceptions. I'm not suggesting that the years of something not working be highlighted in the table, just the fact of where it doesn't work.