I plan to hike to Everest base camp in December and my guide told me to arrive in Lhasa. I am currently in Shenzhen and for some reason I am unable to find Lhasa tickets directly from Shenzhen. Which city is the best place to take a direct flight to Lhasa? Or which city in Tibet is the best place to start if I want to go trekking?
I redid a web configuration interface for a hardware element. Think of a configuration interface of a standard router. You install this hardware on your network and access the configuration via your browser. The user interface is normally accessible from a PC and should also be available for mobile devices, but the computer is our focus.
I need to implement a configuration form with a submit button. The old design was done in hardware design and had this layout:
Form1, Form2 are slightly different configuration forms, which have a similar subject (currently active SubMenu1). Think about "IP Address", "Router Name", "DHCP Configuration" etc. it was a router. All have the same Submit button in the upper right corner that applies only the modified entries. For example, if there is an entry for a password, this one will only be applied if it has been changed; otherwise, the old password will remain even if the password has been changed. entrance was empty. The send button, although located on a menu bar, is floating (when the menu bar is not there) and always stays on the screen exactly in the same place when you scroll .
I redo a user interface in the same way, preserving the appearance more or less, but changing the forms to group them into cards:
But I hesitate to use the same location for the Submit button because I think it poses serious problems from the point of view of UI / UX.
- The location is extremely strange and unintuitive. The button is located in the menu that is common to all views and appears / disappears simply depending on the view. Users do not expect it to be there
- The button, although located in the menu, is not associated and floats when the menu is not.
- It is not obvious that if you do not change the password and leave it blank, the password is not changed. My first thought is that it sends a blank password to the system. However, I'm not 100% sure that it's a problem, just find it weird.
The problem is that I do not know where to put the submit button here. My first hypothesis is to float it and place it in the lower right corner. I do not know how to solve the password problem though.
Is this a good suggestion? If not, what should I do? And is it a good idea to leave the password box as it is, or should it be changed?
Stablecoins have similar use cases to Makerdao CDP Dai, as does a room for privacy protection like Monero. But is there a project combining these 2 technologies to create a private stablecoin where you can not see the amounts sent and where and from where they come from?
There are some good practices when designing data tables, but there are no specific guidelines. In a way, it depends a lot on the data you display on each table and the available actions that you allow the user to perform.
There are filtering actions, search actions, customization actions. In your case, you are talking about actions for individual elements / lines of data such as delete / edit / display, so here is my personal opinion about the possibilities you mentioned:
I like this option a lot. This is something we often see in emails such as gmail, Outlook, etc. This reduces the overall visual footprint of the page, but to maintain a proper UI and UX, you need to consider the case where the data is too long and the user has to scroll. Then, the header must be "sticky" and always visible so that when a user clicks on a data item, the actions are displayed. You should also take into account the other actions of the databank that might be visible in the header table. For example, if you have 3 or 4 filters and a search bar on the datatable header, you limit the space to add specific actions to the item.
In my opinion, this option is only viable if the data is small and you do not have many columns. Otherwise, it will take a lot of space to better display another piece of data.
Icons in general are very convenient as long as the user can easily identify them. The 3 points indicate that there are more actions relating to a specific item and that it takes up less space than the previous option, but this requires more interactivity on the part of l & # 39; user. For example, by clicking on the points (1st action), view the most available actions and possibly click on one of them (2nd action).
For the last option (when a user flies over), this reduces the visual clutter as above, but this may again cause detectability issues because the user must interact with the table for view the presentation of the available actions. However, it is a very common practice because the user is already focused on a specific item and expects to have an action on it, either by clicking on it or fly over to see it.
In addition to the possibilities above, you can consider the following options:
Use icons for each action. For example, some icons can clearly represent the actions "edit", "delete", "view / details", which could be added at the end of a table row to minimize the space that they occupy and hence reduce the visual clutter now a better discoverability of available actions.
Use the modal windows at the click of a button / icon to view the available actions, but this poses problems as the 2nd option.
Make the table's lines like accordions / make them extensible. This is more useful when multiple actions are available.
The correct answer to your question is to note each time the data you will display on a scale of data, to consider the number of rows and columns present, to think about the available actions applied to the global table and each data. item / row and design the table and actions according to the above and do not follow a general rule.
Think about the importance of each action, the possibility of action on the part of a user and think as a user to see what would be more convenient for you. Are actions easily discoverable? Can you expect interactions to be needed to act?
Here are some resources for good practices in table design:
As for actions, I would say "delete", "edit", "details" and many more. How to display this on a desktop application. Some possibilities that I have already used could be:
- Add at the top before the header and display when an item is selected
- Inside the row at the beginning or at the end
- With a three-dot icon after the first cell, you can see in Sharepoint.
- At the top of the line when you're done with the mouse
My comments are as follows …
For the first, it's good to define the batch action (what you do with a group of things) or with the table as a whole. But sometimes you also see actions for the selected item. Could be good when you have a lot, like 5 to 10 actions. And it's a good idea because you have space and on your datatable you only have DATA and nothing else. But for a user, it is not always easy to understand the link between the actions performed on the higher data server and the selected article.
For the second, I like it because you understand directly that these actions are for the purpose. But if you put in the end and your table has multiple columns or if your screen is small, you should always scroll and you have not seen them directly. If you put in the beginning this can take up a lot of space and the most important thing (the data) is pushed to the bottom and maybe outside the visible part of the page
With the third, you can group it and save space. Your button will always be visible and will not take up too much space. But the user has not seen the actions directly and for all the actions that he wants to do, he has to do one more click to open the menu, then find in the menu what's wrong. he wants, then click again. The activation of an action takes longer than other solutions.
The last one … I'm not a big fan, it covers the data and you think there is a little problem on the screen.
To summarize, there is no satisfactory solution or standard in material design and that's a shame.
If you have articles / comments that speak around this problem … please send me!
I have installed Android x86 8.1 and with some modifications
silead_ts.fwI managed to make the touch screen work properly because the one that was originally was buggy. But, I installed another x86 – PrimeOS distribution. Now the touch screen does not work at all even after replacing the right silead file under
I tried to run
getevent. Although the 8.1 detects the touch screen as being the Silead 1680, PrimeOS does not show it at all. I've found that the touch screen on PrimeOS seems to work for some.
Is there a way to activate the touch screen? Or, debug the problem?
I'm using PrimeOS Standard with the Linux 4.14.x kernel
How can I integrate custom JS payment gateway sure check out page?
I want to call JS method on click event of To order after that
bring up a modal and after payment with ** JS **, wait for it payment response finally submit the order.
So we currently have the following:
MYTABLE COLUMN: ID (INTEGER Primary key, auto-incrementer) COLUMN: START (DATE) COLUMN: COMPANYID (INTEGER, Foreign key to COMPANY) COLUMN: DELETED (INTEGER) CHECK: DELETED = 0 OR DELETED = 1
Now, it is necessary to allow an unlimited number of deleted records, but to allow only one record not deleted for each date + company.
I suggested changing the schema to:
MYTABLE COLUMN: ID (INTEGER Primary key, auto-incrementer) COLUMN: START (DATE) COLUMN: COMPANYID (INTEGER, Foreign key to COMPANY) COLUMN: ACTIVE (Nullable INTEGER) CHECK: ACTIVE = 1 OR ACTIVE IS NULL UNIQUE: START, COMPANYID, ACTIVE
Although my colleague believes that this "goes too far with constraints" and that we should simply trust the verification of uniqueness in the application.
Is there a generally accepted best practice here?
I integrate a custom payment gateway module into magento2.
How can I use JS / ajax on the payment page when clicking on a command in order to trigger a js event?
Since I need to display a modal on an order click, we must prevent the submission from creating the order and check the payment response with js, then submit the order form with the payment response.
An idea how is this possible?
What happens is that I store this in a php variable:
$datos = "
" . ""; " . "" . " " . " $documento" . " C" . "
but when i go to print it, i get it like this:
All in lowercase and I would like to keep uppercase letters, how can I make sure that uppercase letters are not changed to lowercase? I appreciate your help in advance.