jeopard

4 ms·

1. 1.▲
   Developing a mobile cross-platform library in JavaScript(skyscanner.net)

   1 points by jeopard 13y ago|0 comments
2. 2.▲
   by jeopard 13y ago

   No, unfortunately, it needs polishing before open-sourcing it. If there's enough demand, I might consider it...
3. 3.▲
   by jeopard 13y ago

   In iOS, things are simple. The deallocating code is very concise and safe. Why having the performance overhead of smart pointers? On the other hand, it could be useful to have them in Java and avoid manual destruction. However, this wasn&#x
4. 4.▲
   by jeopard 13y ago

   Apportable doesn't let you build libraries. You can only translate whole iOS apps to Android.
5. 5.▲
   by jeopard 13y ago

   it's back up
6. 6.▲
   by jeopard 13y ago

   I'm sorry if this wasn't clear. The purpose of building this library was to have something which could be distributable to any mobile developer, not just the ones using Xamarin. If you did it through Xamarin, you could only give i
7. 7.▲
   by jeopard 13y ago

   It might, but unfortunately, you can't build a library with it. It only transforms whole apps. Apportable was investigated in the first part here http://www.skyscanner.net/blogs/developing-mobile-cross-plat...
8. 8.▲
   Developing a mobile cross-platform library in C++(skyscanner.net)

   47 points by jeopard 13y ago|44 comments
9. 9.▲
   Developing a mobile cross-platform library – Part 1. Exploring(skyscanner.net)

   3 points by jeopard 13y ago|0 comments