In Glide, we call this a relation, and it’s just one type of computation we can run on an app’s underlying data (others include rollups, template strings, and more).Ī Glide App is intertwined with its data source. For example, a recipes app might have an associated `Recipes` table, and each item in that table might reference multiple rows in the just-mentioned `Ingredients` table (for example, the recipe for a ham and cheese sandwich might reference the `ham`, `cheese`, and `bread` rows of the `Ingredients` table). Glide can derive complex relationships between the tables, columns, and rows that drive an app. This table might have columns like `name`, `cost`, `color`, etc. For example, a grocery-tracking app might use an `Ingredients` table, where each row describes an ingredient. In Glide, apps often use data that lives in a data source like Google Sheets or Glide Tables. How can we make it easier for these new users to pick up some of the concepts they’ll need to be successful with Glide? Basic structure of a Glide Appįor context, it’s first worth describing the basic structure of a Glide App. Ultimately, they may get frustrated trying to make Glide do what they want. Either way, if they’re they're unfamiliar with some of the nuances and mental models associated with Glide, they may not know how to get started (for example, how to structure their data or how to use advanced features like relations, rollup columns, and user profiles). This project started out as a question: how can we make it easier for new users to learn Glide? Sometimes users come to Glide with specific ideas, and other times they just want to experiment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |