0
0
Application
• Definition: An application is a complete software program that you build and run.
• Example: Think of a simple to-do list app that you can create using Oracle Visual Builder Studio. This app would be an example of an "application" where you can add, view, and manage your tasks.
Artifact
• Definition: An artifact is any file or piece of content that is part of your project.
• Example: In your to-do list app, the HTML file that defines the structure of your pages, the CSS file that styles your app, and the JavaScript file that contains the logic for adding tasks are all examples of "artifacts."
Branch
• Definition: A branch is a way to work on different versions of your project at the same time without affecting the main version.
• Example: If you want to add a new feature to your to-do list app, like adding due dates, you can create a new branch to work on this feature. Once you're happy with it, you can merge it back into the main version of your app.
Remote Branch
• Definition: A remote branch is a version of your project that is stored on a remote server, typically used for collaboration.
• Example: When working on your to-do list app, you might push your changes to a remote branch so that other team members can access and review them.
Local Branch
• Definition: A local branch is a version of your project that is stored on your own computer, used for individual development.
• Example: You might create a local branch to work on a new feature for your to-do list app without affecting the main version until you're ready to share it.
Main Branch
• Definition: The main branch, often called the "master" or "main" branch, is the primary branch in a Git repository where the official, stable version of your project is kept.
• Example: In your to-do list app project, the main branch would contain the latest stable version of your app that is ready for deployment or use by others. Any new features or changes are typically merged into this branch after they have been tested and approved.
Build
• Definition: A build is the process of turning your code into a working app that can be run or deployed.
• Example: When you finish writing the code for your to-do list app, you would run a "build" to compile everything into a working app that you can then use or share with others.
Pipeline
• Definition: A pipeline is a series of steps that automatically build, test, and deploy your app.
• Example: Your to-do list app's pipeline might automatically build the app, run tests to make sure it works, and then deploy it to a server where users can access it.
Package Jobs
• Definition: Package jobs are specific tasks within a pipeline that prepare your app for deployment, often by bundling it into a package.
• Example: In your to-do list app's pipeline, a package job might compile your code and package it into a format ready for deployment.
Deploy Jobs
• Definition: Deploy jobs are tasks within a pipeline that move your app to a server or environment where it can be used by users.
• Example: After your to-do list app has been built and tested, a deploy job would move it to a production server where users can access and use the app.
Business Object
• Definition: A business object is a way to represent data in your app, like a customer or an order.
• Example: In your to-do list app, you might have a "Task" business object that stores information like the task name, description, and due date.
CI/CD (Continuous Integration/Continuous Deployment)
• Definition: CI/CD is a way to automatically build and deploy your app whenever you make changes, making development faster and more reliable.
• Example: Every time you add a new feature to your to-do list app, CI/CD can automatically build the app and deploy it to a test environment where you can check if everything works as expected.
Business Rules
• Definition: Business rules are conditions or logic that define how your app should behave in certain situations.
• Example: In a to-do list app, a business rule might prevent users from deleting a task that is marked as "completed" to keep a record of finished tasks.
Field Properties
• Definition: Field properties are the characteristics and settings of a data field in your app, like its type, label, and validation rules.
• Example: In your to-do list app, a "task name" field might have a property that limits its length to 50 characters to keep it concise.
Advanced Expressions
• Definition: Advanced expressions are complex formulas or conditions used in your app to control behavior or calculations.
• Example: You might use an advanced expression in your to-do list app to calculate the priority of tasks based on their due date and urgency.
Nested Rules
• Definition: Nested rules are business rules that are contained within other rules, allowing for more complex logic.
• Example: In your to-do list app, a rule might check if a task is overdue, and if so, a nested rule could then change its priority to high.
Page Properties
• Definition: Page properties are the settings and configurations for a specific page in your app, like its layout and behavior.
• Example: The "home page" of your to-do list app might have a property that sets it as the default landing page when users log in.
Workspace
• Definition: A workspace is a shared area where team members can collaborate on projects and manage their work.
• Example: In Oracle Visual Builder Studio, you and your team might use a workspace to work on different features of your to-do list app simultaneously.
Designer
• Definition: The designer is the visual tool in Oracle Visual Builder Studio that lets you build and design your app's user interface and components.
• Example: You would use the designer to drag and drop UI elements onto the pages of your to-do list app, arranging them to create an intuitive layout.
Dependencies
• Definition: Dependencies are other pieces of software or components that your app needs to function correctly.
• Example: Your to-do list app might have a dependency on a calendar library to display due dates, requiring you to include that library in your project
Dynamic Components
• Definition: Dynamic components are parts of your app's UI that can change or update based on user interactions or data changes.
• Example: In your to-do list app, a dynamic component might show a list of tasks that updates in real time when a user adds or completes a task.
Fragments
• Definition: Fragments are reusable pieces of UI or logic that can be included in multiple places in your app.
• Example: You might create a fragment for displaying a task in your to-do list app, which you can reuse on different pages like the home page and the completed tasks page.
Runtime
• Definition: Runtime refers to the time when your app is actually running and being used by users.
• Example: When a user opens your to-do list app and starts adding tasks, that's the "runtime" phase where the app is actively in use.
Extension
• Definition: An extension is a piece of software that adds new features or capabilities to Oracle Visual Builder Studio.
• Example: You might use an extension to add advanced charting functionality to your to-do list app, allowing users to visualize their task completion rates.
Project
• Definition: A project is a collection of all the files and resources you need to build your app.
• Example: Your to-do list app project would include all your code files, images, and configuration files needed to make the app work.
Git Repository
• Definition: A Git repository is a central place where all the files and resources for your project are stored, managed by Git.
• Example: You would store all the files for your to-do list app in a Git repository so that you and your team can access and update them easily.
Project Protection
• Definition: Project protection refers to the security measures and access controls set up to protect your project from unauthorized changes or access.
• Example: You might set project protection rules in your to-do list app project to ensure that only certain team members can make changes to the main branch.
Merge Request
• Definition: A merge request is a way to propose changes from one branch to another, typically used for review and approval before merging.
• Example: After working on a new feature for your to-do list app, you would create a merge request to have your changes reviewed and then merged into the main branch.
Jobs and Builds
• Definition: Jobs and builds refer to the automated tasks that build, test, and deploy your app.
• Example: In your to-do list app, a "build job" would compile your code, while a "test job" would run automated tests to ensure everything works as expected.
Code Review
o Definition: A code review is when other developers check your code to make sure it's good quality and follows the rules.
o Example: Before you merge your new due date feature into the main version of your to-do list app, a teammate might do a "code review" to make sure your code is clean and works well with the rest of the app.
• Commit
o Definition: A commit is when you save your changes to the version control system so they can be tracked.
o Example: After you've added the new due date feature to your to-do list app, you would "commit" those changes to save them and record what you've done.
• Deployment
o Definition: Deployment is the process of making your app available for others to use, usually by moving it from a development environment to a production environment.
o Example: After you've finished building and testing your to-do list app, you would "deploy" it to a server where other people can access and use it.
• DevOps
o Definition: DevOps is a set of practices that helps developers and IT teams work together more effectively to build, test, and deploy apps faster and more reliably.
o Example: In your to-do list app project, using DevOps practices could mean setting up automated tests that run every time you make a change, and then automatically deploying the app if those tests pass. This helps ensure that your app is always working and up-to-date.
• Environment
o Definition: An environment is a specific setup where your app runs, like a development environment for building and testing, or a production environment for users to use the app.
o Example: You might have a "development environment" where you build and test your to-do list app, and a separate "production environment" where users actually use the app. This helps keep your testing separate from what users see.
• Extension
o Definition: An extension is a piece of software that adds new features or capabilities to Oracle Visual Builder Studio.
o Example: If you want to add a calendar view to your to-do list app, you might use an "extension" that provides calendar functionality, making it easier to integrate without writing all the code from scratch.
• Flow
o Definition: A flow is a sequence of steps or actions that define how users move through your app, often shown as a diagram or workflow.
o Example: In your to-do list app, the "flow" might start with the user logging in, then going to the main page to see their tasks, adding a new task, and finally logging out. You can map this out to make sure the app is easy to use.
• Git
o Definition: Git is a tool that helps you keep track of changes in your code over time and lets multiple people work on the same project.
o Example: When you're working on your to-do list app with a team, you can use Git to save your changes, see what others have done, and combine everyone's work smoothly.
• Issue
o Definition: An issue is a task, problem, or new feature that needs to be worked on in your project.
o Example: If users report that they can't see their completed tasks in your to-do list app, you would create an "issue" to fix this problem and track its progress.
• JET (JavaScript Extension Toolkit)
o Definition: JET is a set of tools that helps you build web apps using JavaScript, which is integrated into Oracle Visual Builder Studio.
o Example: You can use JET to add interactive charts to your to-do list app, showing how many tasks you complete each week.
• Merge
o Definition: Merge is the process of combining changes from different versions of your code into one main version.
o Example: After you and your teammate work on different features of your to-do list app, you would "merge" those changes back into the main version of the app so everyone can use them.
• Page
o Definition: A page is a single screen or view in your app that users can interact with.
o Example: Your to-do list app might have a "home page" where users see their tasks and a "settings page" where they can change their preferences.
• Pipeline
o Definition: A pipeline is a series of steps that automatically build, test, and deploy your app.
o Example: Your to-do list app's "pipeline" might automatically build the app, run tests to make sure it works, and then deploy it to a server where users can access it.
• Project
o Definition: A project is a collection of all the files and resources you need to build your app.
o Example: Your to-do list app project would include all your code files, images, and configuration files needed to make the app work.
• Repository
o Definition: A repository is a central place where all the files and resources for your project are stored, managed by a version control system like Git.
o Example: You would store all the files for your to-do list app in a "repository" so that you and your team can access and update them easily.
• Service
o Definition: A service is a part of your app that does a specific job, like getting data from a database or sending emails.
o Example: In your to-do list app, you might have a "task service" that handles adding, updating, and deleting tasks.
• Stage
o Definition: A stage is a specific step in a pipeline, like building the app, running tests, or deploying it.
o Example: In your to-do list app's pipeline, the "build stage" would compile your code, the "test stage" would check if everything works, and the "deploy stage" would make the app available to users.
• Tag
o Definition: A tag is a label you can put on a specific version of your project to mark it as important or for release.
o Example: When you release version 1.0 of your to-do list app, you might "tag" that version so you can easily find it later.
• Task
o Definition: A task is a specific piece of work or action item assigned to someone in your project.
o Example: Adding a new feature to your to-do list app, like setting priorities for tasks, would be a "task" assigned to a team member.
• UI (User Interface)
o Definition: The UI is what users see and interact with when they use your app.
o Example: In your to-do list app, the buttons, text boxes, and layout that users see on the screen are all part of the "UI."
• UX (User Experience)
o Definition: UX is how users feel about using your app, including how easy it is to use and how enjoyable it is.
o Example: If users find your to-do list app easy to navigate and satisfying to use, you've done a good job with the "UX."
• Version Control
o Definition: Version control is a system that helps you track changes to your code over time and work with others on the same project.
o Example: Using version control, you can see how your to-do list app has changed over time and revert to an earlier version if needed.
• Visual Builder
o Definition: Visual Builder is a part of Oracle Visual Builder Studio that lets you build web and mobile apps visually, without writing all the code by hand.
o Example: You can use Visual Builder to drag and drop components to create the UI for your to-do list app quickly and easily.
• Webhook
o Definition: A webhook is a way to automatically trigger actions in your app when certain events happen, like when someone commits code.
o Example: You could set up a "webhook" in your to-do list app project to send a notification to your team whenever someone adds a new task.
• XML (eXtensible Markup Language)
o Definition: XML is a way to store and transport data in a structured format.
o Example: You might use XML to store the data for your to-do list app, like the names and descriptions of tasks.
• YAML (YAML Ain't Markup Language)
o Definition: YAML is a human-readable format for storing data and configuration.
o Example: You might use a YAML file to configure the settings for your to-do list app's pipeline, specifying what steps to run and when.
I hope this blog post was helpful for you. If you have any questions or feedback, please leave a comment below.