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



TextView


TextView It's a simple class to show a piece of text. You can specify its font, size, bold, italic and color.

Basic usage

<TextView Id="MyText" Text="Hello World!" />

// Or you can create it using C#:
this.Add(new TextView { Text="Hello world" });

Width

Like all other Zebble objects, the width of a TextView is determined by the general width rules, which means an even allocation of width among horizontal siblings. But if you want the TextView to take only the space needed by its actual text string and font, you can set AutoSizeWidth to true.

MarkUp:

<TextView Id="MyText" Text="Hello World!" AutoSizeWidth="true"
Style.Border.Width="2" />

 

<TextView Id="MyText2" Text="Hello Galaxy!!" AutoSizeWidth="false" Style.Border.Width="2" />

 

 

Enabled & Ignored

Stylesheet has a boolean property named Ignored, which is false by default. When set to true it works the same as "display: none" in HTML. It means that the element will not only be invisible, but also it won't occupy space on the screen.

View has a boolean property named Enabled, which is true by default. When set to false the object will not respond to UI gesture events. But it will remain visible. Also, its PseudoCssState will be set to "disabled" which allows you to specify a visual style for it in CSS.

MarkUp:

<TextView Id="MyText" Style.Height="20" Text="TextView 1" />
<TextView Id="MyText" Style.Height="20" Text="TextView 2" Enabled="false" />
<TextView Id="MyText" Style.Height="20" Text="TextView 3" />
<TextView Id="MyText" Style.Height="20" Text="TextView 4" Ignored="true"/>
<TextView Id="MyText" Style.Height="20" Text="TextView 5" />

PseudoCssState

PseudoCssState is a boolean value that if it will be set to "disabled", it allows you to specify a visual style for it in CSS.

 Font and color

MarkUp:

<TextView Id="MyText" Text="Hello World!"
Style.TextColor="#AA00BB" Style.Font.Name="Arial"
Style.Font.Bold="true"/>

Box Shadow

Zebble components have a special effect which is named BoxShadow. As you can see in next image, it has start X and Y position for effecting and the amount of radious.

MarkUp:

<TextView Style.Height="40" Text=" TextView 1" Style.BoxShadow.Color ="red" Style.BoxShadow.BlurRadius="5" Style.BoxShadow.XOffset="5" Style.BoxShadow.YOffset="5" Style.Border="1"/>

Wrapping

TextView has a method named ShouldWrap() which determines whether the text should be wrapped. By default, it will return true when the text size is larger than 20 characters. But you can override it by setting the Wrap property manually.

<TextView ... Wrap="true"/>

 

 

Text

<TextView Id="MyText2" Style.Height="30" Text=" TextView 2" Style.Border ="1" Style.TextColor="gold"/>

 

 

 

<TextView Id="MyText5" Style.Height="30" Text=" TextView 5" Style.Border ="1" TextAlignment="Middle"/>

 

 

 

Position

 MarkUp:   <TextView Id="MyText6" Style.Height="30" Text=" TextView 6" Style.Border ="1" Style.X="100" Style.Y="300"/>

TextTransform

You can set a text transform value to the style or css settings of a text view. When you do so, the original Text value will hold the original casing, but when rendered on the platform, the transformation will be applied. It works just like html.

The supported values are

  • None (same as the original text)
  • Uppercase
  • Lowercase
  • Capitalize (first letter of each word will be upper case).

<TextView Id="MyText1" Text="Hello World!"
TextTransform="None"/>

 

 

<TextView Id="MyText2" Text="Hello World!"
TextTransform="Uppercase"/>

 

 

<TextView Id="MyText3" Text="Hello World!" TextTransform="Lowercase"/>

 

 

 

<TextView Id="MyText4" Text="hello world!" TextTransform="Capitalize"/>

 

Css settings

In addition to all common CSS settings such as border, padding, margin, etc, the following css settings are supported specifically for text view and its descendants such as Button:

.my-selector {
   color: #553300;
   text-transform: uppercase;
   font-family: 'Arial';
   font-weight: bold;
   text-align: center;
   vertical-align: top;
}

You can set the Css of text view object by following below:

<TextView Id="MyText" Text="Hello World!" CssClass="MyTextClass"/>

Events:

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



‹
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