Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Standalone clockface/dail #151

Closed
chancezeus opened this issue Jun 8, 2019 · 4 comments
Closed

[Feature] Standalone clockface/dail #151

chancezeus opened this issue Jun 8, 2019 · 4 comments

Comments

@chancezeus
Copy link

Hi,

I just saw the update you have pending (3.2.0) and made a local build for testing. The package is really nice but I have one question:
I have a project build on @angular/material and I'm in need of a nice time input similar to your clockface. However because of certain requirements I'd like to be able to embed the "plain" component (without the ngx-material-timepicker overlays/backdrop/open+close logic) into a custom modal. Would it be possible to also make the various underlying components that make up the current "ngx-material-timepicker" component as either a single standalone/inline component or as they are now (i.e. seperate components and it'll be up to the dev to combine them correctly)...

Keep up the good work!

@Agranom
Copy link
Owner

Agranom commented Jun 10, 2019

Hi,
So you just want plain html/css, am I right?

@chancezeus
Copy link
Author

I'd want direct access to the underlying clock face(s) and input field without the "modal" wrapper, this could be a standalone component (only the modal "body") or simply export these components, that way I can use the dialog/modal feature of @angular/material (or any other framework) instead of your custom implementation...

@Lavoiect
Copy link

I'd want direct access to the underlying clock face(s) and input field without the "modal" wrapper, this could be a standalone component (only the modal "body") or simply export these components, that way I can use the dialog/modal feature of @angular/material (or any other framework) instead of your custom implementation...

Do you ever figure this out?

@Agranom
Copy link
Owner

Agranom commented Dec 22, 2019

Done. Update to v5.3.0.

@Agranom Agranom closed this as completed Dec 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants