Hmmm, it's kind of hard to ask a question because I know something, but only that I don't know much yet 😕.
I want to go back to learning in the project.
Blocks to use: #android , #kotlin , #mssql
Interface in Kotlin already covered (as such ) Database in MS SQL (not the worst, a bit of my hubby ) Connection covered.
And here comes the conundrum of which way to go. Conditions to be met:
1. Work with the database offline/online.
2. When resuming the connection, the client data is synchronized with the server connection test is carried out "independently"
3. data update on the server is done "independently"
4. In offline mode, customer data cannot be lost even after restarting the device
I was thinking of using #sqllite #maven on a device between user and #mssql
Do you know any simple tutorial?
Most of the tutorials I've come across end with "select * from table"; and the rest is up to you. Hurrah 😕
It sounds like you already know many of the basics, so the next step is to figure out how to implement the conditions you listed. You reminded me of this question when I was studying cotlin, but to write, also required a database. You will need to figure out how to establish a connection between the client and the server, and how to ensure that the data is synchronized when the connection is resumed. In addition, you'll need to figure out how to ensure that the data on the server updates itself, and how to make sure that client data isn't lost even after a device reboot. Good luck!
I've checked the many blogs and forums and github but nothing found related/help for implementing shoutcast v1 or v2 in android, only ref which is helpful I've found in github isthis:
but above code only work with icecast server and also very limited use and files which is used for broadcasting is *.so files so we can not change or override the exiting methods.
is there any guide or helpful link or source code which I can use to build shoutcast broadcasting in
If you want to know more about this you need to dig inside the documents and read them from the Intend Service. The battery status is generally taken by the Battery Manager which broadcast all the battery and charging details.
I am getting an an error when I try to display 2 input views. They are captured in one fragment screen and then I try to display them on a second fragment screen. The navigation works but they display as resources?... i do not even know what it is called.
This is the setOnClickListener that calls up that screen. I suspect it has something to go with safeArgs
val username = binding.editTextUsername.toString()
val password = binding.editTextPassword.toString()
val action = LoginFragmentDirections.actionLoginFragmentToWelcomeFragment(username, password) findNavController().navigate(action)
Android Studio related question.. someone might know...
I am watching a tutorial... am curious as to what drives these code insights to show up.
in the images below,.. one is from the tutorial, the other in mine"lixo.frag....."
I have an idea for an app but I'm very confused and don't know where to start I want to program an application to search for contacts by name or phone number use java or kotlin or flutter
The mechanism of its work is when the user installs the application, the contacts are pulled from the phone and then uploaded to an external database. This process is done for all users so that when one of the users tries to search by phone number, it displays all to him from the database the names that are registered in all other users’ phones I ask fellow engineers to help me from where to start and how to program it Thank you from the bottom of my heart
Start by writing down on paper a precise specification of what you want your app to do.
Then research the available languages and frameworks, and pick one that will do what you want.
Learn that language and framework. Write the code for your app. Test and debug until it works.
Then, based on the description of your app, hire the best lawyer you can afford. If it ever gets into an app store, you'll end up being sued for massively breaching your users' - and their contacts' - privacy.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
The phone already a contacts database, and your app, as useless as it now is, will need the users permission to get at that database. So your essentially bypassing the security of your contacts database.
Now, try to understand this from the users point of view. "You want to upload all of my contacts to some central database? FOR WHAT NOW?" "F*** that!" Why on earth would anyone want to search the contacts of, say, their ex-gfs phones? I assure you it's for nothing legal.
How are you going to prevent spammers from getting their hands on that data? I'm sure everyone would love to get spammed from your contact database (not!)
Your app idea is going to get you sued the first time it's used for the wrong purpose, and it's really easy to do that! You'll be paying that judgement off for the rest of your life.
Drop the idea. Nobody in their right mind would subscribe to it.