Working with the SageTea Components in Text-to-Software
In this section, you can find more information on working with Text-to-Software components:
When adding an activity to a state, it means the group (and related sub-groups) the activity contains displays on that screen in the application. For a screen to be displayed in an application, it must contain an activity.
For more information about States, please see States in Glossary of Terms.
Activities are tasks or processes a user does. They contain and manage groups. A group has to be in an activity in order to appear in a state.
For more information about Activities, please see Activities in Glossary of Terms.
To make sure the elements that belong together are displayed together, they must be organized into groups. Elements will not appear in an application unless they are brought together in a group.
Groups organize elements (and other groups) so that they travel together. For example, if an application has seventeen elements that should appear together in a state, they would be joined together under a single group.
For more information about Groups, please see Groups in Glossary of Terms.
Elements are the basic building blocks of all applications. Elements also become instantiated into groups, activities, and states.
As an example, some of the elements for the use case related to maintaining a client database may be client name, home phone number, work email address, etc.
For more information about elements, please see Elements in Glossary of Terms.
Transitions make things happen or move the user from place to place in the application. On the user interface, any two screens need a transition between them to allow users to move from one to another. The transition is the process that happens when a user clicks on a button, for example, but it is not the button itself.
For more information about Transitions, please see Transitions in Glossary of Terms.
Events define under what conditions a transition will occur; i.e. it triggers a transition. An event can be initiated by a user (such as a button click) or by the system (such as a timer counting down).
For more information about Events, please see Events in Glossary of Terms.
Actions define what happens when an event triggers a transition. For example, when the internal clock reaches a particular time (event), then the system will check for email (action).
When setting-up a transition for the user interface, events and actions will be defined automatically.
For more information about Actions, please see Actions in Glossary of Terms.