my 1.txt file will be full of base64 text data. As you may know already, base64 data is a text form of image, ie, we can use the base64 text data to produce the exact image back. So, I am planning to send each base64 data from 1.txt to List.Elements and each list-element text (base64) will be converted back to image and stored in TinyDB/ASD.
Sometimes, I may open the 1.txt from external memory and store it in ASD to do the process that I said above.
So, I shall create a new app for testing purpose. The goal of the app is 1) to upload the text file contains base64 data 2) Split the base 64 data from that text file and put it in Listview.elements. 3) Use KIO4Base64 extension blocks to convert each Listview.element into image. Let me create it.
Text file contains several confusing paragrapgh like this 'kuygjuyfyc uytfythfytfytgjhjvbm uyyfjvjghjhghv' but the lengthy paragraph. This is called base64 data of image. By using base64 extension we can convert these data back to image. And, I guess, the generated images can be stored in TinyDB and can be displayed in another Listview.
I checked if it is possible to add image in text file and I thought it is impossible. Can we add images as well in text file? Is it possible? Then, that is good.
It is not possible, am I right?
If there is possiblity, I need to convert the base64 data into images and make a new text file with those images as output.
The Input text file (The file that we upload from phone memory) contains only base64 text data and no images.
Yes, I got it. The text file of one image will already be very large, so there is little point in adding more. Why would you? Explain in more detail what the goal of your app is.
List of base64 text (yes large text) will be in the text file. We have to upload the text file within app and the app will process all the base64 text, one after other and produce multiple image files.
These multiple image files will be placed in a new listview one after other.
In the front end, user will not feel any complexities. He/She simply upload a text file and get image files. This is the plan.
I already created an app (name: App A) to generate base64 text of any images. This will be shared as a text file via email from one user to other user.
The other user has to upload that text file to the app (name App B), to convert into images.
So, user A can send images to user B in this way by only using TinyDB database.
To get product details from clients to upload in my ecommerce shop. (I will sell their product online via my ecommerce shop). So, they have to send the product details to me.
To stick with TinyDb to avoid hackers. (Main point that I thought)
I want multiple product details in a single page as a .csv file. (but right now i wish to do everything as a text file.)
So, client will have one app and I will have other app. In client's app, they simple enter the product details and images and generate final output as text file. They will share that text file to me via email.
From my side, Il upload that text file and convert all base64 data and produce images. etc. etc.
I wish to accomplish this much first, and il say other features later. Other features include producing final output as .csv file after converting images into customized url after uploading online.
I shall create the second app also using MFile but I don't know to solve 1 error. For that I will need help. Sometimes, by using SAF extension that error can be solved. I don't know to use this extension. After creating the app I shall ask for help.
By sticking with TinyDB, we cannot share list of images, so base64 idea can solve this. In the front end, users will not feel these complexities. They simply upload product details and forward to me as a text file. I will simply convert the text-file-data to see the product details with images. Then after creating custom url for images, I will enter the urls within app and generate .csv file of product details.
copy any images that you need, from wherever, to your ASD, into a separate folder, then you have access to them from within your app
just store the image filename in your tinydb for a record (you will know the path)
consider how your external users would like to receive the data for a record or records if using sharing, e.g. send a message with the text elements of your record and attach the actual image file
consider using an online resource, such as google drive or firebase storage, to upload data files and images, then you only have to provide the links to your other users