Getting Started with BugTracker
1. Import the following source code folders needed for BugTracker either from CVS according to the tutorial. You may need to adjust the exact folders you import depending on the database you plan to use. In this case, I have added the FrontBase plugin as well as all the other frameworks that BugTracker expects to find in its build pathlocal Wonder source tree or from Wonder CVS server as discussed below.
The next three screenshots are showing the folders that can be found on the CVS server for Wonder. I have split them up because all the folders don't fit on the screen at once! As you can see, the folders that are necessary are found in several different sub-folders.
You may need to adjust the exact folders you import depending on the database you plan to use. In this case, I have added the FrontBase plugin as well as all the other frameworks that BugTracker expects to find in its build path.
2. Check out the folders into their own projects in your workspace.
6. Change the Properties located in the resources folder to match the requirements for your database. Wonder applications need Properties files to manage their configuration correctly. There are a number of different places in the Wonder frameworks that application properties will be read from. In the original example, the Database connection properties are taken from a logged in user's properties file, in this case it is named "Properties.ak". I moved the relevant lines to the Application Properties file that described the Global connection dictionary for BugTracker to access my FrontBase database. Alternatively (a recommended way) you can create your own "Properties.username" file by duplicating "Properties.ak"
You can either set Global properties for your database, or you can set them for a specific model. See the Wonder docs for more information about Properties files and database configuration ERXConfigurationManager documentation