Version: v9.1p_2014-07-23/Pro Deployment
We are currently working on translating our app.
We have many LinkItem or ButtonItem that have a fixed width. Those widths were based on English text and we explicitly used the "width" attribute for aesthetic.
Now, the 2nd language we want to use in the app has longer labels.
Candidly, we thought that we could switch the "width" attribute to "minWidth" and everything would be like we wanted:
we still respect the "minimal" aesthetic and, potentially, buttons/links grow wider to accomodate the longer languages.
Unfortunately, we just realized that there doesn't seem to be support for "minWidth" in ButtonItem or LinkItem.
We do not want to maintain a map of "language => width" for all our buttons and links for all the languages we'll support.
Do you have another suggestion that would leverage ISC's features ? Could FormItem.canvasProperties come to the rescue ?
Thanks !
-C
We are currently working on translating our app.
We have many LinkItem or ButtonItem that have a fixed width. Those widths were based on English text and we explicitly used the "width" attribute for aesthetic.
Now, the 2nd language we want to use in the app has longer labels.
Candidly, we thought that we could switch the "width" attribute to "minWidth" and everything would be like we wanted:
we still respect the "minimal" aesthetic and, potentially, buttons/links grow wider to accomodate the longer languages.
Unfortunately, we just realized that there doesn't seem to be support for "minWidth" in ButtonItem or LinkItem.
We do not want to maintain a map of "language => width" for all our buttons and links for all the languages we'll support.
Do you have another suggestion that would leverage ISC's features ? Could FormItem.canvasProperties come to the rescue ?
Thanks !
-C
Comment