I agree, and have done both on a very small scale. I don't think the OP fully understands the issues involved, despite me and @jschell trying to point out some of the things that need to be understood.
Thanks man for your answer. What do you think about PHP and mySQL. I heard that PHP is getting less and less popular these days, based on the trend. What do you think about that? Is that true? Can PHP still be promising to learn in the next 5 or 10 years? Or do I need to step on another programming language that can still connect to the database to our website?
Years ago I track down how that site collects their data. Which seems much more reasonable than any other trend report which almost always seems to be based on something like 'we surveyed 50 companies and they said they will be using X in the next year.'
Building an e-commerce app or website can be an exciting venture. The general steps you can follow to create your e-commerce platform:
Establish your app's goals. ...
Decide on your target audience. ...
Determine the essential features. ...
Choose the technology. ...
Build the app's minimal requirements and features. ...
Publish and Market the app. ...
Keep building the app with your users' feedback.
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....."