[ADF-1549] Moved docassets folder inside docs folder (#2367)

This commit is contained in:
Andy Stark 2017-09-22 16:29:30 +01:00 committed by Eugenio Romano
parent a9eff7fbaf
commit 7f3a4fc513
112 changed files with 80 additions and 80 deletions

View File

@ -41,7 +41,7 @@ You can also hide chart parameters UI by setting the `hideParameters` to `true`:
</adf-analytics>
```
![Analytics-without-parameters](../docassets/images/analytics-without-parameters.png)
![Analytics-without-parameters](docassets/images/analytics-without-parameters.png)
### Events

View File

@ -54,7 +54,7 @@ If you want to show some specific apps you can specify them through the filtersA
In this specific case only the Tasks app, the app with deploymentId 15037 and the app with "my app name" will be shown.
![how-filter-apps](../docassets/images/how-filter-apps.png)
![how-filter-apps](docassets/images/how-filter-apps.png)
You can use inside the filter one of the following property

View File

@ -2,7 +2,7 @@
Indicates the current position within a navigation hierarchy.
![Breadcrumb](../docassets/images/breadcrumb.png)
![Breadcrumb](docassets/images/breadcrumb.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

View File

@ -2,7 +2,7 @@
Displays a configurable property list renderer.
![adf-custom-view](../docassets/images/adf-custom-view.png)
![adf-custom-view](docassets/images/adf-custom-view.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

View File

@ -2,7 +2,7 @@
Displays comments from users involved in a specified task and allows an involved user to add a comment to the task.
![adf-comments](../docassets/images/adf-comments.png)
![adf-comments](docassets/images/adf-comments.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

View File

@ -2,7 +2,7 @@
Displays Upload Component(Drag and Click) to upload the attachment to a specified process instance
![process-create-attachment](../docassets/images/process-create-attachment.png)
![process-create-attachment](docassets/images/process-create-attachment.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

View File

@ -2,7 +2,7 @@
Displays Upload Component(Drag and Click) to upload the attachment to a specified task
![task-create-attachment](../docassets/images/task-create-attachment.png)
![task-create-attachment](docassets/images/task-create-attachment.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

View File

@ -2,7 +2,7 @@
Displays data as a table with customizable columns and presentation.
![DataTable demo](../docassets/images/datatable-demo.png)
![DataTable demo](docassets/images/datatable-demo.png)
See it live: [DataTable Quickstart](https://embed.plnkr.co/80qr4YFBeHjLMdAV0F6l/)
@ -186,7 +186,7 @@ onRowClick(event) {
}
```
![](../docassets/images/datatable-dom-events.png)
![](docassets/images/datatable-dom-events.png)
### Custom Empty content template
@ -246,7 +246,7 @@ You can use any HTML layout or Angular component as a content of the empty templ
| dragDropMsg | String | Drag and drop | The default drag and drop message |
| additionalMsg | String | Drag and drop | The default additional message |
![](../docassets/images/adf-empty-list.png)
![](docassets/images/adf-empty-list.png)
### Loading content template
@ -427,9 +427,9 @@ onExecuteRowAction(event: DataRowActionEvent) {
}
```
![](../docassets/images/datatable-actions-ui.png)
![](docassets/images/datatable-actions-ui.png)
![](../docassets/images/datatable-actions-console.png)
![](docassets/images/datatable-actions-console.png)
Developers are allowed to use any payloads as row actions.
The only requirement for the objects is having `title` property.

Binary file not shown.

After

Width:  |  Height:  |  Size: 67 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 55 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 80 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 40 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 74 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 120 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 58 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 55 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 57 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 36 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 133 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 173 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 58 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 62 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 49 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.8 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 102 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 133 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 53 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 77 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 90 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 90 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 84 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 63 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 192 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 90 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 94 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 89 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 56 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.2 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.0 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.3 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.8 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 100 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 119 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 83 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 100 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 5.2 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 55 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 74 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 79 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.6 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 5.2 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 37 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 155 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 171 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 136 KiB

View File

@ -321,7 +321,7 @@ export class FilesComponent implements OnInit {
We've added `console.log(node)` for the `getNodeInfo` callback just for study and debug purposes.
It helps examining other valuable information you can have access to if needed:
![documentLibrary](../docassets/images/documentLibrary.png)
![documentLibrary](docassets/images/documentLibrary.png)
**Important note**: for this particular scenario you must also trigger `changeDetector.detectChanges()` as in the example above.
@ -377,7 +377,7 @@ adf-document-list >>> adf-datatable tr.is-selected .image-table-cell::before {
Once your application starts you should see the following icon for each selected row:
![view-child](../docassets/images/document-list-custom-icon.png)
![view-child](docassets/images/document-list-custom-icon.png)
### Calling DocumentList api directly
@ -436,7 +436,7 @@ export class MyAppComponent implements AfterViewInit {
Example above should produce the following browser console output:
![view-child](../docassets/images/viewchild.png)
![view-child](docassets/images/viewchild.png)
Now you are able to access DocumentList properties or to call methods directly.
@ -485,7 +485,7 @@ A custom set of columns can look like the following:
</adf-document-list>
```
![Custom columns](../docassets/images/custom-columns.png)
![Custom columns](docassets/images/custom-columns.png)
You can also use HTML-based schema declaration used by DataTable, TaskList and other components:
@ -669,7 +669,7 @@ In the Example below we will add the [ng2-alfresco-tag](https://www.npmjs.com/pa
</data-column>
```
![Tag component in document List](../docassets/images/document-list-tag-template.png)
![Tag component in document List](docassets/images/document-list-tag-template.png)
### Actions
@ -749,7 +749,7 @@ export class MyView {
All document actions are rendered as a dropdown menu as on the picture below:
![Document Actions](../docassets/images/document-actions.png)
![Document Actions](docassets/images/document-actions.png)
### Default action handlers
@ -799,7 +799,7 @@ export class MyComponent {
}
```
![Delete show notification message](../docassets/images/content-action-notification-message.png)
![Delete show notification message](docassets/images/content-action-notification-message.png)
#### Delete - Disable button checking the permission
@ -823,7 +823,7 @@ The ContentActionComponent provides the property permission that must contain th
</adf-document-list>
```
![Delete disable action button](../docassets/images/content-action-disable-delete-button.png)
![Delete disable action button](docassets/images/content-action-disable-delete-button.png)
#### Download
@ -843,13 +843,13 @@ Initiates download of the corresponding document file.
</adf-document-list>
```
![Download document action](../docassets/images/document-action-download.png)
![Download document action](docassets/images/document-action-download.png)
#### Copy and move
Shows the destination chooser dialog for copy and move actions. By default the destination chooser lists all the folders of the subject item's parent (except the selected item which is about to be copied/moved if it was a folder itself also).
![Copy/move dialog](../docassets/images/document-action-copymovedialog.png)
![Copy/move dialog](docassets/images/document-action-copymovedialog.png)
```html
<adf-document-list ...>
@ -891,7 +891,7 @@ Defining error, permission and success callbacks are pretty much the same as doi
- The success callback's only parameter is the translatable success message string (could be used for showing in snackbar for example)
- The permissionEvent callback is the same as described above with the delete action
![Copy/move document action](../docassets/images/document-action-copymove.png)
![Copy/move document action](docassets/images/document-action-copymove.png)
### Folder actions
@ -943,7 +943,7 @@ export class MyView {
}
```
![Folder Actions](../docassets/images/folder-actions.png)
![Folder Actions](docassets/images/folder-actions.png)
### Context Menu
@ -953,7 +953,7 @@ DocumentList also provides integration for 'Context Menu Service' from the
You can automatically turn all menu actions (for the files and folders)
into context menu items like shown below:
![Folder context menu](../docassets/images/folder-context-menu.png)
![Folder context menu](docassets/images/folder-context-menu.png)
Enabling context menu is very simple:
@ -1159,11 +1159,11 @@ Now you can declare columns and assign `desktop-only` class where needed:
**Desktop View**
![Responsive Desktop](../docassets/images/responsive-desktop.png)
![Responsive Desktop](docassets/images/responsive-desktop.png)
**Mobile View**
![Responsive Mobile](../docassets/images/responsive-mobile.png)
![Responsive Mobile](docassets/images/responsive-mobile.png)
### Custom row permissions style
@ -1225,7 +1225,7 @@ adf-document-list >>> adf-datatable tr.document-list__disable {
By default DocumentList provides the following content for the empty folder:
![Default empty folder](../docassets/images/empty-folder-template-default.png)
![Default empty folder](docassets/images/empty-folder-template-default.png)
This can be changed by means of the custom html template:
@ -1241,7 +1241,7 @@ This can be changed by means of the custom html template:
That will give the following output:
![Custom empty folder](../docassets/images/empty-folder-template-custom.png)
![Custom empty folder](docassets/images/empty-folder-template-custom.png)
### Customizing default actions

View File

@ -91,7 +91,7 @@ rendered within `<activiti-form>` component.
First let's create a simple Alfresco Activiti form with `Text` widgets:
![default text widget](../docassets/images/text-default-widget.png)
![default text widget](docassets/images/text-default-widget.png)
Every custom widget must inherit `WidgetComponent` class in order to function properly:
@ -158,7 +158,7 @@ export class MyView {
At runtime it should look similar to the following:
![custom text widget](../docassets/images/text-custom-widget.png)
![custom text widget](docassets/images/text-custom-widget.png)
## Replacing custom stencils with custom components
@ -168,7 +168,7 @@ This is a short walkthrough on rendering custom Alfresco Activiti stencils by me
First let's create a basic stencil and call it `Custom Stencil 01`:
![custom stencil](../docassets/images/activiti-stencil-01.png)
![custom stencil](docassets/images/activiti-stencil-01.png)
_Note the `internal identifier` value as it will become a `field type` value when corresponding form is rendered._
@ -180,17 +180,17 @@ Next put some simple html layout for `Form runtime template` and `Form editor te
Now you are ready to design a test form based on your custom stencil:
![custom stencil form](../docassets/images/activiti-stencil-02.png)
![custom stencil form](docassets/images/activiti-stencil-02.png)
Once wired with a new task it should look like the following within Alfresco Activiti web application:
![custom stencil task](../docassets/images/activiti-stencil-03.png)
![custom stencil task](docassets/images/activiti-stencil-03.png)
### Creating custom widget
If you load previously created task into ADF `<activiti-form>` component you will see something like the following:
![adf stencil](../docassets/images/adf-stencil-01.png)
![adf stencil](docassets/images/adf-stencil-01.png)
Let's create an Angular 2 component to render missing content:
@ -252,4 +252,4 @@ export class MyView {
At runtime you should now see your custom Angular 2 component rendered in place of the stencils:
![adf stencil runtime](../docassets/images/adf-stencil-02.png)
![adf stencil runtime](docassets/images/adf-stencil-02.png)

View File

@ -360,7 +360,7 @@ You can now use the 'fieldValidators' property with the Form or Task Details com
Now if you run the application and try to enter "admin" in one of the text fields (either optional or required), you should see the following error:
![](../docassets/images/demo-validator.png)
![](docassets/images/demo-validator.png)
## Other documentation
@ -387,7 +387,7 @@ You subscribe to the `formFieldValueChanged` event and check whether event is ra
The result should be as following:
![](../docassets/images/form-service-sample-01.png)
![](docassets/images/form-service-sample-01.png)
#### Listen all form Events

View File

@ -1,6 +1,6 @@
# ADF Like component
![Custom columns](../docassets/images/social1.png)
![Custom columns](docassets/images/social1.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

View File

@ -2,7 +2,7 @@
Authenticates to Alfresco Content Services and Alfresco Process Services.
![Login component](../docassets/images/custom-footer.png)
![Login component](docassets/images/custom-footer.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->
@ -88,7 +88,7 @@ export class AppComponent {
### Change footer content
![Login with custom footer](../docassets/images/custom-footer.png)
![Login with custom footer](docassets/images/custom-footer.png)
You can replace the entire content in the footer of the login component with your custom content.
@ -100,7 +100,7 @@ You can replace the entire content in the footer of the login component with you
### Change header content
![Login with custom header](../docassets/images/custom-header.png)
![Login with custom header](docassets/images/custom-header.png)
You can replace the entire content in the header of the login component with your custom content.
@ -125,7 +125,7 @@ This becomes handy in case you need to extend it with custom input fields handle
Here's an example of custom content:
![Login with custom content](../docassets/images/login-extra-content.png)
![Login with custom content](docassets/images/login-extra-content.png)
### Custom logo and background
@ -140,7 +140,7 @@ It is possible changing logo and background images to custom values.
Should give you something like the following:
![Login with custom logo and background](../docassets/images/custom-login.png)
![Login with custom logo and background](docassets/images/custom-login.png)
Alternatively you can bind to your component properties and provide values dynamically if needed:

View File

@ -5,7 +5,7 @@ All metadata is stored inside `properties` property.
Here's an example of basic image-related metadata fetched from the server:
![](../docassets/images/metadata-01.png)
![](docassets/images/metadata-01.png)
## Custom column template
@ -90,12 +90,12 @@ You will need to enable `versioning` feature for the Document List to be able to
Drag and drop any image file to upload it and ensure it has `1.0` displayed in the column:
![](../docassets/images/metadata-02.png)
![](docassets/images/metadata-02.png)
Now drop the same file again to upload a new version of the file.
You should now see icons instead of version label.
![](../docassets/images/metadata-03.png)
![](docassets/images/metadata-03.png)
You can see on the screenshot above that only files with version `2.0` got extra icons.

View File

@ -2,7 +2,7 @@
Adds pagination to the component it is used with.
![](../docassets/images/basic.png)
![](docassets/images/basic.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

View File

@ -30,7 +30,7 @@ Displays involved users to a specified task
</adf-people>
```
![activiti-people](../docassets/images/activiti_people.png)
![activiti-people](docassets/images/activiti_people.png)
### Properties
@ -65,7 +65,7 @@ In this way will be easy customize the people component to involve the user with
</adf-people>
```
![involve-people-single-click-and-close-search](../docassets/images/involve-people-single-click-and-close-search.gif)
![involve-people-single-click-and-close-search](docassets/images/involve-people-single-click-and-close-search.gif)
### Involve People single click without close search
@ -78,7 +78,7 @@ In this way will be easy customize the people component to involve the user with
</adf-people>
```
![involve-people-single-click-without-close-search](../docassets/images/involve-people-single-click-without-close-search.gif)
![involve-people-single-click-without-close-search](docassets/images/involve-people-single-click-without-close-search.gif)
### Involve People double click and close search
@ -91,7 +91,7 @@ In this way will be easy customize the people component to involve the user with
</adf-people>
```
![involve-people-double-click-and-close-search](../docassets/images/involve-people-double-click-and-close-search.gif)
![involve-people-double-click-and-close-search](docassets/images/involve-people-double-click-and-close-search.gif)
### Involve People double double without close search
@ -104,4 +104,4 @@ In this way will be easy customize the people component to involve the user with
</adf-people>
```
![involve-people-double-click-without-close-search](../docassets/images/involve-people-double-click-without-close-search.gif)
![involve-people-double-click-without-close-search](docassets/images/involve-people-double-click-without-close-search.gif)

View File

@ -2,7 +2,7 @@
Provide a way to fetch the Process Audit information in the pdf or json format.
![adf-process-audit-directive](../docassets/images/adf-process-audit-directive.png)
![adf-process-audit-directive](docassets/images/adf-process-audit-directive.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

View File

@ -99,4 +99,4 @@ The AccordionComponent is exposed by the alfresco-core.
</adf-accordion>
```
![how-create-accordion-menu](../docassets/images/how-to-create-accordion-menu.png)
![how-create-accordion-menu](docassets/images/how-to-create-accordion-menu.png)

View File

@ -2,7 +2,7 @@
Sub-component of the process details component, which renders some general information about the selected process.
![adf-process-instance-header](../docassets/images/adf-process-instance-header-attachment.png)
![adf-process-instance-header](docassets/images/adf-process-instance-header-attachment.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

View File

@ -1,6 +1,6 @@
# ADF Rating component
![Custom columns](../docassets/images/social2.png)
![Custom columns](docassets/images/social2.png)
## Basic Usage

View File

@ -2,7 +2,7 @@
Displays a dropdown menu to show and interact with the sites of the current user.
![Dropdown sites](../docassets/images/document-list-dropdown-list.png)
![Dropdown sites](docassets/images/document-list-dropdown-list.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

View File

@ -2,7 +2,7 @@
Displays Start Process, allowing the user to specify some basic details needed to start a new process instance.
![adf-start-process ](../docassets/images/startProcess.png)
![adf-start-process ](docassets/images/startProcess.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

View File

@ -2,7 +2,7 @@
Creates/Starts new task for the specified app
![adf-start-task](../docassets/images/adf-start-task.png)
![adf-start-task](docassets/images/adf-start-task.png)
<!-- markdown-toc start - Don't edit this section. npm run toc to generate it-->

Some files were not shown because too many files have changed in this diff Show More