My name is Ismael Chang Ghalimi. I build the STOIC platform. I am a stoic, and this blog is my agora.
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.

More thoughts on surveys

Now that we have a super-easy-to-use object builder with drag-and-drop form designer, there is no reason not to create totally ad hoc objects for complex surveys. As a result, the refactoring of our survey engine done for the purpose of STOIC Education┬áis more appropriate than ever. Bottomline: we’ll provide a handfull of objects for basic survey templates, then let users clone them, or create ad hoc survey objects from scratch for advanced scenarios.

Form Designer Coming

A visual Form Designer is finally coming to the STOIC Platform. Florian and I have been discussing it in details over the past two days and agreed on a basic set of features. It’s a big deal for two reasons: first, it’s the most requested feature today; second, it will give us an opportunity to totally refactor our Object Editor and Field Editor, which today are the weakest parts of our entire user interface. We should have a first set of screenshots to share tomorrow. Stay tuned…

The content of Advanced Relationship can now be eddited in plain text. This is part of our effort to provide an “Edit Source” mode for 100% of our platform. It’s like “View HTML” for your web browser, but with editing capabilities. We still need to add this mode for a handful of components, such as Dashboards and Views.

We just added a new Styles object to the Display module of Platform. This object will be used to define reusable CSS styles that can be applied to the cells of sheets and to other UI elements. It is made of two fields, Class and Declarations. Initially, we will only support basic CSS syntax. Support for pre-processed languages like LESS and SASS will be added later.
We just added a new Styles object to the Display module of Platform. This object will be used to define reusable CSS styles that can be applied to the cells of sheets and to other UI elements. It is made of two fields, Class and Declarations. Initially, we will only support basic CSS syntax. Support for pre-processed languages like LESS and SASS will be added later.
We just added a new Styles object to the Display module of Platform. This object will be used to define reusable CSS styles that can be applied to the cells of sheets and to other UI elements. It is made of two fields, Class and Declarations. Initially, we will only support basic CSS syntax. Support for pre-processed languages like LESS and SASS will be added later.

We just added a new Styles object to the Display module of Platform. This object will be used to define reusable CSS styles that can be applied to the cells of sheets and to other UI elements. It is made of two fields, Class and Declarations. Initially, we will only support basic CSS syntax. Support for pre-processed languages like LESS and SASS will be added later.

When opening a new object, the spinner is now vertically centered.

Since our user interface is getting pretty fast, taking that screenshot took a few attempts…

It’s a tiny detail, but the color of the quantity unit (d), currency symbol ($), and percent sign (%) has been made a bit lighter than the color of the value that it is attached too, but not as light as the light grey that we’re using for placeholder values.