Generates a view for users to input information into the system. For more information, see Input Views in Building Bixby Views.
This key and its child keys must be defined in an *.view.bxb
file. This file must be in an appropriate locale-specific resources
folder or the base
folder.
Be aware of which components you are adding to your layouts and layout macros, because different components are available under different views. If you call a layout or layout macro in a view and that layout specifies a component that the view does not support, Bixby Developer Studio will throw an error. Similarly, you should consider which layout macros are being called within a layout itself. The same layout macro invoked in one component might not be valid if used within a different component, as the list of supported child components could differ.
You can read the Designing with Bixby Views Design Guide and the Building Bixby Views (UI) Developers' Guide to check if your layout is using the correct components for that moment and that view.
For example, the components you can use in a layout macro for the summary of selectable items in selection-of
(which you define under the where-each
block) are different from the components you can define in a layout macro for the details of each item (which you define under the main render
block). The components you can specify in a highlights
are also different than the details of each item.
input-view {
match {
MyDuration (duration)
}
message ("How long of a duration?")
render {
duration-picker {
initial-value("#{durationBetween(addDuration(now(), 'PT1H'), now())}")
type (MyDuration)
}
}
}
For more examples, see the Input Forms sample capsule.
match required | Match patterns are used to dynamically look up the appropriate data (layout, dialog, selection strategies, or views) for the current context |
conversation-drivers optional | Provides convenient shortcuts to related actions |
message optional | Message to display to users |
no-response-message optional | This key is for internal use only |
overrides optional | Specifies overrides for certain behaviors on a per-view basis |
refresh optional | Allows for the results to be periodically refreshed, as long as the UI remains open |
render optional | Renders the specified view for users |