Guidelines
    Overview
  • Welcome to RamBase Guidelines
  • Applications and components
  • RamBase client overview
    Design guidelines
  • Colors & borders
  • Layout
    • Standard layouts
  • RamBase Application overview
    • Context menu
    • Expanders
    • Splitter
    • Tab controller
    Development guidelines
  • Setup environment
  • Creating applications
    • Creating your first application
    • AppEditor
    • Context menu
  • Creating components
    • Creating your first component
    • Component layout
    • Component data service
    • Keyboard handling
  • APIs
    UI Elements
  • Alertbox
  • Button
  • Checkbox
  • Complex dropdown
  • Date
  • Datetime
  • Dropdown
  • Email
  • Grid
  • Icons
  • Navigate
  • Number
  • Password
  • Popover
  • Popup
  • Progressbar
  • Radiobutton
  • Textarea
  • Textfield
  • Toastr
  • Treeview

Standard RamBase layouts

You should always aim to use the standard RamBase layouts. All users will quickly recognize the layout and know how to navigate within your new applications.

List / details view

The recommended app structure contains two sections (columns). The left section typically contains a listview of data. When the user selects an item in the listview, the right section will show detailed information for the selected item. The two sections should be divided by using the splitter element, available from appeditor. The splitter makes the applicaton more customizable for the user by supporting resizing and collapsing of sections. In mobile view the splitter sections will be wrapped and a bulletpoint navigation area will appear to the right.

It is also recommended to have a splitter between the menu and the detail view.

Tabs are generally used to break content into multiple sections and to save space on the screen. Tabs are generally used in the right section of the application.

Drilldown view

If there are much information to be displayed in the item level, you should consider to create this as a separate application. Then you would create a navigtion point from the main application to the item application. In many cases an item application can also be used as a standalone application. The COA and COAITEM applications are examples of this.