Hey guys
I'm using Kendo UI Mobile for quite a long time, and since the beginning I'm a bit disappointed with the ModalView. I think it should have more features that a regular View has. Examples and other ideas:
- Zoom
- Layout
- AfterClose event
- AfterOpen event (or beforeOpen? Can't remember right now if the open event is triggered after or before the opening animation)
- URL parameters
- Possibility of specifying different sizes for tablets
- Automatic height (is this achievable on current version?)
The app we're working now needs a image viewer, and we thought that the ModalView would be best for this, to not interfere with the navigation flow, but the lack of zoom hindered that idea.
So I ask, please, give more love to the ModalView!
Thanks!
I'm using Kendo UI Mobile for quite a long time, and since the beginning I'm a bit disappointed with the ModalView. I think it should have more features that a regular View has. Examples and other ideas:
- Zoom
- Layout
- AfterClose event
- AfterOpen event (or beforeOpen? Can't remember right now if the open event is triggered after or before the opening animation)
- URL parameters
- Possibility of specifying different sizes for tablets
- Automatic height (is this achievable on current version?)
The app we're working now needs a image viewer, and we thought that the ModalView would be best for this, to not interfere with the navigation flow, but the lack of zoom hindered that idea.
So I ask, please, give more love to the ModalView!
Thanks!
1 Answer, 1 is accepted
0
Hello Fernando,
thank you for contacting us. I am glad to inform you that most of your the features you describe can be achieved with the current version of the widget. Following are more details about each request:
- Indeed, the modalview does not expose the zoom option. Yet, you can nest a scroller in it and set its zoom configuration option to true.
- Applying layout to a modalview sounds like an interesting idea. However (unlike views), you can have several modalviews open at the same time stacked on top of each other - something which the layout does not support. The header and footer are instantiated once, and their instances are attached/detached to the currently active view.
- Indeed, such events are useful in certain scenarios. I will log this in our system for further consideration.
- The modalview is a dialog widget, and does not have its own URL (nor URL parameters). To be honest, this was not the best decision, since this means that we don't/can't support closing when the back button is pressed. At this point, changing the implementation would be a huge breaking change for the existing implementations. However, you achieve the same by extracting data attributes from the DOM element which was used to open the modalview.
- the root element of the mobile application has km-phone or km-tablet CSS class applied. You can use that to style any widget (including the modalview) accordingly.
- The modalview uses automatic height in our current demo - please check it.
Once again, thank you for raising these concerns. I think that this thread will be useful for other modalview users as well.
Regards,
Petyo
Telerik
thank you for contacting us. I am glad to inform you that most of your the features you describe can be achieved with the current version of the widget. Following are more details about each request:
- Indeed, the modalview does not expose the zoom option. Yet, you can nest a scroller in it and set its zoom configuration option to true.
- Applying layout to a modalview sounds like an interesting idea. However (unlike views), you can have several modalviews open at the same time stacked on top of each other - something which the layout does not support. The header and footer are instantiated once, and their instances are attached/detached to the currently active view.
- Indeed, such events are useful in certain scenarios. I will log this in our system for further consideration.
- The modalview is a dialog widget, and does not have its own URL (nor URL parameters). To be honest, this was not the best decision, since this means that we don't/can't support closing when the back button is pressed. At this point, changing the implementation would be a huge breaking change for the existing implementations. However, you achieve the same by extracting data attributes from the DOM element which was used to open the modalview.
- the root element of the mobile application has km-phone or km-tablet CSS class applied. You can use that to style any widget (including the modalview) accordingly.
- The modalview uses automatic height in our current demo - please check it.
Once again, thank you for raising these concerns. I think that this thread will be useful for other modalview users as well.
Regards,
Petyo
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!