herzbube
commented
2 years ago Some general ideas:
- The popup client should have to specify as little as possible, i.e. it should be the job of the popup handler to find out in which direction the popup should extend.
- Ideally the popup client should only specify a source view or a bar button item, same as for popovers in iOS.
- The popup should use scrolling if the popup view is too large.
- The popup should support optional animation so that it appears as if the popup view slides in from the source.
Specifically for the markup type:
- There are currently 11 items to select from - simply having a list of 11 items will make the popup too long.
- The popup could therefore consist of two columns with 5 markup types each (column 1: 5 symbol markup types, column 2: 2 markers, 1 label, 2 connections), bounded at the end by the eraser that spans both columns.
- To make the popup small only icons should be displayed.
When the user wants to select a new type of markup to place on the board, the app currently displays an ItemPickerController. On iPad the resulting view can be displayed in a popover, which is quite nice, but on iPhone the view is displayed similarly to an action sheet, which blocks the view of the entire board.
To add a nice graphical touch the markup type selection should be possible in a popup on iPhone devices as well. Popup meaning here, something similar to an iPad popover. Ideally the solution that is developed should be reusable, at least to some extent, to lay the foundation for a tutorial or help mode.
One problem that still is not solved is: How can user code determine the
UIButtonthat iOS creates to represent aUIBarButtonItem? Popovers on iPad support specifying either a sourceUIView(useful when theUIButtonis known), or a sourceUIBarButtonItemfor the popover. If aUIBarButtonItemis specified then iOS "magically" detects the button that is the source view. So far I have not found an API in UIKit that lets my user code perform the same detection.