icefaces ace components have a big fonts - icefaces-3

i am using icefaces 3 .
I have all my ace components displayed properly with css, but the only problem is all my ace components have a big font size and big size.
the size is much bigger compared to the size of the components shown in the icefaces showcase.
Can someone please shed some light on what could be causing this problem.

Related

Change display properties of graphics in lithium theme

First of all thanks to the developers of blogdown. I just started my first blogdown-blog on github / netlify and it looks really nice.
There is one issue that I would like to change:
On mobile devices, graphics from R code chunks are displayed in a way that I can see only the left part of the graphics. Ideally, I would want to reduce the size of the graphics on mobile devices so they fit to the height and the width of the screen.
Is this possible? Where would introduce changes?
Here is the link to my blog: https://sbloggel.netlify.com/
(I have only the most minimal knowledge about web programming).
Thanks in advance for any advice or pointers to relevant resources to start learning and best greetings,
Sebastian
I just accidentally found a potential solution that is sufficient to me.
Most (maybe all) figures on my blog will be produced by R code chunks.
By specifying the 'out.width'-parameter in the code chunk that produces the figure, the size of the figure will be fitted to the screen size as far as I can see:
```{r out.width = "100%"}
plot(1:10)
```
Thanks nonetheless!

Why GUI Component in Qt5 shows different sizes when deployed on system with different resolution

I am developing an application in Qt5. when I deployed it on the machine on which it is developed it looks fine. But when I deployed it on laptop with higher resolution, the size of components like QPushButtons etc,reduces.Please help me, I have no idea why it is happening.
I'm not sure how are you specifying the size but, maybe you are using fixed sizes? If so, when deploying on a higher resolution display the interface is apparently smaller but in fact has the same size than in the smaller resolution display.
Try using relative sizes or at list show how you are setting the size right now

White image while inserting a SVG image in TCPDF

I'm trying to insert some SVG images in a PDF using TCPDF with the method TCPDF::ImageSVG, but when I try this I get a white space.
If I try to enable TCPDF::setRasterizeVectorImages the image shows in the PDF file, but it is rasterized of course and so its quality is not good.
Do you have any idea?
Thank you very much for your help!
Unfortunately, TCPDF's SVG handling is quite limited, and the cause of your issue depends on the SVG you are trying to use. Later versions of TCPDF support more SVG functionality, so if you haven't done so, try using a later version of TCPDF.
If an update doesn't resolve the issue, and you're forced to use raster images, you can improve quality at the cost of file size. You can do this by rasterizing them at a high DPI yourself outside of TCPDF. Once you've done this, take your new high-resolution raster image and add it to your PDF with the Image method like any other raster image. At work we usually rasterize to 300dpi, but your application may call for more or less.
If your image gets added to the PDF far larger on the page than you expected, specify at least one of the dimensions so TCPDF knows how much of the page you're intending the image to use.

Font hinting behavior in PhantomJS?

I need to render text contained within divs on HTML document into PDF. I'm thinking of using PhantomJS, but one thing is very important. Different browsers and platforms render the text differently. So if I have the following code:
<div style='width:150px; height:80px; position:absolute; top:130px; left:78px'>
<p> Some text, yayy! :) </p>
</div>
It may render on one browser like this:
Some text, yayy!:)
But on another like this:
Some text,
yayy!:)
What happened was that (because of font-hinting, I guess), the text in the first example ended up with a certain width that fit into the containing div, but because of the font rendering on the second browser, the text ended up taking just a little more space that didn't fit in the container, and had to wrap around to the next line. I can't afford this kind of unreliability on how the output turns out. If the HTML had it on one line, I need the PDF to have on the same line too.
I've actually asked a related question here: Make fonts on Windows render like Mac/Linux: disabling font-hinting and/or deal with anti-alias on client side with no luck, but it was basically in trying to solve this same issue.
Can PhantomJS do anything about this? Or can PhantomJS at least somehow calculate the true width of a text, without font hinting and any other things involved? Or maybe calculate what it might render to if hinting were included? Or anything, as long as things come out on the PDF as they look on HTML. (Given the application I'm working on, I do not have the freedom change the CSS style of the containing DIV).
Font hinting is almost certainly not what is changing the width of text here. Font hinting involves making small adjustments to line up edges in an outline font to screen pixels; the adjustments are made within each character and should not change the overall width of that character.
Across platforms, there are slightly different versions of a font because of licensing issues. macOS and GNU/Linux can't usually go out and copy Microsoft's fonts exactly, for legal reasons, so the nearest you'll get is a font that basically looks the same (and has a similar name) but isn't really the same font. So some width variations across platforms are to be expected, unless you can provide your own font files along with the page (web fonts).
PhantomJS uses the system's fonts just like any other browser. So using PhantomJS will not automatically give you some "cross-platform" set of fonts that's different from your system fonts.
If you need 100% reproducibility then I suggest creating a virtual machine (or Docker image) with a standard set of fonts installed, and use that everywhere. Just don't forget to apply security patches to it when needed.

Screen Resolution issue with Metro app when running in local machine (Windows 8 desktop)?

Hi I am developing a Windows 8 C# / Xaml Metro application. I have taken grid template project and customized to my design requirement.
When I am testing the application in Windows 8 simulator it works fine, but when I run the application in Windows 8 desktop using VS2012 local machine option I am facing many problems.
If I am using standard resolution of 1366 * 768 it works fine.
If I am using a low resolution like 1280 * 720 etc (low end resolutions), the screen shrinking in many cases and it causes many problem, including irregular and inconsistent look.
My doubt is:
As per my knowledge is that Metro unique feature is to scale/render in different resolutions in same way, then why is it not able to achieve it properly?
Am I missing anything very important regarding Windows 8 Metro screen resolution?
How to make the Metro app work in different resolutions of desktop in same way and give a consistent look?
Please let me know.
Thanks in advance.
This MSDN article is an excellent source on how to scale your app:
Scaling To Different Screens
Points from the article that may be relavent to you:
The minimum screen resolution for an app is 1024 x 768. Your resolution above (1280 x 720) does not meet this minimum.
For the grid graphics - it may help if you provide the suggested sizes of (100%, 140%, and 180%). For example, for the standard grid size (250 x 250), you should provide images of the sizes of 250 x 250 (100%), 350 x 350 (140%), and 450 x 450 (180%). You have to use one of the two naming schemes (file name scheme, or folder name scheme) for your app to automatically select the size. For example, if your graphic in the xaml is named "mygraphic.jpg", then you can provide the scaled images named "mygraphic.scale-100.jpg", "mygraphic.scale-140.jpg", and "mygraphic.scale-180.jpg".
Since you are not very specific in indicating what is wrong, it is hard to suggest other things. Definitely take a look at the article.
Wrap your content panel in a Viewbox. It will scale the content to fill the available space.