Nuxeo IDE enables developers to extend the Nuxeo application with new features, but they also use Studio in parallel. Nuxeo IDE provides a way to use each customization tool's content into the other one. For instance, use operations created in Eclipse using Nuxeo IDE from Nuxeo Studio, or exploit the document types defined in Nuxeo Studio in your code in Eclipse.
- Configuring a Nuxeo Online Services Account — To enable Nuxeo IDE to leverage your Nuxeo Studio customization, you need to configure your Nuxeo Online Services account so Nuxeo IDE can connect to Studio.
- Browsing a Studio Project Content — The Studio view enables you to browse the list of your Studio customizations. You can see all the document types, schemas, content views, automation chains, etc, that you have configured in Nuxeo Studio.
- Binding Studio Projects to an Nuxeo IDE Project — The whole purpose of enabling to work with Nuxeo Studio is to be able to use elements configured in Studio from Nuxeo IDE, and to benefit from Eclipse key features such as code completion. As you may have several projects (both in Nuxeo Studio and in Nuxeo IDE), you need to indicate which Studio project the Nuxeo IDE project should be bound to.
- Uploading Custom Operations in Nuxeo Studio — Nuxeo IDE enables you to code new features, that can be complementary to your Studio customizations. Typically, you can use Nuxeo IDE to develop new Automation operations, that want to leverage in the Nuxeo Studio automation chain builder. Just like you can browse your Nuxeo Studio project from Nuxeo IDE, you can also use your operation in Nuxeo Studio.
- Deploying a Project with Studio Dependencies — For now, when deploying your projects on the server (using the a deployment profile) the Studio projects are not automatically deployed. In order to deploy both your Nuxeo IDE projects and their Studio project dependencies, your need to:
- Creating a Custom Nuxeo Package — Nuxeo IDE enables you to create Nuxeo Packages for your Nuxeo project. A Nuxeo Package is the easiest way to distribute a plugin, as it contains all the bundles, libraries and runtime properties that would be required to make your new plugin work, all in one single ZIP file.
- Settings Eclipse Development Templates