Wouldn't it effect the entire window of all the menus.
Ideally we would not like to do that right.
I was thinking of may be having a field to enter the column size in the tab level of "Windows, Tab & Fields" and we can use that while designing the window. We can make use of the flag "same line" in the field level.
This way, the entire process of how a window fields are defined can be controlled by the AD(Application dictionary).
Please let us know about the suggestion.
Thanks & Regards,
Sunil
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes. you are absolutely right.
But my thinking is that we can move the value set in Global.ctx.getContextAsInt("#XXX_WEB_COLS");" to be set in the tab level of the window and based on this value set, we can design the window to be a 3 column or 4 column or 2 column layout.
This way we can be certain that the window looks the way it is defined by AD and not taking gobal ctx value.
Please let us know about the suggestion.
Thanks & Regards,
Sunil
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In our environment XXX_WEB_COLS is coming from AD_Message.
This is a limit, to keep tab consistency from a user poin of view.
Cause the real amount of column is deduced from AD (with SameLine), So the number of column is "tab parametrized" BUT cannot be more than XXX_WEB_COLS.
It's easier to use ctx to handle XXX_WEB_COLS cause it's client side.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Team,
Please give an idea/option to enable 3 column layout in Compiere 3.8.0 web client.
Thanks,
M.Vignesh Kanna
Hi Vignesh,
Thanks a lot!! for the suggestion.
I understand it deals with the view composition.
Could you please elaborate as to why we might need this?.
Thanks & Regards,
Sunil
We change GridComponent this way :
// XXX999 : Permettre plus de colonnes
// else if (currentColumn >= 4)
// {
// ++currentRow;
// currentColumn = 2;
// }
// XXX999
else
{
// could be 6
int nbCols = Global.ctx.getContextAsInt("#XXX_WEB_COLS");
}
// XXX999
Let us know ...
Last edit: Steven Renaud 2015-06-22
Hi Steven,
Wouldn't it effect the entire window of all the menus.
Ideally we would not like to do that right.
I was thinking of may be having a field to enter the column size in the tab level of "Windows, Tab & Fields" and we can use that while designing the window. We can make use of the flag "same line" in the field level.
This way, the entire process of how a window fields are defined can be controlled by the AD(Application dictionary).
Please let us know about the suggestion.
Thanks & Regards,
Sunil
It works like that.
AD SameLine
Field1 N
Field2 N
Field3 Y
Field4 N
Fiels5 Y
Field6 Y
Whill show output like
Field1
Field2 Field3
Field4 Field5 Field 6
Hi Steven,
Yes. you are absolutely right.
But my thinking is that we can move the value set in Global.ctx.getContextAsInt("#XXX_WEB_COLS");" to be set in the tab level of the window and based on this value set, we can design the window to be a 3 column or 4 column or 2 column layout.
This way we can be certain that the window looks the way it is defined by AD and not taking gobal ctx value.
Please let us know about the suggestion.
Thanks & Regards,
Sunil
In our environment XXX_WEB_COLS is coming from AD_Message.
This is a limit, to keep tab consistency from a user poin of view.
Cause the real amount of column is deduced from AD (with SameLine), So the number of column is "tab parametrized" BUT cannot be more than XXX_WEB_COLS.
It's easier to use ctx to handle XXX_WEB_COLS cause it's client side.
Thanks Sunil and Steven for your efforts.. I really get some ideas from your discussions.