A lot of people I talked to seem to think action button (UIBarButtonSystemItemAction) is for Share or Export functionalities (e.g. like its use in the Photos app).
According to HIG, this meaning of button is to:
"Open a modal view that lists system-provided and app-provided actions
that can work with the current content."
Question - what do you use this button for in your app?
Related
I'm trying to implement a sidebar like the one used in the macOS Notes app. I've got the storyboard and sidebar working. But how can I implement the content window / detail view on the right? I want to show something based on the selection made in the sidebar. I tried doing it by hiding stuff in one view but it gets messy real quick. I'd rather switch views in the same window somehow. What is the commonly accepted way of doing this?
I'm building an Ionic 4 PWA and I am looking for a "simple" solution to the following:
For each item in a list e.g. a newsfeed or comments list: I want a "more" icon (the dotdotdot icon) to show a list of options the logged in user has available e.g. if they own the comment or newsfeed item they will have extra options like "edit" and "delete" etc.
Now I can use an ActionSheet to show these options and dynamically add the correct options into the sheet - all well and good. But this only looks good on a mobile device. If the user is on a desktop then an action sheet looks out of place. So, a Popover would look better but only on the desktop view.
Is it possible to dynamically create a popover in code without having to create a component for it as the items in the popover list will vary depending on what type of object it is e.g. newsfeed, comment etc and their access rights to that object e.g. edit/delete etc.
Not sure if I have explained this very well but looking for a slick, simple UI Ionic 4 way of displaying "options" to the user when then click/tap on the more icon depending on device.
I did go down the route of having ActionSheet for mobile users and Material Design Mat-Menu for the desktop but it just seems over complicated.
Any advice would help.
Thanks,
Rowie
How about a popover with a custom css class that is using a screen media query?
I am fond of the type of side navigation menu that is common in mobile apps. An example is: http://www.jqueryscript.net/menu/jQuery-Animated-Side-Navigation-Menu-Plugin-Sidebar.html
Which works also for web pages. However, the vast majority of my page is in KendoUI, and I don't want to load another framework just for that.
Is there a combination of tricks with Kendo (draw control for example) that I could use to get the same effect?
Alternatively, I am all wet. I just want a quick way to have a "pop-up" of settings that are only occasionally used, and most of the time save the screen real-estate. So maybe just a button and a pop-up window is the correct approach?
Any advice?
I’m working on an application for Android and iOS, which requires a certain flexibility for one or two views. That’s why we created & implemented a service that translated a basic list of objects into a user interface for both iOS & Android. But now that Xamarin.Forms is released, we decided to replace our service by the one Xamarin provides. I did succeed in creating the views with Xamarin.Forms, resulting in better looking & smoother running pages. But my problem lies in the navigation of it. Here is a little drawing on what I would like to achieve:
I would like my app to start an activity that starts with a custom fragment. After clicking a button on this fragment, I would like the page I created with the Xamarin.Forms api to be added to my current navigation stack! Once the user is finished with the Xamarin.Forms page, it navigates to a second custom fragment, all that without breaking the navigation cycle. Does anybody have an idea on how I can achieve this?
For the iOS developpers: replace Activity with NavigationController & Fragment with ViewController
Take a look at CarouselPage for Xamarin.Forms' own approach. It doesn't look like that's what you need but you can also look at its source code and maybe make a custom renderer yourself.
You may also want to take a look at MVVM
As for the easier/hackier way you'd want to make a button on each page and when the button is tapped execute Navigation.PushModalAsync(nextPage) - there won't be a "< Back" button any more, you may need to implement that yourself if you need it.
If by your meaning of 'current navigation stack' is for using the native Navigation of each platform, then remember that you don't have to use Xamarin.Forms' Navigation Model and functions such like PushAsync.
If you prefer to do Navigation with code specific to each platform then you can do this the same as normal. Just create your stub pages in each platform specific project and set the Xamarin.Forms content for each page from the shared project.
From each platform specific stub page (Activity / UIView / PhoneApplicationPage) you could then execute an Action<> call setting on the shared Xamarin.Forms page to help with the navigation, or alternatively, hook into a custom-event that is raised from the Xamarin.Forms** page back to the platform specific stub page to allow you to do navigation from there.
Like Sten mentioned there won't be any 'Back' button so you will most likely have to do that yourself.
I'm currently working on my first iOS application to run on the iPad, and I've come across a problem. I have been asked to implement menu's similar to the ones in the default applications such as when you click on the "Calendars" button in the top left of the calendars app.
Only issue is, I cant seem to find a standard UI object that looks like these, with the arrow connecting the menu to the button etc. Is this a standard UI component that I should be able to use, or will I have to imitate them by creating a custom object?
Thanks for any help.
That is a UIPopoverController. There isn't an Interface Builder control for this. You need to create one programmatically:
UIPopoverController *popover = [[UIPopoverController alloc]initWithContentViewController:someTableViewController];
See the documentation for more information and sample projects, specifically ToolbarSearch: