Eclipse is comprised of two major organizational features: Perspectives and Views. A Perspective is a grouping of related views – often associated with a particular workflow. For instance, two very common perspectives you will likely use are the Java Perspective and the CVS Perspective. The Java Perspective contains all the typical views you associate with editing Java files – Package Explorer, Java Hierarchy Browser, Problems List, Source Code Editor, etc. CVS Perspective contains a Repository Browser, a Revision Browser, a Synchronization View, etc. For the purposes of this tutorial, however, you will be using to the WOLips Perspective, which is very similar to the Java perspective but adds a few WO-related features.
1. In the upper right of your new Eclipse window is the quick access icons for common perspectives.
2. WOLips might not be in that list. If it isn't, click on the Add Perspective icon and choose "Other"
3. Select the WOLips Perspective from the list and click "OK"
4. Eclipse now switches to the WOLips perspective and you'll notice the WOLips icon now appears in your perspective bar.
5. Ctrl-click (Right click) in Package explorer and select "New" => "WOApplication"
6. The "New Project" dialog opens. Enter the name of the project – in this case, we chose "WOLipsTest". Click "Finish" when you are done.
7. You now have a (mostly) empty WO Application in your Package Explorer view. There are several notable elements that appear in the project that you should be aware of:
- Package Explorer shows a virtual view of your project, including source folders, frameworks, jar files, etc in a single unified hierarchy.
- The "src" folder is the folder that is setup as your default source folder. It contains the Java source code for your project. Note that it has a folder icon as the base icon. Anything with a folder icon is an actual folder on your filesystem.
- The "WO Frameworks" entry is a virtual folder that shows you all the framework dependencies for your project. A later tutorial shows how to change the list of dependencies.
- The "JRE System Library" entry is a virtual folder that represents the list of system jar files that are being used to build and run your project.
- The "build" folder is a dynamically updated folder that contains a .woa-like build of your application. Any time you make changes to your app, Eclipse and WOLips will incrementally compile the changes into this folder. When you Debug or Run your WOA from inside of Eclipse, it is actually executing out of this folder. Incrementally compiling is one of the most helpful features of Eclipse, because at any time you can see the current warning/error state of your code and WO's that is always kept up-to-date.
- The "Main.wo" folder is a default WO Component that was created as part of the new project template. WO Components do not have to appear off of the project root – you can reorganize them into subfolders if you prefer.
- The "Main.api" file is the .api file for the Main WO. The API file lists required bindings and validations that WOLips can use to ensure that you are using the WO properly in your projects. For instance, if you declare a required binding, WOLips will display an error in your Problems view if you use the Main WO without declaring that binding in your WOD file.
WOLips Bug: If you DO NOT see all of the items listed below, or if your src folder does not have a package icon on it, you have hit a WOLips bug that we are actively trying to track down. This particular bug is a race condition in project creation from a template where it ends up not creating a proper Java/WOLips project, so it doesn't autobuild or include all the frameworks. Try deleting and recreating until it looks more like the picture below. You can also try closing the project by right-clicking and choosing Close Project, then reopening the project in a similar fashion. We're working on this one.
8. You now have a WO Application shell to work from. You can now continue on to the Edit a WO Component tutorial.