Zebble
  • About Zebble
  • Compare
  • Documentation
  • Themes
  • Plug-ins
  • Contact Us

    • What is Zebble?
    • Structure of a Zebble solution
    • Zebble Designer (UWP)
    • Installing - Introduction
    • Change log
    • Introduction
    • ViewModel development
    • VM.EXE
    • View development
    • Dialogs
    • Lists and Collections
    • Tips and shortcuts
    • List views
    • ViewModel testing
    • Automatic Views
    • View development process
    • Hello World - Core Concepts
    • Layout: Sizing & Positioning
    • Event handling
    • Navigation
    • Alerts, Dialog, Prompt and toast
    • View lifecycle
    • Managing Files & Resources
    • Config & Debugging
    • Forms
    • Page templates
    • Device API
    • Animations
    • Web Api - Part 1 (reading data)
    • Web Api - Part 2 (post and delete)
    • Web Api - Part 3 (server vs client domain model)
    • Gesture events
    • View class
    • Zebble Markup (.zbl files)
    • Data Binding and MVVM
    • Stack class
    • Sizing and positioning
    • Layout examples
    • ScrollView class
    • Page class
    • Styling in Zebble
    • CSS property mapping to Zebble
    • Supported selectors
    • Zebble CSS: Under the hood
    • Inline styling
    • CSS real-time updates
    • Dynamic expressions in CSS
    • Gradient background colours
    • CSS Pseudo-classes support
    • Using Bold and Light Fonts in Zebble
    • Rotation in Zebble
    • Using custom fonts in Zebble
    • Flashing on tap using AutoFlash
    • Button
    • Carousel class
    • Checkbox class
    • DatePicker
    • Drawing class
    • FilePicker class
    • Grid class
    • IconButton class
    • ImageView
    • ItemPicker class
    • ListView & Grid classes
    • OptionsList
    • SearchInput class
    • Slider class
    • Switch class
    • Tabs Class
    • TextInput class
    • TextView
    • TimePicker
    • TreeView
    • Waiting Indicator
    • WebView class (displaying html)
    • C# Methods and Properties Of UI Components
    • Nav.Forward() vs Nav.Go()
    • Passing parameters to the destination page
    • Going Back
    • Showing Popup pages
    • Waiting class
    • Hardware Back button (e.g. Android)
    • NavigationBar class
    • Tabs class
    • Caching (pages)
    • Navigation without event handler
    • Use the Windows version
    • Logging messages for Debugging
    • Debugging Zebble/Plugin
    • Exception handling in Zebble
    • Debugging layout and styles
    • Zebble Device API
    • Device.Screen and orientation (landscape | portrait)
    • Code that should run on a specific platform
    • Using Lamp (aka Flash, LED and Torch)
    • Using Compass (Smooth compass)
    • Using Accelerometer (device angle)
    • Using Gyroscope (device motion speed)
    • How to Vibrate the device?
    • Launching the device browser
    • Finding device model and manufacturer
    • Responding to System events
    • Handling device shake event
    • Permissions
    • Permissions declaration (manifest files)
    • Sharing
    • Prompt for rating the app
    • Finding if Internet connection is available
    • Device messaging (Make a phone call, send SMS or Email)
    • Showing a local notification
    • Copying to Clipboard
    • Accessing device contacts
    • Reading and writing into Gallery (albums)
    • Playing & Recording Audio
    • Cache and temp files and folders
    • C# async / await
    • Understanding Zebble Threading
    • Debugging - the StackTrace problem
    • Not awaiting (running in parallel)
    • Timer (interval / scheduled running)
    • Post-render changes to the UI (dynamic)
    • Introduction of Geo location
    • Map & Location Services
    • Launch directions to a location (external)
    • Getting current Location
    • Tracking user location
    • Device.Media: Taking and picking photos
    • Playing an audio file
    • VideoPlayer class
    • Augmented reality
    • Recording audio
    • Virtual Reality
    • Speech Recognition
    • Recording or picking video
    • Playing remote videos in iOS
    • Text to speech
    • Introduction to the importance of Mobile Testing
    • Why and what to test
    • Testing mobile apps on different devices
    • Testing mobile apps
    • Xamarin Profiler
    • Performance optimization
    • Moving a view to another container at run-time
    • Attaching custom data (tag) to objects
    • Saving a view as image
    • Naming best practices
    • Fastest way to update your nuget package
    • Tips for Clean and Brief code
    • Splash screen and icon generation
    • Advice for passing Approval
    • Options for iOS app distribution
    • Test Release (internal and UAT)
    • Application Icons in IOS
    • Submitting to App Store
    • Releasing to App Store
    • Crash reporting
    • Optimized Release Build
    • Android - Generating an APK for manual installation
    • Payment (subscriptions & in-app purchases)
    • Introduction to push notifications
    • Registration process (App)
    • Push notification setup - iOS
    • Push notification setup - Android
    • Push notification setup - Windows
    • Sending a push message from the web app
    • Introduction
    • Connecting Zebble to Web API
    • Installation
    • Creating an API class
    • GET APIs
    • Calling a GET API (in the mobile app)
    • POST, PUT, PATCH and DELETE APIs
    • Domain Model
    • Web API and Authentication
    • Versioning
    • Uniquely identifying installations (token)
    • Settings file: config.xml
    • Standard Zebble settings
    • Login/Register with Facebook
    • Creating a composite component / plugin
    • Creating a Zebble component using Html and Javascript
    • CustomRenderedView: Third-party native components / plugins
    • Mapbox
    • Naming considerations
    • Random problems?
    • Display Keyboard for Visual Studio Android Emulator
    • iOS goes mad?
    • Configuring a Windows phone for ad-hoc testing
    • Fixing Error DEP0001 : Unexpected Error: -2147009287 while deploying Windows UWP app on device
    • Fixing Error DEP0001 : Unexpected Error: -1988945906 while deploying Windows UWP app on device
    • Unable tp Connect to the Mac agent from Visual Studio
    • Can't connect to the Mac agent from Visual Studio?
    • Choosing the CPU architecture
    • Zebble CLI
    • How to add a Device API to Zebble source?
    • About Automated UI testing
    • What should we test in mobile applications?
    • Creating an Automated UI Test in Zebble



