My name is Ismael Chang Ghalimi. I build the STOIC platform. I am a stoic, and this blog is my agora.
The display of perspective bindings and parameters has been improved. Instead of showing bindings on an horizontal bar and parameters on a vertical panel, both are shown on the vertical panel. And while we distinguish them by hiding parameters behind a “More parameters…” menu, we do not make this distinction more explicit, so as not to use the word “bindings” because it is considered a bit too technical.
The display of perspective bindings and parameters has been improved. Instead of showing bindings on an horizontal bar and parameters on a vertical panel, both are shown on the vertical panel. And while we distinguish them by hiding parameters behind a “More parameters…” menu, we do not make this distinction more explicit, so as not to use the word “bindings” because it is considered a bit too technical.
The display of perspective bindings and parameters has been improved. Instead of showing bindings on an horizontal bar and parameters on a vertical panel, both are shown on the vertical panel. And while we distinguish them by hiding parameters behind a “More parameters…” menu, we do not make this distinction more explicit, so as not to use the word “bindings” because it is considered a bit too technical.

The display of perspective bindings and parameters has been improved. Instead of showing bindings on an horizontal bar and parameters on a vertical panel, both are shown on the vertical panel. And while we distinguish them by hiding parameters behind a “More parameters…” menu, we do not make this distinction more explicit, so as not to use the word “bindings” because it is considered a bit too technical.

See the CSS3 icon at the top right of the first screenshot? It’s missing some padding on the right. On the second screenshot, it’s been fixed. Well, fixing this kind of problem, is really tricky, because we have so many different types of iconographies, as you can see on the following screenshots. Some are using raster images, other vector images. And sometimes we’re using icon fonts. And every type of iconography needs slightly different padding rules. In this particular case, we actually added padding to the SVG image itself. Once again, it’s all in the little details…
See the CSS3 icon at the top right of the first screenshot? It’s missing some padding on the right. On the second screenshot, it’s been fixed. Well, fixing this kind of problem, is really tricky, because we have so many different types of iconographies, as you can see on the following screenshots. Some are using raster images, other vector images. And sometimes we’re using icon fonts. And every type of iconography needs slightly different padding rules. In this particular case, we actually added padding to the SVG image itself. Once again, it’s all in the little details…
See the CSS3 icon at the top right of the first screenshot? It’s missing some padding on the right. On the second screenshot, it’s been fixed. Well, fixing this kind of problem, is really tricky, because we have so many different types of iconographies, as you can see on the following screenshots. Some are using raster images, other vector images. And sometimes we’re using icon fonts. And every type of iconography needs slightly different padding rules. In this particular case, we actually added padding to the SVG image itself. Once again, it’s all in the little details…
See the CSS3 icon at the top right of the first screenshot? It’s missing some padding on the right. On the second screenshot, it’s been fixed. Well, fixing this kind of problem, is really tricky, because we have so many different types of iconographies, as you can see on the following screenshots. Some are using raster images, other vector images. And sometimes we’re using icon fonts. And every type of iconography needs slightly different padding rules. In this particular case, we actually added padding to the SVG image itself. Once again, it’s all in the little details…
See the CSS3 icon at the top right of the first screenshot? It’s missing some padding on the right. On the second screenshot, it’s been fixed. Well, fixing this kind of problem, is really tricky, because we have so many different types of iconographies, as you can see on the following screenshots. Some are using raster images, other vector images. And sometimes we’re using icon fonts. And every type of iconography needs slightly different padding rules. In this particular case, we actually added padding to the SVG image itself. Once again, it’s all in the little details…
See the CSS3 icon at the top right of the first screenshot? It’s missing some padding on the right. On the second screenshot, it’s been fixed. Well, fixing this kind of problem, is really tricky, because we have so many different types of iconographies, as you can see on the following screenshots. Some are using raster images, other vector images. And sometimes we’re using icon fonts. And every type of iconography needs slightly different padding rules. In this particular case, we actually added padding to the SVG image itself. Once again, it’s all in the little details…

See the CSS3 icon at the top right of the first screenshot? It’s missing some padding on the right. On the second screenshot, it’s been fixed. Well, fixing this kind of problem, is really tricky, because we have so many different types of iconographies, as you can see on the following screenshots. Some are using raster images, other vector images. And sometimes we’re using icon fonts. And every type of iconography needs slightly different padding rules. In this particular case, we actually added padding to the SVG image itself. Once again, it’s all in the little details…

We’ve improved the way image iconographies are shown in the Record View: paddings have been removed, and the image takes the whole height of the header bar on the Record View. As a result, rounded corners have been removed as well.

When you click once on a cell from the grid perspective, the record is selected and displayed on the Record View, but the cell that was clicked is not activated (first screenshot). It’s only when you click again on the cell that you can edit its content (second screenshot). This is to prevent the involuntary editing of cells. And when the grid is displayed in full screen mode, selecting a record does not open the Record View anymore (third and fourth screenshots).
When you click once on a cell from the grid perspective, the record is selected and displayed on the Record View, but the cell that was clicked is not activated (first screenshot). It’s only when you click again on the cell that you can edit its content (second screenshot). This is to prevent the involuntary editing of cells. And when the grid is displayed in full screen mode, selecting a record does not open the Record View anymore (third and fourth screenshots).
When you click once on a cell from the grid perspective, the record is selected and displayed on the Record View, but the cell that was clicked is not activated (first screenshot). It’s only when you click again on the cell that you can edit its content (second screenshot). This is to prevent the involuntary editing of cells. And when the grid is displayed in full screen mode, selecting a record does not open the Record View anymore (third and fourth screenshots).
When you click once on a cell from the grid perspective, the record is selected and displayed on the Record View, but the cell that was clicked is not activated (first screenshot). It’s only when you click again on the cell that you can edit its content (second screenshot). This is to prevent the involuntary editing of cells. And when the grid is displayed in full screen mode, selecting a record does not open the Record View anymore (third and fourth screenshots).

When you click once on a cell from the grid perspective, the record is selected and displayed on the Record View, but the cell that was clicked is not activated (first screenshot). It’s only when you click again on the cell that you can edit its content (second screenshot). This is to prevent the involuntary editing of cells. And when the grid is displayed in full screen mode, selecting a record does not open the Record View anymore (third and fourth screenshots).

The labels of form sections are now using an uppercase font. In general, we should use uppercase strings in more areas of the user interface, because it provides yet another way of distinguishing different visual elements from each other, without having to use different fonts.