All tagged java
DataBinding is one of those things that once you learn, you have no idea how you lived without it before.
Being one of the most important things you can learn about XAML, this lecture builds on the example that we have been building in previous lecture to complete an introduction to the Xamarin platform. After this, you will be much more efficient when creating and linking your interfaces to your apps’s logic.
So now you have read the data from the SQLite table into a list of C# objects that are ready to be listed into the user interface.
Now it is time to learn how to use ListViews, which will be the go-to element when you need to display a collection of data to your users.
Reading a database will be very straight forward, especially once you know how to establish the connection to the database, which you should already know thanks to our previous post.
All you have to make sure of now is that when reading, you get all that data in the correct format, not as a simple query to a database, but as an actual list of elements. So in this lecture I cover how to do exactly that.
Well, now that the Model is ready, and the database is created for both Android and iOS scenarios, there is nothing left for us to do but to start adding the functionality for the necessary requests inside of our application.
In this video, I start by explaining how to insert to the database, and how a specific usage of the using keyword will be rather important for you to understand.
In this video we create the C# class -or Model- that will represent the SQLite table that will exist in the database.
This class, of course, will also contain the properties that will represent all the columns in the table, as well as some attributes that will be very important for when the database is created.
When using SQLite inside of your applications, you will need to set the location for the database file.
In this video I cover what you have to do for the iOS scenario, which indeed will be slightly different from the Android one, which means that we will have two versions of the same code -one per platform- and that we will need to code some functionality in the platform-specific projects.
When using SQLite inside of your applications, you will need to set the location for the database file.
In this video I cover what you have to do for the Android scenario, which indeed will be slightly different from the iOS one, which means that we will have two versions of the same code -one per platform- and that we will need to code some functionality in the platform-specific projects.
So SQLite can be quite useful in a lot of scenarios. I believe most apps should use this light-weight version of a database, even when they rely on another cloud database for their information.
But before we learn how to implement SQLite into our apps, let’s first take a look at how can we add third-party functionality into our apps, so we don’t have to code SQLite functionality from the ground up.
Testing on an iOS Simulator is not as straight forward as on Android. You will find that it is still pretty easy but can get a bit confusing if you don't know about the restrictions that Apple sets, and how Visual Studio can help you meet those restrictions for your app to be able to run on a simulator, whether you are on macOS or Windows (this video covers Windows).
The iOS Simulator is quite easy to use, but here is the process you should follow.
The Android simulator can be tricky, here is what you have to do to make your app run perfectly in one of those.
Navigation is crucial in all applications, you better get it right, here is what you should do.
Toolbars and Toolbar items are awesome if you ask me, they look great on both Android and iOS apps.
What if you want to use a different page as the starting page of your project? Basically replacing the MainPage for something else? Here is how to do that.
Handling button clicks is super important to build any app, here is how do do it programmatically from the C# file.
In the previous post, I showed you how you could handle multiple states for a specific element using the VisualStateManager and defining various groups and VisualStates.
In this post, we will use this same feature to change the UI of an example application so that it hides a title when the device is on portrait mode, so there is more space for the main component of the interface, which will be a ListView.
If there is something that can take a good-looking app to an incredible-looking app that may very well be Visual States. By defining different Visual States you are able to define how a certain element must look depending on some interaction from the user. The simpler example is with buttons, with which you are able to see when someone hovers over them (perhaps they change color), someone presses them (maybe in addition to colors the scale also changes), maybe also when they lose focus.
Handling button clicks is super important to build any app, here is how do do it from the XAML file.
It could be a bit of a pain to try to use Images as buttons, for those scenarios when you needed to display a certain image but also needed the user to be able to click on it, with all that that implies. A nice animation, perhaps change of color, and of course the triggering of an event or the ability to bind a Command. As of Xamarin Forms 3.4, this is no longer a pain, now you can define an ImageButton like you would define any element in the interface, and use it similarly to how you would use an Image, and make it respond to how a Button would.
Mastering the StackLayout will make your UIs look so much better, and it is quite simple. Here is how.
