Different ways of exposing data

Asked

Viewed 97 times

4

It is wrong to expose data and actions that should (inputs, and buttons) be made on these data in tables?

Example in the figure below this being displayed data and actions that should (inputs, and buttons) be made in table form (in red) marked with a green arrow this the header and blue the contents of the table, this form of exposure is correct (remembering the tableless)?

SS

html layout

  • Don’t get it, can you edit and explain the question better? Want to know if you should use table or division in this case?

  • Yes, I wonder if in this case the use of tables goes against the tableless patterns

  • I see no problem having actions within the table, but of course, this is a matter of opinion =). However, if the table will have few records / rows, I believe a different way to display the data is better, as a card for example. Link

  • Hello @Oeslei, well there will be a few dozens of data, I think this amount would make the use of cards impossible but I will see if I apply among other points (I think it is very interesting)

  • Hello. I don’t know what the "tableless pattern" is, but if I understand correctly your question is very close to this one: http://answall.com/questions/31286/usability-de-a%C3%A7%C3%B5es-em-grid

1 answer

4


Right or wrong is relative. I doubt there is a definitive answer to each case. You have to do what is ideal for the situation. In fact it needs experience to get each case right, especially when it seems that two solutions are viable, and this is important. The problem with using the table as a formatter (which occurred in the past) is that it made a lot of things impossible, for one reason or another.

At first you would not see much problem in using a table in this case because you will assemble a table of data. It is clear, mainly by the header, that you have a table there, but you have to ask yourself if you are dealing with a data table or just with presentation formatting. This must be the criterion.

If it is a table, it seems to be, you have to see if it is composed of several rows and only one column. Or if it will have several columns per row. Again you should ask yourself if these row data are separate items from the table, are true cells or are separated only by formatting. Having multiple columns doesn’t feel wrong.

I don’t like having action buttons in a column. They’re not given. But I’m not saying it’s all wrong. The checkbox it’s also an action and I think few people will say it’s an abuse to put it on the table.

I still think they should be somewhere else, possibly in a room in another layer and maybe even just trim when they pass the mouse. Even if they stay fixed, they look like intruders in the data room. The "Status" also has a button but it does not look intrusive, it seems suitable as UI to change the state of the data contained there. The problem of others is that they appear to be related to the whole line and this needs to be demarcated better.

Maybe a hybrid is doing well, like almost everything else. You can use divisions just about anywhere. Use table where it is a table but whenever it is not clear that an element is a data cell, use division.

Making it clear that the exclusive use of divisions is perfectly feasible as well and some people would prefer this way. An example. This solution can give more power and flexibility, although it is slightly more complex to assemble a table. Consider these points. What is more important in this case? Think a little about the future too.

I researched known projects what was the choice and their motivations. It seems that no one has a definitive word because they have chosen to use divisions exclusively. Probably get more guarded using something more modern and complete. I saw in many cases that could have used table without problems. That is, it doesn’t really seem to have right or wrong but there is a clear preference for divisions.

Of course this makes a lot of sense in libraries that will be used by many, the extra work (which is not great) pays off. For a quick thing I don’t know if it pays off. But also if you do something once that can be reused other times, maybe it pays off.

I’ve given you some allowances, let you know what’s right.

  • Excellent answer, what really bothered me was the buttons inside the columns

  • 2

    I do not see why it is wrong to have actions along with the data, since the actions are executed on the data of the respective lines. I wasn’t familiar with the term "tableless pattern", but searching saw that it is about avoiding using HTML tables to format nontabular content (because you should use CSS for this). Note, however, that this is not the case of AP, since it has a tabular list of elements. :)

  • 2

    This is not the @Luizvieira I know, as you may not have heard of tableless? :P But you’re right, I would probably use table in this case. If one day it turned out wrong I would simply change. I would certainly do it in a way that wouldn’t be too traumatic to change. I think purists will say that having buttons in there is wrong, but I never give a damn about purists.

  • 2

    Hahaha It happens in the best families (well, at least I’m glad I learned a new term today!). Purists could be refuted with usability criteria (my not-so-secret weapon of habit hehehe). :)

Browser other questions tagged html layout

You are not signed in. Login or sign up in order to post.