Tabs Class


 

Tabs is a horizontal stack for implementing Tab Menu. It is the base class for your customized TabMenu class. Each tab has a title and Icon and destination page name.

To use this component, install the Zebble.Tab nuget package. 
It's open source and available on GitHub. Also we welcome any contributions to enhace it.

 

Create a tabs control:

Note: This is usually done in the template, as opposed to each page. See the new project template for an example.

var myTabs = this.Add(new Tabs());Or in markup:

<Tabs id="myTabs"/>

Adding tab to TabMenu: 

myTabs.AddTab<Destinition page>("Title", Icon");

Example:  <Tabs Id="myTabs">
    <Tabs.Tab  Label.Text="Settings" Icon.Path="Images/Icons/Settings.png"></Tabs.Tab>
    <Tabs.Tab  Label.Text="Map" Icon.Path="Images/Icons/Map.png"></Tabs.Tab>
    <Tabs.Tab  Label.Text="Types" Icon.Path="Images/Icons/Types.png"></Tabs.Tab>
    <Tabs.Tab  Label.Text="Videos" Icon.Path="Images/Icons/Video.png"></Tabs.Tab>
    <Tabs.Tab  Label.Text="Share" Icon.Path="Images/Icons/Share.png"></Tabs.Tab>
    <Tabs.Tab  Label.Text="Check" Icon.Path="Images/Icons/Check.png" ></Tabs.Tab>
  </Tabs>

 

 

 

 

Note1: Based on the standard design, For iOS, tabs should appear at the bottom of the screen and for Android, it should be at the top of the screen, below the navigation bar.

 

Note2: If you want to seot other properties, you should use C# codes and then use them in your markup.

 

 

 

 

 

 

 

Tab with a custom action:

If your tab needs to do anything other than a simple navigation you can easily create it using the following method:

var customTab = myTabs.Add(new Tab("Tab text"));
customTab.Icon.Path = "images/tabs/my-icon.png";
// You can define the custom action here:
customTab.Tapped += Nav.Go<Pages.SomePage>(new { myParam = "..." });
You can also specify when this tab should be highlighted as "current".

if (...)
{
     customTab.Selected = true;
}  
Alternatively, you can specify a page type for automatic highlighting. This way whenever the Nav.Stack contains that page, then it matches that (regardless of the nav parameters) the tab will be highlighted. For example when the user is on that page, or if the user is on a sub-page of that page (with BACK being enabled on the nav bar).

customTab.TargetPageType = typeof(Pages.SomePage);

Events:

  • on-Flashed: Raised when the object is flashed.
  • on-Initialized: Raised when the object is created and rendered.
  • on-Initializing: Raised when the object is being created and rendered.
  • on-LongPressed: Raised when user clicked on the object for a long time.
  • on-PanFinished: Raised when user panned on the object.
  • on-Panning: Raised when user starts to pan on the object.
  • on-PreRendered: Raised when the object object is not started to rendered before rendering.
  • on-Swiped: Raised when user swiped on the object.
  • on-Tapped: Raised when user tapped on the object.



‹
Zebble is a product of Geeks Ltd , a software house based in London, UK. All rights are reserved.

Telephone: +44 (0)845 643 6229

Email: hello@zebble.net

Address: 66a London Road, Morden

Greater London, United Kingdom, SM4 5BE

Privacy Statement
Terms & Conditions
Contact Us