I am new to Couchbase lite.
I have already setup of Couchbase lite 1.3.1 in Objective-C and it's working fine. I have to upgrade this with Couchbase lite 3.0.
In latest Couchbase lite list of changes. Ex: CBLManager is not supporting, properties object is not available in CBLDocument ...
Could you please guide me how I can start this?
Any document where I can find not supporting class, methods, properties alternative?
I think you will find that there is no documentation specifically describing how to move from 1.3.1 to 3.0. The 1.x versions of CBL were sunset several years ago.
There is good documentation of the 3.0 version here:
https://docs.couchbase.com/couchbase-lite/current/objc/quickstart.html
I suspect that reading that documentation would be a very good start.
Related
COMtype compatibility issue :
As we know mediapipe works well with higher versions of python. i.e., 3.x and higher.
I am looking a for ways to implement features of mediapipe into pikinect2 for hand tracking and currently stuck at comtype errors.
Current suitable version of comtype for pykinect2 is v1.1.4
Kindly provide solutions to any one problem below.
An alternative solution to mediapipe at python version 2.7
Alternative way to make use of pykinect2 library for python 3.5 or higher versions without getting comtype errors.
Thanks
I have a project that uses Python.Net for which I specify to customers that they need 'Python 3.6 or later'. However, when for example, Python 3.10 becomes the current default download from Python.org, does this mean that there will be a period of time where my applicaion won't work because Python.Net hasn't been updated to work with Python 3.10?
Or do I have to tell customers an upper bound value for the required Python verion?
That strongly depends on how are you distributing Python.NET.
If you are shipping Python.NET before 3.0 (3.0 has not been released yet) with your .NET app, it can only work with the specific python version it has been built for.
If you are asking users to install Python.NET using pip, I think it is possible to do it from source, in which case it should work with any Python 3.6+. You can check that by installing Python 3.10 preview and trying from there. Wheels of course are only built for existing python versions.
Python.NET 3.0 should be able to support future Python 3.x versions once released. But right now it is in flux, and the next release might take 6-12 months: many features are still being developed and/or reworked.
Is there a function like "DS_viewingIsOn()" in DM script?
I found a function, DSisAcquisationAcive(), but it is not available before GMS 2.3. Can we sense the digiscan action before GMS 2.3?
I believe the command was added in GMS 2.2 and just documented from GMS 2.3 onward. Before introducing this command, there was no such scripting capability.
If you are on the GMS 2.x series you should be able to update to the latest GMS 2.x for free.
I am looking at Nexus 3.00 OSS Edition.
The recent release of Nexus 3.0 (OSS Edition) seems to have dropped support for rpms.
I don't see any specific note declaring that they are going to be dropping some features from 2.x.
So i am not sure whether the rpm/ yum repositry support is actually removed Or is it being supported differently with the new Nexus 3.0 or this feature has been made exclusive for the Paid version.
Not yet. The progress of this can be tracked in http://issues.sonatype.org/browse/NEXUS-10191. Feel free to watch for release details.
I'd like to get the latest Mono 2.x version.
According to the official Mono release history page it is 2.10.9
According to what appears to be the official archive it is 2.11.4
However the latest modification date in the archive above for a 2.X release actually belongs to 2.10.12
There is no mentioned of the latter two versions in Mono's website (according to Google at least).
Any ideas what's going on?
I found this blog post that suggests 2.11.4 may be an Alpha release (see the comments). Perhaps the same is true for 2.10.12, and the latest stable version was indeed 2.10.9?
A similar questions arises for the latest version of MonoDevelop supporting Mono 2.X.
According to a Xamarin rep in their mailing list it is 2.8.6.5, but the GitHub release history shows 2.9.6, and the following link works: http://download.xamarin.com/monodevelop/Mac/MonoDevelop-2.9.5.dmg.
Is it again a case of an Alpha / Beta release ?
Mono 2.10.12 is the latest stable 2.x release (although 2.10.10, 2.10.11, and 2.10.12 were really just MacOS-specific releases, iirc).
Mono 2.11.x releases were previews for Mono 3.0.
The latest stable 2.x release of MonoDevelop was 2.8.6.5.
MonoDevelop 2.9.x releases were previews for 3.0.
At the time, we used the same version scheme as the Linux kernel for both Mono and MonoDevelop, where an even minor version meant stable and an odd minor version meant development/unstable/preview/alpha/whatever-you-want-to-call-it.
I think Mono still uses the same version scheme, but MonoDevelop no longer does (starting with 5.0). For example, MonoDevelop 5.1 is stable even though the minor version number is odd.