Is it possible to develop google glass apps using objective c? - objective-c

I have gone through a deep research on developing google glass apps using objective c ,but I have found that we should only use Java/Python/PHP to develop google glass apps. Since I am an objective c developer I am looking for some static library or framework for xcode, which is built to develop apps for google glass. Please give me any idea, is there any such frameworks/Library? Any of your suggestions would be much appreciated.

Yes, Google provides an Objective C API library at https://code.google.com/p/google-api-objectivec-client/ that includes generated routines for the Mirror API. You should probably also consult the documentation at https://developers.google.com/glass/develop/mirror/index for a broad understanding of how the Mirror API works.
Note that this will allow you to develop web services that work with Glass. It will not allow you to develop applications that run on Glass itself. It also will not allow you to write iOS applications that communicate directly with Glass - it will need a network connection to the Mirror server at Google and there may be some restrictions about how a callback will work.

Android SDK is what you use to create .APK files to run on an android or google glass device. It is based on the java platform.
Just like Prisoner says you can mess with the mirror API by sending cards to your device in almost any language via those starter kits.
If you are actually trying to make glassware you will need the Android SDK. Unless you are a very experienced programmer I wouldn't try to program in C to create apps going on glass.
On a side note: if you are a new programmer and are only experienced in C, try to learn python. Python is great for programming in C with a variation called CPython.

Related

Open standard for native RTC with no plugins

Recently I have worked using WebRTC and I'm wondering if it would make more sense to implement a Real Time Communication open standard at a native level.
Let's say that instead of a web browser API we have a native API that any native app, including the browser can leverage.
Part of the promise of WebRTC is to have RTC on the browser without plugins but why stop there, why not have RTC on any device with media capabilities without plugins. There are many devices with media capabilities that will not run a web browser, e.g., wearables. It seems to me that the browser itself has become the plugin and I think we need to get rid of it as far as RTC is concerned.
It sounds like OpenWebRTC is going in a similar direction but so far they are only working inside the browser.
Are there open standards for native RTC? So far it looks like RTCWeb is only concerned about the browser.
Are there any projects/initiatives for native implementations of an open standard for RTC?
webrtc definition. webrtc is stuck into two parts, complementary but separated. the W3C consortium is standardizing a JS API for browsers named webRTC. The IETF is standardizing the underlying protocols and what happen on the wire for interoperability, it is named rtcweb.
the IETF's rtcweb group defines everything you need to interoperate with a browser, without being a browser yourself, i.e. for gateways, devices, .... It has been made explicit at the latest meeting in hawaii last november, and there is for example a corresponding draft.
On the client side, the implementation of webRTC JS API is done on top of c/C++ implementations. Those "native" (as in non-browser, C/C++) APIs can be use directly for servers, embeddable devices, gateway, ect, or can also be wrapped in different languages (obj-c, java) to provide "native" (as in mobile native) APIs.
Note that BOTH openWebrtc.io and webrtc.org have a full implementation of webRTC in C/C++ that you can use. openWebrtc provides iOS wrappers, and webkit wrappers (for safari), but do not provide data channel support, ORTC API support, nor compile under windows. webrtc.org supports all desktop OSes, and provide wrappers for both iOS and Android. The build tools are specific to google's chrome though, unlike openWebRTC which uses standard auto tools, github, ...
HTH
Currently there is no effort in this direction. The guys in the webrtc standardization committee have their hands full standardizing just the javascript API. As you know the current spec is not final and is currently still worked on. And now ORTC will generate even more work.
There are many reasons why no one is currently trying to standardize any form of native RTC. Here are some that come to my mind:
What exactly is native? Javascript is native for the browsers. The chrome version of webrtc is in C++ but the OpnWebRTC one is in C. Android developers use mostedly Java, iOS developers use ObjectiveC. Should there be standards for all these languages? That's going to take forever.
As I said standardization committee already have their hands full.
There is still quite a lot of experimentation that goes on with WebRTC. Standardization may prevent this.
The API of the native libraries tend to be very similar to the JS API.

Develop iPhone App on Windows / Compile on Remote Mac

I realize it's been asked countless times whether iPhone apps can be built in Windows and that the simple answer is no, with workarounds such as using VM or even something like Dragon SDK which requires the app to be written in C/C++, but I would like to build an app using Objective C.
My question is can the code for an iPhone app not be developed on a Windows computer, uploaded to a remote Mac computer, compiled on the Mac, and then downloaded back to Windows to install via iTunes? I don't want to buy a Mac mini to get my feet wet with iPhone development, but I don't want to be limited to writing an HTML 5 app using Phone Gap or similar.
If nothing else, wouldn't it be possible to develop the app directly on a remote / virtual Mac using a remote desktop connection?
If either of these are possible, does anyone know of a company offering such a service? If not, what would be a likely reason that it hasn't been created? It seems like there would be enormous demand.
Perhaps http://www.macincloud.com/ is what you are looking for.
I believe what you're trying to do is not possible but how about MonoTouch ?
http://xamarin.com/monotouch
Using .NET on Windows technologies to develop iPhone and other apps ?

