I have one question
I’m sorry for the details.
For instance
How to put a text input under the Data table
Even if i drag the text input from the component and move it below the data table,
Could not be placed
(Target line does not appear under Data tabel)
But when I dragged it to the right of the Data table, I was able to place it below
Is this the right move?
coud you post a video or animated gif to illustrate your issue?
Drag a Text component below the data table.
Target line displays a green target line to the right of the datatable
It is difficult to drag right or down the Data table
did you try using a stylebox as a container?
just curious, i think most layout/alignment control needs to be done with style boxes.
I tried it
When placing text compornent, etc. on the right side of the data table,
Direct placement is not possible
The current means are:
Place the Data table in the stylebox, and then place the Style box again on the right side of the same stylebox,
It was solved by placing text compornet in it
In Conclusion
Basically, I feel that putting compornent inside a stylebox is a good way to do it
Especially when placing compornent directly, I feel that the conditions will be stricter
i came up with this, because i thought you originally wanted to have your fields under your data table:
i have styleboxes both bottom and right. right is for buttons. bottom is for text input fields. i don’t know of any other way to do this well.
if you are looking for something like this
for the webForm or the stylebox’s parent.
This is a question about frequently used web forms such as the image shown here
From the top in the Web form
1.Text input for search
2.Data table
3.A group of text inputs for inputting and editing the selected entity
4.The number of entity selections in the data table, and the group of text components that display the aggregate results
5.Save button for the selected entity
6.Delete button for the selected entity
7.A button to prepare a group of text inputs of an empty entity for the registration of a new entity
8.Button to save the text input group of the newly entered entity
I was able to create most of the items from 1 to 6 with no code
However, the buttons for new registrations of 7 and 8 do not divide the work well if they use the same entity text input as editing, save, and delete
Is there any better way?
Or would it be safer to create a separate web form for new registrations and separate them?
As a general case, I’d be happy to get some advice on how best to do Qodly
this thread is also asking this very question.
we’re all trying to solve this problem…
If up to 8 is resolved
The next thing I want to solve is
Calculation in the group of entities in 3 above
For instance
Calculate the quantity * amount and put it in the total
All of these are text inputs
To master N to 1、、、
If you input text input or select box in the group of N entities in 3 above,
Entity is called from another 1 table
For instance
When you enter a commodity code, the product price in the related products table is called up
To master 1 to N、、、
For instance
Assume that the data table in 4 above is N.
Add a new data table to the left of the datatable and assume that it is 1
In order to CRUD 11 above, select the data table on the left and set the related entity selection of the datatable on the right to
Delete and edit at the same time
In other words, if the invoice-level CRUD is
As an alternative to the above 11
If you click on the list of invoices in the data table on the left, you can also open the details of a single invoice in another web form or tab.
I think it’s good
From now on
In order to make it easier to understand the 9 to 12 assignments, I plan to create and upload a web form sample
And I’m going to try to master up to 12
9 to 12 development challenges, as well as 4D
If you can do it with almost no code, follow the steps in the manual, and do it with simple operations,
I think there will be more cases of migration from other database development tools to Qodly
What do you think?
i have not tested any of this, but, based on what i’ve figured out, so far, i THINK
a calculated field would work
on #10 and #11, an alias or a calculated field would work: relationname.relatedDataClassAttributeName
12 is a matter of adding an event to the dt for onCellClick.
in the function that you generate, you would have something like this:
(note that in my dt, when i call this function, i send both the collection, and the selected line (which is an object) that was clicked, because i’m manipulating the entire collection. you could just send the object representing the line, or even just the id attribute of the line)
exposed function cellClicked(c:collection, l:object):collection
var myForm: 4d.WebForm
var event : object
var prompt:string
var row:integer
var newValue:string
myform=webForm
event=webEvent
row=event.data.row
prompt="Clicked row: "+string(row)+". Column name: \""+event.data.name+"\". ID (from passed object):"+l.ID
About CRUD
Thank you for your advice
Sorry for the late reply
I’ll sort out what I’ve been thinking about
1.Create a Web Form
2.Place the data table on the left
There you will see a list of invoices
3.Place the data table on the right side
There you will see the details of one invoice
4.Select the list on the left and you will see the details of one invoice on the right.
Can be edited
(Place the text input for editing under the data table on the right)
(In addition, create a save button for text input)
5.Next, add the Create and Delete buttons for the invoice list on the left
I would like to create this far, preferably with no code
It is for those who are not yet familiar with ORDA coding
did you watch @ayoub’s video on the topic? Thanks to @laviregen for pointing it out (i found it very informative). it sounds like what you’re asking for.
thank you
The content of the video is very much appreciated
I’m looking forward to seeing Qodly evolve to start with no-code and go all the way to full code
it’s not “low code”, it’s “less code”, or “lower code”, right?
the client-side framework will probably be what dictates where it goes, from here. i’d also like it to be more capable/less crippled.