I want to show content of a website: www.google.com in my TVOS app, but TVOS don't support UIWebView (In the first ViewController(MainScreen), I have a view, and I want to show web content at here)
I haven't any idea.Please help me.
Edit: I try with post : Web app in tvOS but it will be rejected by apple if I use UIWebView
Accessing dynamic web content is strictly prohibited in tvOS for the foreseeable future. Even if you find a way to hack around the restriction, the likelihood of the app being accepted into the tvOS App Store is nil.
There are a number of reasons Apple is making this stance, specifically:
• Apple can better control the quality experience of apps if they know exactly what content is going to be displayed
• Limit potential web exploits (phishing, viruses, etc.)
• Force developers to support native features and layouts
Though it appears like this may change in the future (see: https://twitter.com/ryanolsonk/status/642069462452056064).
Additional reading material on the subject: http://thenextweb.com/apple/2015/09/14/apples-made-it-difficult-to-build-tvos-apps-and-thats-good-for-users/
Related
latest chromecast app will provide content discovery right inside chromecast (though i haven't seen this yet, only cast-capable app icons). but according to the screenshots by google, youtube/netflix featured content will be shown on this screen to promote content instead of apps.
i don't find SDK describing related content discovery API, is there something i've missed, or it's not planned to open to 3rd party apps yet (only that google chromecast app selectively cooperated with some famous partners?)
Currently there is no mechanism for developers to publish their content in that section.
We are trying to extend IBM Connections 4.5 CR3 with own XPages apps not on the well described widget extension level for communities but on the application level.
Our goal is to extend the applications menu and load our apps inside the connections framework just like the original blogs or forums IBM apps.
Some others tried the same thing like this one:
http://blog.riand.com/2014/06/get-your-application-integrated-within.html?m=1
It seems that the trick for coming around the CORS trouble is not well documented in there.
Mikkel has put some code onto GitHub for the server side page generation:
https://github.com/lekkimworld/ic-wrapper
Can someone over here solve this or help us to come some steps further?
There are a number of approaches you can take, depending how daring you are.
The most pragmatic approach would be:Load a connections page, steal the HTML that makes up the Menu bar, copy that into a XPages custom control and you are done (of course you had added a link to your application beforehand in LotusConnectionsConfig.xml
Check the JSP that reads the LotusConnectionsConfig.xml how it is rendering the menu bar. Configure the Apache HTTP to expose the XML for read access, so you can dynamically create that menu - saves work when your menu changes often
Use the approaches described by Phil
Add a small JS that you call in your added menu. It would remove the content of the Connections page below the menu level and insert an iFrame which loads your XPage
Cheat by building a widget for a community homepage and have just that one widget (taking the whole page as real estate) in that Community
That's just off my head. Hope it helps
In the Google Cast SDK Overview video published on YouTube by Google, the presenter says
There are design implications that are driven from the Design Checklist so in addition to the platform specific guidelines for Android, iOS and Chrome, it is important to do a thorough review of the Google Cast Design Checklist.
The sentence reads like legal-speak, but more importantly, it mentions existence of platform specific design guidelines for Chrome. I never knew that there is anything like that. I attempted googling around, I could find guidelines for Android, iOS, but nothing for Chrome. Does anybody know where the Chrome guidelines can be found?
The design checklist is here: https://developers.google.com/cast/docs/design_checklist
The starting point for Chromecast developer doc is here: https://developers.google.com/cast/
There is an unified design guide for both Android and Web Apps that was announced on June 25 2014 at the Google I/O keynote. It is available at the https://www.google.com/design/ site. Regarding Google endorsed UI frameworks, there are two. Polymer Paper and Google Web Starter Kit. Additionally, there are stylesheets on GitHub from various people that aim to replicate the look and feel of the Chrome Settings page as well as various widely-used opinionated Responsive CSS Frameworks that can provide design clues, most notably Twitter Bootstrap and Foundation.
Polymer Paper
Polymer Paper is a set of Polymer Web Components which implements the unified mobile and web UI concept called Material Design. Some of the distinctive characteristics is the use of drop shadows and animated transitions to hide latency and give feeling of responsiveness. The components are built with the Polymer framework on top of web components, so it works best in cutting edge browsers.
Google Web Starter Kit
Together with the Google Web Fundamentals developer guide the Starter Kit provides a starting point regarding look and feel for your web app (a style guide with UI elements, e.g. sandwich sidebar), as well as preconfigured selection of helper tools to better manage your CSS styles, minify resources, keep performance considerations in mind and so on. The Starter Kit employs production ready tools and procedures that can be used today.
There is nothing like that, the presenter probably just misspoke. The Thinking in Web Apps page on Google Developers could give you some hints, but it feels outdated in many aspects.¨
Just some more general advice on that:
People tend to gravitate towards Twitter Bootstrap these days, so base your design on that and you will play well with others.
Watch the trends and adopt what the big players are using. For example, the sliding drawer on the side seems to be big now.
Regarding the ongoing effort by Google to allow easy porting of Chrome Apps to mobile phones, looking at the Android and iOS guides may help. Most importantly try to optimize your app for touch, avoiding hover, right clicking and minimize the need to type.
The html + css standards difficulties of supporting IE as a browser translate into using it as part of the WebView control where there are further limitations on functionality.
Other difficulties include:
It renders on top of the XAML
- Using the recommended approach of WebViewBrush isn't a valid scenario if your pages have dynamic content on them.
It doesn't support HTML5
You can't access the content
You can't access the content
- Trying to debug issues with it is nigh on impossible.
Are there any alternative embeddable browsers available or in the works?
To answer your question, I think Jim is correct that there are no other embeddable browsers available, and it's not something I'd expect to see.
I would also recommend that you review the Windows Store Certification requirements, as many may be applicable in this case, including:
2.4 "The primary experiences your app provides must take place within the app" (as opposed to coming from the web)
3.6 "Your app must fully support touch input, and fully support keyboard and mouse input" which covers requirements for touch, including the need for your app's touch support to be consistent with the Windows 8 touch language.
While it's obviously appealing to re-use content across platforms, it's also important to keep in mind that this may lead to degraded experiences for end-users. If those experiences are too far afield of the established behaviors for Windows Store apps, they could also result in your app failing store certification.
For more info on Windows Store app development, register for Generation App.
I have an application that will need to better support tablets in the future. I have seen some apps already created with UP1 and ExtLib Mobile Controls but I was wondering if anyone knows of specific functionality that simply is too challenging to even consider bringing to a mobile device?
For example, are there partial refresh issues on specific devices? Can managed beans still be used behind the scenes? Is dynamic content totally viable on mobile?
I'd be interested in hearing what big challenges/functions people had to give up when they mobilized their existing XPage apps.
There isn't really anything in XPages that would prevent building mobile web apps as with other web app dev models. In other words: Everything you can do with web apps on mobile you should be able to do with XPages.
XPages 8.5.3 UP1 comes with Dojo Mobile 1.6.1. However that does not prevent developers from using other frameworks like JQuery or anything else.
There are some advantages in general for native apps and hybrid apps. But personally I think most of the typically rather simple business apps can be built with mobile web apps. If you need local data/offline that might be different though.
You can use Xpages to do anything that is possible with mobile web developement. Dynamic content may not be the way to go for everything, but it will run just fine. In ITANA available for free on openntf.org, i created a simple replication engine to replicate notes tasks from the local device using sqlite to the domino server. This makes it run very fast and allows the app to run offline as well.
So i believe anything you want to try will work, you can make the Xpage output anything you want, from html, to xml, or json, to accomplish your tasks.
I know that XPages was totally incompatible with older Blackberry's. I assume that's not the case these days but back at OS 5.0 I think even buttons wouldn't work. So if you're doing anything with BB make sure it's modern and tested.
We're not really getting tablet support in ext. library until the next dojo rev I think. But there is a preview of tablet support somewhere that you can get. I've not looked yet but it was mentioned at Lotusphere. so if you want to hit tablets you might want to roll your own right now until that comes available.
Tablets are a little more challenging as the mobile controls are designed for the mobile phone size devices. That said with a little trial and error you can get a nice navigator split screen and still use the one page app mobile controls to streamline it, with records opening in their own page just like the phone version. Type ahead as I'm discovering should be handled differently if you are using the iPhone themes from oneui2.1
The oneui2.1 gives your navs and views nice styling. The forms may need a bit of custom styling.
Split your design into custom controls then you can use a server ate xpage for mobile devices and straight web. Or if you forgo the use of mobile single page controls you can always just have a seperate style sheet to accommodate the iPad. Really depends on the functionality needed. Good luck
My suggestion for anyone wanting to do tablet specific development using XPages is to move to Notes 9.0 and dojo 1.8 asap. Dojo 1.8 has an experimental control called ScreenSizeAware. This is miles ahead of anything else either the Extension Library Mobile controls or Dojo provides for Tablet development.