How to trigger a Symbian C++ application within a J2ME application for Nokia phones using J2ME API?

Anyone knows how to trigger a Symbian C++ application using any J2ME API call? I have a J2ME application that needs a customized photo taking application in Symbian C++. The reason for separating into two applications is because J2ME has a limit in heap size and the J2ME needs to know the path of photo after taking it.
Thanks a lot for your help.
Regards,
Kenny
Take a look at APIBridge on Forum Nokia: http://www.forum.nokia.com/info/sw.nokia.com/id/d697a64f-ddae-4937-8151-be157b542d26/ApiBridge.html
Designed specifically for MIDP apps to access services provided in the Symbian C++ environment.
I don't think there is an API for doing that. One thing you could try is to have your two applications communicate over a socket interface. For example the Symbian application could set up a socket server at localhost and the J2ME application would connect to it. I am not sure that this is possible in a phone's environment however. It could also have other implications as well, such as having to sign your applications.

Application framework to develop web and desktop applications?

Recently I was asked by someone if there is such a magic framework that will allow one let's say to design and build once a single library of controls and then use them separately to build web and desktop applications.
Does Google, Microsoft or other company have such a RAD framework and tools?
Thx
Depends on how you define a Web App. If you consider RIAs to be Web Apps, then yes...
Microsoft has Silverlight and Adobe has Flex/AIR.
Well, you can always go and look for adobe flex, adobe flash or even microsoft silverlight, which in the next version will support desktop applications as well.
Other types of frameworks currently do not build so well under desktop/web environments.. Take .NET for example, which can be used in so many set of environments, but there are limitations if you want to use it for mobile, web, desktop or XNA, everyone has his own set of tools.
That is mostly resumed in the capability of the desired environment, since you can browse a web page in an iphone, which does not have the same capabilities of a desktop or even laptop PC.
Seva is telling you how this is normally dealt with. MVC is a good start.
The Eclipse foundation offers Rich Client Platform vs Rich Ajax Platform - one allows you to build desktop apps, the other web-based apps, all using SWT concepts. I wouldn't describe it as magical though - the reality is it is much more difficult and I would not recommend RAP.
Adobe has AIR, and Google wants everybody write HTML5+JavaScript. both Chrome and FireFox can run those as standalone apps.
Were such thing to exist, it would produce lousy desktop apps and lousy Web apps. The underlying platforms and ideologies are too different. You'll do better by isolating as much of business logic away as possible, then building two separate clients.
EDIT: assuming that by a "Web app" you mean an HTML-based app, as opposed to something that happens to execute within a browser. For the latter option, you can have Flash, Silverlight, Java Applets, ActiveX controls... And for the vice versa, you can have a desktop app that opens a Web browser control and runs a Web app in it. :)
Microsoft has a Smart Client Factory that has a lot of built-in guidance packages that make development fairly quick and standardized.
http://msdn.microsoft.com/en-us/library/aa480482.aspx
It is entirely possible that I misunderstand this question, but if all you need, is the ability to seperate models an business logic into some kind of reusable library, just about any programming platform/language will do.
Java: keep models and business logic in seperate project, compiled to jar
.NET: keep models and business logic in seperate project, compiled to DLL
Python, Ruby, Perl: keep models and business logic in separate directory, and include as module
What are the requirements for the desktop application? On which platforms should it run? If Windows only, .NET seems like an obvious choice, otherwise Python and Qt or Java if you like to Swing.
I also would go for a Webservice and implement as much Business-Logic as possible in the Service. You can then build a very small Clinet in Html/JS, Java, .Net or Whatever.
You should choose that Framework you feel most familiar with.
If you are a .Net-Developer you can develop a WCF-Service (is also great with WP7).
For Java, i would choose Google-App-Engine or the Play-Framework.
And of course you can make a PHP-Webservice, for examble with the Flow-Framework
Check CrossUI RAD tool. It enables developers to rapidly develop and package the exactly same code and UI into Web Apps, Native Desktop Apps(Windows, OS X, Linux and UNIX) as well as Mobile Apps.

Carbon development on intel based mac

I am trying to make an application on mac.i am trying to develop a user authentication module that uses the OS authorization dialog and use its functionality in my application. i have two questions regarding the mac development;
1) Is there a possibility to port the carbon applications to cocoa? (i don't have any concern
with 64 bit, i want to develop in cocoa for simplicity and also because it doesn't go to
low level programming.)
2) secondly, please tell me that i am using an intel based mini mac with OS 10.5, so, if
there is no possibility of porting the carbon application to cocoa then can i develop on
this intel based mini mac for Carbon?
Regards
Yes, but there's no automatic way to do it. If you write your Carbon application in C++, then you can use Objective-C++ to integrate Cocoa without having to change your existing classes too much, but you still have to do all of the heavy lifting.
You can develop Carbon applications on OS X 10.5.
Note that Apple's "Getting started with Carbon" guide is now part of the legacy documentation library, and an increasing number of new features are only accessible through Cocoa APIs. I would strongly suggest using Cocoa for your new application, instead of starting with Carbon then porting.