We are enhancing an Android app to have advanced SEARCH features.
The app uses Couchbase-mobile (version 2.0.0) as a an Android service...
I have these questions with implementation:
How simple it is to integrate something like [CouchDB-Lucene][1].
I guess we will have to trigger the couchdb-lucene java process on the Android device (as a service), but not sure if configuring the local Couchbase's .ini file is the only thing needed.
Is CouchDb-Lucene okay for Android or too heavy?
Would be great if anyone could provide some pointers.
Looks like someone got started here: https://github.com/ArtooTrills/TouchDB-Android-Lucene
I should note that this version of the Android syncronizing database is old. We are working on a new lighter version of it, check out the Couchbase mobile mailing list to get the latest info: https://groups.google.com/forum/#!forum/mobile-couchbase
Related
I am quite new to azure hubs. But spent three days to understand the flow(to use in xamarin forms).
Currently tying to link with android only(through xamarin forms). So when I thought everything needed is ready(GCM key and azure access policies) from my side, I started coding using vs2015.
First thing I did was creating "Blank portable cross platform" project.
Then,tried to install Microsoft.Azure.NotificationHubs package. PFA
But I am getting following errors( related to Profile259).
I spent whole day to understand what error is saying and I understood that package is expecting different target framework than what I am referring.
So I tried changed to other versions and through some blogs I found that maybe this Profile259 directory is missing.But it's all there.
Package is expecting .Net Framework 4.5 Full Profile. I cross checked it by following the link
I updated my azure version.Nuget package is also latest.
So what could possibly go wrong.
Please guide me in right way to get push notifications in devices.
PFA below.
I had to add it as a component. Go to the Components under the Android and iOS project, select edit components off the context menu, and add the "Azure Messaging by Xaramin" component. You'll probably have to download it by clicking "Get More Components".
If you're working on Android only for now, try removing all other targets from screenshot #2. There's a chance the error message is caused by one (or all) of the Windows targets.
I am new in developing apps for Android with Java Eclipse.
I get a simple problem: after following the procedure explained here:
http://www.tutorialspoint.com/android/android_hello_world_example.htm
I tried to push the "Finish" button to create my first app, but it doesn't work: the wizard remains open and nothing happens.
Also, I have several problems in the Demo apps, errors like:
'<>' source operator is not allowed for source level
and many more.
I guess I created problems with the configurations.
Thanks if you can help me to create my first app for Android and to load
the demos.
It is really had to tell what is the problem, but as Abdullah advised to use android studio because it is well designed to develop android applications. and most of the company's now days use android studio as there IDE preference, but still its developer's choice. Eclipse ADT plugin is buggy
I am a android beginner. I am going through the book listed in the title. I haven't even made it past the first chapter without running into problems. I have installed the latest version of Eclipse. However, the examples shown in the book are not much like my version. For instance, this main.xml file that's supposed to be in the layout folder is not there. The "New Android Project" dialog box is arranged very differently and the package explorer is called project explorer. Is there a way to get this kind of eclipse in the book? Or do I just have to interpret it best I can? Any help would be much appreciated! This question has been down voted and closed by another user. Could someone please tell me why? I am just trying to get some help.
As different Android APIs(ICS, JB, etc.) are released, they sometimes change the ADT (Android Development Tools) for Eclipse. The ADT is plugin for Eclipse. This plugin is what gives you all those neat buttons in the toolbar and the XML layout interaction.
The book you are reading was designed for Android 4.0(Ice Cream Sandwhich). As of right now, Google has released up to Android 4.2.2(JB 4.2). There has been some significant changes to the ADT going from ICS to JB, but in my opinion, they are for the good. Lots of really neat and new features. Here is a Google resource explaining the different API releases for Android: http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels
I would say continue reading the book as it will teachs you the basics of Android, but when you want to do some in depth coding, that book isn't going to be very useful and you may have to do a little research online. Reason is, Google releases at least two new versions of Android every year. Every version changes, and adds new features. In other words, the book you are reading is already out of date. Android OS development moves way to fast for authors to keep updating their books.
To answer your question, your probably going to have to interpret it the best you can since, most likely, by June/July, Key Lime Pie is going to out, and the ADT your using NOW will be outdated. You should really learn the fundamentals of Android OS and how it works in the background and how processes things. After that, everything else should be easier to learn.
An alternative to the book you are reading is this: http://developer.android.com/training/basics/firstapp/index.html. This is straight from Google and is constantly updated and tweeked. This will be the most updated and useful information on how to write Android apps.
Hope that helps!
I have download a set of android source code, which has folders such as "bionic, bootable, build, dalvik, development, frameworks, hadware, packages, prebuilt" and so on. When I browse the whole code, wonder how "import android.preference.PreferenceActivity;" works in Settings.java(D:\android-srce\Google-source\packages\apps\Settings\src\com\android\settings\Settings.java). I guess there is a android.jar file somewhere after compilation. But how does Settings.java import PreferenceActivity correctly?? I'm a beginner in Android, please help me.
Sounds like you have downloaded the source code to the Android OS. If you want to build your own ROMS then you need to study about building the OS for a particular hardware platform. This is not trivial.
If you want to build an Android app that runs on an Android device then you want to download the SDK instead - start at Android SDK and follow your nose, buy a book, read the sample code.
There is not a lot of information how to change parts of Android. However, you can read information that is connected with the aosp tag. The first cite is source.android.com After the installation of android build system you can see video from marakana group. You'll find a lot of valuable information there.
I create a ASP.net MVC 4 project by using Visual Studio 2010 IDE.
I want to make sure that my web application could run at Desktop PC as well as Mobile Browsers which is not the same sizes and properties.
After learning from this, I found that I need to use 51Degree when it comes to android based opera browsers detection.
But unfortunately, when i use nuget command
Install-Package 51Degrees.mobi
The downloaded data is not like I already expected.
Below is my current project situation after I downloaded by using nuget Command,
01.)51Degrees.mobi.config [found]
02.)AppStart_51Degrees.cs [not found]
03.)FiftyOne.Foundation.dll [found]
04.)~/App_Data/wurfl.xml.gz [not found]
05.)~/Mobile [found]
06.)<redirect> element inside <fiftyOne>
[not found at web.config]
[found at 51Degrees.mobi.config]
Could anyone please give me any suggestion or any reference links which using Razor and 51Degree.mobi?
51Degrees.mobi has been updated to version 2 since the blog post you refer to was written. The files you mention are no longer required. I suggest you look at this blog post for guidance on MVC4 mobile detection.