Thread Previous • Date Previous • Date Next • Thread Next |
But I don't see any way for supporting multipledifferent framework versions in an app, on a system that is designed tobe a single rolling release.
I've asked this before [1], but I've yet to receive a satisfactory response: What about the desktop? The killer feature of this new SDK, we've been told, is that it'll work on the phone and the desktop equally well. So,
1) Is the desktop moving to a rolling release? As an LTS-to-LTS kinda guy, I certainly hope not.
2) Will the SDK be kept up to date via backports or PPAs on the desktop? So far, it hasn't happened.
3) Will the SDK be completely backwards compatible? Obviously not -- the point of versioning it is to add features.
4) Will there be some way for apps to react to the framework they find themselves running under? So far I've heard "no".
Without any of these, we app authors have to (a) target a framework old enough to be on the oldest desktop we're interested (likely a LTS, and do you really want people using Ubuntu.Components 0.1 until 2016?) and (b) hope that the old frameworks are completely forward-compatible on newer images (they aren't). Already, I find that the only way to get my app to run both on a current device and the 14.04 desktop is to do Loader hacks to detect which framework is supported [2]. It'd be much better if there were a straight-forward way to do this.
Robert [1] https://plus.google.com/108747901910183509998/posts/GZLFqo3GJVS[2] https://github.com/rschroll/beru/commit/6ffc8f0a8f659afdce7b04ac3bb49ff58ae65563
Thread Previous • Date Previous • Date Next • Thread Next |