You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

We well know that one example is worth a thousand words, therefore, we present you with a handful of examples illustrating various functionalities that can be used in your custom applications. Each of them can be copied and directly used in your workspace, and, later, modified to better suit your research.

Contents of this guide

This guide contains links to sample ready-to-use applications, that will help you to understand different possibilities related to custom applications. Each sample application is described presenting the aspects of its configuration it shows. The guide contains also an instruction on how to copy and use the sample applications for yourself.   

How to use the examples

Each example contains a link to the sample application within the Application Workbench. After accessing it, you will see a list of its files, where you can browse them (you will not be able to edit them at this point). If you decide you want to test this application in your workspace and later use it as a base for your own codes, use the Fork button in the right upper corner of the page (see Figure 1).   

Note that, to access and fork the sample applications you will have to log in to the Application Workbench first.

Figure 1. Page displaying sample application with Fork button marked

Upon this action, you will be able to decide on the name under which the application will be copied to your account (Repository Name, marked with (1) in Figure 2). You will be also able to add your custom description (Description, marked with (2) in Figure 2). 

Figure 2. Creating a new forked repository

After confirming with the Fork Repository button, your copy of the application repository will be created and presented to you. The copied application will have the same contents, therefore, the view will much resemble the original application (Figure 1). However, notice the change of the user name (the repository name may also be changed if you did that in the previous step) and the information that the repository is forked (marked in Figure 3). The button Fork will also be disabled as you cannot create another fork from a repository that already is a fork. You will also have more controls enabling management of your repository and edition of files.

Figure 3. Forked repository view

Example 1

https://epos-apps.grid.cyfronet.pl/tcs-test-user/SampleApp1

  • No labels