NimbleKit 1.6.2 is released!

[Alexander Voloshyn]

Changes in version (v 1.6.2)
New functions and improvements:

1. JSON support
2. Method setMaximumBuffersCount for NKInternetPlayer
3. setDelegateCallback for NKMapView to receive notification about map
loading progress
4. getTabPositionsArray method for saving/restoring Tab Controller
user-rearranged tabs
5. NKSettings now can save and load javascript objects

Bug fixes:
1. Fixed disappearing of views with flipleft/flipright and
fastpushleft/fastpushright are mixed in NKMoveToPageAnimated
2. onPageShow not always called is fixed now
3. [NKBridge sharedInstance] fixed, which also fixed OnApplicationQuit
and all the methods using it in obj-c/js mix
4. NKInternetPlayer extended memory usage fixed, memory usage greatly
reduced.

[Andrew Waters]

Jumping on it now :P

> --
>
> You received this message because you are subscribed to the Google
> Groups "NimbleKit" group.
> To post to this group, send email to nimb...@googlegroups.com.
> To unsubscribe from this group, send email to nimblekit+...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/nimblekit?hl=en
> .
>
>

[Orien Colmer]

nimblekit is getting some press here:

http://apprejections.com/index.php/post/63

Someone who knows the inner workings should probably clarify the
questions they've asked over there.

-- Orien Colmer
-- Stickybuzz.com

[Alexander Voloshyn]

I'm sorry, but I find this article just stupid, very simple investigation can prove NimbleKit does not use any private APIs and abstract discussion without knowing a thing about topic is pretty lame.

The situation happened when some NimbleKit APIs were given same names as Apple's APIs fixed by simple renaming.

The answer I posted on the topic:

My name is Alexander Voloshyn and I’m the developer of NimbleKit framework. This situation is a simple misunderstanding, those API names are NimbleKit APIs and not Apple’s private. Think now by yourself, how would you call the method which sets parameters? I think that Apple is very wrong in this situation as private APIs should have special names like “setInternalPrivateParameters” or something complicated which can not be the same as half developers would call their methods, for instance Microsoft calls their private APIs with 2-3 dashes at the beginning of the name, so they are sure people won’t call functions like that. However this has been already changed, I renamed NimbleKit APIs to be setNKParameters, setNKCurrentPage, setNKWebView, etc so now this is solved and application won’t be rejected anymore. This is not big deal or problem, if you NimbleKit user all you have to do is update and resubmit your application.

_____

Alexander Voloshyn

[Orien Colmer]

Yeah, that's what I thought, so I wanted to make sure you had a chance
to respond to it.

--O