In a silverlight composite application, is it possible to implement navigation, so that the back and forward buttons would be functional?
Take a look at this article (http://csharperimage.jeremylikness.com/2009/11/dynamic-module-loading-with-silverlight.html) written by Jeremy Likness. He is using Prism and Navigation framework and its a good article to get you going with.
The "Navigated" on the Navigation Frame object will be called whenever the user click on the browser back or forward button.
Hopefully this is enough to get you going. If you have any more questions just let me know.
Related
I have a client that adamantly insists on a solution with embedded camera in terms of having a ContentPage with an camera stream and custom buttons and icons, similar to https://github.com/pierceboggan/Moments, or at very least as I understand it seeing as it is a Snapchat clone. And my client wants similar swipe capabilities as to how navigation works in Snapchat.
However, as far as I can tell most of what is utilized in that solution has been deprecated.
I have suggested using the Media Plugin https://github.com/jamesmontemagno/MediaPlugin but they're not satisfied with the camera being pushed on the stack.
I've looked into implementing it natively and using dependency injections but it appears to be an overwhelming amount of work just to implement the most basic functions, particularly for Android's Camera2.
I'm hoping someone can provide me with good news of an easier alternative or an alteration to either Moments or Media Plugin or anything similar that will facilitate the requirements or if my only option is time consuming and complex?
From the code of Moment, you can do what you want to achieve. I did this for iOS.
You will have to create a custom renderer to display the camera page. You will be able to add buttons on top of it.
You could try this example which use custom renderer to add a take photo button and switch camera button on the camera view. Which is able to use on iOS and Android platform.
Main Page:
Camera View with custom button page:
I'm looking from a couple of hours now about "How to design my app around my camera view"
So, I searched about how to use the camera and the Xamarin XLabs and the MediaPlugin are the ones that shows up the more.
However, when I'm looking at them, also when I'm looking at Moments, I can't find the way or understand how can we use the camera as an XAML component, to be able to design on the live view of the camera?
I'm not coding with an MVVM logic but with a MVC logic, so maybe that why I don't get it, I don't know.
You can create a view renderer for your camera, so you just have to add the view in your XAML, and you can add the design you want in your same XAML.
Take a look on this:
https://developer.xamarin.com/guides/xamarin-forms/application-fundamentals/custom-renderer/view/
If you open your iTunes and in the Help menu select iTunes Quick Tour you will be presented with a guide on how to use the app. I want to create something that resembles the transitions this window has. I am trying to start this using Storyboards instead of programmatically. The dots at the bottom allow you to jump to a specific view as well as transition to the next view or previous view.
I am developing this guide in swift for an OS X application.
1) Would this be easier done using a Page Controller or a Tab View Controller or something entirely else?
2) I googled but couldn't find any guides that were close enough to help me get this done. Any guides for this would be appreciated.
I am trying to make a drop down navigation menu for an iPhone client to my website. The menu type that I am searching for is the one used in Facebook's iPhone client. It is found in the upper left-hand corner of Facebook's application after you sign in. Is anyone familiar with this?
Here is a link to an open source controller that implements a slide out like the facebook app.
http://ipup.github.com/PPRevealSideViewController
slide out menu
There are a few other examples around in the community, but I've had luck with this one and hopefully you will too.
be well!
I am building an app in which at some point I have to show TabBar Controller but my app allready has Navigation Controller, so the most obvious sollution would be to push TabBar onto Navigation.
Apple in it's developer documentation states following:
"You never want to push a tab bar controller onto the navigation stack of a
navigation controller. Doing so creates an unusual situation whereby the tab bar appears only while a specific view controller
is at the top of the navigation stack.
Tab bars are designed to be persistent, and so this transient approach can be confusing to users."
Well I made it this way not knowing about this recomendation :). Now I am wondering if my app could me rejected because of this. Do you have any experiences with this? What do you think aboute this?
I don't think they're going to reject your app (not sure about it, but I don't think anyone can be), but your structure seems very confusing.
have a look at this: iOs Human Interface Guideline
For example:
"Use a tab bar to give users access to different perspectives on the same set of data or different subtasks related to the overall function of your app. When you use a tab bar, follow these guidelines:
Don’t use a tab bar to give users controls that act on elements in the current mode or screen. If you need to provide controls for your users, use a toolbar instead (for usage guidelines, see “Toolbar”).
In general, use a tab bar to organize information at the application level. A tab bar is well-suited for use in the main app view because it’s a good way to flatten your information hierarchy and provide access to several peer information categories or modes at one time."
I think you should transform your tab bar in a tool bar.