When developing the screen,
You may want to have screen modes like "reference mode" and "registration/update mode".
In "reference mode", for each input control,
I want to disable it.
At that time, there are as many input controls as there are input controls.
Setting the if Widget to hide it takes a lot of effort, so
I would like to create a system that does not create n if Widgets when creating a screen.
◆Plan 1
Gets a list of text widgets present on the screen.
I would like to do something like set the Enable property of that object to False.
(*List box widgets etc. are also controlled in the same way)
◆Plan 2
Something like the Change Enable interface,
Assuming each widget is implemented,
Gets the list of "widgets with Change Enable Interface" from the screen.
I want to do something like set the Enable property of that object to False.
Excellence, thank you!I would like to improve the appearance, such as the break between the item name and item value. I will do my best.
So a view and edit mode. Make a webblock for each, and switch between them with an If statement
Do NOT use the Enable/disable property for input controls
Input controls should only be on the Edit mode webblock, and in the View only mode use Expressions to show the values of whatever you're displaying
That was my idea at first too.
◆First Approach
①Create an extended widget (block) that has a “Mode” property on the standard widget
② In the extended widget (block), use the If statement to switch between input control and label.
I thought I'd use them on the registration screen.
(Text boxes, list boxes, radio buttons, etc.)
◆Problem
I think of the strengths of "Low Code Development" as follows.
``You can develop quickly by simply dragging and dropping Entities onto the Form.''
I think this is a very useful advantage.
(I would like to avoid the work of having to replace the widget being used.)
◆Requests from system users
For the UI in display mode, it is OK to express the label, or it is OK to set the Input control to Enable.
Either is fine.
Neither system users nor the development team are particular about this.
The point of contention is that we want to make development easier.
Hello Keiichi.
I made this very basic sample of what I'm trying to say, in around 20 minutes. Bear in mind, it's barebones and doesn't have much in way of form/input validation (nothing, really) but it illustrates a little bit of how you can leverage Edit and View modes
Thank you very much!
View Mode also
Is there a method similar to the development procedure that says, "You can develop quickly by simply dragging and dropping Entities onto a Form"?
It would be nice if it could be made easily, but I would like to avoid doubling the number of screens.
Yes, there is.
Let's use the same app I provided as an example
I create a new screen called SampleEntityScaffolding, and fetch a single record by its Id, in an aggregate:
Now, I expand the Aggregate, and grab the Record inside it and drag and drop it onto the screen:
Result:
It's very basic, but it's essentially what you were asking for
As suggested by @Mariano Picco , please use Blocks instead of manipulating elements on the screens. This approach will keep your code clean and manageable.