Editing The Perl Lazarus Workshop (section)

== At the workbench: draw your workshop map ==

Before installing the full stack, prepare a workshop inventory.

{| class="wikitable"
|+ The Perl Lazarus Workshop
! Layer
! Selected tool
! Work performed
! Verification
|-
| Perl environment
| Strawberry Perl
| Runs Perl and supplies native build tools
| Confirm the intended <code>perl.exe</code>, architecture, and compiler
|-
| Native GUI library
| wxWidgets
| Supplies windows, controls, events, and platform integration
| Confirm the wxWidgets version used by wxPerl
|-
| Native-library bridge
| <code>Alien::wxWidgets</code>
| Describes or supplies the wxWidgets build used by Perl
| Query the installed module version and build configuration
|-
| Perl GUI binding
| <code>Wx</code> / wxPerl
| Makes wxWidgets available to Perl
| Run a minimal frame and <code>Wx::Demo</code>
|-
| Visual designer
| wxGlade
| Saves the visual design and emits Perl or XRC
| Generate and run a small Perl interface
|-
| Editing environment
| MSYS2 and vim
| Supplies a familiar Unix-like editing shell
| Confirm vim and the project paths
|-
| Revision control
| Git
| Preserves history, diffs, and recoverable checkpoints
| Create a repository and commit the generated project
|-
| Executable packaging
| PAR, <code>wxpar</code>, and <code>pp_autolink</code>
| Packages Perl and discovers native dependencies
| Run the EXE outside the Strawberry Perl terminal
|-
| Installer
| Inno Setup
| Produces the Windows installation experience
| Install, launch, upgrade, and uninstall on a clean machine
|-
| Independent test bench
| Clean Windows virtual machine or physical system
| Reveals dependencies accidentally supplied by the workshop
| Test without Strawberry Perl or the development tools installed
|}

For each tool, answer:

# What exact task does it perform?
# Which other layer does it depend upon?
# Which version has actually been tested?
# How will success be verified?
# Where will installation and build logs be kept?
# What license governs its use?
# What labor and knowledge did its authors contribute?
# What would happen to the workflow if the tool disappeared?
# Is the project data stored in an open or inspectable format?
# Can the important build steps be reproduced without a graphical helper?

The purpose is not to produce paperwork for its own sake.

The map helps the craftsman understand his shop before something breaks.