#!/bin/bash echo "===== Extracting test coreschema XML files =====" # ---------------------- actionAndComponentUsingViewerExtension.xml ---------------------- # Example taken from distributed source ./sdk/libraries/cepcoreschema/testdata/actionAndComponentUsingViewerExtension.xml cat < actionAndComponentUsingViewerExtension.xml A CEP with one action and one component that required a viewer extension Emmanuel.Promayon@univ-grenoble-alpes.fr This CEP contains a new type of component and an action that can do something with it where both require the medicalimageviewer viewer extension. This test the link between an action and a component defined in the same CEP as well as the dependency to a viewer. Test Actions This extension description is really useless. Test Action This description is void. TestMeshBasedComponent Testing CepGenerator Test components This extension description a new / specific component TestMeshBasedComponent My description is useless... Mesh specific EOF # ---------------------- exampleComponents.xml ---------------------- # Example taken from distributed source ./sdk/libraries/cepcoreschema/testdata/exampleComponents.xml cat < exampleComponents.xml Example Of Tinman With Components Celine.Fouard@imag.fr Tinman Test file containing several kinds of Component Extensions. Example with no file suffix This component tests the ability of Tinman to create and make compilable and executable component extensions which do not handle any file suffix (components should then be created from actions). my own cube A Mesh Cube Mesh Example with one file suffix Simple Mixed component extension handling .example files Tinman Example File Simple component handling .example files with no representation. None example Example with several file suffixes Simple Mixed component extension handling .example files Tinman A File Simple component handling .a files with an image representation. Image a Tinman B File Simple component handling .b files with a Mesh representation. Image b Tinman C File Simple component handling .c files with no representation. None c EOF # ---------------------- actionsExamplesLicence.xml ---------------------- # Example taken from distributed source ./sdk/libraries/cepcoreschema/testdata/actionsExamplesLicence.xml cat < actionsExamplesLicence.xml CEP created by Wizard Celine.Fouard@imag.fr Example of empty CEP Wizard created image actions This action extension proposes several actions on image components Example of Image Action Example of simple action on image component. ImageComponent CreatedByWizard Image Example of Image ITK Filter Example of an itk image action. ImageComponent CreatedByWizard Image itk Wizard created mesh actions This action extension proposes an action on mesh components Example of Mesh Action Example of action on a mesh. MeshComponent CreatedByWizard Mesh Example EOF # ---------------------- actionsExamplesNoLicence.xml ---------------------- # Example taken from distributed source ./sdk/libraries/cepcoreschema/testdata/actionsExamplesNoLicence.xml cat < actionsExamplesNoLicence.xml CEP created by Wizard Celine.Fouard@imag.fr Example of empty CEP Wizard created image actions This action extension proposes several actions on image components Example of Image Action Example of simple action on image component. ImageComponent CreatedByWizard Image Example of Image ITK Filter Example of an itk image action. ImageComponent CreatedByWizard Image itk Wizard created mesh actions This action extension proposes an action on mesh components Example of Mesh Action Example of action on a mesh. MeshComponent CreatedByWizard Mesh Example EOF # ---------------------- actionAndComponent.xml ---------------------- # Example taken from distributed source ./sdk/libraries/cepcoreschema/testdata/actionAndComponent.xml cat < actionAndComponent.xml Yet another example of CEP Emmanuel.Promayon@imag.fr This CEP contains a new type of component and an action that can do something with it. This test the link between an action and a component defined in the same CEP. Another Example Of An Action Extension This extension description is really useless. DoSomethingOnSpecific This description is void. SpecificMeshBasedComponent Testing CepGenerator OnlyOneVec3D Check compilation of an action with only a QVector3D parameter (check bug#189). Testing CepGenerator Specific component This extension description a new / specific component SpecificMeshBasedComponent My description is useless... Mesh specific EOF # ---------------------- empty.xml ---------------------- # Example taken from distributed source ./sdk/libraries/cepcoreschema/testdata/empty.xml cat < empty.xml empty Celine.Fouard@imag.fr Emmanuel.Promayon@imag.fr Example of empty CEP EOF # ---------------------- completeTest1.xml ---------------------- # Example taken from distributed source ./sdk/libraries/cepcoreschema/testdata/complete-test-1.xml cat < completeTest1.xml Complete test CEP 1 timc-camitk@univ-grenoble-alpes.fr This CEP is trying to achieve a complete test of all possible cepcoreschema element This CEP is trying to achieve a complete test of all possible cepcoreschema element. Probably some specific cases are not included, but it is our best shot Test Action Extension 1 Test the first action extension Test Action 1 Test a first action, for image component, with a lot of parameters ImageComponent Complete Test Actions #1 Test Action #1 ImageComponent Test Action 2 Test a second action, with no tag, no component, and with just one non editable parameters Complete Test Actions #1 Test Action 3 Test a third action, with non existing \"Mesh Component\", and with lots of parameters and defautl editable Complete Test Actions #1 Mesh Component Test Action Extension 2 Test the second action extension Test Action 4 This action use the Test Component 1 TestComponent1 Complete Test Actions #2 Test Action #2 Test Component 1 testapp Test application testappdir Test Component Extension 1 Test the first component extension Test Component 1 Test a first action with an image representation Image test testlib A simple test lib. This lib will not compile unless some minimal C++ code is present in the generated source. Copy TestLib.h and TestLib.cpp to the library directory before configuration time. EOF # ---------------------- viewerExample.xml ---------------------- # Example taken from distributed source ./sdk/libraries/cepcoreschema/testdata/viewerExample.xml cat < viewerExample.xml Test Viewer CEP Emmanuel.Promayon@univ-grenoble-alpes.fr Example of a CEP with two viewer extensions Test Viewer 1 This viewer extension manages a default viewer Test Viewer 1 Example of simple embedded viewer EMBEDDED MeshComponent ImageComponent Test Viewer 2 This viewer extension manages three named viewer First Test Viewer Second Test Viewer Test Viewer 2 Example of simple docked viewer DOCKED Component EOF echo "[OK]"