I am trying to use voice controls on Samsung tv app (2016 model). I have found this page on the official documentation:
http://developer.samsung.com/tv/develop/legacy-platform-library/API00006/recognition_128
After including the script "deviceapis.js" I still can not access the deviceapis object.
"script type="text/javascript" src="$MANAGER_WIDGET/Common/webapi/1.0/deviceapis.js">/script>"
I am using Caph3 with jquery.
With model 2016 you must use new library
<script type="text/javascript" src="$WEBAPIS/webapis/webapis.js"></script>
Related
I'm a tech teacher and I'm designing a coding course for high school students. I want to teach them Ionic without also having to teach them React, Angular, or Vue. They already know basic web development, so I want them to be able to create iOS, Android, and web apps using only vanilla Javascript + Ionic.
When I run "ionic init" to get started, I'm forced to select from Angluar, React, Vue, or Custom. So, of course, I select Custom.
Then I start building a "Hello World" app. When it comes time to view the simple app in Android Studio, I run "ionic capacitor add android" and then "npx cap open android." All good.
The problem arises when I start adding more to my simple app, and then try to view those changes in Android Studio. Normally, this would be done by running "ionic capacitor copy android". But that doesn't work in my custom app. I get this error message:
[ERROR] Cannot perform build.
Since you're using the custom project type, you must provide the ionic:build npm script so the Ionic CLI can build your project.
How do I solve this problem? How I provide a build script for my custom app?
Thank you for your help!
Since you are using vanilaJS you shouldn't need any build step at all. Just put your index.html to www folder, with some content. You can start off with something like
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Ionic without any framework</title>
<script type="module" src="https://cdn.jsdelivr.net/npm/#ionic/core#latest/dist/ionic/ionic.esm.js"></script>
<script nomodule src="https://cdn.jsdelivr.net/npm/#ionic/core#latest/dist/ionic/ionic.js"></script>
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/#ionic/core#latest/css/ionic.bundle.css"/>
</head>
<body>
<!-- We create a vanilla Javascript function to call the alert -->
<script>
hello = async function () {
alert('Hello World!');
};
</script>
<!-- We declare an Ionic app using the <ion-app/> element -->
<ion-app>
<!-- Cool thing, the Ionic CSS utilities could be used too -->
<ion-content text-center>
<h1>Basic usage</h1>
<!-- We add an ion-button with an onclick event -->
<ion-button onclick="hello()">Click me</ion-button>
</ion-content>
</ion-app>
</body>
</html>
and then ionic capacitor copy android should work. (I assume following initialization steps ionic init, npm init, ionic capacitor add android)
I think what is needed after making any changes is to run npx cap sync and then npx cap open android.
Since it would appear you are trying to teach them the bar bones of development I would not even use Ionic. It is a framework for cross-platform development. And once you make a choice of using that framework, you may as well buy in to one of the Javascript/Typescript development frameworks to get the advantages those bring.
For doing POJO work targeted to iOS and Android, I would investigate using Cordova.
Consider it the difference between teaching a student the basics of audio recording on a four-track tape deck rather than a 128-track digital studio with all the bells and whistles.
Many of the basics are the same without the complications of all the advancements.
At my day job doing Enterprise-level financial applications we still use Cordova and have no plans to migrate any time soon.
In my admittedly biased opinion, Cordova would be a better starting point for a "Plain old Javascript object" based introduction to cross-platform development.
This will make the leap into Ionic and Capacitor easier.
Because, again just my opinion, if they haven't learned the advantages of a framework like Angular, going to Ionic/Capacitor is the cart before the horse.
Do you have an idea what is this "Install this web app" bubble called? I want to know whats the name of that thing so I can research more about it.
Do you also have an idea on how to implement it? I need it to function exactly like the one on the image.
Any useful links related to it will be a great help.
see this .
is very simple to use
<link rel="stylesheet" href="path/to/add2home.css">
<script type="application/javascript" src="path/to/add2home.js"></script>
I'm a newbie in BB10 Webworks... I am doing some experiments with the dev alpha's magnetometer...
how can I put these to work? I tried
function magCallback(sensor, data) {
$("#xvalueut").html(data.x);
$("#yvalueut").html(data.y);
$("#zvalueut").html(data.z);
}
blackberry.event.addEventListener("devicemagnetometer", magCallback);
and didn't worked, I also put <feature id="blackberry.sensors" /> in the config file, and inserted a <script src="local:///chrome/webworks.js" type="text/javascript"></script> in the index.html
I hope you can help me...
We have a really good sample app in our GitHub repo that you'll probably want to check-out. It deals with all of the sensors you can access via BlackBerry WebWorks.
Here's the link: Sensors Sample App
We are currently running Google Analytics on an iPhone app, and we got two strange devices appearing at several percents: "DoCoMo P502i" and "Google Wireless Transcoder".
What are these strange devices?
I see the same after implementing the v2 SDK on iPhone. There's not a lot of visits, but enough to do some research.
Google Wireless Transcoder is a project that strips down everything from the page from scripts to styles back to it's bare bones. Some mobile browsers might use the service to reduce the page size before downloading it and showing on mobile devices.
http://www.google.com/gwt/n
It seems that you can instruct Google Wireless Transcoder to not process your page and instead redirect the user to another webpage using:
<link rel="alternate" media="handheld" href=”mobile_page.htm” />
Source: http://www.elc-seo.com/search-engines/google/mobile-search-the-google-wireless-transcoder/
I'm afraid I couldn't find out much about "DoCoMo P502i yet. It also seems to be related to some kind of Google Proxy. Look at the full UserAgent it uses:
DoCoMo/1.0/P502i/c10 (Google CHTML Proxy/1.0)
Source: http://user-agents.my-addr.com/custom_user_agent_lookup-ua_string_analysis_checker_tool.php?i=395&u=DoCoMo_1_0_P502i_c10_Google_CHTML_Proxy_1_0
I'm pretty sure the 2.0 beta versions of the Google Analytics SDK for iOS report an iPod touch as a DoCoMo P502i.
I've just set up a new Analytics profile & tested on two devices, and that's what's I'm seeing.
Yup. A sweet phone, the DoCoMo P502i.
What method are you using for the Facebook Like button functionality for your mobile web sites?
On desktop sites, I've used the following:
<script src="http://connect.facebook.net/en_US/all.js#xfbml=1"></script>
<fb:like href="websiteurl" show_faces="true" layout="button_count"></fb:like>
However, this does rely on JavaScript libraries being loaded, which can be problematic for some mobile devices, especially since the Facebook JavaScript library is pretty big, and we're trying to keep the size of the site to a minimum.
The other option is to use an the iframe functionality, which seems to be the best way to handle it, however, some mobile devices don't support iframes.
We're supporting the following:
iPhone
Android
Blackberry
Windows Mobile
So looking to target as many of those devices as possible. I'm beginning to think the iframe is the best way to handle it, but am not sure how supported it is across the board for the devices above.
Thanks all
Recently announced:
https://developers.facebook.com/blog/post/2012/06/20/bringing-like-to-mobile/
There is unfortunately not a great way to do this at the moment. Facebook is working on it, but there is not yet a timetable for launch.