First Steps [3/7] Workflow

    This site uses cookies. By continuing to browse this site, you are agreeing to our use of cookies. More details

    • First Steps [3/7] Workflow



      First Steps [3/7]
      Workflow




      This chapter will have a look on the development of a WCF plugin with the Project Manager from a bird's eye view. The following chapters will show the details step by step with a Hello World example.


      Creating a project with the Project Manager
      If you have an idea for a new plugin, the starting point is the ACP in the local WCF installation where you add a new project. When adding a project you have to choose a project directory, which will contain the project's files.


      Adding the project to the IDE
      Next open the IDE and create a new PHP project. In Eclipse select File > New > PHP Project. The project name can be chosen freely. Select Create project at existing location (from existing source) in Contents and enter the project directory in Directory. Afterwards add the PHP project by pressing the Finish button. Set the PHP project's dependencies to the WCF and respectively to applications and other project's.


      Implementation
      The Project is now created in the ACP and therefore known to the WCF and it is available in the IDE. You can write the source code for the project's PHP, template and Javascript files in the IDE. You can use the abstractions of the WCF in the ACP with the many forms the Project Manager provides.


      Live testing
      After you added data with help of the Project Manager and wrote source code, you can test your plugin live without any delay. For example if you added new content to the user profiles with your plugin, you can open an user profile in the local WCF installation and have a look at your plugin's results. If errors occur oder anything does not work as intended, you can observe that and start with the debugging.


      Export
      When all functionality is implemented and tested, the project can be exported with help of the Exporter. After the export is done, the plugin can be saved and published.


      Versioning
      Subsequently the next version of the project can be added. For example, if you exported version 1, then you create version 2. It is not necessary to create a new project, because the Project Manager can handle multiple versions of each project.

      If you completed the new features for version 2 and fixed errors of version 1, you export version 2, save and publish it. The Project Manager generates the proper update instructions for updates from version 1 to version 2. After publishing version 2, the next version can be created.


      Note about versioning
      At this point only a linear versioning of projects is possible. In order to create a new version, all other versions have to be exported and published. The new version has to have the highest version number. The foundation for non-linear versioning is laid and will be available with upcoming versions of the Project Manager.


      Summary
      A short overview: You create the project in the ACP and the IDE. You implement all functions and test them live. You export the package and create a new version. You can fix bugs and add new functions in the new version.


      Next chapter: Coming soon.