I would like to be able to have multiple UIViews (like with native tabs) but WITHOUT the tabs.
The reason is, there are many cases where it would be advantageous to maintain multiple independent UIViews, but at the same time, native tabs might not be desired.
As it is apparently implemented with multiple UIViews which are hidden/shown above a native tabbar, it should be a simple matter to use the existing code with a the setting of some option to simply omit the tabbar and enlarge the size of the UIView. It would then be up to the developer to provide their own (HTML) UI (or none at all, depending on requirements) for switching between the views using Webview.navigate with a window ("tab") number.
I can modify the code myself I suppose, or else write a small native extension to kluge it to remove or hide the tabbar and expand the height of the UIView. But as this has general utility, it would be good if it were a part of the platform.
This should be really easy to implement, and would be VERY useful! I've requested it before, but seems to have fallen on deaf ears. Maybe now with seemingly greater effort being made on new features, this is something that can be considered.
Post by Dmitry Soldatenkov on Jan 7, 2017 1:00:07 GMT
I think we can add "invisible_tabbar" option for current TabBar - in this case we will all the same with current TabBar but without visible TabBar on screen. It should be investigated on Android too - I think it is possible. What do you think about it ?
Best regards, Dmitry A. Soldatenkov E-mail: email@example.com Skype: soldatenkoff
Dmitry, that works for me! Whatever way makes it possible.
I've had use cases for this in the past but It happened that the tabbar worked-out for that case, but now it is a less-favored UI, and by being able to get rid of (or hide) the tabbar, then the means for initiating the switch is completely open to whatever is now in fashion (or what makes sense for the app).
I think whatever limitation on quantity that is currently present is fine, as I think this makes sense only for a very small number of UIView. Otherwise, it is abusive and some developers will try 10 or 100 and then they will blame you for the poor performance.
I can see it very useful for chat and map windows for example.