error-message
success-message
saving-message
warning-message
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
This is a snapshot of this object as it looked in the past. | Go to the most recent version
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
This panel will allow the exploration of files that are contained within artifacts in the archive.
Every object is a set of files, even objects that simply wrap a single
file. This is because each object has a metadata file called
object.json
that has its name, type, and other descriptive and
instructive information. This file is hidden in this view since it is
viewable by the other panels.
Each other file is the actual content that makes up this object. These are listed here in the listing side-panel. Each object can be further subdivided into directories which contain files, etc. The file listing contains further help to assist on what each action does and how to upload new content.
You can open any of the files by selecting them from the listing. If there is an association for that file to some software in the archive, the panel will load that software to view or interpret the file. It will load each file in its own tab that you can quickly switch between as you explore.
If you wish to directly use some software, you can swing out the queue side-panel and select "Queue" to select how to deploy a viewer or editor (if the object is also open for editing) for that file. The run queue side-panel also contains the currently running software viewing the currently open file panel. To close it, you can press the "shutdown" button resembling an X in that listing. Closing the file tab will close all software for that file.
This is the file listing that shows the files within directories of this current object.
When you are editing your own objects, you can perform some actions to update the files. We will discuss these actions now.
You can upload files by either dragging them into the file listing from your local machine or by using the buttons near the listing.
You can create a new file by using one of the buttons near the listing. This will allow you to give the file a name which you can then click on to open the blank file to edit it further.
You can add a new directory to organize your files by using another button near the listing. Once you press the button, you can name the directory and then click on it to traverse to this empty directory.
Note that you cannot have a directory or file with the same name in the same directory. This includes not being able to have a directory and file with the same name.
Clicking on a file in the listing will open the file. If you are editing the object, then it may open an editor for that file. Otherwise you will receive a read-only view of the file. The viewer or editor will depend on your associations for the type of file. Most text files, for instance, will open in a text editor.
The actions button to the right of each file in the listing will select further actions to be done on each file. These actions will be discussed now.
The remove action will delete the file from the current view of the object when you have such permissions.
The download action will download a copy of the file to your local machine.
The set as main action will set the given file as the main file for
the object. For many objects, this has special significance. It will
essentially set the file
field of the object to the path to this file.
You can refer to it in a run or build command to make the object more
flexible and extensible instead of hard-coding such paths. Other
objects might expect a file
to be chosen when they take an object as
input in a workflow. In these cases, the main file highlights which
file is most important. Occam especially handles HTML documents and
widgets by loading the main file as the entry point to the interactive
program or document.
Cannot upload file: Read only access.
0 | B |
0 | B |
1.18 | KiB | application/x-sh | build.sh | ||
2.35 | KiB | data/extension-patch | glibc-sigaltstack.patch | ||
430 | B | data/extension-patch | glibc-signal.patch | ||
710 | B | data/extension-patch | glibc-statp.patch | ||
958 | B | data/extension-patch | glibc-ucontext.patch | ||
916 | B | data/extension-patch | glibc-ustat.patch | ||
10.38 | KiB | data/extension-patch | libsanitizer-xdr-fix.patch |
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
Confirm message?