How to develop “360 flat image view” in “panorama view” for web application - panorama-control

My friend wanted me to find “360 jpg image (Taken by phone) in panorama mode in web application”. What would be the best technology for develop that module.
Are there are any open source technology/libraries, reference materials or any tutorials?

For Android, you can try this demo
Try GoogleCardBoard Sample

Try including this to your build.gradle
compile 'com.gjizhe:PanoramaImageView:1.0'

Related

How to implement Remote Desktop for Android?

I want to develop a Remote Desktop application for Android , Part of my project, Can please someone help me out? or have tried any thing?
Maybe you can take a look at some open-source solutions and gain some inspiration. After some quick search on google I found this project http://jrdesktop.sourceforge.net/ which is an open source java implementation of a remote dsktop app. I also found a SO discussion on the topic: Implementing my own remote desktop in java
Good luck! :)

How to make android app that reads pdf books easily

I am trying to build an android application that reads PDF books .
I am developing using android studio
the books will be within the app files ,, so the app is not for reading other PDF books on the phone.
also i will add a feature to it ,,so that when i click on a paragraph ,a sound file will be played.
I hope you can help me out and guide me at least with the main steps to do that.
Many thanks in advance.
Apache PDFBox is an API to read pdf documents.
Start with this tutorial-https://pdfbox.apache.org/2.0/getting-started.html

HoloLens holographic app

When you use the "Holographic DirectX 11 App" template in Visual Studio, it creates an app that occupies the entire HoloLens view (I believe it's call the Holographic View).
How do you build a Holographic App like the Hologram demos where you can re-size the box and place the app in the Holographic Shell?
BTW, can someone with a higher reputation create a new tag "hololens-directx". I think there are beginning to be more DirectX development and this would help distinguish from the Unity questions.
Short Answer: Not Yet
Microsoft is reserving development right such as this as well as live tiles. Of the many forum posts regarding this, an official Microsoft team has formally responded to this one below.
To understand more options available to you in your app development, see this page about the app model.
The ability to place holograms into the Holographic Shell is not exposed to app developers.
Hologram app is an inbox app and third party apps cannot replicate this functionality.
App developers can only place GLTF model into Shell as a link to their app.
https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-uap5-mixedrealitymodel

Can I drag a file out of a node-webkit app and drop it on the Desktop?

The client is trying to figure out whether they'd like to go with a node-webkit app with AngularJS, but their one sticking point is that they'd like to be able for their users to drag a file out of the app and onto the desktop or an email client (such as Outlook or Lotusnotes) like you can do with an applet (which I'm desperately trying to avoid).
As far as I can tell, this doesn't look possible, but I'm not well versed yet with the latest stuff you can do with HTML5 and Chrome specifically. Any guidance is greatly appreciated.
Edit: I've also never used node.js
http://www.html5rocks.com/en/tutorials/dnd/basics/#toc-dnd-files
http://www.thecssninja.com/javascript/gmail-dragout
The answer is yes. Here is some more text so that I can submit my answer.
#tjb1982 Using a demo like this one:
http://www.thecssninja.com/javascript/gmail-dragout worked for simple files, but when trying to drag a WAV file or MP3 file into a audio software( like logic, pro tools, ableton ) they won't recognise it as an audio file.

Code sharing between MonoTouch and MonoForAndroid

What would be the best practice to share busines logic c# code between MonoTouch and Mono For Android projects?
Edited:
Initially, my question was about the physical file sharing:
What do you propose to use: network file sharing or some code
version control (git, svn)? In my case I am using two workstations -
Mac (MonoDevelop with MonoTouch) and PC (Visual Studio with
MonoDroid).
What about Solution/Project folder structure? In
"Blog Post: Xamarin Mobile World Congress 2012 Unofficial
Conference App Released!" example structure is quite confusing:
several solutions in one folder and then different platform projects in one
subfolder with different folder and project names. It can not be accomplished nativly
with IDE. Are they editing content of solution files and folder names manualy
outside of IDE environment?
And for projects of common code what kind of profile (template) to
use? Monotouch has several: Empty Project, MonoTouch Library
Project and MonoTouch Binding Projects? In Android i supose -
Android class library?
This is a very general question, but here are a few resources that may help you get started:
Video: Cross-platform Mobile Development
Blog Post: Shared Libraries For Windows Phone 7, MonoDroid and Beyond
Book: Mobile Development with C#
Blog Post: Xamarin Mobile World Congress 2012 Unofficial Conference App Released!
Edit (to answer your new questions)
The idea behind linking files across projects is that there is only one actual copy of the file, rather than having to manage multiple copies and keep them in sync yourself. The file will actually exist in just one project and be linked into the others, but when the projects are compiled it treats the file as if it were actually there.
I can't speak to exactly how they created their folder structure, but I know there have been many cases where I would manually edit project or solution files to get the folder structure I want, because there was no way to get what I wanted through the IDE alone. This really boils down to personal preference on how you want your folders to be structured.
In the end, what you need is a class library project for every platform you want to target. When going with the linked file approach, it's totally up to you where you put the physical files. One approach I use often is to actually create a standard .NET 4.0 class library, put the files in there, and then link them into my Mono for Android and MonoTouch class libraries. If all you care about is targeting iOS and Android, that may be more trouble than it's worth, and you can just let the files live in one project and link them into the other.
Disclaimer: I've got a particular Mvvm methodology that I use for sharing code across multi-platform projects...
Despite this, I genuinely don't believe in "one size fits all" frameworks - I think you need to be careful to pick an approach that best suits your project, your developers and your organisation.
With that said, some of the tools you can use within the Mono development approach are:
using Portable Class Libraries to share exactly the same code between platforms
using platform specific Class Libraries to share code between platforms, linking these using the Project Linker tool from Microsoft
using #define code within your class libraries to provide platform specific implementations of the projects (I personally try to avoid this approach, but it does often provide the quickest route to market)
using DI/IoC techniques to provide components for those occasions when platform specific implementations really are required.
using a assembly linking to provide IoC - e.g. this is what the Xamarin MobileAPI does
using server-based logic for genuine shared functionality - e.g. using REST or SOAP-XML services to implement logic
sharing tests (e.g. NUnit) between platforms to assure the quality of your logic
using shared code techniques - MVC (MonoCross) or MVVM (MonoMobile.Views or MvvmCross) for UI "controller" logic; MonoTouch.Dialog and MonoDroid.Dialog for "View-level" abstractions; CrossGraphics for UI "drawing"; SQLite.Net for database; etc.
I'm finding the MonoTouch, MonoDroid and the Microsoft tools provide real and signigicant benefits in developing cross platform code - but you do have to work and think to achieve this.

Resources