picker | 该库作者不再维护，picker 的维护移交至 cube-ui

I think this should align your text and fix your issue.

I am not sure what package you are using to convert into the required format, but if you are using 'moment.js' package, you can take a look at this website

Link to moment.js ==> https://momentjs.com/

What you want to do is something like this:

I removed this component and used the other ones.

You just need to add watcher like this:

I try to avoid text only answers; including code is best practice but the question about storing images comes up frequently and it's not really covered in the documentation so I thought it should be addressed at a high level.

Generally speaking, Realm is not a solution for storing blob type data - images, pdf's etc. There are a number of technical reasons for that but most importantly, an image can go well beyond the capacity of a Realm field. Additionally it can significantly impact performance (especially in a sync'ing use case)

If this is a local only app, storing the images on disk in the device and keep a reference to where they are (their path) stored in Realm. That will enable the app to be fast and responsive with a minimal footprint.

If this is a sync'd solution where you want to share images across devices or with other users, there are several cloud based solutions to accommodate image storage and then store a URL to the image in Realm.

One option is part of the MongoDB family of products (which also includes MongoDB Realm) called GridFS. Another option is a solid product we've leveraged for years is called Firebase Cloud Storage.

Now that I've made those statements, I'll backtrack just a bit and refer you to this article Realm Data and Partitioning Strategy Behind the WildAid O-FISH Mobile Apps which is a fantastic article about implementing Realm in a real-world use application and in particular how to deal with images.

In that article, note they do store the images in Realm for a short time. However, one thing they left out of that (which was revealed in a forum post) is that the images are compressed to ensure they don't go above the Realm field size limit.

I am not totally on board with general use of that technique but it works for that specific use case.

One more note: the image sizes mentioned in the question are pretty small (500 ~~ 800 kb img size) and that's a tiny amount of data which would really not have an impact, so storing them in realm as a data object would work fine. The caveat to that is future expansion; if you decide to later store larger images, it would require a complete re-write of the code; so why not plan for that up front.

MaterialDatePicker is already DialogFragment. In your case picker.getDialog() returns null because under the hood the DialogFragment write value to DialogFragment.mDialog(value of this filed returns picker.getDialog()) filed from life-cycle callback onCreateDialog() which will be called async after invoke the the dialog's show method, i.e. when you call to picker.show(fragmentManager) then in picker's onCreateDialog you will can get not null value from getDialog() method.

In your case you should not extend DialogFragment or MaterialDatePicker (it is final ) instead that you can just create method like birthDateUpdater:

You should use the EnhancedDatePicker https://vaadin.com/directory/component/enhanced-datepicker

There you can set pattern and even parsers. For example:

• When you're trying to share data in between screens, it's often useful to use app methods instead of specific methods of screens.

• And when you need to create lots of buttons, maybe inside a loop, and bind methods on its events( on_press, on_release), it's often bad to create button instances on the fly and bind methods on its events because you'll need to do extra work to make sure that those bound methods are called with right parameters when events are fired. Rather create a custom class template and use that instead.

Created custom GridLayout:

I replace date piker js file with this files and the problem was solved.