Graphical user interface design: How to present the Actions buttons (eg, CRUD) without diverting attention from the main content?

If you have a means to select individual objects with something like your Select column, then you do not need separate command buttons like your Actions column, and vice versa. Choose one or another approach. The action-selection-object approach is preferable when the space is reduced and / or has many commands. Have a single sidebar menu (web application) or drop-down / pop-up (mobile) menu that displays each command once. The user selects one or more objects and then selects the actions that will be executed on the selected objects. Each command only appears once, so you can use longer text labels, which are generally easier to understand than the icons. You may want to consider abbreviated commands with especially long labels. Use the information on tools to provide the full name of the command for users who are still learning the application.

Drop-down menus in particular can be relatively laborious to use, so you can also have context menus (right-click). However, contextual menus are generally considered backup access experts, since they have little detection capability, especially in a web application, where users can assume that clicking with the right button only displays the contextual menu of the browser. Therefore, they should be used in addition to a pull-down menu / sidebar.

You can also provide expert shortcuts using acceleration keys and gestures, including double-clicking and drag-and-drop. Unfortunately, there are no standard gestures for CRUD functions for mobile devices; We need them. For a web application, the Insert and Delete keys are obvious options as accelerators for the Create and Delete functions. Obtaining details (ie, Properties or Details) can be achieved by double-clicking on the object or by clicking on the identifier of the object represented as a link. The latter is easier and more visible, but it makes it problematic to admit the edition instead of the identifier.

Yes, the ideal is to use the edition in place to support the update function. Use the appropriate control to support the editing of each field wherever it appears. This not only eliminates the Edit command, it simplifies the menu, it also keeps the focus on the main content and eliminates the navigation steps and even the entire pages, thus simplifying the entire application. A Save command can save all changes (including Deleted and Created), or, better yet, can save automatically, delete another command and prevent data loss.

The recovery function is usually best handled through a separate query dialog, although that may divert the user's attention away from the main content. To minimize that, keep the simple and simple query basic dialog box, admitting only the three to five main types of queries that probably represent 80% of all queries made, then provide an Advance or More button to get a further dialogue detailed. for general ad hoc consultations. It may also make sense for controls for a basic type of query (for example, by object identifier) ​​to be shown full-time at the top of the main content page (for example, as "search").

java – Why could this method be defined in the interface but not implemented in class?

Let's say that here I have a Java Eat interface:

public interface eat
eat vacuum by default (flesh of meat) {}

eat worthless emptiness (meat of the flesh, humor) {}

And I have an abstract class that implements only one method in the interface:

The public abstract class DogBase implements Eat {
empty public eat (meat meat) {}

And I have a class that extends the abstract class:

Dog of public class extends DogBase {


Then I found that in the unit test for the Dog class, the method was disused:

eat worthless emptiness (meat of the flesh, humor) {}

defined in the Eat interface can be called by an object of the Dog class.

Why is this possible? In my understanding, the DogBase abstract class only implements the non-deprecated method defined in the interface so that the Dog class does not have the method deprecated.

Graphical user interface design: iOS configuration standards: use Checkbox instead of changing

If you are familiar with iOS devices, you know that the configuration application uses the UISwitch control to show that a parameter is enabled or disabled. This control appears as a toggle switch and even has an animated switch movement that tracks the user's finger as the switch slides from one side to the other.

On my iPad, I noticed an exception to this. A check box is used for what would normally be associated with a radio button.

The toggle switch takes up a significant amount of space on an iPhone, which I can use better.

I have access to the configuration with a user interface from within my application (and only from my application), and I can get out of this practice of using the switch, replacing it with a check box. (This would simply be a custom UIButton). I wonder if there is a drawback in doing this from the perspective of the user experience.

Design – What is the best / most used web user interface builder?

I would like to know which user interface tool most web developers use, or do you try to do a bit with CSS until the result is correct? I have a hard time creating the user interface and it still looks ugly, even in my standards.

I have used Microsoft Frontpage for a long time and I really liked it. Dreamweaver is too cumbersome for most of the part, plus it generates a huge amount of code.

Any help / tips / pointers would be appreciated.

html: the best way to implement a simple HTTP server for the user interface in Python?

I'm doing a web scraping tool and I want to be able to take advantage of the power of HTML, CSS, JavaScript, etc. I used to be an independent web developer and I feel much more comfortable creating a web page than designing a GUI.

So far, it seems that trying to implement my own simple HTTP server will be a lot of code and will take more time than the scraper itself. Are there good options specifically for this kind of thing?

graphical user interface design – native date pickers VS custom date pickers

What is the case of using best practices for the selectors of date (calendar)? Native or personalized?

Native looks great on iOS and Android devices, however, when looking at non-mobile calendar pickers, browsers vary in design and ease of use. The requirement is to design a calendar selector that is mobile for the first time but compatible at larger breakpoints.

Has anyone encountered this situation before? How did you approach it? What should I consider?

graphic user interface design – button bar: criteria and position

Is it a good idea (separate the action from the navigation buttons)?

Would the criteria be clear to end users?
If they are well executed, they will not notice it but will act as if.

However, your improvement violates a golden rule:

Navigation buttons go before What they affect.
Confirmation buttons go after what confirms

However, in that particular case, I would say that it is not a big problem to violate this, given the design indications (for example, the separation line) that it suggests.

It would still be fine if I had them in a row, the confirmation on the left, "Select company" on the right.

If that is not a pop-up window / secondary form, you might consider removing the explicit "Closure", since this is usually in the window frame.

ios: How will XCode, UIKit and Interface Builder be used?

I'm immersing myself in iOS development these days, and I've been very confused about XCode and the Apple Dev ecosystem.

First, there are no more Storyboards and Interface Builder tutorials in official Apple documents (or I have not seen any).

Nor is there a way forward to enter the development of iOS.
It seems that XCode is not a good tool.

There is not a good divisor between What you should do programmatically and what you should do in Interface Builder.

If I analyze some open source projects, it seems that the full programmatic approach is much preferred over Interface Builder, but it is still necessary to have at least one Storyboard.

XCode feels that it is inconsistent in its state. I have seen that Apple is developing SwiftUI, which seems to be completely programmed and declarative.

So here comes my real question: Is Apple in a transitive phase of what has been a design flaw (Interface Builder)?

If it is a no How do you think Apple's tools should be used?

I do not know if it is not based too much on the opinion, but I would like to know the "good practices" and the "best practices" in the development of iOS.

Graphic user interface design: Does the text of the scrolling status button have to comply with the accessibility guidelines?

Yes of course. WCAG 2.0 version 1.4.3 did not mention anything specific regarding the color change for the button text in the scroll / focus states. It is safe to assume that the button text in the shift / focus states must maintain a contrast ratio of 4.5: 1 or more to pass the AA conformance level of WCAG 2.0. You can find more information here:

If you are looking for accessibility guidelines for content in focus / displacement states in general. They are clearly explained in the latest version of WCAG 2.1 2018 in the success criteria 1.4.13

Input fields – How to display text with label in the user interface of the material?

On a single page, I would like to show the text fields for the user's entries and the texts, which are static, but have labels. I tried using the same text fields but with the attributes disabled:

enter the description of the image here

However, I am not happy that the disabled fields are not bright enough. Actually, those fields never pretended to be editable, so it seems that the disabled state is not for them. I also looked at some elements of the Material UI, which is text with a label, but I could not find anything appropriate.

How material UI is representing elements with important text and label?