So @hammerhai , how much time should I post the use(reason) of this extension?
My extensions is never made for the use of only one person whether it is you or someone else.
I can’t leave the idea of creating an extension if the extension isn’t usable for one.
What you think strange?
It depends on koder who use it. It can send the data through screens without saving it to any local storage. I would like to ask you that isn’t it better than a tiny db.
Really?
Are you serious do you think really it is possible with in built dictionary?. I don’t think.
It would be great if you do so with in built dictionary if you success then I want to request you to post here.
Dont take my words wrong. I just mentioned that you said and asked me. Stay calm because I haven’t said any bad word to you
And please now don’t spam this topic. I don’t wanted to let moderators to close it.
The reasons you listed are nearly all the exact same… You don’t have to use TinyDB and can use this extension through multiple screens without needing additional configuration, however, this extension isn’t good for any of those reasons since you can do the exact same with the TinyDB component.
I’m not saying it’s a bad extension, but there is no valid reasoning for why you came up with this?
TinyDB is good for long term usage where you need to access same data again and again but for short or one time usage this extension is fine.
TinyDB takes storage while this extension takes ram.
I mentioned that we can get data without using start value at my first post. I’ve been using that method till now. For start value, we should Make a list/dictionary of variables to a global variable and then pass it to the next screen which doesn’t look like getting variables easily and efficiently. Also, What if you don’t close the first screen and you want to transfer a variable back from the Screen2 to Screen1.
Eg. App (Screen1) > Settings (Screen2) - Here I only open the Screen2 and for returning back to Screen1 from Screen2. I just use close screen in Screen2. How can I transfer the variable to Screen1 using open with start value. This is a valid reason.
Of course you can’t transfer variables from screen2 to screen1 using the open with start value block, but instead, you can use these blocks to transfer variables from Screen2 to Screen1.