You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I always tell other developers to use the right kind of report item for a given task.
A "List" and "Table" with exactly one column are similar, but one should normally not use a one-column table for a list, because this is semantically different and may be treated differently by the emitter. A trivial example is the HTML emitter, but once a PDF emitter supports creating accessible PDFs this would also make a difference.
For another example, in my hvbtup/birt repository, I can optionally tell the Word emitter to not generate any additional layout elements for a List item (to avoid nested tables in the generated word document), thus such a List item is more or less just a for-loop.
So, sometimes I find myself converting a List item to a 1-column Table item or vice versa by editing the XML manually. This is error-prone.
Do other developers find themselves in the same situation?
Then it would be nice if the context menu for Table/List items would contain a "Convert to List item"/"Convert to Table item" entry.
The "Convert to List item" should be enabled only for 1-column tables.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I always tell other developers to use the right kind of report item for a given task.
A "List" and "Table" with exactly one column are similar, but one should normally not use a one-column table for a list, because this is semantically different and may be treated differently by the emitter. A trivial example is the HTML emitter, but once a PDF emitter supports creating accessible PDFs this would also make a difference.
For another example, in my hvbtup/birt repository, I can optionally tell the Word emitter to not generate any additional layout elements for a List item (to avoid nested tables in the generated word document), thus such a List item is more or less just a for-loop.
So, sometimes I find myself converting a List item to a 1-column Table item or vice versa by editing the XML manually. This is error-prone.
Do other developers find themselves in the same situation?
Then it would be nice if the context menu for Table/List items would contain a "Convert to List item"/"Convert to Table item" entry.
The "Convert to List item" should be enabled only for 1-column tables.
Beta Was this translation helpful? Give feedback.
All reactions