is it possible to reduce/limit the Qt API features to specific earlier versions?
In the API documentation there is e.g. information that methods are introduced with version major.minor.
Can you restrict the API features of an installed newer version to the earlier ones without installing?
I don't think so, because there are no version conditions in the header files.
But maybe you know for sure...
Is there a tool which detects the usage of incompatible API to a specific version?
Thanks
Markus
Related
The version compatibility of Vulkan SDK is documented in LunarG's whitepaper, but I'd like to know whether those extensions controlled by the flags listed below are following the same rule as well.
VK_USE_PLATFORM_DIRECTFB_EXT
VK_USE_PLATFORM_ANDROID_KHR
VK_USE_PLATFORM_FUCHSIA
VK_USE_PLATFORM_IOS_MVK
VK_USE_PLATFORM_MACOS_MVK
VK_USE_PLATFORM_METAL_EXT
VK_USE_PLATFORM_VI_NN
VK_USE_PLATFORM_WAYLAND_KHR
VK_USE_PLATFORM_WIN32_KHR
VK_USE_PLATFORM_XCB_KHR
VK_USE_PLATFORM_XLIB_KHR
VK_USE_PLATFORM_XLIB_XRANDR_EXT
VK_USE_PLATFORM_GGP
VK_USE_PLATFORM_SCREEN_QNX
VK_ENABLE_BETA_EXTENSIONS
I believe if the VK_ENABLE_BETA_EXTENSIONS is enabled, then the version compatibility is not guaranteed, but how about those platform extensions?
For the time being, SDK copies the versioning of the specification. If the SDK version is same or higher, the headers should include all the functionality published with a given spec version(and protected by an appropriate macro, as you listed them), and layers should not break (exept for an occasional bug).
SonarQube's web service api/tests is deprecated since SonarQube 5.2.
What would be a new good way to access this information?
api/tests has been deprecated in 5.6, but it still exists.
The related tickets are SONAR-7619 and SONAR-7623, but we haven't add any description...
The reason of this deprecation is that this feature is not highly used (as most IDEs provide this information easily), and it does not bring a lot of value in SonarQube.
For the moment this API is still there but it may be removed in SonarQube 7.X.
I am supposed to migrate a website from Sitecore 7.1 to 8.0
I am mainly concerned with Lucene Search and indexing part of search functionality which is to be migrated as well.
I just need a heads-up for errors and bugs for the same and a question (for which no answer was found on web) is that will the search functionality be severely affected by the migration? what care should be taken while migrating?
Any helpful and relevant links are appreciated.
From what comes into my mind, there were certain changes in search configuration
contentSearch/configuration/defaultIndexConfiguration/analyzer
has moved to:
contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/analyzer
there were also changes in ContentSearch namespaces
Also check EncodedNameReplacements setting for media library as it may break some of your links.
If you are using modules - check modules compatibility table by this link https://kb.sitecore.net/articles/541788 as some of them may not yet be available for 8.0. Sitecore.Kernel is now on .NET 4.5 so please keep .NET version updgrade in mind as well
I usually get two clean installations with following versions and check configuration changes in diff tool, where applicable, you may find this practice helpful as well.
Please go carefully through upgrade notes from Sitecore and consider if they have to be performed on your solution. Official upgrade notes to 8.0 can be found here https://dev.sitecore.net/en/Downloads/Sitecore_Experience_Platform/8_0/Sitecore_Experience_Platform_8_0.aspx (but you may need SDN account to access that)
Some other useful references:
https://theagilecoder.wordpress.com/2015/03/09/keystone-considerations-when-upgrading-to-sitecore-7-5-or-sitecore-8/
http://laubplusco.net/quick-tip-upgrading-sitecore-fast-easy/
http://www.velir.com/blog/index.php/2015/06/25/the-art-of-the-sitecore-upgrade/
When i try to use the statement google.load("dojo", "1.6.1") in a web app I am developing, I receive the error:
Module: 'dojo' with version '1.6.1' not found!
This latest version of dojo, enables a certain amount of support for IE 9.0, and that is why I need to reference it. Is this supported by Google as a library? Either way, if anyone has suggestions as to how I can work around this?
1.6.1 is not yet in the Google ajax library repositories. See the latest version note here. I'm sure it will be within a day or two. There is a note on the dojo download page in big red letters saying that the CDN's are still behind on 1.6.0 and saying where to get notified when they are updated.
You can always use the "1.6" nomenclature to always have the latest version and your app will move up to 1.6.1 as soon as it hits the Google CDN. If a couple days is really going to make or break you you should consider compiling and using your own local version. Dojo makes this really easy.
I'm working on a cross-platform solution currently. The solution uses XmlMtomReader and XmlMtomWriter from .NET framework 3.0.
Now i need to know if these two classes (and all the nessasary infrastructure around them) are fully supported in Mono project from the porting-it-to-linux point of view. :)
You can check it on the mono status:
http://go-mono.com/status/
You can also check your code using the mono migration analyser
http://www.mono-project.com/MoMA
I checked they are currently not implemented
The APIs are available on the current Mono 2.6 preview, but they are not available on the 2.4 release (the current official release).