Expertise spectrum UIs
=======================
Introduction
-------------
I’m building this tool to create boring business applications. However, I discovered that people use different terminologies for the same thing based on their expertise.
(DIR) tool
Some speak of tables and columns , for example, others of entities and attributes . Still others make it even more confusing; they say relationship when they talk about a table . You wonder how they name a relationship 1 .
(DIR) 1
When I wanted to introduce globalization, that gave me the solution. Terminology can be used as language. It does make it difficult to do this for all languages, though. An explosion of combinations to build and maintain.
Demo
-----
This is what it can look like in a simple form. The UI uses terminology based on the expertise level of the user.
Name | Rows | Links
Customers | 17 | Orders
Orders | 21 | Customers, Products
Products | 52 | Orders
3 entities
Duke Nukem says
----------------
This table shows an overview of used terms and their translations.
Difficulty Level | Table | Column | Row | Value | Relationship
Piece of Cake | Sheet | Column | Row | Value | Link
Let’s Rock | Table | Field | Row | Value | Relationship
Come Get Some | Relation | Attribute | Record | Value | Foreign Key
Damn, I’m Good | Entity | Attribute | Tuple | Datum | Relationship Set
----------------------------------
- It’s called a ‘relationship set’. ↩︎
It’s called a ‘relationship set’. ↩︎
(DIR) ↩︎
Related
--------
(DIR) Data compression 101
(TXT) /img/fallback.svg (.svg)
(DIR) Fixed point explanatorial
(TXT) Bits (.svg)
(DIR) Unfriendly dates
(TXT) /img/fallback.svg (.svg)
(DIR) Pythagoras theorem
(TXT) Pythagoras example (.svg)
(DIR) Vibrato vs. tremolo
(TXT) Waveform (.svg)
(DIR) About me
(TXT) /img/fallback.svg (.svg)