Important Views Of EGL

Out of the dozens of Workbench views available to assist you with your development, there are an essential nine:
1.Project Explorer
2.Content Area
3.Page Data
4.Palette
5.Properties
6.Console
7.Servers
8.Problems
9.Outline

Project Explorer:
Organizes your project…and…allows you to:
Create new resources:
§ EGL programs, services, etc.
§ Web pages and other files
Open files into the Content Area
Manipulate files:
§ Delete, Move and Rename
Run pages
Debug EGL programs
Generate (compile)
Refactor
§ When “A” is changed change related “B” resources
Set project-level properties
§ By Right-clicking over a resource in the Project Explorer you access a “Context Menu” that provides options è
By double-clicking over a resource in the Project Explorer you open that resource in the Content Area view
Content Area:

Double-clicking a file in Project Explorer opens it in the Content Area
The appropriate editor for that file-type will also open
Here’s Page Designer è
Page Designer is an RBDe editor that is used for laying out and creating your pages from JSF (graphical) components
Page Data VIEW:
View of the JSF Handler (EGL) resources you can drag and drop onto your web page
Variables – which become labels and input/output controls
Functions – which become Submit Buttons
Services – which become entire forms, based on their parameters and functions

Palette View:
Provides a drag & drop way to add controls to your U.I. (web page or rich client or console U.I. form)If the Palette View is not available by default, open it from the menu:
Window >Show View > Other… General (expand)> Palette

Properties View:
Allows you to specify the behavior and characteristics of a U.I. control declaratively (without having to code at the source API level). One of the primary development constructs is that you:

Server Veiw:
Allows you to start and stop the application server in which you run and debug your application. And to publish (re-deploy) your application.

Console View:
Allows you to see a trace of the run-time events and messages to “system out” that happen as your application executes on the server.

Problem View:
Allows you to see syntax or structural problems (unset project properties, etc.) in your application.
Note, by double-clicking on a problem the file in question is opened in the Content Area, and your mouse is positioned to the line (and even characters) in question.

Out Line View:
Provides a consolidated, click-able list of your programs:
Imports
Functions
Variables
Other EGL resources
$ Especially useful for:
Navigating throughout large source files
Top-Down code analysis
Learning – or getting the giste of some code quickly

What is in Java Resources: src and Web Content

\src\ is the default highest level folder that contains all of the generated Java, for each and every successfully compiled (or in EGL terms, “generated”) EGL resource
You will rarely if ever need to actually open or even view the contents of \src\
But the folder structure of \src\ will match \EGLSource\ one-for-one
Your generated java files will end with a .java extension
\WebContent\ is the default highest-level folder under which all of your web resources will be organized, including:
Web Sitemap (Web Site Navigation)
Web Pages (*.jsp)
* \theme\ - Graphics (*.gif, *.jpg)
* \theme\ - Template pages (*.htpl)
* \theme\ - Cascading Style Sheets (*.css)
If you’re not familiar with the above types of web files don’t worry. We’ll be covering them later on in the course

What is in \EGLSource\

\EGLSource\ is the default folder that is the highest level folder under which all of your EGL resources are organized.
These EGL resources include EGL:
Programs
Libraries
Data
Services
JSFHandlers
Typically you will create sub-folders under \EGLSource\ to manage your EGL resources
We will define what is in all these EGL resources a bit later in this course
For now, it is enough to know that all EGL files end with the extension: .egl

What is in a Project?

Workspace projects organize and manage related application resources. They can be designed along lines of:
4 Batch – or – Online applications
4 Different business applications (Accounts Payable, Inventory, Claims, Part Assembly, etc.)
4 Common (shared) projects consisting of data and record definitions that can be reused

Projects also contain configuration data, such as build files** and generation options for EGL Java and/or COBOL generation

Projects may be further divided into folders

EGL-Web projects contain at the following high-level folders:
\EGLSource\
\Java Resources: src\
\WebContent\