Date: Tue, 19 Mar 2024 13:09:21 +0000 (UTC) Message-ID: <1922230089.9929.1710853761347@911f0a1bad02> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_9928_1431229145.1710853761347" ------=_Part_9928_1431229145.1710853761347 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This chapter lists definitions of terms and concepts used to des= cribe items in the Eclipse IDE, and specifically, how they relate to Servoy= . The chapter is organized from macro to micro; that is, it first describes= concepts relating to the general development environment and goes down to = its specific parts.
A workspace is where all the developer's work is stored= in Eclipse. It is a collection of Eclipse project files and metadata. The = developer can have multiple workspace folders, but can only work with one a= t a time.
Upon installation, a default Servoy workspace is created as ../ser=
voy_workspace
. This Servoy workspace folder is used to store solutio=
n metadata, style, and security information; it will also house separate fo=
lders for each Servoy solution. Users have the option to create new workspa=
ces and switch between workspaces during development as needed using the File > Switch Workspace menu item.
Eclipse organizes different code sets into projects. Se= rvoy has the following types of projects:
A Servoy solution is typically assigned a resource project upo= n creation. For more information, see Working Wi= th Resource Projects.
In case circular projects support is needed, see Setting Preferences in S= ervoy below.
The Eclipse workbench is the graphical user interface window for Eclipse= . It can contain many different perspectives, as described below, but only = one perspective can be active at a time.
The Servoy Design perspective is where the average Serv= oy developer will spend most of their development time.
Definitions:
A perspective in Eclipse is a set of views and editors,= that is, everything one sees on a screen. The individual views and editors= that appear can be customized and saved as a 'perspective.'
Views are windows within a perspective. Developers use = views to view, edit, and manage these resources and data.
Editors are views in Servoy that provide users with spe= cialized tools to edit resources, such as scripts, tables, and others.
= =20The Servoy Design perspective contains views for workin= g with Servoy solutions and all their parts. Servoy-specific views include = the Solution Explorer, Script and Form Editors, and the Properties views. T= hese views are described further in the Servoy De= sign Perspective chapter.
Other perspectives used when programming in Servoy include Debug= and Team Synchronizing. These are discussed in t= heir respective chapters as well.
Perspectives can be customized to the taste of the developer via the
Servoy preferences can be accessed via the Window > = Preferences menu (respectively, Servoy Developer <= /strong>> Preferences on a Mac). Three important prefer= ence items are highlighted below:
If installed, SQL Explorer options are also set using t= he Preferences menu.