Hi Dioc,
it seems that there hasn't been to much response to your request, so when I
came across the same (annoying) problem, I recalled your question...Here's my
little tip, just in case there are still some readers who need hints on this
There are (as always) several possible solutions:
1. Change the code in qooxdoo framework
2. Apply a patch to the qooxdoo framework class in your application
3. Overwrite only the code for the instance you need
4. Derive your own CellRenderer and assign it to your table
I have not done all these options, so here I give you just the hints to the
options I've checked:
1. Add one CSS definition line to the constructor of
qx.ui.table.cellrenderer.Abstract : (somewhere around line 48)
> " -o-text-overflow: ellipsis;" +
> " white-space:nowrap;" + // <= this is the new line!!!
> " border-right:1px solid #eeeeee;" +
2. Add following code somewhere in the main() of your application:
> qx.Class.patch(qx.ui.table.cellrenderer.Default,
> qx.Mixin.define("myApp.patch.CellRenderer",
> {
> members :
> {
> _getCellStyle : function(cellInfo) {
> return (cellInfo.style || "") + " white-space:nowrap;";
> }
> }
> })
> );
The other two options should be something similar, but I do not present code
here 'cause I had to choose the second option...although the fourth would be
the "cleanest" I think.
The trick is "just" to set the "white-space:nowrap;" CSS-style.
By the way: If there's anyone out there with a better/cleaner/ more qooxdoo'ish
solution, feel free to post ;)
/Peter
-------- Original --------
From: Dioc
Date: 26.09.2007 09:50
> In version 0.7.1 table's cell contents were being cut off by column border
> and occupied all column width. Now in version 0.7.2 this behaviour was
> changed and cell contents are being cut off by words. I.e. if a word that is
> a part of cell contents is not fit in column entirely, it will not be
> displayed. Often such behaviour is not useful. Is it possible to restore
> behaviour for a table that was used in version 0.7.1? Does table or some of
> its components have a property/option that allows tuning this behaviour? If
> not, how to subclass qx.ui.table.Table to get previous behaviour?
> Thanks in advance.
>
> Best wishes,
> Denis aka Dioc
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
