I know this is not a critical issue, but still I was giving it some thought since it is impacting most of my queries.
One of the issues in working around this is that if I define the query width to resolve the issue then things start to look very funny as you scale resolutions. Assuming you want % based width layout then no matter what combination of VP/Query options you use you will end up with one of the following:
- Both title bars: two different sizes, looks funny, wastes space
- Using VP title bar: a scalable layout, but no query tools
- Using Query title bar: query tools, but no scaling
That's not really a new limitation, but it becomes more pronounced with these Firefox changes. This got me thinking:
Perhaps an elegant solution is to separate the query title from the grid and have 2 width properties for a query object. The first would be for the title bar, boarders, etc. which would be % or PX, and a second separate setting for the grid which would be absolute and based on the column definition or a total value.
This method would allow the title to be say 100% but the gird is 1600px. Allowing the users several benefits,
- Fix to the core issue stated in this thread: no more '...' icons
- If a query is over the allotted width, H-scrolling is limited to the grid; tools/title stay in place.
- Single title bar can both 100% wide while still having the query tools
- Aware can always respect the stated width of a column, no more variable scaling to fit 100%.
- Cleaner scaling to various resolutions
One could even take this a step further you could use column locking to 'freeze' the Aware function columns in place. so they do not scroll way.
I know this is not cookie cutter EXTJS methodology, but we did something very similar with EXT in another product... I just can't remember how much work it was :lol:
Anyhow, just an idea.
