I am using version 5 of highcharts and unfortunately upgrading to version 8 is not an option. I also using highcharts-more and highcharts-3d, both deprecated at the moment. My question is, even using version 5 can I remove "more" and "3d" from my dependencies and reference the ones on highcharts folder?
Related
I have an Angular app which doesn't load on older iOS version (14 & lower). Angular documentation on browser support mentions that the support is only available for latest 2 versions.
I am assuming polyfill is the solution to support older versions; but I am not able to figure out which polyfill to use and where to download it from.
Any help would be much appreciated.
The browsers you support are defined in your browserlist.src you can see which browsers are supported by running the command npx browserslist. You can play around with your browserlist in here browserlist playground. If you edit your browserlist the polyfills will be automatically added on build.
I am using covalent/core version 4 in my Angular 12 project and unable to find the covalent/core/loading, covalent/core/media and few more libraries which are available in the covalent/core version 3 or below. The problem is the version 3 doesn't support Angular 12 and version 4 doesn't have the libraries present in version 3 which is necessary in my project. How do I handle this? Is there any alternative library which is similar to covalent/core that supports Angular 12?
I provide a Swift framework for my customers.
It would only work in Xcode 10.3 (Or am I doing anything wrong?)
For other Xcode, it does have Swift compatibility issues.
So I am planning to release a series of versions of my framework so that a customer with a particular Xcode version can have the respective framework version of mine.
And it is pretty complex. Because for every release or bug fix I need to generate a bunch of versions.
I just want validation if this is the right approach.
How do I simplify this?
The compatibility issue you have is not from the version of the Xcode, is from the Swift version of the Framework. There is a difference.
In every project you can set the Swift version, but unfortunately you can't have more than one swift version per project. The current accepted ones are Swift 4, Swift 4.2 or Swift 5, as you can see in Xcode > Target > Build Settings:
Xcode 10.0 was the last version to support Swift 3 and is currently obsolete. I wouldn't create a framework version for it.
So, I would recommend you to either focus only on the latest Swift version and create a new Framework version every time a new Swift version appears (the most common approach), or start with the current three Swift versions and give them maintenance until the Swift version is deprecated.
I downloaded Highcharts using bower. The file bower_components/highcharts/adapters/standalone-framework.js is empty. I also looked at the CDN version at http://code.highcharts.com/adapters/standalone-framework.js - it's also empty. Is this intentional?
Since 4.2 version, the standalone-framework is included in the highcharts.js core.
More information you can find here: http://www.highcharts.com/component/content/article/2-news/198-highcharts-drops-adapters
I have made a project in xcode4.2 and when i opened it with xcode4.5 ,iOS 6 SDK it gives error 255 and the reason seems to be absence of libxml2.2.7.3.dylib.
What are my options is there any other substitute provided?
thanks
Xcode 4.5, or more precisely the iOS6 SDK (because the libraries available are dependent of the SDK, not the Xcode version) still has libxml2.2.dylib.
It is just probably not the version 2.2.7.3 but a newer, up-to-date 2.2.x.y version that is embedded in the SDK now.
You should generally not link your application with a specific version of libraries like that, but better with a generic version like libxml2.dylib or libxml2.2.dylib.
Generally libraries respect the semantic versionning, meaning that:
their major version change only when the API is not backward compatible with the previous major version,
the minor version change only when new methods are introduced in the API, but are still compatible with the previous API,
patch version means that some bug fixes have been made, but the API hasn't changed.
So if libxml respect this semantic versioning (and I guess is does, like quite every standard library), every version 2.2.x.y of libxml is API-compatible with any other 2.2.x.y version and will continue to work with your program. A hypothetic new version libxml2.2.x.z will simply fix bugs, but won't introduce any change in its API. And when a version of libxml2.3.x.y will arise, it will still be backward compatible with 2.1 and 2.2 too (just adding new features but not dropping the existing ones).
Thus, you can safely link your application with the generic library version libxml2.dylib, which will automatically point to the latest 2.x.y.z version available in the current SDK. Or link with libxml2.2.dylib which will point to the latest 2.2.x.y version (these are symbolic links to the latest versions, as all UNIX-like OSes use to do)
I think SDK for iOS6 just contains different version of libxml