One of unique and powerful aspect of kBridge is the ability to organize Designs, Models, resources, and user interfaces into a Project, then share that Project with others. This is important because it enables us to:
▪Encapsulate and share important applications, or elements of an application with other application developers
•As mentioned earlier, virtually all engineering is a collaborative process and requires bringing together various elements of expertise. Projects are the vehicle for doing that
▪Share an application with end users
•By creating an application-specific UI and enabling the Project for run-time sharing, we can enable others to run the application without seeing (or being confused by) all the details underneath. This is called an application, or app for short.
Projects include:
▪Designs
•This includes all the Designs that you have created in the Project as well as any Designs that the Project acquired by sharing from another Project
•Note that whether you can see or edit those borrowed Designs depends on how the Project was shared.
▪Models
•When you create a Model in the Editor, it is possible to save that Model. The saved Model includes a record of all of the inputs that were used to create it and it enables you to recreate the model with those inputs at any time.
▪Resources
•Resources are your Project’s library of files.
▪Shared Projects
•References to all shared Projects.
There are different ways of sharing a Project:
▪Full Access (Write)
•Full access enables the borrower to view, edit, and use Designs and Models in the borrowed Project.
▪View Only (Read)
•For View Only, you can see and use the Designs and Models, but you are not allowed to change them.
▪Closed
•Provided by a developer for other developers to use, but the underlying Rules are not exposed.
▪Runtime Only (End User)
•This is simply an ‘app’. Running the Project will simply bring up the Designated runtime user interface so that the application can be run. (Not fully implemented yet.)
