Comment by Toxip
Sailorgram doesn't necessarily need one since the Telegram one doesn't either. There are only a few options that it needs and they should fit nicely in pulley.
View ArticleAnswer by itdoesntmatt for Silica tab component
we really need a sort of this implementation or alternative one in Silica. Apps with a lot of potential options (eg sailorgram) are too strict with just pulley menu..
View ArticleComment by Toxip
They are indeed buttons and they should be to help people who are still learning the system but their primary purpose is act as indicators that there's a page that can be found by swiping. Using them...
View ArticleComment by chemist
@Toxip but that is what you are asking for... well I rethought it to fit the design as a tab-bar is bloat, and I do not understand how "more hidden" indicators are better to understand?! Dots that add...
View ArticleComment by Toxip
@chemist I disagree. The current system gives a stronger visual cue for the user that it is possible to swipe left or right. The breadcrumbs was indeed handy but didn't have as strong a visual cue as...
View ArticleComment by chemist
@Toxip what @r0kk3rz said - possibility to assign icons to pages instead of just showing dots, and yes return to pre-Uitukka, that is needed anyway (not knowing how deep you are in pages slows me down)
View ArticleComment by r0kk3rz
sounds like a return to what we used to have Pre-Uitukka, with multiple dots on the left and right edge which showed where in the page stack you were...
View ArticleComment by Toxip
could you elaborate this a bit? I'm not sure if understand what you're after.
View ArticleAnswer by chemist for Silica tab component
IMHO I'd like it much more without actual tabs. My idea be that pages can have specific types of `dots`(*icons instead of dots*) indicating what is stacked left and what is coming to the right. So an...
View ArticleComment by Toxip
This is an example of how not to do it... The tab bar should only be on the main page and the page shouldn't have any other pages on the stack unless when you tap on something. It shouldn't be used...
View ArticleComment by ossi1967
This application is a particularly bad exaple: There's no need for this complicated structure in the UI at all, it would have been better to have all the settings in one page. Come think of it it's a...
View ArticleAnswer by BirdZhang for Silica tab component
You need SlideshowView :) Checkout :https://github.com/steffen-foerster/sailfish-barcode/blob/master/qml/pages/SettingsPage.qml
View ArticleComment by ron282
I had exactly the same question one year later. Tabs are present in Android, iOS, Window Phone. They avoid using a list of items to access to the distinct tabs. Navigation is faster with swipe between...
View ArticleComment by Toxip
It's not uncommon usage of the tab bar. For example on iOS, the tabs are solely used on the main page. Pulley menu is not very handy for navigation between many pages. Pulling the menu to keep...
View ArticleComment by Toxip
should probably be placed in the bottom instead of top after all for easier navigation.
View ArticleComment by AliN
If we restrict developers to use tabs only on the main page, so no need to a new componant; they can currently use pully menu, or horizontal pages instead of tabs. Horizontal pages will work like tabs...
View ArticleComment by r0kk3rz
Whilst I agree that having vendor supplied Silica components is a good thing, but if a developer wants this kind of UI its not impossible to create and they can always share the code for it for other...
View ArticleComment by Toxip
@r0kk3rz Indeed some have already created such a UI, but having a vendor supplied Silica component would unify those and have one single tab bar component everyone could use. This would reduce...
View ArticleComment by Toxip
@ossi1967 maybe I wasn't clear enough. I didn't mean that it would be possible to swipe to a sub-page from the main page because that would just make it more confusing and have two conflicting...
View ArticleComment by ossi1967
@Toxip at least the way you describe it makes it sound confusing to me. You original post indicates that it should be possible to swipe from a tab to a sub-page. This made me ask how one...
View ArticleComment by Toxip
@ossi1967 the tab bar animation would distinguish them and the light ball indicates when the left swipe moves backwards or forwards. However it shouldn't be used anywhere else but the main page because...
View ArticleComment by ossi1967
@toxip How would you distinguish between a 'move to next tab' gesture and a 'show next page' gesture? It's both a swipe sideways, isn't it?
View ArticleComment by Toxip
@AliNa it won't if it's done properly and conveyed to the user. A good example how it's done well is tweetian.
View ArticleComment by AliN
@Toxip and this left- and right-swipe will be mixed up with back/forward gestures. However, I think SimpleWeather with multiple cities is a good example.
View ArticleComment by Toxip
@ossi1967 I don't see how tab bar is the SFOS philosophy. Quite the contrary, they would fit well in the gesture centric UI. You could swipe left and right to switch between the tabs.
View ArticleComment by Toxip
@r0kk3rz that is indeed possible it has a drawback. The user doesn't know where on the stack and has to learn where each page is. With a proper tab bar, you can see where you are and wont get lost. HN...
View ArticleComment by r0kk3rz
nothing stopping a developer pushing several pages onto the stack and persisting them as a tab-like structure. Navigation by scrolling left and right.
View ArticleComment by ossi1967
I'm not sure I understand. When would you need such a component? I've seen a tab-like UI once and it felt out of place. It was nothing that couldn't have been placed in one longer flickable page... or...
View ArticleSilica tab component
The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has...
View Article