0.3Discovering the editor & creating a project
The essentials in 30 seconds
- The project is the unit of work: it groups the analysis, windows, reports, queries and code, in a folder to back up.
- The environment brings together the ribbon, the project explorer (the compass), the central editing area and the panes (field catalog, properties).
- You create a project through a wizard (name, location, type, skin, languages); the F1 reflex opens the help in French.
Mini-case thread — Yacine creates his management project
Yacine launches the WinDev project creation wizard for his electrical equipment SME in Oran. He enters the project name, the folder location and the application type, then chooses a skin: all the windows of his management application will adopt the same style without him styling each field. Once the project is created, he finds his way around the environment: the ribbon at the top for commands, the project explorer as a table of contents for all elements (windows, reports, queries, analysis), the central editing area that changes with the element opened, and the side panes (field catalog to drop, properties organized in tabs). He creates a first window, drops a label and a button into it, and adopts the F1 reflex on an element to open the contextual help. Reflex: everything lives in the project folder, which must be backed up entirely.
Standalone case for this section: it returns in the course, the diagram, the script and the 48h challenge of section 0.3.
1. The project, unit of work
The notion of a project is central in WinDev. A project groups all the elements of an application: the analysis (the data model), the windows (the interface), the reports (the prints), the queries, the code (procedures, classes) and the settings. It is stored in a folder on disk: this complete folder is what must be backed up and versioned. For Yacine, the “NegoceElec” project is the box that contains his entire management application.
2. The development environment
The editor brings together several areas. The ribbon at the top groups commands by thematic tabs (Home, Project, Analysis, Window, Code, Test…). The project explorer lists all the elements — it is the compass. The central editing area changes with what you are editing (window, code, analysis, report). The side panes give access to the field catalog (components to drop) and to the properties, organized in tabs.
3. Creating a project and the skin
You create a project through a wizard that asks the structuring questions: name, location, application type, skin (the visual style automatically applied to the whole application), data management, languages. Each element has a properties window organized in tabs (General, UI, Details, Binding, Style…). Finally, the F1 contextual help is a reflex to adopt very early: PC SOFT documentation is rich and in French. Yacine chooses his skin at creation time to stay consistent effortlessly.
🔎 Concrete example — 🔎 Concrete example — filling a table when a window opens
In Yacine's customer management window, the initialization code scans the Customer file:
// Initialization of the customer list window
TableSupprimeTout(TAB_Clients)
POUR TOUT Client
TableAjouteLigne(TAB_Clients, Client.Nom, Client.Ville, Client.Telephone)
FINReading: the window (FEN_Clients) and the table were created by drag and drop from the field catalog.
Lesson: the project explorer serves as a compass to find each element and open its code.
Section vocabulary
- Project
- Unit of work grouping all the application's elements, stored in a folder to back up.
Simple example: Yacine versions the NegoceElec project folder.
What it is not: a code file isolated from the rest.
Reflex: group everything → project.
- Project explorer
- Pane listing all elements (windows, reports, queries, code, analysis).
Simple example: Yacine uses it to open a window.
What it is not: a license display area.
Reflex: navigate → project explorer.
- Ribbon
- Command bar organized by thematic tabs, adapted to the current editor.
Simple example: Yacine inserts a new window there.
What it is not: the field catalog to drop.
Reflex: find a command → ribbon.
- Skin
- Consistent visual style automatically applied to the whole application, chosen at creation.
Simple example: Yacine picks a skin for his management windows.
What it is not: a style applied field by field by hand.
Reflex: visual consistency → skin.
- Contextual help (F1)
- Help in French opened on the selected element, accessible everywhere in the editor.
Simple example: Yacine presses F1 to understand a property.
What it is not: a mandatory external search engine.
Reflex: understand quickly → F1.
In practice — In practice — creating your first project
- Launch the project creation wizard: name, location, application type, then choose a skin.
- Identify the areas of the environment: ribbon, project explorer, central editing area, field catalog.
- Create a first window, drop a few fields into it (label, button) by drag and drop, and open their properties.
- Test the application (Test/Run mode) and, like Yacine, adopt the F1 reflex on any element to open the contextual help.
Step-by-step script — creating the NegoceElec project (Yacine)
// Creating Yacine's management project // 1) Wizard: name NegoceElec, location D:\\Projets\\NegoceElec // 2) Application type: Windows // 3) Skin: chosen from the start // 4) Project explorer: add analysis, windows, reports // 5) F1 on an element: the contextual help opens Info("Projet NegoceElec prêt")
Choosing the skin at creation avoids tedious rework later.
Copy-paste template — searching for a customer from a window
// Yacine's template — BTN_Rechercher button of the FEN_Clients window
sNom est une chaîne
sNom = SAI_Nom
HLitRecherchePremier(Client, NomClient, sNom)
SI HTrouve(Client) ALORS
SAI_Ville = Client.Ville
SAI_Telephone = Client.Telephone
SINON
Info("Client introuvable : " + sNom)
FINCreation wizard
Yacine names his project, chooses the location and the Windows application type.
Skin chosen early
Yacine sets the skin at creation time for homogeneous windows.
Explorer as compass
Yacine finds each window, report or query through the project explorer.
F1 reflex
Yacine opens the contextual help in French on a property he does not know.
✓ Best practices
- Back up and version the whole folder of the project.
- Choose the skin at creation time.
- Adopt the F1 reflex very early (help in French).
✗ Common pitfalls
- Backing up only the project's main file.
- Styling each field by hand and then wanting to change the skin.
- Looking for an element without going through the project explorer.
Key takeaways
- The project is the unit of work: it groups all elements and lives in a folder to back up.
- The environment brings together the ribbon, the project explorer, the editing area and the panes.
- You create a project through a wizard and choose a skin from the start.
- Each element has properties in tabs; the F1 reflex opens the contextual help in French.
48h challenge — apply it tomorrow
Like Yacine, create a WinDev project (name, location, Windows type) and choose a skin. Then identify the four areas of the environment, create a window with a label and a button, then press F1 on an element. Finally, note where the complete folder to back up is located in your folders.
- I know that a WinDev project groups all elements in a folder.
- I navigate the environment (ribbon, explorer, editing area, panes).
- I create a project through the wizard and use the F1 contextual help.
Frequently asked questions
What is a skin in WinDev, and why choose it from the start?
It is the consistent visual style (colors, fonts, appearance of buttons, fields, tables) automatically applied to the whole application. Chosen at creation, it guarantees a homogeneous, professional interface without styling each field by hand — and changing it in the skin propagates everywhere. Yacine therefore sets it from day one.
What does a WinDev project actually contain, and what must be backed up?
A project is a folder containing the analysis (the data model), the windows, the reports, the queries, the code (procedures, classes), the resources and the skin, plus possibly test data. Since elements are interdependent, you must back up — and ideally version — the whole folder, never an isolated file.
What is a WinDev project?