I'm new to WP7, coming from .Net/Silverlight.
I like the Panorama idea, which would work well with the application I have in mind. However, on the side of the panorama, I need to have a few other screens which do not interact with the main Panorama, so I was thinking of creating a menu at the beginning to select in which branch the user wants to go.
Can I use the Panorama app to meet this need, or do I need to do a classic app and handle myself the screen transitions?
You can do this with the panorama.
It's quite common for a panorama to have an item which is a menu containing links to other parts of the app.
This can help you have a better picture of how you can embed menu in your panorama control:
http://mobilewares.net/images/WP7/BSRV1/sm/panorama.png
Related
I've been playing around with creating a Menu Bar app for macOS.
The app consists of an icon along with a title. The title displays additional context and can be dynamic width.
I've noticed that when the Menu Bar does not have enough room to display the icon AND context, it hides the whole app completely (icon and context) until there is space once again to show it.
Is it possible to prevent it from doing this somehow? Or at the very least maintain the icon visibility without the title, if room doesn't allow?
Unfortunately no, NSStatusItem lacks methods to indicate visibility or occlusion. The functionality you want might be possible via notification, but that is up to Apple to implement.
You may use two separate NSStatusItem. Looks like after creation they should be adjacent, until user reorders them with Cmd-drag.
I create my first app for Windows 10. I will use the app for Windows 10 desktop and phone. Great that one code will run on desktop and phone. In my old application for Windows Phone 8 I use Panorama control with three tabs. But I can not decide which component to use - SplitView or Pivot? For desktop better suited SplitView . For phone better suited - Pivot. Need to choose one solution. What do you advise?
First, your following statement is incorrect.
For desktop better suited SplitView. For phone better suited - Pivot.
SplitView and Pivot are for different purposes -
SplitView consists of two parts - Pane and Content. The Content is where the main content goes. The Pane is really just a drawer. This control is meant to provide a very common drawer navigation pattern to the new UWP apps, similar to many iOS and Android apps.
Note that this control is also very flexible, you can use AdaptiveTrigger to customize its DisplayMode to completely hide the Pane when it's on a phone, and make it always visible when on a desktop machine.
Prior to UWP, the original Metro Design heavily relied on the Panorama control (i.e. the Hub control in UWP) for menu navigation and this later becomes a bit boring since almost all the apps that need a menu, use a Pano. So having a new SplitView will definitely help developers be a bit more creative on the main layout design. And besides, the drawer navigation is so widely used across other platforms and users generally know how to interact with it.
Pivot on the other hand, is simply a swipe-enabled tab control. It's meant to display information at the same level and should never be used like a navigation frame. Leave the navigation bit to the SplitView or the old panorama style Hub control, or whatever creative ways you can come up with.
So to answer your question, you don't have to choose one between them, these two controls can co-exist since one does the navigation and the other shows the information, just like what's in the picture below -
I have a screen in my application which has GPS details. Now I am thinking I will add a map to this page. So I want to display this map when user swipes from left to right .I feel panorama app will be good for this. Any idea how do I convert this to panorama app ?
Create a new project and select the Panorama Template.
Then add the UI code of your old app, add as the Panorama item of new project. You can any no of Panorama items. Check this Panorama Control link
If you open up the WP7 settings app there is a pivot control, and when you select an item in the list (say, the WiFi settings item) it has a nice, pretty navigation to a subpage where you tell it exactly what settings you want.
I want to do the same thing in my app - have a list of items, and when an item is selected, I want to navigate to a new subpage in the same beautiful manner. This seems like a simple task, but I don't think I'm searching for the right terms in Google. How is that effect achieved?
Please see these tutorials on making wp7 navigation transitions:
http://windowsphonegeek.com/articles/Windows-Phone-7-Navigation-Transitions-Step-By-Step-guide
or this one:
http://rhizohm.net/irhetoric/post/2010/11/09/Page-Transition-Animations-and-Windows-Phone-7.aspx
I am new to windows phone (WP7) and to me it looks like everything on WP7 is about pages. I want a small window to pop up from the bottom of a page while staying on the same page. The small window will have some controls (like slider, list etc.). It should not behave like a modal dialog box though, i.e. the rest of the page (which is not covered by the small window) should still be active and user should be able to do something there. And I want to have a separate C# class which will handle the events from the controls on the small window.
This is very easy on iPhone, using view controllers, is there something similar on windows phone?
It sounds that it would make sense to make your "pop up" part of the page with the content it is intended to manipulate content on that page. If you want to encapsulate the functionality of the "pop up" you could make it a UserControl. If you went this route then animating it to slide onto the screen will be straightforward.
Windows Phone 7 typically uses an MVVM model compared to iPhone's MVC one for app structure. The direct comparison therefore isn't appropriate. WP7 also uses a very different design language to that of the iPhone and so a straight port of application design and layout is also unlikely to create a great experience on WP7.
I'd recommend taking some time to understanding the differences in the platforms and how your existing design would be best suited to recreation on WP7. Not only will this help you create a better experience on WP7 but enable to see if this your question actually relates to something you should be doing or not.
This very much sounds like something that goes against the nature of the platform, and the general design guidelines.
If you're providing some available configuration options to the user, you should do it on a separate page, so the user can change the settings there, approve it, and then be navigated back to the previous page.
However, if you really want to, you're talking about displaying a UserControl inside a Popup. But it wouldn't be a very good user experience, and confuse most users, as it doesn't follow the same look&feel as the rest of the platform.