Hi Namik, > Alright, I'll try with a scrollbar then. > > > I've added the scrollbar, and went back to using native widget styles in > the home screen. Here's a screenshot: > > http://pokit.org/get/img/e1f2f00e2c54701eba99811744a37369.jpg
Thanks, looks good (also on Linux). > I really don't like those barely visible groupbox borders, which is why > I tried customizing them. Unfortunately, my customization does not work > so well on other platforms. I think it would be better to go with native > looks if we want to avoid compatibility troubles. At least for now. Yep. I find the native look more appealing then the customized look on Linux, and it also fixed layouting issues :-) Seems like optimizing the look for one platform will make things worse on other... Best regards, Karli > On Mon, Nov 24, 2014 at 11:45 AM, Namik Karovic <namik.karo...@gmail.com > <mailto:namik.karo...@gmail.com>> wrote: > > Hi Karl, > > A static build is unfortunately not possible because WebKit+Qt > cannot be built statically. A static build of QWebKit is > officially *disabled*: > > > https://qt.gitorious.org/qt/__qtwebkit/commit/__2573bb654e49a0bfb00ced6446caca__e3a41fd776 > > <https://qt.gitorious.org/qt/qtwebkit/commit/2573bb654e49a0bfb00ced6446cacae3a41fd776> > > I did not know that. > > Most of the package size stems from the WebKit engine (the .dll > is 30 MB). If we really want to cut down the program size, we > have to replace the WebKit-based MatrixMarket Browser with a > static list of matrices (after 1.0.0 of course... ;-) ). > > > Yeah, I guess that the best thing to do in this case. > > Be careful with global changes at this point ;-) I think that it > will suffice if you add a scrollbar to the widget on overflow. > > > Alright, I'll try with a scrollbar then. > > Regards, Namik > > On Mon, Nov 24, 2014 at 11:35 AM, Karl Rupp <r...@iue.tuwien.ac.at > <mailto:r...@iue.tuwien.ac.at>> wrote: > > Hi Namik, > > > It worked fine on my Windows 7 desktop machine; later I will test > it on > > my Windows 8 laptop and report if anything is missing. > I guess linking Qt dynamically is ok for the time being. But > we should > think about a static build for the long run. > > > A static build is unfortunately not possible because WebKit+Qt > cannot be built statically. A static build of QWebKit is > officially *disabled*: > > https://qt.gitorious.org/qt/__qtwebkit/commit/__2573bb654e49a0bfb00ced6446caca__e3a41fd776 > > <https://qt.gitorious.org/qt/qtwebkit/commit/2573bb654e49a0bfb00ced6446cacae3a41fd776> > > > It would reduce the program > size significantly. > > > Most of the package size stems from the WebKit engine (the .dll > is 30 MB). If we really want to cut down the program size, we > have to replace the WebKit-based MatrixMarket Browser with a > static list of matrices (after 1.0.0 of course... ;-) ). > > > A few smaller issues are still left and will be > addressed tomorrow. > @Namik: Do you have some time to fix the layout on the > start screen > for multiple OpenCL devices (see screenshot)? Adding a > 'scrollable' > property might do the trick already... > > > I thought I fixed that already... Damn, this cross-platform > widget > customizing is so annoying. I think I'll just revert back to > using > native widget styles... > > > Be careful with global changes at this point ;-) I think that it > will suffice if you add a scrollbar to the widget on overflow. > > > > - The plots were hard to read because rather small on > my laptop. I would > > love to be able to make the plot fullscreen, or to > display the data as a > > table when I click on a curve. I don't know how easy > this is to do with > > qt-creator, though... > Yeah, this is a resolution issue. On full-HD resultion > it's much better > to view/navigate, but still it's hard to extract the > x/y values. At some > later point we definitely have to offer a data export. > For the time > being I'll try to display a label if the mouse pointer > is over a > data item. > > > A fullscreen option is a good idea indeed. And not too hard > implement. > I'll see what I can do. > As for displaying a label on mouseover, it's not as easy as > it may seem. > The plotting library we use doesn't provide that functionality > out-of-the-box, so we'll pretty much have to make our own > solution. It's > not impossible, but not easy either. I've tried to do it > during GSoC, > but there were more important things to back then. Here's a nice > explanation on how it can be achieved: > > http://www.qcustomplot.com/__index.php/support/forum/54 > <http://www.qcustomplot.com/index.php/support/forum/54> > > > I found a similar discussion yesterday on the web, including > some more code snippets. If there's time left this afternoon, > I'll look into it. > > Best regards, > Karli > > > ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
