Is there any lib I can use in NativeScript app to show national flags? .ttf would be the best option I guess.
It's no where related to NativeScript framework. Those must be simple images you must find in internet. It can't be font as most national flags are not mono coloured.
Related
I'm designing and prototyping an android app in Figma Linux but there is no way to add custom/desktop font in the application or in the web version. Figma only lists the Google fonts only. Please help me to solve this issue. I really need to add some fonts for my native language.
I don't know what to try as I couldn't find any documentation about this topic.
I have a localized (in English and in French) iPhone app on the App Store and there's something I'm wondering for a while without being able to get a response.
As you can see on the image below (from Xcode), English is set as the Development Language but not as the Base one so I'm wondering what happens for a user in Spain (with a phone in Spanish) or in Germany (in German), etc? What language did he sees on the App Store?
Maybe I'm freaking out for nothing! But English as the Base and not the Development Language would be more logic? Unfortunately, I can't try it myself, making my phone in Spain/Spanish because I still get the French App Store.
Thanks!
The localization setting has nothing to do with the AppStore. It's related to the end user's device (or app-specific) region. You can add your localized files for any localization you need (by selecting the file and adding to the desired localization from the right pannel), but the default localization will always be English.
So don't worry
I am searching a way to programmatically create buttons in a vertical scroll alignment layout in MIT App Inventor but unable to find proper tutorial or documents not available. Could someone highlight if it's possible.
Thanks.
To create components dynamically is not possible in the core system of MIT App Inventor, but there is an extension you can use, which is able to do it, see here Dynamic Components Extension (for all App Inventor components) by Yusuf Cihan
See the App Inventor Extensions document about how to use an App Inventor Extension.
For the extensions directory see here.
I'm developing an app with Xamarin.Android and Xamarin.iOS. I would like to keep my color values (hex, rgb, or whatever) in a common project so that they can be accessed by both the Android and iOS projects. Is there a way to do this? I'm also using MvvmCross so is there a plugin for this? Or is this a bad idea?
I'm going to be using the colors in the Android layout files (.xml files) and back-end code for both platforms.
Is there a way to do this? [Share colors between platforms]
Yes, you can use MvxColor.* (With some limitations)
I'm also using MvvmCross so is there a plugin for this?
MvxColor is available via a plugin on NuGet.
Or is this a bad idea? [Share colors between platforms]
Use Case: I'm going to be using the colors in the Android layout files (.xml files) and back-end code for both platforms.
MvxColor will not work directly in XML. But can be used through bindings or assigning colors via the code behind. Therefore, if you want to use any Android XML design time tools with colors then MvxColor will not work.
I have a PDF that seems to have some internal color profile attached. If I render this in iPhone simulator the colors come out as they look in Photoshop which apparently can parse this color profile. If I render the same PDF on Mac I get the same colors (less bright, muddy) as in Preview and Pixelmator.
Is there some way how I can achieve the same (correct) rendering result on Mac as I was getting in iPhone simulator?
On iOS Simulator, I used CGColorSpaceCreateDeviceRGB with a kCGImageAlphaPremultipliedFirst bitmap context. I also set rendering intent kCGRenderingIntentPerceptual, though I don't know if this makes any difference.
on Mac I tried the same settings, as well as all the different kinds of color spaces, but I'm never able to achieve the same result us in Simulator.
I also tried the two ICC based approaches mentioned here: http://developer.apple.com/library/mac/#qa/qa1396/_index.html
I'm getting desperate. What is different between iOS simulator which gets the colors right and Mac? I thought iOS doesn't do color correction, but Mac does? Right now I am drawing the individual pages with PDFKit. Is there a difference in PDFKit on Mac versus iOS related to color correction that makes it work properly on iOS Simulator, but fails on Mac?
I also took a JPG that was rendered from this PDF in iOS Simulator, put it into a new PDF in Preview and there preview and my Mac rendering yielded exactly the same colors as the input.
It looks to me like iOS Simulator has a magical ability to use a color profile embedded in this PDF which Preview or Quartz on Mac does not.
Please help!
kind regards
Oliver Drobnik
I don't know exactly how simulator works, but I can assure you that both Preview and iOS have very incorrect handling of certain features of PDF files; especially when it comes to color management, transparency, overprint, advanced compression of images etc...
Two tips:
On Mac, open the PDF file in Adobe Reader (free download from Adobe.com). The color you see in Reader should be very close to the actual truth. If your PDF file contains ICC profiles (for objects in the file or in the output intent, meaning for the whole file) it will be used correctly. On iOS, also look at Adobe Reader - it currently is the best (highest quality) display tool on that platform.
Secondly, if you want to know what the simulator or some other tool can or cannot do, have a look at the test patches from the GWG (http://gwg.org/ghentoutputsuite.phtml). These patches were designed to give very easy to interpret results on whether certain tools or printers can handle specific PDF features.
These two steps should at least tell you what works and where it works. That should make it easier to figure out what you need to correct.
Unfortunately this is a confirmed bug in CGPDF on Mac. It manifests itself if you have CMYK as a transparency color space. iOS ignores this correctly, the Mac messes up the colors.