I'm trying to generate a Flutter app, to create a stateful text field that I can call from other class (passing a name of the field and a limit for the field)., but I don't know how to do that,
Basically, I'm trying to be concise and reduce the amount of code for (variables)consecutive text fields.
Could someone help me?
In Flutter, you don't usually work like that.
Instead, use state management classes to store any manage state information, and provide a Stream instance that is then used to update your widgets (TextField) when state changes.
Related
Hi I am developing and application that showing list of document and editing document.
In every document there is a possibility of having a lots of nested document as well. If I edit child document, parent document state have to change.
I also need to access parent document in any nested level of child document.
What is the best state management approach for me to invest in this application
Summary of application:
List of Document screen => Clicking a document => showing a Edit screen of document=> clicking one of the child document => List screen=> same cycle
If possible please show me with simple code example
Thanks a lot for your time.
hope I understand what you want.
you can start by create structure as Tree every item has parameter parent now we can access to all item by write "recursive method" and can edit any item with parent
NOW WHAT STATE MANAGEMENT SHOULD I USE
you can do that in any state management you know Bloc River Pod.
I recommended to use Bloc its help you to separate logic and state and have a lot of features
I hope that help you to get started
I have many pages and I want to share file content between some pages, also giving this pages ability to modify content, the file contains (obj, data (int, bool, ...)).
1st: share file content between some pages can be done by using Constructor.
2nd: ability to modify conten can only be done by global variable+ key, but go for stateManagement.
I suggest, you should go for StateManagement. It can handle that.
I perefer using riverpod, also people suggest using getx being easy to use.
for more read this.
You can try the provider package as it's an effective tool for sharing data a cross your flutter app: https://flutter.dev/docs/development/data-and-backend/state-mgmt/simple
Either use constructors to dig through the widgets or simply use one of the packages for state management like provider, getx, bloc and many others.
But if you are a beginner then go with provider package as it is recommended by flutter team
Recently I'm working in a basic project to learn a little bit more of flutter.
But I found a blocker... which is that I have to pass data consistently and updated between a widget and its parent, so I wonder if is there any tool or extension to add that let me manage global scopes in my widgets.
Something like redux o a similar concept... Is there any of it? How can I control data in a flutter project if I need to use them in different widgets?
Thanks for your help
Please note i am not talking about the .abr files.
I have been following several tutorials on internationalization in Flutter using the intl package. I noticed that they always use a single AppLocalization class for storing all the messages that will be used in the application. Since it was a tutorial, I am wondering if we will always have to do it that way. I mean in a real application we will probably have hundreds messages to maintain. It would be a mess to put them all in a single class.
Maybe we should have a localization class for each Page?
What are your suggestions?
Flutter Intl package it's the right solution; also i used to Easy Localization.
This package has a "inherited widget " concept, so if you want to change automatically change UI for changed Local Language, it will be quite useful to you.
Maybe you want to localization JSON update to server and use application new key-value without deploy store. EasyLocalzation does read the server-side JSON file.
I have an interesting question. Seeing Flutter's MaterialApp class, you will find congruences with an activity on the entire application that we are going to build for Flutter. But my doubt is this. Do I have to enter N MaterialApp for each section where I can't go back? Or is it thought to be unique?
The internal design of MaterialApp indicates that it is designed to be used only once in the application. It has fields like localizationsDelegate,theme, and routes, which will be bad design if it used more than once , because most of these field will resort to default values causing a significant memory waste.
If you just want to use it to prevent navigating back to other screens or "sections", there are plenty of options provided by flutter like Navigator and WillPopScope.