We just made our first weekly release today, in the coming weeks when you send a build or update the client
libraries you should get a new version every Friday. We hope this will help us provide better consistency between
the docs/device builds and the simulator.
We finally completed the overhaul of the developer guide which now clocks at 732 pages. This doesn’t mean the
guide is perfect or covers everything there is but rather that we covered the bigger pieces and reviewed the whole
document for accuracy and relevance. There are still big pieces we’d like to add e.g. a section about the common
cn1libs is something that I would personally like to see.
|
If there is something you feel isn’t covered properly in the docs let us know in the comments below or just edit the wiki directly! |
Now that the guide is complete and the JavaDocs are far improved we are targeting better videos for the website and
IntelliJ support. We are still overworked with the new Windows port so that is slowing our general progress on
everything else.
JavaScript Promotion Ended
We ended the JavaScript build promotion
we started last month. If you were a pro user and remain a pro user
you should have that ability into 2017. Everyone else now needs an enterprise license to enjoy that feature.
Notice that if you let your subscription lapse you might lose this ability since we won’t have a way to distinguish your builds
from everyone else.
4 Comments
Good to hear there’s progress on the WP port. Is it already possible to predict when we can expect the first release? 🙂
One of the reasons we didn’t want to go into this whole mess is the level of complexity. We put in a tremendous amount of work and are still at a stage where we might need to throw everything away and start from scratch!
We are trying to take a shortcut that would save us the need to port ParparVM to Windows, if we need to go thru that route it could take quite a while.
I think you don’t need ParparVM for Windows port because gc is implemented internally in C# and this is main advantage od ParparVM for iOS.
If we would go with ParparVM (which we probably won’t as we made good progress with iKVM) we would use C and not C#. We had a horrible experience when translating Java bytecode to C#. They differ at just the right amount to make translation darn near impossible.