Perl Guilds - Getting Medieval with Perl - User contributions [en]

Raising a Working wxPerl Shop on Windows

2026-07-20T06:28:32Z

104.181.193.235:

{{DISPLAYTITLE:Raising a Working wxPerl Shop on Windows}}

''This is the third essay in the series [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]. It follows [[The Perl Lazarus Workshop]] and moves from explaining the selected tools to assembling and using them.''

A collection of tools is not yet a workshop.

The craftsman must know where each tool belongs, how to verify that it works, and how to move from one stage of the work to the next without losing what he has already made.

This essay will raise a practical wxPerl shop on Windows. By the end, the programmer should possess:

* a known Strawberry Perl environment;
* a working installation of <code>Alien::wxWidgets</code> and <code>Wx</code>;
* a visible wxPerl demonstration;
* wxGlade configured to emit Perl;
* an MSYS2 terminal with vim and Git;
* a small wxGlade project;
* generated Perl source;
* at least one working event;
* and a Git commit preserving the first successful state of the shop.

This is not yet the construction of a commercial application. It is the preparation of the place in which such an application can be built.

The distinction matters.

A programmer who begins a major project before verifying the workshop may later be unable to tell whether a failure belongs to the application, the GUI design, the active Perl, the native library, the generated code, or the operating environment.

The prudent craftsman proves each layer before placing the next one upon it.

== What counts as a working shop? ==

The shop is working when the entire development cycle can be repeated:

# Open or create a wxGlade project.
# Change the graphical design.
# Emit Perl source code.
# Inspect the generated changes.
# Add or revise application behavior.
# Run the application with the intended Strawberry Perl.
# Correct the work.
# Preserve a known-good state in Git.

The goal is not merely to install several programs without error messages.

The goal is to establish a rhythm of work.

{| class="wikitable"
|+ The daily wxPerl working cycle
! Stage
! Primary tool
! Result
|-
| Design
| wxGlade
| A saved <code>.wxg</code> XML project
|-
| Emit
| wxGlade
| Perl source generated from the visual design
|-
| Inspect and edit
| vim under MSYS2
| Reviewed source and handwritten behavior
|-
| Run
| Strawberry Perl terminal
| The actual wxPerl application
|-
| Compare and preserve
| Git under MSYS2
| A diff and recoverable checkpoint
|}

The distinction between these environments will be repeated throughout this essay because it prevents one of the most confusing failures in the workflow:

<blockquote>
Use MSYS2 to edit and manage the project, but run the wxPerl application using Strawberry Perl.
</blockquote>

MSYS2 may have its own Perl. That Perl is not the Perl against which the selected wxPerl stack was built.

== Begin with a tested profile ==

A craftsman may enjoy experimenting with the newest tools, but he should first establish a known working reference point.

The living version matrix is maintained at [[Developing and Distributing wxPerl Applications on Windows#More Specific Version Combinations with Detailed Instructions & Links|Developing and Distributing wxPerl Applications on Windows]]. At the time this essay was prepared, the documented profiles included:

{| class="wikitable"
|+ Selected wxPerl installation profiles
! Status
! Strawberry Perl
! <code>Alien::wxWidgets</code>
! <code>Wx</code>
! Use
|-
| Previously tested reference
| 5.40.2.1, 64-bit UCRT MSI
| 0.71
| 3.008
| The safer starting point for reproducing the established workflow
|-
| Newer PDL-oriented profile
| 5.42.2.1, 64-bit UCRT PDL ZIP
| 0.73
| 3.009
| A newer path which should be treated according to the current verification status on the wiki
|-
| Archived reference
| 5.40.0.1, 64-bit UCRT MSI
| 0.70
| 3.005
| Historical comparison and regression troubleshooting
|}

The exact versions will change. This essay therefore explains the process using the previously tested 5.40.2.1 profile, while the maintained installation page remains authoritative for current links and newly verified combinations.

A tested profile is not a claim that newer software is bad.

It is a statement about evidence.

The programmer who chooses an experimental profile should record that decision. He should not later describe the result as though it had received the same testing as the reference profile.

== Prepare a work record before installing anything ==

Create a plain-text file named:

<pre>
wxperl-environment.txt
</pre>

Record:

* the date;
* Windows edition and version;
* whether the system is 64-bit;
* the selected Strawberry Perl profile;
* the selected <code>Alien::wxWidgets</code> version;
* the selected <code>Wx</code> version;
* the wxGlade version;
* the Python version used by wxGlade;
* the MSYS2 installation date;
* and links to the instructions followed.

This file is not bureaucracy.

It is a record of the workshop at the moment it was built. Six months later, when another machine behaves differently, the file may be more useful than memory.

Create a directory for installation logs as well:

<pre>
C:\wxperl-shop\logs
</pre>

The installation BAT file being developed for the Perl Lazarus Project should eventually automate much of this work. It should preserve the same order and should make each stage visible:

# identify the selected profile;
# run one installation stage;
# preserve its output;
# stop clearly when that stage fails;
# verify the result;
# and continue only when the layer beneath it is sound.

The batch file should preserve successful labor. It should not turn the installation into an unknowable ritual.

The manual steps remain important because they allow the craftsman to understand and repair the automated process.

== Install Strawberry Perl ==

For the previously tested profile, use the instructions at:

* [[Wx 3.008, Alien::wxWidgets 0.71, Strawberry Perl 5.40.2.1]]

The documented installer is the 64-bit UCRT MSI distribution of Strawberry Perl 5.40.2.1.

Run the installer normally. When it completes, close any command windows which were already open. A terminal started before installation may not see the updated <code>PATH</code>.

Open:

<pre>
Start menu → Strawberry Perl → Perl (command line)
</pre>

This should produce an ordinary Windows command prompt prepared for Strawberry Perl.

Run:

<pre>
where perl
perl -v
perl -V:archname
perl -V:cc
where gcc
where gmake
</pre>

The first <code>perl</code> reported by <code>where perl</code> should be the intended Strawberry Perl executable, normally under a path resembling:

<pre>
C:\Strawberry\perl\bin\perl.exe
</pre>

The exact compiler version is less important than proving that Strawberry Perl's compiler and build tools are available.

Save the output:

<pre>
where perl > C:\wxperl-shop\logs\strawberry-baseline.txt
perl -v >> C:\wxperl-shop\logs\strawberry-baseline.txt
perl -V:archname >> C:\wxperl-shop\logs\strawberry-baseline.txt
perl -V:cc >> C:\wxperl-shop\logs\strawberry-baseline.txt
where gcc >> C:\wxperl-shop\logs\strawberry-baseline.txt
where gmake >> C:\wxperl-shop\logs\strawberry-baseline.txt
</pre>

Do not proceed until the intended Perl is clear.

A large number of Windows development failures are not failures of the language or module under examination. They are failures to identify which executable is actually running.

== Install Alien::wxWidgets ==

Remain in the Strawberry Perl command-line window.

For the tested profile, run:

<pre>
cpanm --verbose https://github.com/sciurius/perl-Alien-wxWidgets/releases/download/R0.71/Alien-wxWidgets-0.71.tar.gz
</pre>

Preserve the output if practical:

<pre>
cpanm --verbose https://github.com/sciurius/perl-Alien-wxWidgets/releases/download/R0.71/Alien-wxWidgets-0.71.tar.gz > C:\wxperl-shop\logs\alien-wxwidgets-install.txt 2>&1
</pre>

This stage may require time. Native libraries and build configuration are involved.

Do not mistake a quiet period for certain failure. Do not mistake a long stream of compiler output for success either.

Wait for the final result.

Then verify:

<pre>
perl -MAlien::wxWidgets -e "print qq{Alien::wxWidgets $Alien::wxWidgets::VERSION\n}"
</pre>

For this profile, the output should identify version 0.71.

If Perl reports that the module cannot be found, do not attempt to install <code>Wx</code> repeatedly in the hope that the missing layer will repair itself. Read the log and correct this stage first.

== Install Wx / wxPerl ==

Once <code>Alien::wxWidgets</code> is installed and can be loaded, install the Perl binding:

<pre>
cpanm --verbose https://github.com/sciurius/wxPerl/releases/download/R3.008/Wx-3.008.tar.gz
</pre>

To preserve the complete output:

<pre>
cpanm --verbose https://github.com/sciurius/wxPerl/releases/download/R3.008/Wx-3.008.tar.gz > C:\wxperl-shop\logs\wxperl-install.txt 2>&1
</pre>

Then verify:

<pre>
perl -MWx -e "print qq{Wx $Wx::VERSION\n}"
</pre>

The selected profile should report:

<pre>
Wx 3.008
</pre>

Also verify both layers in one command:

<pre>
perl -MAlien::wxWidgets -MWx -e "print qq{Alien::wxWidgets $Alien::wxWidgets::VERSION\nWx $Wx::VERSION\n}"
</pre>

A successful module load is important, but it is not yet a complete graphical test.

The binding must create an application and enter the Windows event loop.

== Run a minimal hand-written wxPerl application ==

Create:

<pre>
C:\wxperl-shop\hello-wx.pl
</pre>

with the following contents:

<syntaxhighlight lang="perl">
use strict;
use warnings;
use Wx;

package HelloWxApp;
use parent 'Wx::App';

sub OnInit {
my ($self) = @_;

my $frame = Wx::Frame->new(
undef,
-1,
'The Perl Lazarus Workshop',
);

$frame->SetSize(640, 360);
$frame->Centre();
$frame->Show(1);

return 1;
}

package main;

my $app = HelloWxApp->new();
$app->MainLoop();
</syntaxhighlight>

Run it from the Strawberry Perl terminal:

<pre>
cd /d C:\wxperl-shop
perl hello-wx.pl
</pre>

A blank frame titled “The Perl Lazarus Workshop” should appear.

This small program proves several things at once:

* Strawberry Perl is active.
* <code>Wx</code> can be loaded.
* The native wxWidgets libraries can be found.
* A Windows frame can be created.
* The event loop can run.
* The application can close normally.

Do not dismiss the blank window as trivial.

It is the first physical proof that the shop has been raised.

== Install and run Wx::Demo ==

The next verification is broader.

From the Strawberry Perl terminal:

<pre>
cpanm --verbose Wx::Demo
</pre>

Then run:

<pre>
wxperl_demo.pl
</pre>

<code>Wx::Demo</code> provides working examples of controls and facilities exposed through wxPerl. It is both a verification program and an early reference catalog.

Spend some time opening examples.

Look at:

* buttons and text controls;
* list and tree controls;
* notebooks;
* menus;
* dialogs;
* drawing examples;
* timers;
* and event handling.

The purpose is not to memorize the entire toolkit. It is to understand that wxPerl is larger than the blank frame and that many common interface patterns already have working examples.

If <code>hello-wx.pl</code> runs but <code>Wx::Demo</code> does not, the error is narrower than it would have been without the first test. The core binding works; the problem lies in the additional module, its scripts, or its dependencies.

This is why the craftsman tests in layers.

== Install wxGlade ==

[[File:WxgladeWinExample.png|thumb|right|380px|alt=wxGlade running on Windows while designing a GUI for a wxPerl application|wxGlade supplies the visual portion of the shop. It is written using wxPython, but it can emit Perl source code directly.]]

wxGlade is a separate application. It is written using Python and wxPython, even though the application being developed will use Perl and wxPerl.

That is not a contradiction.

A tool need not be written in the same language as the work it helps produce.

The tested recipe currently documented at [[Developing and Distributing wxPerl Applications on Windows#wxGlade - a Perl Friendly Cross-Platform GUI Builder|Developing and Distributing wxPerl Applications on Windows]] uses:

* Python 3.10.11;
* wxPython installed through <code>pip</code>;
* and wxGlade 1.1.1.

Later Python combinations may work, but the living page should be consulted before replacing a tested profile merely because a newer Python release exists.

Install Python 3.10.11 using the link in the maintained instructions. Enable the option to add Python to the Windows <code>PATH</code>.

Open a normal Windows Command Prompt, not the Strawberry Perl terminal, and verify:

<pre>
where python
python --version
python -m pip --version
</pre>

Install wxPython:

<pre>
python -m pip install wxPython
</pre>

Download and unpack wxGlade 1.1.1. A reasonable location is:

<pre>
C:\Tools\wxGlade-1.1.1
</pre>

Change to that directory:

<pre>
cd /d C:\Tools\wxGlade-1.1.1
python wxglade.py
</pre>

If the distribution provides <code>wxglade.pyw</code>, it can also be launched without retaining a console window.

Create a small wrapper named:

<pre>
C:\Tools\wxGlade-1.1.1\start-wxglade.cmd
</pre>

with:

<pre>
@echo off
cd /d "C:\Tools\wxGlade-1.1.1"
start "" pythonw wxglade.pyw
</pre>

Adjust the path and filename to match the actual installation.

A Windows shortcut may then point to <code>start-wxglade.cmd</code>. The change of directory is useful because wxGlade may expect to find supporting files relative to its own directory.

The desktop shortcut is not a mere convenience. A tool used frequently should be easy to start correctly. Requiring the programmer to remember a fragile launch ritual creates needless opportunities for error.

<div style="clear:both;"></div>

== Install MSYS2, vim, and Git ==

MSYS2 provides a Unix-like terminal and package-management environment for Windows.<ref>[https://www.msys2.org/docs/what-is-msys2/ MSYS2, “What is MSYS2?”]</ref>

Install MSYS2 using its current official installer. Follow the official update procedure, which may require closing and reopening the terminal during a full system update.

Then install vim and Git:

<pre>
pacman -S vim git
</pre>

Verify:

<pre>
vim --version
git --version
</pre>

If Git will communicate with a remote repository over SSH, create or import the appropriate key and register the public key with the remote service.

A useful optional <code>~/.vimrc</code> for the author's preferred MSYS2 workflow is:

<pre>
set mouse=
set noautoindent
set nosmartindent
set nocindent
</pre>

These are personal workflow choices rather than universal requirements. They make ordinary terminal copying easier and prevent automatic indentation from interfering with pasted or generated blocks.

The critical check is:

<pre>
which perl
perl -v
</pre>

Inside MSYS2, the reported Perl may be:

<pre>
/usr/bin/perl
</pre>

This is not Strawberry Perl.

That is acceptable because MSYS2 is being used for vim, Git, shell navigation, and source inspection.

Do not use that Perl to run the generated wxPerl application.

Use the Strawberry Perl command-line window for:

<pre>
perl your-application.pl
</pre>

and later for:

<pre>
cpanm
wxpar
pp_autolink
gmake
</pre>

The following table should remain mentally visible:

{| class="wikitable"
|+ Two terminals, two responsibilities
! Environment
! Use it for
! Do not assume
|-
| MSYS2
| vim, Git, SSH, diffs, shell navigation
| That its <code>perl</code> is Strawberry Perl
|-
| Strawberry Perl command line
| Perl modules, wxPerl execution, application tests, packaging
| That Unix paths or MSYS2-specific shell behavior will apply
|}

A craftsman should know which shop he is standing in.

== Create the first project directory ==

Use a simple project for the first complete cycle.

From the MSYS2 terminal:

<pre>
mkdir -p /c/work/hello-wxperl/screenshots
cd /c/work/hello-wxperl
git init
</pre>

Create a short <code>README.md</code>:

<pre>
# Hello wxPerl

First wxGlade-generated wxPerl project created while raising the
Perl Lazarus development shop.
</pre>

The directory will eventually contain:

<pre>
hello-wxperl/
├── hello-wxperl.wxg
├── hello-wxperl.pl
├── README.md
└── screenshots/
</pre>

This is intentionally smaller than the structure of a production application.

The purpose is to prove the cycle before introducing application modules, tests, build directories, installer files, and documentation.

== Design the first interface in wxGlade ==

Open wxGlade.

Create a new application containing:

* one frame;
* one panel;
* one vertical box sizer;
* one static-text control;
* one button.

Use names which communicate purpose:

{| class="wikitable"
! Object
! Suggested name
! Label
|-
| Frame
| <code>MainFrame</code>
| The Perl Lazarus Workshop
|-
| Static text
| <code>status_text</code>
| The shop is ready.
|-
| Button
| <code>hello_button</code>
| Test wxPerl
|}

Select the root '''Application''' object in the wxGlade object tree.

Set:

* output language to '''Perl''';
* wxWidgets compatibility to '''3.0''';
* output path to the project Perl file;
* code generation to '''Single file''';
* and '''Keep user code''' to enabled.

[[File:Applicationsettings.png|thumb|left|330px|alt=wxGlade application output settings configured for Perl code generation and preservation of user code|The important initial wxGlade settings include Perl output and Keep user code. Without code preservation, a later generation may overwrite handwritten work.]]

Save the wxGlade project as:

<pre>
C:\work\hello-wxperl\hello-wxperl.wxg
</pre>

Set the Perl output file to:

<pre>
C:\work\hello-wxperl\hello-wxperl.pl
</pre>

Press:

<pre>
Ctrl-G
</pre>

to generate the Perl source.

The <code>.wxg</code> file is not the Perl program. It is the XML project describing the visual design.

The <code>.pl</code> file is the code emitted from that design.

Both are valuable source artifacts and both should be kept in Git.

<div style="clear:both;"></div>

== Inspect what wxGlade emitted ==

Return to the MSYS2 terminal:

<pre>
cd /c/work/hello-wxperl
ls -l
vim hello-wxperl.pl
</pre>

Do not immediately begin changing random portions of the generated code.

First inspect:

* the packages wxGlade created;
* the frame constructor;
* the controls;
* the sizers;
* the generated identifiers;
* the event-handler placeholders;
* the application class;
* and the final call to the event loop.

Look for wxGlade's generated-code markers. Their exact form may change among releases, but they identify sections which wxGlade owns and may regenerate.

The '''Keep user code''' option is intended to preserve code outside those protected generation blocks.

It is not permission to ignore source control.

Before adding handwritten behavior, commit the generated baseline:

<pre>
git add hello-wxperl.wxg hello-wxperl.pl README.md
git commit -m "Generate initial wxGlade wxPerl application"
</pre>

Now there is a recoverable point before the first manual edit.

== Run the generated Perl with Strawberry Perl ==

Open the Strawberry Perl command-line window.

Run:

<pre>
cd /d C:\work\hello-wxperl
where perl
perl hello-wxperl.pl
</pre>

The frame should appear with the static text and button.

The button may not yet perform useful work. That is expected.

At this stage the entire visual generation path has been verified:

<pre>
wxGlade .wxg project
↓
Perl source emission
↓
Strawberry Perl
↓
wxPerl / wxWidgets
↓
Windows frame
</pre>

If the generated program does not run, do not begin installing PAR or building an executable.

The source application must work first.

Read the error from the Strawberry terminal. Confirm that the active Perl is correct. Compare the generated application with the hand-written <code>hello-wx.pl</code> which already worked.

The proven lower layer is a diagnostic advantage.

== Wire the first event ==

Return to wxGlade and select the button.

Assign its button-click event to a handler named:

<pre>
on_hello
</pre>

Save the project and press <code>Ctrl-G</code> again.

Return to vim. Allow vim to reload the changed file if it detects that wxGlade has modified it.

Locate the generated <code>on_hello</code> handler. Add behavior only in the user-preserved area intended for the handler:

<syntaxhighlight lang="perl">
sub on_hello {
my ($self, $event) = @_;

Wx::MessageBox(
'Your wxPerl shop is working.',
'Perl Lazarus Project',
Wx::wxOK(),
$self,
);
}
</syntaxhighlight>

The exact generated function signature or location may vary with the wxGlade release and project structure. Preserve the structure emitted by wxGlade and add the application behavior to the appropriate handler.

Save the file.

Run it again from Strawberry Perl:

<pre>
perl hello-wxperl.pl
</pre>

Click the button.

A message box should appear.

The shop now supports the complete elementary cycle:

* visual design;
* Perl generation;
* manual wiring;
* execution;
* and user interaction.

Commit the result:

<pre>
git add hello-wxperl.wxg hello-wxperl.pl
git commit -m "Wire first wxPerl button event"
</pre>

== Practice the edit–emit–wire–run cycle ==

[[File:Wxperl-workflow.png|thumb|right|410px|alt=Windows desktop arranged with Strawberry Perl, MSYS2 vim, and wxGlade for an efficient wxPerl development workflow|A practical working arrangement: wxGlade emits Perl, vim under MSYS2 inspects and edits it, and the Strawberry Perl terminal runs the application.]]

Make one further visual change:

* change the frame title;
* add another label;
* alter the button text;
* or adjust the spacing.

Before generating, check Git:

<pre>
git status
</pre>

Commit or stash any unfinished handwritten work.

Generate again with <code>Ctrl-G</code>.

Inspect the diff:

<pre>
git diff
</pre>

Confirm that the handler remains present.

Run the application with Strawberry Perl.

Then commit the visual revision.

This cycle should become habitual:

<pre>
Design in wxGlade
↓
Save the .wxg project
↓
Generate Perl with Ctrl-G
↓
Inspect the diff in MSYS2
↓
Wire or revise behavior in vim
↓
Run with Strawberry Perl
↓
Test the actual user action
↓
Commit the known-good result
</pre>

Generated code should never become an excuse to stop reading code.

The craftsman should know what changed.

<div style="clear:both;"></div>

== Using AI without surrendering the craft ==

AI can be effective at two points in this workflow.

First, it can prepare a first-draft wxGlade XML project from a plain-language description.

Second, it can assist with the Perl wiring which connects generated controls to application behavior.

The [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates wxPerl and wxGlade template repository] demonstrates this possibility. Its GUI templates were initially created with ChatGPT and then used as wxGlade projects and Perl examples.

A productive AI-assisted cycle is:

# Describe the intended window and controls.
# Ask for a wxGlade-compatible <code>.wxg</code> draft.
# Save the XML to a file.
# Open it in wxGlade.
# Correct invalid properties, names, nesting, and layout.
# Save it through wxGlade.
# Emit Perl.
# Run the generated application.
# Ask for assistance wiring a named event.
# Review every change.
# Test the user action.
# Commit only the result which has actually been verified.

A useful prompt might specify:

<pre>
Create a first-draft wxGlade 1.1.1 XML project for a wxWidgets 3.0
application. The output language will be Perl. Include one frame,
a panel, a vertical box sizer, a status label, and a button named
hello_button. The button event handler should be named on_hello.
</pre>

The AI-generated file is not authoritative merely because it is well formed.

wxGlade is the first practical judge of whether the XML describes a valid project. The generated Perl and the running application provide further tests. The craftsman provides the final judgment.

God is the source of human intelligence and talent. AI is a human-made tool assembled from created materials, accumulated knowledge, infrastructure, and labor. It is not a person, an apprentice, a master, or a moral agent.

It can assist the work.

It cannot accept responsibility for it.

== Troubleshoot in the order the shop was built ==

When the project fails, resist the temptation to change everything at once.

Use this order:

=== 1. Confirm the active Perl ===

In the Strawberry command window:

<pre>
where perl
perl -v
</pre>

In MSYS2:

<pre>
which perl
perl -v
</pre>

Know which result belongs to which environment.

=== 2. Confirm the modules ===

<pre>
perl -MAlien::wxWidgets -e "print qq{$Alien::wxWidgets::VERSION\n}"
perl -MWx -e "print qq{$Wx::VERSION\n}"
</pre>

=== 3. Run the hand-written frame ===

<pre>
perl C:\wxperl-shop\hello-wx.pl
</pre>

If this fails, the problem is beneath wxGlade.

=== 4. Run Wx::Demo ===

<pre>
wxperl_demo.pl
</pre>

This provides a broader binding test.

=== 5. Run the generated program ===

<pre>
perl C:\work\hello-wxperl\hello-wxperl.pl
</pre>

Read the first meaningful error rather than only the last line.

=== 6. Inspect the most recent generation ===

From MSYS2:

<pre>
git diff
git status
</pre>

Check whether handwritten code disappeared or a generated block changed unexpectedly.

=== 7. Return to the last known-good commit ===

Do not destroy evidence in panic. Create a branch or preserve the broken state before reverting.

=== 8. Change one layer at a time ===

Do not simultaneously update Strawberry Perl, wxPerl, Python, wxGlade, and MSYS2 while investigating one failure.

A workshop can be repaired only when the craftsman knows what changed.

== The craft and the virtue ==

This stage of the journey requires spiritedness, or fortitude, rather than impatience.

Installation work is often wearying because the visible reward comes late. The programmer may spend considerable time reading compiler output, comparing paths, waiting for native builds, and discovering that one command was executed from the wrong terminal.

Impatience responds by changing versions randomly, rerunning commands without reading their output, disabling safeguards, or abandoning the whole effort as soon as the first path fails.

Fortitude does not mean mindless repetition.

It means remaining with a worthy difficulty long enough to understand it.

<blockquote>
“And if a man love justice: her labours have great virtues; for she teacheth temperance, and prudence, and justice, and fortitude.”
<br />— Wisdom 8:7, Douay-Rheims
</blockquote>

The craftsman begins with gratitude.

The world in which he works was created by God. His intelligence, memory, patience, opportunity, and capacity to learn are gifts. The compiler, language, GUI library, editor, examples, documentation, and operating system also contain the labor and talents of other persons.

Raising the shop is therefore an exercise in stewardship.

The programmer receives tools and knowledge, develops his own abilities, and prepares himself to perform work for others.

A failure does not diminish the programmer's God-given dignity. A successful installation does not make him superior to the apprentice who is still learning. Technical progress measures the present state of the work, not the worth of the worker.

Fortitude allows the programmer to admit:

* “I used the wrong Perl.”
* “I do not yet understand this generated block.”
* “The experimental profile has not been verified.”
* “I need to return to the documented version.”
* “My AI-generated XML is invalid.”
* “I overwrote my code because I failed to enable the correct setting.”
* “I need help from another craftsman.”

These admissions are not defeats.

They are acts of truth.

The shop becomes dependable when the craftsman prefers truth over appearance: a real test over an assumption, a saved log over memory, a Git diff over confidence, and a known working profile over the prestige of using the newest release.

The purpose is not to boast that wxPerl can display a window.

The purpose is to prepare a place in which useful software can be built faithfully and brought to completion.

== At the workbench: the first-shop checkpoint ==

Before proceeding, confirm that all of the following exist:

{| class="wikitable"
! Check
! Evidence
|-
| Strawberry Perl is active
| Saved output from <code>where perl</code> and <code>perl -v</code>
|-
| Native build tools exist
| <code>gcc</code> and <code>gmake</code> are found
|-
| <code>Alien::wxWidgets</code> loads
| Version command succeeds
|-
| <code>Wx</code> loads
| Version command succeeds
|-
| A hand-written frame runs
| <code>hello-wx.pl</code> opens and closes
|-
| <code>Wx::Demo</code> runs
| Demonstration controls can be opened
|-
| wxGlade runs
| The application launches through a repeatable shortcut or command
|-
| wxGlade emits Perl
| <code>hello-wxperl.pl</code> exists
|-
| The generated application runs
| The frame appears under Strawberry Perl
|-
| An event is wired
| The button displays a message
|-
| MSYS2 contains vim and Git
| Both version commands succeed
|-
| The two Perl environments are understood
| <code>which perl</code> and <code>where perl</code> have been compared
|-
| The project is preserved
| At least two meaningful Git commits exist
|-
| The process is documented
| <code>wxperl-environment.txt</code> and logs exist
|}

Also preserve:

* the <code>.wxg</code> project;
* the emitted Perl;
* the hand-written verification program;
* one screenshot of the running application;
* the installation logs;
* and the project history.

The result is modest, but it is real.

The programmer now possesses a working Windows wxPerl shop.

== Continue the journey ==

The next essay, [[From wxGlade Layout to Working Perl Application]], will move beyond the demonstration project.

It will examine:

* how wxGlade-generated Perl is organized;
* which parts of the source belong to the generator;
* how controls should be named;
* how events should be assigned;
* how business logic can be kept outside the GUI;
* how repeated regeneration can remain safe;
* when separate generated classes or XRC may become useful;
* and how a graphical prototype becomes a maintainable Perl application.

The shop has been raised.

The next task is to practice the craft within it.

<references />

{{DEFAULTSORT:Raising a Working wxPerl Shop on Windows}}

'''Previous essay:''' [[The Perl Lazarus Workshop]]

'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]

'''Next essay:''' [[From wxGlade Layout to Working Perl Application]]

[[Category:The Virtuous Perl Programmer]]
[[Category:Perl Lazarus Project]]
[[Category:wxPerl]]
[[Category:Perl Guilds]]
[[Category:Windows]]
[[Category:Strawberry Perl]]
[[Category:wxGlade]]
[[Category:MSYS2]]
[[Category:Git]]

Wx 3.009, Alien::wxWidgets 0.73, Strawberry Perl 5.42.2.1 PDL

2026-07-05T06:30:21Z

104.181.193.235: Created page with "=== Step 1 - Install Strawberry Perl PDL (5.42.2.1) === Install the Strawberry Perl PDL ZIP edition from the Strawberry Perl release page: <big>[https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54221_64bit Strawberry Perl 5.42.2.1 64-bit release assets]</big> Download: <big><code>strawberry-perl-5.42.2.1-64bit-PDL.zip</code></big> ==== Installing Strawberry Perl (5.42.2.1) + PDL ==== This build uses the Strawberry Perl PDL edition rather than..."

=== Step 1 - Install Strawberry Perl PDL (5.42.2.1) ===

Install the Strawberry Perl PDL ZIP edition from the Strawberry Perl release page:

<big>[https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54221_64bit Strawberry Perl 5.42.2.1 64-bit release assets]</big>

Download:

<big><code>strawberry-perl-5.42.2.1-64bit-PDL.zip</code></big>

==== Installing Strawberry Perl (5.42.2.1) + PDL ====

This build uses the Strawberry Perl PDL edition rather than the standard MSI. The PDL ZIP conventionally unpacks under:

<big><code>C:\sw\pdl</code></big>

This provides a Windows Perl environment that includes the Perl Data Language. See [https://wiki.perl-guilds.net/Portal:SciTech notes on creating a Perl environment using Strawberry Perl that includes PDL].

After extracting the ZIP, make sure the following directories are available in the active <code>PATH</code>:

<pre>
C:\sw\pdl\c\bin
C:\sw\pdl\perl\site\bin
C:\sw\pdl\perl\bin
</pre>

You can verify the Perl and PDL installation with:

<big><code>C:\> perl -v</code></big>

<big><code>C:\> perl -MPDL -E "say $PDL::VERSION"</code></big>

Once this is set up, the rest of the instructions starting with Step 2 below should work the same.

=== Step 2 - Install Alien::wxWidgets (v 0.73) ===

Once Perl is installed and the Strawberry Perl PDL directories are in the active <code>PATH</code>, open a Windows CMD window or PowerShell window using that environment.

Type the command at the <code>C:\></code> prompt:

<big><code>C:\> cpanm --verbose <nowiki>https://github.com/sciurius/perl-Alien-wxWidgets/releases/download/R0.73/Alien-wxWidgets-0.73.tar.gz</nowiki></code></big>

=== Step 3 - Install Wx / wxPerl (v 3.009) ===

<big><code>C:\> cpanm --verbose <nowiki>https://github.com/sciurius/wxPerl/releases/download/R3.009/Wx-3.009.tar.gz</nowiki></code></big>

=== Verified Version Combination ===

{| class="wikitable"
! Component
! Version
! Link
! Notes
|-
| Strawberry Perl
| 5.42.2.1 64-bit UCRT, PDL ZIP edition
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54221_64bit SP_54221_64bit]
| PDL edition; conventionally unpacks under <code>C:\sw\pdl</code>.
|-
| Alien::wxWidgets
| 0.73
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.73 R0.73]
| wxWidgets discovery/configuration layer for wxPerl.
|-
| Wx / wxPerl
| 3.009
| [https://github.com/sciurius/wxPerl/releases/tag/R3.009 R3.009]
| Perl bindings for wxWidgets.
|}

Developing and Distributing wxPerl Applications on Windows

2026-07-05T06:28:51Z

104.181.193.235: /* Installation */

== Introduction ==

This article is part of the Perl Lazarus Project, an effort to make Windows GUI development in Perl practical again by identifying a working toolchain for creating, packaging, and distributing desktop applications.

The name is a nod both to Lazarus of the Bible and to the excellent Lazarus IDE for Free Pascal. Perl does not currently have a direct equivalent to that kind of unified rapid application development environment, so this project focuses on documenting a practical path using the tools that are available today.

This page is about installing wxPerl under Strawberry Perl for application development and distribution as a Windows executable.

=== Why Perl GUIs, why Windows? ===
This is a critical ability for any freelance Perl developer, since it complements a Perl journeyman's ability to do many things on servers, such as create remote services. Being able to transfer these skills to the desktop environment is especially useful on Windows, where users are accustomed to paying for software. In short, Perl programmers who want to make a living on their own need to know how to create and distribute Windows GUI applications; this page covers a large piece of how to do that.
[[File:FreeAPIGUI.png|alt=wxPerl GUI running on Windows as a double-clickable EXE file!|thumb|wxPerl GUI running on Windows as a double-clickable EXE file! Created using wxGlade, a RAD-ish tool. See [https://github.com/oodler577/FreeAPI-Perl-API-Explorer more images] on Github.]]
Instructions are provided with the versions detailed below. If there are newer versions of any of the modules, you may try them out (of course); but understand they have not been tried and shown to work like the version combinations below.

=== [https://dev.to/sciurius/wxperl-revival-5fde See] the original call for a [https://dev.to/sciurius/wxperl-revival-5fde wxPerl Revival]! ===

=== Git Repository of wxGlade / wxPerl Examples ===
https://github.com/The-Perl-Cottage-Guild/wxPerl-Templates
== Installation ==

=== General Steps ===

{| class="wikitable"
! Step
! Component
! Link
! Notes
|-
| 1
| Strawberry Perl
| [https://strawberryperl.com/releases.html releases]
| Install Strawberry Perl first. For the newer PDL-based build, use the PDL ZIP edition rather than the standard MSI.
|-
| 2
| Alien::wxWidgets
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/ github]
| Install after Strawberry Perl and wxWidgets are available.
|-
| 3
| Wx / wxPerl
| [https://github.com/sciurius/wxPerl/releases github]
| Install last; this is the Perl binding used by wxPerl applications.
|}

=== More Specific Version Combinations with Detailed Instructions & Links ===

{| class="wikitable"
! Status
! Strawberry Perl
! wxWidgets
! Alien::wxWidgets
! Wx / wxPerl
! Detailed Instructions / Links
! Notes
|-
| Latest / Experimental PDL Build
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54221_64bit 5.42.2.1 64-bit UCRT, PDL ZIP edition]
| [https://github.com/wxWidgets/wxWidgets/releases/tag/v3.2.9 3.2.9]
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.73 0.73]
| [https://github.com/sciurius/wxPerl/releases/tag/R3.009 3.009]
| [[Wx 3.009, Alien::wxWidgets 0.73, Strawberry Perl 5.42.2.1 PDL]]
| The PDL ZIP conventionally unpacks under <code>C:\sw\pdl</code>. Add <code>C:\sw\pdl\c\bin</code>, <code>C:\sw\pdl\perl\site\bin</code>, and <code>C:\sw\pdl\perl\bin</code> to the active <code>PATH</code>.
|-
| Previously Tested
| 5.40.2.1
| Not separately documented on this summary page
| 0.71
| 3.008
| [[Wx 3.008, Alien::wxWidgets 0.71, Strawberry Perl 5.40.2.1]]
| Previously documented working combination.
|-
| Archive
| 5.40.0.1
| Not separately documented on this summary page
| 0.70
| 3.005
| [[Wx 3.005, Alien::wxWidgets 0.70, Strawberry Perl 5.40.0.1]]
| Earlier archived working combination.
|}

== Verify Installation ==
The information provided in this section ought to be unrelated to the verified version combination outlined in the Installation section above.

=== Install Wx::Demo ===
Wx::Demo is nice demonstration application, highlight many (if not all) of the wxWidget features available via xPerl.

<big><code>C:\> cpanm --verbose Wx::Demo</code></big>

.. then once installed, run it with this command (which is available in the PATH already),

<big><code>C:\> wxperl_demo.pl</code></big>

== wxGlade - a Perl Friendly Cross-Platform GUI Builder ==

=== Trigger Warning: wxGlade is written in wxPython, so you must install it if you want to use wxGlade to build your GUI. ===
Totally worth it!

=== Install wxGlade ===
[https://sourceforge.net/projects/wxglade/ wxGlade] is a GUI builder for wxWidgets applications. It is written in Python, but critically supports outputting Perl code. It is actively developed, and the developer is very responsive on Github to bugs and feature requests. It is the closest thing we have in Perl to a rapid application development environment, in the spirit of [https://www.lazarus-ide.org/ Lazarus] for Free Pascal.

Developers interested in earlier wxWidgets GUI builders and older Perl-capable tools can also see the [[Developing and Distributing wxPerl Applications on Windows#Longer List of RAD Tools and GUI Builders|longer list of RAD tools and GUI builders]] near the end of this page, including some useful but discontinued, archived, or historically important projects.
=== Step 1 - Install Python 3.10.11 for Windows ===
Install via following link,

https://www.python.org/ftp/python/3.10.11/python-3.10.11-amd64.exe ([https://www.python.org/downloads/windows/ linked here])

'''Notes''':

# Last tested on '''25 Jan 2025''', although later versions of Python 3 were tested (specifically, 3.12.8), wxPython would install but not run wxGlade properly
# install as admin (checkbox should be already checked; also opt'd to add "python" to the PATH)

=== Step 2 - Install wxPython ===

# open up the Windows CMD window
# use pip,

<big><code>C:\> pip install wxPython</code></big>

'''Note''': if this fails, you may need to reinstall pip; but it should be available in the CMD window. Based on experience, pip doesn't seem to be available via the Strawberry Perl terminal, so be sure to get a standard Windows CMD window to do this part.

=== Step 3 - Download and unzip wxGlade ===
You should probably check if there is a [https://github.com/wxGlade/wxGlade/releases '''new release'''], but to get the latest at the time of this update, download: https://github.com/wxGlade/wxGlade/archive/refs/tags/v1.1.1.zip (may want to also try [https://downloads.sourceforge.net/project/wxglade/wxglade/1.1.0/wxGlade-1.1.0_win_amd64.zip?ts=gAAAAABnlJMXBQlBk2CGz7kaN89RrjqS4GEmSk7spuPtf-gFaK_VqcAQAiFCT24GT-SYsq8SVVmCjmhkzq0VycLd7ofhOQoVlA%3D%3D&r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fwxglade%2Ffiles%2Fwxglade%2F1.1.0%2FwxGlade-1.1.0_win_amd64.zip%2Fdownload%3Fuse_mirror%3Dphoenixnap%26use_mirror%3Dphoenixnap%26r%3Dhttps%253A%252F%252Fsourceforge.net%252Fprojects%252Fwxglade%252Ffiles%252Fwxglade%252F1.1.0%252F wxGlade-1.1.0_win_amd64.zip] - the difference between the two is unclear, but both are tested and both work.)
[[File:WxgladeWinExample.png|alt=wxGlade running on Windows, showing the design window of a GUI about to be run using wxPerl!|thumb|wxGlade running on Windows, showing the design window of a GUI about to be run using wxPerl!]]
Via Windows CMD terminal, navigate to the unzipped directory and run the command,

<big><code>C:\> python wxglade.py</code></big>

=== Getting wxGlade Help ===
''wxGlade''<nowiki/>'s developer is responsive on Github and there is a semi-active email list on SourceForge,

* Github repo - https://github.com/wxGlade/wxGlade
* email list - https://sourceforge.net/p/wxglade/mailman/wxglade-general/

== Development Workflow Notes ==
This section outlines some different workflows that are found among members of the community who use wxPerl. Like any workflow, the based on level of experience and particular application.
[[File:Wxperl-workflow.png|alt=Example layout with Strawberry Perl for running the application and Makefile, vim under MSYS2 for more streamlined workflow. wxGlade is under there, too; when there is a change to the GUI, the project is saved and code generated using "ctrl-g". vim is used to edit the code and will update whenever wxGlade updates it, if you do it right your custom code won't get clobbered.|thumb|Example layout with Strawberry Perl for running the application and Makefile, vim under MSYS2 for more streamlined workflow. wxGlade is under there, too; when there is a change to the GUI, the project is saved and code generated using "ctrl-g". vim is used to edit the code and will update whenever wxGlade updates it, if you do it right your custom code won't get clobbered.]]

=== Editor and <code>git</code> Options on Windows ===
The best way to recreate the "edit-run-fix" workflow of code editing enjoyed by vim users is to install [https://www.msys2.org/ MSYS2] and use its terminal to install both <code>vim</code> and <code>git</code>:

<big><code>pacman -S vim git</code></big>

Note: you do not want to run the Perl code generated by wxGlade inside of the MSYS2 terminal. When you install <code>git</code>, it will install its own perl and clobber Strawberry Perl in your <code>PATH</code>. Run the Perl code for your project from a Strawberry Perl terminal.

Just like the editor options in Windows is not ideal, neither are the Git options (GH's "Git for Windows" is exceptionally awkward to use, not sure how to it is possible to be good in "Windows" tbh; YMMV.) Under MSYS2's terminal, you may install <code>git</code> and use it as you may be accustomed on Linux. You may want to generate an ssh-key, which will be vailable in `~/.ssh/` by default. So you can do all the normal git workflow stuff from there once your key is created and added to your Github keyset.

==== Pro Tip: Turn Off MSYS2's <code>vim</code> Mouse Support and Auto/Smart Indenting ====
I have found that this is required to "copy" text from the MSYS2 <code>vim</code>, you may not need it. But by default <code>vim</code> is aware of the mouse.

To turn all that off, put the following lines in your <code>~/.vimrc</code> file:

<pre>
set mouse=
set noautoindent
set nosmartindent
set nocindent
</pre>
=== Using wxGlade's "Single file" + "''Keep user code''" Options ===
wxGlade has some settings that tells it to not overwrite changes you made in the output Perl script, but '''beware''' - this option is not on by default. That means that means that your file will get overwritten if you tell wxGlade to generate new code again. The general workflow is as follows:

# start a new project (or open an existing one)
# click on the root "Application" object in the object viewer
# find the output pane, set the output to be "'''Perl'''"
# set version of wxWidgets to be "'''3.0'''"
# [[File:Applicationsettings.png|alt=Recommended settings for using wxGlade for Perl development.|thumb|Recommended settings for using wxGlade for Perl development.]]check "Keep user code", this will make sure wxGlade doesn't overwrite code that is outside the bounds of very clearly marked blocks in the code

=== Using wxGlade's "''Separate file for each class''" Option ===
... to do

== Creating Windows EXEs ==
This section is more of a work in progress since a reliable method of distributing single file executables (or developing installation packages for Windows) is still an open question, there is hope that this will end up being a relatively smooth process. Needless to say, it is critical for Perl developer to be able to distribute Perl based GUI applications as single file (.exe) or via installation on Windows. The client should NOT need to be running through any of the instructions above to run a program that you would like to sell them for actual money.

Below are the initial instructions for generating an EXE file. There are also many ways that wxPerl developers go about doing, based on their use case and experience.

=== PAR::Package, App::PP::Autolink, and Wx::Perl::Packager ===

==== Step 1 - Install PAR::Package, App::PP::Autolink, and Wx::Perl::Packager ====
<big><code>C:\> cpanm --verbose PAR::Package App::PP::Autolink Wx::Perl::Packager</code></big>

'''Note''': <code>pp_autolink</code>, provided by <code>App::PP::Autolink</code>, has proven to be absolutely critical to finding the required DLLs that need to be added manually to the <code>wxpar</code> command below via the <code>--link</code> flag.

==== Step 2 - Generate the EXE ====
Assuming you have a Perl script generated either via wxGlade (see above) or one you have created/updated by hand, the command is as follows:

<big><code>C:\> wxpar YOURPROGRAM.pl -o YOURPROGRAM.exe</code></big>

===== Important Notes About wxGlade Generated Code =====
# Earlier versions of wxGlade introduced an improper idiom at the bottom of the generated Perl script that caused a problem when running via a PAR::Packed executable. TLDR: remove the "unless(caller)" block and just run the Wx event loop unfettered. For more information, please read the [https://metacpan.org/dist/PAR/view/lib/PAR/FAQ.pod#If-I-try-to-compile-my-wxGlade-generated-script%2C-it-doesn%27t-run.-What%27s-wrong%3F PAR::FAQ.]
# Earlier versions of wxGlade also used a non-Exporter import tag that wxpar could not properly follow; see the code "before" and "after" below:

<pre>
use Wx qw[:allclasses];
use strict;

...

package main;

unless(caller){
my $local = Wx::Locale->new("English", "en", "en"); # replace with ??
$local->AddCatalog("app"); # replace with the appropriate catalog name

my $app = MyApp->new();
$app->MainLoop();
}
</pre>

Should be modified to look like the following:

<pre>
use Wx;
use strict;

...

package main;

my $local = Wx::Locale->new("English", "en", "en"); # replace with ??
$local->AddCatalog("app"); # replace with the appropriate catalog name

my $app = MyApp->new();
$app->MainLoop();
</pre>

See [https://github.com/wxGlade/wxGlade/issues/568 this Github issue] for wxGlade, where both were fixed. At the time of this writing, the changes have not been put out in an official release; but they are applied in the master branch.

==== Special Cases ====

===== <code>Makefile</code> for an Application uses HTTP::Tiny and calls out to SSL-enabled sites =====
Example - [https://github.com/StormSurgeLive/nhc-advisory-gui/blob/master/asgs-storm-bug.pl https://github.com/StormSurgeLive/nhc-advisory-gui/]

(copied from the [https://github.com/StormSurgeLive/nhc-advisory-gui/blob/master/Makefile Makefile]) - Note, mentions using [https://metacpan.org/pod/App::PP::Autolink App::PP::Autolink] to suss out required DLLs (provides <code>pp_autolink</code>, which helped!)

<pre>
all:
wxpar --verbose -o ./dist/nhc-explorer.exe -l c:/strawberry/c/bin/libcrypto-3-x64__.dll -l c:/strawberry/c/bin/zlib1__.dll -l c:/strawberry/c/bin/libssl-3-x64__.dll ./asgs-storm-bug.pl --gui
wxpar --verbose -o ./dist/DEBUG-nhc-explorer.exe -l c:/strawberry/c/bin/libcrypto-3-x64__.dll -l c:/strawberry/c/bin/zlib1__.dll -l c:/strawberry/c/bin/libssl-3-x64__.dll ./asgs-storm-bug.pl

# It was an adventure finding all the dependencies related to the wxpar command,
# particularly those around what was needed. The basic process entailed:
# 1. use wxpar, which generates an options file with all the Wx DLLs
# 2. install App::PP::Autolink, which provides the utility "pp_autolink"; this
# utility scans the .pl file you're packing, in this case, "asgs-storm-bug.pl",
# for DLLs - lo' and behold, it found the ones I needed; in particular the critical
# one that was not getting picked up by pp or wxpar, "libcrypto-3-x64___.dll!"
# 3. run the "wxpar" command above
# 4. test in a non-Strawberry Perl window, such as the MSYS2 terminal, using the command:
#
# PERL_DL_DEBUG=5 dist/nhc-explorer.exe
#
# I learned about this command while searching, here:
#
# https://stackoverflow.com/questions/423330/why-cant-dynaloader-pm-load-ssleay-dll-for-netssleay-and-cryptssleay
</pre>
==== Important Note About Finding all DLLs ====
It is worth repeating that <code>pp_autolink</code>, provided by <code>App::PP::Autolink</code> has proven to be absolutely ''critical'' to finding the required DLLs that need to be added manually to the <code>wxpar</code> command below via the <code>--link</code> flag.

If you are having problems finding all the DLLs (some which may not be obvious until the EXE generated is tried on a different machine,) you need to give <code>pp_autolink</code> a shot.

=== Martha - ''A lightweight wxPerl helper for packaging Perl applications on Windows'' ===
In February 2026, an exciting new project was launched to help Perl programmers bootstrap creating Windows executables and program installers. Martha, formerly referred to here as wxPerl Helper, is designed to work within the development environment described herein (Strawberry Perl, Alien::wxWidgets, wxPerl, wxGlade). Given this environment, the current "beta" version of the software can assist with the following:

* automatically finds required DLLs
* generates Makefile, based on using wxpar (a pp wrapper)
* user can tweak and save the Makefile
* user can load an existing Makefile
* user can run the Makefile to create the executable
* user can run the executable
* user can configure an Inno Setup provided it is installed
* run the Inno Setup file to generate an installer for their program
* finally, they may test the installer directly from the GUI

Martha is targeting the gap that exists for a user that is able to generate Perl code from wxGlade, but then is unsure how to actually distribute their application in the way Windows users expect.

For more information and updates on the project, visit the Github repo [https://github.com/The-Perl-Cottage-Guild/wxPerl-Helper here].

=== Background: Perl, wxWidgets, and RAD on Windows ===

For historical context on earlier Perl/wxWidgets GUI builders, RAD tools, and discontinued Windows application-building efforts, see [[Perl and wxWidgets RAD on Windows]].

== Creating Installers for Windows EXEs ==
Professional Windows programs are expected to provide installers. This section will be developed as I figure out how to do this. A few notes:

* Strawberry Perl itself uses '''[https://wixtoolset.org/ WiX Toolset]''' (Windows Installer XML Toolset) to generate its MSI installer (see [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/blob/master/share/msi/MSI_main-v2.wxs.tt here])
* '''[https://nsis.sourceforge.io/Main_Page NSIS]''' (Nullsoft Scriptable Install System) is another option - ([https://nsis.sourceforge.io/Category:Tutorials tutorials], [https://nsis.sourceforge.io/Category:Code_Examples examples], [https://nsis.sourceforge.io/Screenshots screenshots]) - it also has its own IDE for visually designing installers! [https://nsis.sourceforge.io/NSIS_Dialog_Designer See more here].
* A possible "old school" approach, may be to use Office'97 Office Developer Edition (ODE) - via Access'97 there is an installer builder - this is a last resort and still needs to be verified to work for non-Access distributions
* [https://jrsoftware.org/isinfo.php Inno Setup] ([https://github.com/jrsoftware/issrc github]) - ''Inno Setup is a free installer for Windows programs by Jordan Russell and Martijn Laan. First introduced in 1997, Inno Setup today rivals and even surpasses many commercial installers in feature set and stability.''
* [https://www.revenera.com/install/products/installshield InstallShield] (commercial - software monetization services)

=== Using Inno Setup ===
This section briefly describes using [https://jrsoftware.org/isinfo.php Inno Setup] to build an installed for a Windows executable. It seems to be pretty easy to use and has support for many more things than most Perl programmers may actually need. One important thing to note is that it is free for non-commercial use, there is a [https://jrsoftware.org/isorder.php commercial license] required by the author for using this to distribute commercial programs. The license is one-time and entitles the end-user to 2 years of updates. After that, they may continue to use it but will not receive the updates. For all intents and purposes it is a one-time fee, and may considered worth it for some software authors.

Using Inno Setup consists of creating a configuration file, then using the Inno Setup Compiler's GUI to open up an ".iss" file, then run it interactively. It may also be run on the command line or as part of a Makefile.

[https://github.com/StormSurgeLive/nhc-advisory-gui/blob/master/installer/nhc-explorer.iss Click here] to see an example configuration file used by the NHC Advisory GUI.

[https://github.com/The-Perl-Cottage-Guild/wxPerl-Helper Support] for creating configurations and installers with Inno Setup is also being included in [https://github.com/The-Perl-Cottage-Guild/wxPerl-Helper Martha], the wxPerl helper application being created as part of this Perl Guilds effort to make it easier for traditional Perl programmers to break into the world of commercial Windows GUI programs.
== Underdeveloped Sections ==
The following sections are "works in progress," and remain open questions (for this author anyway). Contributions to develop these sections are greatly appreciated, but not expected. Over time I will update these sections as I learn more about using wxGlade and Perl on Windows.

=== Distributing EXEs to other Windows Machines ===
While wxpar does indeed create EXEs that can run on Windows machines that do not otherwise have any required libraries on them, I have found some early problems that are most likely due to lack of experience in this area. An understanding of this area is forthcoming.

=== Maintaining Perl Applications using XRC ===
[https://docs.wxwidgets.org/latest/overview_xrc.html XRC] is a language agnostic and XML based way of describing the GUI layout for wxWidgets. It appears to be the right way to maintain the GUI layout of your production grade program, while maintaining the set of Perl handlers in your own source tree. Think of XRC as the separation of the controller and view in MVC - it to GUI programming what templates are to web application programming. It seems that as one advances his skills in this area, he will want to use XRC. The benefit also of this is that one may be able to create controllers in multiple languages rather than tie the GUI construction in Perl or some other language exclusive - of course, wxGlade can output in different languages, but none is as abstract as XRC.
[[File:Xrc.png|alt=Wx::Demo example of loading an XRC file; wxGlade can output directly to XRC, which can then be read in Perl. This is how.|thumb|Wx::Demo example of loading an XRC file; wxGlade can output directly to XRC, which can then be read in Perl. [https://metacpan.org/release/MDOOTSON/Wx-Demo-0.22/source/lib/Wx/DemoModules/wxXrc.pm This] is how.]]
Wx::Demo has a few [https://metacpan.org/release/MDOOTSON/Wx-Demo-0.22/source/lib/Wx/DemoModules/wxXrc.pm good examples] of running XRC applications; wxGlade can output XRC, but it is not aware of any language bindings or drivers for it.

Experience with managing XRC files may allow us as Perl programmers to use RAD tools and GUI builders that were not intended to support wxPerl, but can output XRC files. [http://www.anthemion.co.uk/dialogblocks/download.htm DialogBlocks] is such a professional and commercial GUI builder for wxWidgets, and it is actively maintained.

=== Frequently Asked Questions ===
Nobody actually contacts me to ask these questions, but they seem to be important.

==== Q: Can these wxPerl applications using Strawberry Perl make ''https'' requests? ====
A: Yes! Strawberry Perl comes with HTTP::Tiny (a core Perl module) and Net::SSLeay (used by HTTP::Tiny for https requests).

== Additional Resources ==

=== Printed Books ===
[[File:Wxbook.jpg|alt=This great, but out of print wxWidgets book is available for free (PDF) at https://wxwidgets.org/docs/book/. It mentions wxPerl and has an index of tools and programs that any wxWidgets programmer may find interest.|thumb|This great, but out of print wxWidgets book is available for free (PDF) at https://wxwidgets.org/docs/book/. It mentions wxPerl and has an index of tools and programs that any wxWidgets programmer may find interest.]]
'''Cross-Platform GUI Programming with wxWidgets''' ([https://wxwidgets.org/docs/book/ free PDF!!]) by Julian Smart and Kevin Hock (with Stefan Csomor) is an old, but nice resource to have. It mentions wxPerl quite a bit and has a nice index of tools to help the wxWidgets GUI programmer, regardless of the language they are using. In particular, "Appendix E: Third-Party Tools for wxWidgets" is a very interesting read.

=== Longer List of RAD Tools and GUI Builders* ===

* [[Developing and Distributing wxPerl Applications on Windows#wxGlade - a Perl Friendly Cross-Platform GUI Builder|wxGlade]] (''Latest at this time'', '''Version 1.1.0, July 7, 2024''')
* [https://web.archive.org/web/20131020024033/http://www.wxdesigner-software.de/download.html wxDesigner] (''Latest at this time'', '''2.14 - wxWidgets 2.8.8/ 2.20a - wxWidgets pre-3.0, May 2009''')
** outputs Perl code
** archived but a trial is downloadable [https://web.archive.org/web/20131020024033/http://www.wxdesigner-software.de/download.html here] (archive.org)
** Reliable contact for license: ''undetermined at this time''
* [http://www.anthemion.co.uk/dialogblocks/download.htm DialogBlocks] - '''('''''Latest at this time'', '''Version 5.18, August 21st, 2024)'''
** can export C++, XRC, which wxGlade should be able to import
** No Perl export (see XRC)
** Cross Platform (Windows, Mac, Linux)
** Registration required, but support is discontinued - email support@anthemion.co.uk, they may just give you a free key if you are nice :-)

''*You may want to also check this duplicated internal [[Portal:Software Development Tools#wxPerl (wxWidgets wrapper)|page]].''

Developing and Distributing wxPerl Applications on Windows

2025-08-05T15:25:06Z

104.181.193.235: /* wxGlade - a Perl Friendly(cross-platform) GUI Builder */

== Update Notes - 3/10/2025! ==
Updates to the information on wxPerl on Strawberry Perl 5.40.0.1 + PDL 2.089.

Also added not on importance of using pp_autolink to find the DLLs for use with wxpar.

== Introduction ==
This article is about installing wxPerl under Strawberry Perl for application development and distribution as a Windows executable.

=== Why Perl GUIs, why Windows? ===
This is a critical ability for any freelance Perl developer, since it compliments a Perl journeyman's ability to do many things on servers, such as create remote services. Being able to transfer these skills to the desktop environment, particularly one that is full of users who are okay with paying for software (i.e., Windows). In short, Perl programmers who want to make a living on their own need to know how to create and distribute Windows GUI applications; this page covers a large piece of how to do that.
[[File:FreeAPIGUI.png|alt=wxPerl GUI running on Windows as a double-clicable EXE file!|thumb|wxPerl GUI running on Windows as a double-clicable EXE file! Created using RAD-ish tool, wxGlade. See [https://github.com/oodler577/FreeAPI-Perl-API-Explorer more images] on Github.]]
Instructions are provided with the versions detailed below. If there are newer versions of any of the modules, you may try it out (of course); but understand they have not been tried out and shown to work like version combinations below.

=== [https://dev.to/sciurius/wxperl-revival-5fde See] the original call for a [https://dev.to/sciurius/wxperl-revival-5fde wxPerl Revivial]! ===

== Installation ==

=== Step 1 - Install Strawberry Perl (5.40.0.1) ===
Install via following link,

<big>https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/download/SP_54001_64bit_UCRT/strawberry-perl-5.40.0.1-64bit.msi</big>

==== Installing Strawberry Perl (5.40.0.1) + PDL (2.089) ====
Note: there might be interest in providing a Windows wxPerl environment that includes the Perl Data Language. See [[Portal:SciTech|notes on creating a Perl environment using Strawberry Perl that includes PDL]]. Once this is set up, the rest of the instructions starting with Step 2 below all work the same!

=== Step 2 - Install Alien::wxWidgets (v 0.70) ===
Once Perl is installed, look in the Start menu for the Perl "cmd" window or open up PowerShell

* go to "'''Start menu'''" > ''Strawberry Perl'' > "'''Perl (command line)'''"
* click the Start menu item, it'll open up a Windows CMD window (traditional black DOS prompt)

Type the command at the "C:" prompt,

<code><big>C:\> cpanm --verbose <nowiki>https://github.com/sciurius/wxPerl/releases/download/R3.004/Alien-wxWidgets-0.70.tar.gz</nowiki></big></code>

=== Step 3 - Install Wx (v 3.005) ===
<big><code>C:\> cpanm --verbose <nowiki>https://github.com/sciurius/wxPerl/releases/download/R3.005/Wx-3.005.tar.gz</nowiki></code></big>

== Verify Installation ==

=== Install Wx::Demo ===
Wx::Demo is nice demonstration application, highlight many (if not all) of the wxWidget features available via xPerl.

<big><code>C:\> cpanm --verbose Wx::Demo</code></big>

.. then once installed, run it with this command (which is available in the PATH already),

<big><code>C:\> wxperl_demo.pl</code></big>

== wxGlade - a Perl Friendly (cross-platform) GUI Builder ==

=== Trigger Warning: wxGlade is written in wxPython, so you must install it if you want ot use wxGlade to build your GUI. ===
Totally worth it!

=== Install wxGlade ===
[https://sourceforge.net/projects/wxglade/ wxGlade] is a GUI builder for wxWidgets applications. It is written in Python, but critically supports outputing Perl code. It is actively developed, the developer is very responsive on Github to bugs and feature requests. It is the closest thing we have in Perl to a RAD (rapid application development) environment (e.g., [https://www.lazarus-ide.org/ Lazarus] for FreePascal).

=== Step 1 - Install Python 3.12 for Windows ===
Install via following link,

https://www.python.org/ftp/python/3.10.11/python-3.10.11-amd64.exe ([https://www.python.org/downloads/windows/ linked here])

'''Notes''':

# Last tested on '''25 Jan 2025''', although later versions of Python 3 were tested (specifically, 3.12.8), wxPython would install but not run wxGlade properly
# install as admin (checkbox should be already checked; also opt'd to add "python" to the PATH)

=== Step 2 - Install wxPython ===

# open up the Windows CMD window
# use pip,

<big><code>C:\> pip install wxPython</code></big>

'''Note''': if this fails, you may need to reinstall pip; but it should be available in the CMD window. Based on experience, pip doesn't seem to be available via the Strawberry Perl terminal, so be sure to get a standard Windows CMD window to do this part.

=== Step 3- Download and unzip wxGlade ===
https://github.com/wxGlade/wxGlade/archive/refs/tags/v1.1.0.zip (may want to also try [https://downloads.sourceforge.net/project/wxglade/wxglade/1.1.0/wxGlade-1.1.0_win_amd64.zip?ts=gAAAAABnlJMXBQlBk2CGz7kaN89RrjqS4GEmSk7spuPtf-gFaK_VqcAQAiFCT24GT-SYsq8SVVmCjmhkzq0VycLd7ofhOQoVlA%3D%3D&r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fwxglade%2Ffiles%2Fwxglade%2F1.1.0%2FwxGlade-1.1.0_win_amd64.zip%2Fdownload%3Fuse_mirror%3Dphoenixnap%26use_mirror%3Dphoenixnap%26r%3Dhttps%253A%252F%252Fsourceforge.net%252Fprojects%252Fwxglade%252Ffiles%252Fwxglade%252F1.1.0%252F wxGlade-1.1.0_win_amd64.zip] - the difference between the two is unclear, but both are tested and both work.)
[[File:WxgladeWinExample.png|alt=wxGlade running on Windows, showing the design window of a GUI about to be run using wxPerl!|thumb|wxGlade running on Windows, showing the design window of a GUI about to be run using wxPerl!]]
Via Windows CMD terminal, navigate to the unzip'd directory and run the command,

<big><code>C:\> python wxglade.py</code></big>

=== Getting wxGlade Help ===
''wxGlade''<nowiki/>'s developer is responsive on Github and there is a semi-active email list on SourceForge,

* Github repo - https://github.com/wxGlade/wxGlade
* email list - https://sourceforge.net/p/wxglade/mailman/wxglade-general/

== Development Workflow Notes ==
This section outlines some different workflows that are found among members of the community who use wxPerl. Like any workflow, the based on level of experience and particular application.
[[File:Wxperl-workflow.png|alt=Example layout with Strawberry Perl for running the application and Makefile, vim under MSYS2 for more streamlined workflow. wxGlade is under there, too; when there is a change to the GUI, the project is saved and code generated using "ctrl-g". vim is used to edit the code and will update whenever wxGlade updates it, if you do it right your custom code won't get clobbered.|thumb|Example layout with Strawberry Perl for running the application and Makefile, vim under MSYS2 for more streamlined workflow. wxGlade is under there, too; when there is a change to the GUI, the project is saved and code generated using "ctrl-g". vim is used to edit the code and will update whenever wxGlade updates it, if you do it right your custom code won't get clobbered.]]

=== Editor and <code>git</code> Options on Windows ===
The best way to recreate the "edit-run-fix" workflow of code editing enjoyed by vim users is to install [https://www.msys2.org/ MSYS2] and use its terminal to install both <code>vim</code> and <code>git</code>:

<code><big>pacman -S vim git</big></code>

Note: you do not want to run the Perl code generated by wxGlade inside of the MSYS2 terminal. When you install <code>git</code>, it will install its own perl and clobber Strawberry Perl in your <code>PATH</code>. Run the Perl code for your project from a Strawberry Perl terminal.

Just like the editor options in Windows is not ideal, neither are the Git options (GH's "Git for Windows" is exceptionally awkward to use, not sure how to it is possible to be good in "Windows" tbh; YMMV.) Under MSYS2's terminal, you may install <code>git</code> and use it as you may be accustomed on Linux. You may want to generate an ssh-key, which will be vailable in `~/.ssh/` by default. So you can do all the normal git workflow stuff from there once your key is created and added to your Github keyset.

==== Pro Tip: Turn Off MSYS2's <code>vim</code> Mouse Support and Auto/Smart Indenting ====
I have found that this is required to "copy" text from the MSYS2 <code>vim</code>, you may not need it. But by default <code>vim</code> is aware of the mouse.

To turn all that off, put the following lines in your <code>~/.vimrc</code> file:

set mouse=
set noautoindent
set nosmartindent
set nocindent

=== Using wxGlade's "Single file" + "''Keep use code''" Options ===
wxGlade has some settings that tells it to not overwrite changes you made in the output Perl script, but '''beware''' - this option is not on by default. That means that means that your file will get overwritten if you tell wxGlade to generated new code again. The general workflow is as follows:

# start a new project (or open an existing one)
# click on the root "Application" object in the object viewer
# find the output pane, set the output to be "'''Perl'''"
# set version of wxWidgets to be "'''3.0'''"
# [[File:Applicationsettings.png|alt=Recommended settings for using wxGlade for Perl development.|thumb|Recommended settings for using wxGlade for Perl development.]]check "Keep user code", this will make sure wxGlade doesn't over write code that is outside the bounds of very clearly marked blocks in the code

=== Using wxGlade's "''Seperate file for each class''" Option ===
... to do

== Creating Windows EXEs ==
This section is more of a work in progress since a reliable method of distributing single file executables (or developing installation packages for Windows) is still an open question, there is hope that this will end up being a relatively smooth process. Needless to say, it is critical for Perl developer to be able to distribute Perl based GUI applications as single file (.exe) or via installation on Windows. The client should NOT need to be running through any of the instructions above to run a program that you would like to sell them for actual money.

Below are the initial instructions for generating an EXE file. There are also many ways that wxPerl developers go about doing, based on their use case and experience.

=== PAR::Package, App::PP::Autolink, and WX::Perl::Packager ===

==== Step 1 - Install PAR::Package, App::PP::Autolink, and Wx::Perl::Packager ====
<code><big>C:\> cpanm --verbose PAR::Package App::PP::Autolink Wx::Perl::Packager</big></code>

'''Note''': <code>pp_autolink</code>, provided by <code>App::PP::Autolink</code> has proven to be absolutely critical to finding the required DLLs that need to be added manually to the <code>wxpar</code> command below via the <code>--link</code> flag.

==== Step 2 - Generate the EXE ====
Assuming you have a Perl script generated either via wxGlade (see above) or one you have created/updated by hand, the command is as follows:

<code><big>C:\> wxpar YOURPROGRAM.pl -o YOURPROGRAM.exe</big></code>

===== Important Notes About wxGlade Generated Code =====
# earlier versions of wxGlade introduced an improper idiom at the bottom of the generated Perl script that caused a problem when running via a PAR::Packed packed executable. TLDR; remove the "unless(caller)" block and just run the Wx event loop unfettered. For more information, please read the [https://metacpan.org/dist/PAR/view/lib/PAR/FAQ.pod#If-I-try-to-compile-my-wxGlade-generated-script%2C-it-doesn%27t-run.-What%27s-wrong%3F PAR::FAQ.]
# earlier versions of wxGlade also used a non-Exporter import tage that wxpar could not properly follow; see the code "before" and "after" below:

use Wx qw[:allclasses];
use strict;

...

package main;

unless(caller){
my $local = Wx::Locale->new("English", "en", "en"); # replace with ??
$local->AddCatalog("app"); # replace with the appropriate catalog name

my $app = MyApp->new();
$app->MainLoop();
}
Should be modified to look like the following:
use Wx;
use strict;

...

package main;

my $local = Wx::Locale->new("English", "en", "en"); # replace with ??
$local->AddCatalog("app"); # replace with the appropriate catalog name

my $app = MyApp->new();
$app->MainLoop();
See [https://github.com/wxGlade/wxGlade/issues/568 this Github issue] for wxGlade, where both were fixed. At the time of this writing, the changes. have not been put out in an official release; but they are applied in the master branch.

==== Special Cases ====

===== <code>Makefile</code> for an Application uses HTTP::Tiny and calls out to SSL-enabled sites =====
Example - [https://github.com/StormSurgeLive/nhc-advisory-gui/blob/master/asgs-storm-bug.pl https://github.com/StormSurgeLive/nhc-advisory-gui/l]

(copied from the [https://github.com/StormSurgeLive/nhc-advisory-gui/blob/master/Makefile Makefile]) - Note, mentions using [https://metacpan.org/pod/App::PP::Autolink App::PP::Autolink] to sus out required DLLs (provides <code>pp_autolink</code>, which helped!)

all:
wxpar --verbose -o ./dist/nhc-explorer.exe -l c:/strawberry/c/bin/libcrypto-3-x64__.dll -l c:/strawberry/c/bin/zlib1__.dll -l c:/strawberry/c/bin/libssl-3-x64__.dll ./asgs-storm-bug.pl --gui
wxpar --verbose -o ./dist/DEBUG-nhc-explorer.exe -l c:/strawberry/c/bin/libcrypto-3-x64__.dll -l c:/strawberry/c/bin/zlib1__.dll -l c:/strawberry/c/bin/libssl-3-x64__.dll ./asgs-storm-bug.pl

# It was an adventure finding all the dependencies related to the wxpar command,
# particularly those around what was needed, the basic process entailed:
# 1. use wxpar, which generates an options files with all the Wx DLLs
# 2. installed, App::PP::Autolink, which provides the utility "pp_autolink"; this
# utility scans the .pl file you're packing (in this case, "asgs-storm-bug.pl,")
# for DLLs - lo' and behold, it found the ones I needed; in particular the critical
# one that was not getting picked up by pp or wxpar, "libcrypto-3-x64___.dll!"
# 3. ran the "wxpar" command above
# 4. tested in a non-Strawberry Perl window (MSYS2 terminal) using the command,
#
# PERL_DL_DEBUG=5 dist/nhc-explorer.exe
#
# I learned about this command while searching, here:
#
# https://stackoverflow.com/questions/423330/why-cant-dynaloader-pm-load-ssleay-dll-for-netssleay-and-cryptssleay
#

==== Important Note About Finding all DLLs ====
It is worth repeating that <code>pp_autolink</code>, provided by <code>App::PP::Autolink</code> has proven to be absolutely ''critical'' to finding the required DLLs that need to be added manually to the <code>wxpar</code> command below via the <code>--link</code> flag.

If you are having problems finding all the DLLs (some which may not be obvious until the EXE generated is tried on a different machine,) you need to give <code>pp_autolink</code> a shot.

=== PPL (portable Perl loader) ===
... to fill in (Johan?)

== Creating Installers for Windows EXEs ==
Professional Windows programs are expected to provide installers. This section will be developed as I figure out how to do this. A few notes:

* Strawberry Perl itself uses '''[https://wixtoolset.org/ WiX Toolset]''' (Windows Installer XML Toolset) to generate its MSI installer (see [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/blob/master/share/msi/MSI_main-v2.wxs.tt here])
* '''[https://nsis.sourceforge.io/Main_Page NSIS]''' (Nullsoft Scriptable Install System) is another option - ([https://nsis.sourceforge.io/Category:Tutorials tutorials], [https://nsis.sourceforge.io/Category:Code_Examples examples], [https://nsis.sourceforge.io/Screenshots screenshots]) - it also has its own IDE for visually designing installers! [https://nsis.sourceforge.io/NSIS_Dialog_Designer See more here].
* A possible "old school" approach, may be to use Office'97 Office Developer Edition (ODE) - via Access'97 there is an installer builder - this is a last resort and still needs to be verified to work for non-Access distributions
* [https://jrsoftware.org/isinfo.php Inno Setup] ([https://github.com/jrsoftware/issrc github]) - ''Inno Setup is a free installer for Windows programs by Jordan Russell and Martijn Laan. First introduced in 1997, Inno Setup today rivals and even surpasses many commercial installers in feature set and stability.''
* [https://www.revenera.com/install/products/installshield InstallShield] (commercial - software monetization services)

== Underdeveloped Sections ==
The following sections are "works in progress," and remain open questions (for this author anyway). Contributions to develop these sections are greatly appreciated, but not expected. Over time I will update these sections as I learn more about using wxGlade and Perl on Windows.

=== Distributing EXEs to other Windows Machines ===
While wxpar does indeed create EXEs that can run on Windows machines that do not otherwise have any required libraries on them, I have found some early problems that are most likely due to lack of experience in this area. An understanding of this area is forthcoming.

=== Maintaining Perl Applications using XRC ===
[https://docs.wxwidgets.org/latest/overview_xrc.html XRC] is a language agnostic and XML based way of describing the GUI layout for wxWidgets. It appears to be the right way to maintain the GUI layout of your production grade program, while maintaining the set of Perl handlers in your own source tree. Think of XRC as the separation of the controller and view in MVC - it to GUI programming what templates are to web application programming. It seems that as one advances his skills in this area, he will want to use XRC. The benefit also of this is that one may be able to create controllers in multiple languages rather than tie the GUI construction in Perl or some other language exclusive - of course, wxGlade can output in different languages, but none is as abstract as XRC.
[[File:Xrc.png|alt=Wx::Demo example of loading an XRC file; wxGlade can output directly to XRC, which can then be read in Perl. This is how.|thumb|Wx::Demo example of loading an XRC file; wxGlade can output directly to XRC, which can then be read in Perl. [https://metacpan.org/release/MDOOTSON/Wx-Demo-0.22/source/lib/Wx/DemoModules/wxXrc.pm This] is how.]]
Wx::Demo has a few [https://metacpan.org/release/MDOOTSON/Wx-Demo-0.22/source/lib/Wx/DemoModules/wxXrc.pm good examples] of running XRX applications; wxGlade can output XRC, but it is not aware of any language bindings or drivers for it.

Experience with managing XRC files may allow us as Perl programmers to use RAD tools and GUI builders that were not intended to support wxPerl, but can output XRC files. [http://www.anthemion.co.uk/dialogblocks/download.htm DialogBlocks] is such a professional and commercial GUI builder for wxWidgets, and it is actively maintained.

=== Frequently Asked Questions ===
Nobody actually asks contacts me to ask these questions, but they seem to be important.

==== Q: Can these wxPerl applications using Strawberry Perl make ''https'' requests? ====
A: Yes! Strawberry Perl comes with HTTP::Tiny (a core Perl module) and Net::SSLeay (used by HTTP::Tiny for https requests).

== Additional Resources ==

=== Printed Books ===
[[File:Wxbook.jpg|alt=This great, but out of print wxWidgets book is available for free (PDF) at https://wxwidgets.org/docs/book/. It mentions wxPerl and has an index of tools and programs that any wxWidgets programmer may find interest.|thumb|This great, but out of print wxWidgets book is available for free (PDF) at https://wxwidgets.org/docs/book/. It mentions wxPerl and has an index of tools and programs that any wxWidgets programmer may find interest.]]
'''Cross-Platform GUI programming with wxWidgets''' ([https://wxwidgets.org/docs/book/ free PDF!!]) by Julian Smart and Kevin Hock (with Stefan Csomor) is an old, but nice resource to have. It mentions wxPerl quite a bit and has a nice index of tools to help the wxWidgets GUI programmer, regardless of the language they are using. In particular, "Appendix E: Third-Party Tools for wxWidgets" is a very interesting read.

=== Longer List of RAD Tools and GUI Builders* ===

* [[Developing and Distributing wxPerl Applications on Windows#wxGlade - a Perl Friendly(cross-platform) GUI Builder|wxGlade]] (''Latest at this time'', '''Version 1.1.0, July 7, 2024''')
* [https://web.archive.org/web/20131020024033/http://www.wxdesigner-software.de/download.html wxDesigner] (''Latest at this time'', '''2.14 - wxWidgets 2.8.8/ 2.20a - wxidgets pre-3.0, May 2009''')
** outputs Perl code
** archived but a trial is downloadable [[https://web.archive.org/web/20131020024033/http://www.wxdesigner-software.de/download.html here]] (archive.org)
** Reliable contact for license: ''undetermined at this time''
* [http://www.anthemion.co.uk/dialogblocks/download.htm DialogBlocks] - '''('''''Latest at this time'', '''Version 5.18, August 21st, 2024)'''
** can export C++, XRC, which wxGlade should be able to import
** No Perl export (see XRC)
** Cross Platform (Windows, Mac, Linux)
** Registration required, but support is discontinued - email support@anthemion.co.uk, they may just give you a free key if you are nice :-)

''*You may want to also check this duplicated internal [[Portal:Software Development Tools#wxPerl (wxWidgets wrapper)|page]].''

Developing and Distributing wxPerl Applications on Windows

2025-01-25T20:26:00Z

104.181.193.235:

== Introduction ==
This article is about installing wxPerl under Strawberry Perl for application development and distribution as a Windows executable.

=== Why Perl GUIs, why Windows? ===
This is a critical ability for any freelance Perl developer, since it compliments a Perl journeyman's ability to do many things on servers, such as create remote services. Being able to transfer these skills to the desktop environment, particularly one that is full of users who are okay with paying for software (i.e., Windows). In short, Perl programmers who want to make a living on their own need to know how to create and distribute Windows GUI applications; this page covers a large piece of how to do that.
[[File:FreeAPIGUI.png|alt=wxPerl GUI running on Windows as a double-clicable EXE file!|thumb|wxPerl GUI running on Windows as a double-clicable EXE file! Created using RAD-ish tool, wxGlade. See [https://github.com/oodler577/FreeAPI-Perl-API-Explorer more images] on Github.]]
Instructions are provided with the versions detailed below. If there are newer versions of any of the modules, you may try it out (of course); but understand they have not been tried out and shown to work like version combinations below.

== Installation ==

=== Step 1 - Install Strawberry Perl ===
Install via following link,

<big>https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/download/SP_54001_64bit_UCRT/strawberry-perl-5.40.0.1-64bit.msi</big>

=== Step 2 - Install Alien::wxWidgets (v 0.70) ===
Once Perl is installed, look in the Start menu for the Perl "cmd" window or open up PowerShell

* go to "'''Start menu'''" > ''Strawberry Perl'' > "'''Perl (command line)'''"
* click the Start menu item, it'll open up a Windows CMD window (traditional black DOS prompt)

Type the command at the "C:" prompt,

<code><big>C:\> cpanm --verbose <nowiki>https://github.com/sciurius/wxPerl/releases/download/R3.004/Alien-wxWidgets-0.70.tar.gz</nowiki></big></code>

=== Step 3 - Install Wx (v 3.005) ===
<big><code>C:\> cpanm --verbose <nowiki>https://github.com/sciurius/wxPerl/releases/download/R3.005/Wx-3.005.tar.gz</nowiki></code></big>

== Verify Installation ==

=== Install Wx::Demo ===
Wx::Demo is nice demonstration application, highlight many (if not all) of the wxWidget features available via xPerl.

<big><code>C:\> cpanm --verbose Wx::Demo</code></big>

.. then once installed, run it with this command (which is available in the PATH already),

<big><code>C:\> wxperl_demo.pl</code></big>

=== Install wxGlade ===
[https://sourceforge.net/projects/wxglade/ wxGlade] is a GUI builder for wxWidgets applications. It is written in Python, but critically supports outputing Perl code. It is actively developed, the developer is very responsive on Github to bugs and feature requests. It is the closest thing we have in Perl to a RAD (rapid application development) environment (e.g., [https://www.lazarus-ide.org/ Lazarus] for FreePascal).

=== Step 1 - Install Python 3.12 for Windows ===
Install via following link,

https://www.python.org/ftp/python/3.10.11/python-3.10.11-amd64.exe ([https://www.python.org/downloads/windows/ linked here])

'''Notes''':

# Last tested on '''25 Jan 2025''', although later versions of Python 3 were tested (specifically, 3.12.8), wxPython would install but not run wxGlade properly
# install as admin (checkbox should be already checked; also opt'd to add "python" to the PATH)

=== Step 2 - Install wxPython ===

# open up the Windows CMD window
# use pip,

<big><code>C:\> pip install wxPython</code></big>

'''Note''': if this fails, you may need to reinstall pip; but it should be available in the CMD window. Based on experience, pip doesn't seem to be available via the Strawberry Perl terminal, so be sure to get a standard Windows CMD window to do this part.

=== Step 3- Download and unzip wxGlade ===
https://github.com/wxGlade/wxGlade/archive/refs/tags/v1.1.0.zip (may want to also try [https://downloads.sourceforge.net/project/wxglade/wxglade/1.1.0/wxGlade-1.1.0_win_amd64.zip?ts=gAAAAABnlJMXBQlBk2CGz7kaN89RrjqS4GEmSk7spuPtf-gFaK_VqcAQAiFCT24GT-SYsq8SVVmCjmhkzq0VycLd7ofhOQoVlA%3D%3D&r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fwxglade%2Ffiles%2Fwxglade%2F1.1.0%2FwxGlade-1.1.0_win_amd64.zip%2Fdownload%3Fuse_mirror%3Dphoenixnap%26use_mirror%3Dphoenixnap%26r%3Dhttps%253A%252F%252Fsourceforge.net%252Fprojects%252Fwxglade%252Ffiles%252Fwxglade%252F1.1.0%252F wxGlade-1.1.0_win_amd64.zip] - the difference between the two is unclear, but both are tested and both work.)
[[File:WxgladeWinExample.png|alt=wxGlade running on Windows, showing the design window of a GUI about to be run using wxPerl!|thumb|wxGlade running on Windows, showing the design window of a GUI about to be run using wxPerl!]]
Via Windows CMD terminal, navigate to the unzip'd directory and run the command,

<big><code>C:\> python wxglade.py</code></big>

=== Getting wxGlade Help ===
''wxGlade''<nowiki/>'s developer is responsive on Github and there is a semi-active email list on SourceForge,

* Github repo - https://github.com/wxGlade/wxGlade
* email list - https://sourceforge.net/p/wxglade/mailman/wxglade-general/

== Development Workflow Notes ==
wxGlade has some settings that tells it to not overwrite changes you made in the output Perl script, but '''beware''' - this option is not on by default. That means that means that your file will get overwritten if you tell wxGlade to generated new code again. The general workflow is as follows:

# start a new project (or open an existing one)
# click on the root "Application" object in the object viewer
# find the output pane, set the output to be "'''Perl'''"
# set version of wxWidgets to be "'''3.0'''"
# [[File:Applicationsettings.png|alt=Recommended settings for using wxGlade for Perl development.|thumb|Recommended settings for using wxGlade for Perl development.]]check "Keep user code", this will make sure wxGlade doesn't over write code that is outside the bounds of very clearly marked blocks in the code

== Creating Windows EXEs ==
This section is more of a work in progress since a reliable method of distributing single file executables (or developing installation packages for Windows) is still an open question, there is hope that this will end up being a relatively smooth process. Needless to say, it is critical for Perl developer to be able to distribute Perl based GUI applications as single file (.exe) or via installation on Windows. The client should NOT need to be running through any of the instructions above to run a program that you would like to sell them for actual money.

Below are the initial instructions for generating an EXE file.

=== Step 1 - Install PAR::Package and Wx::Perl::Packager ===
<code><big>C:\> cpanm --verbose PAR::Package Wx::Perl::Packager</big></code>

=== Step 2 - Generate the EXE ===
Assuming you have a Perl script generated either via wxGlade (see above) or one you have created/updated by hand, the command is as follows:

<code><big>C:\> wxpar YOURPROGRAM.pl -o YOURPROGRAM.exe</big></code>

==== Important Notes About wxGlade Generated Code ====

# earlier versions of wxGlade introduced an improper idiom at the bottom of the generated Perl script that caused a problem when running via a PAR::Packed packed executable. TLDR; remove the "unless(caller)" block and just run the Wx event loop unfettered. For more information, please read the [https://metacpan.org/dist/PAR/view/lib/PAR/FAQ.pod#If-I-try-to-compile-my-wxGlade-generated-script%2C-it-doesn%27t-run.-What%27s-wrong%3F PAR::FAQ.]
# earlier versions of wxGlade also used a non-Exporter import tage that wxpar could not properly follow; see the code "before" and "after" below:

use Wx qw[:allclasses];
use strict;

...

package main;

unless(caller){
my $local = Wx::Locale->new("English", "en", "en"); # replace with ??
$local->AddCatalog("app"); # replace with the appropriate catalog name

my $app = MyApp->new();
$app->MainLoop();
}
Should be modified to look like the following:
use Wx qw;
use strict;

...

package main;

my $local = Wx::Locale->new("English", "en", "en"); # replace with ??
$local->AddCatalog("app"); # replace with the appropriate catalog name

my $app = MyApp->new();
$app->MainLoop();
See [https://github.com/wxGlade/wxGlade/issues/568 this Github issue] for wxGlade, where both were fixed. At the time of this writing, the changes. have not been put out in an official release; but they are applied in the master branch.

== Creating Installers for Windows EXEs ==
Professional Windows programs are expected to provide installers. This section will be developed as I figure out how to do this. A few notes:

* Strawberry Perl itself uses '''[https://wixtoolset.org/ WiX Toolset]''' (Windows Installer XML Toolset) to generate its MSI installer (see [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/blob/master/share/msi/MSI_main-v2.wxs.tt here])
* '''[https://nsis.sourceforge.io/Main_Page NSIS]''' (Nullsoft Scriptable Install System) is another option - ([https://nsis.sourceforge.io/Category:Tutorials tutorials], [https://nsis.sourceforge.io/Category:Code_Examples examples], [https://nsis.sourceforge.io/Screenshots screenshots]) - it also has its own IDE for visually designing installers! [https://nsis.sourceforge.io/NSIS_Dialog_Designer See more here].
* A possible "old school" approach, may be to use Office'97 Office Developer Edition (ODE) - via Access'97 there is an installer builder - this is a last resort and still needs to be verified to work for non-Access distributions

== Underdeveloped Sections ==
The following sections are "works in progress," and remain open questions (for this author anyway). Contributions to develop these sections are greatly appreciated, but not expected. Over time I will update these sections as I learn more about using wxGlade and Perl on Windows.

=== Distributing EXEs to other Windows Machines ===
While wxpar does indeed create EXEs that can run on Windows machines that do not otherwise have any required libraries on them, I have found some early problems that are most likely due to lack of experience in this area. An understanding of this area is forthcoming.

=== Maintaining Perl Applications using XRC ===
[https://docs.wxwidgets.org/latest/overview_xrc.html XRC] is a language agnostic and XML based way of describing the GUI layout for wxWidgets. It appears to be the right way to maintain the GUI layout of your production grade program, while maintaining the set of Perl handlers in your own source tree. Think of XRC as the separation of the controller and view in MVC - it to GUI programming what templates are to web application programming. It seems that as one advances his skills in this area, he will want to use XRC. The benefit also of this is that one may be able to create controllers in multiple languages rather than tie the GUI construction in Perl or some other language exclusive - of course, wxGlade can output in different languages, but none is as abstract as XRC.
[[File:Xrc.png|alt=Wx::Demo example of loading an XRC file; wxGlade can output directly to XRC, which can then be read in Perl. This is how.|thumb|Wx::Demo example of loading an XRC file; wxGlade can output directly to XRC, which can then be read in Perl. [https://metacpan.org/release/MDOOTSON/Wx-Demo-0.22/source/lib/Wx/DemoModules/wxXrc.pm This] is how.]]
Wx::Demo has a few [https://metacpan.org/release/MDOOTSON/Wx-Demo-0.22/source/lib/Wx/DemoModules/wxXrc.pm good examples] of running XRX applications; wxGlade can output XRC, but it is not aware of any language bindings or drivers for it.

Experience with managing XRC files may allow us as Perl programmers to use RAD tools and GUI builders that were not intended to support wxPerl, but can output XRC files. [http://www.anthemion.co.uk/dialogblocks/download.htm DialogBlocks] is such a professional and commercial GUI builder for wxWidgets, and it is actively maintained.

=== Frequently Asked Questions ===
Nobody actually asks contacts me to ask these questions, but they seem to be important.

==== Q: Can these wxPerl applications using Strawberry Perl make ''https'' requests? ====
A: Yes! Strawberry Perl comes with HTTP::Tiny (a core Perl module) and Net::SSLeay (used by HTTP::Tiny for https requests).

== Additional Resources ==

=== Printed Books ===
'''Cross-Platform GUI programming with wxWidgets''' ([https://wxwidgets.org/docs/book/ free PDF!!]) by Julian Smart and Kevin Hock (with Stefan Csomor) is an old, but nice resource to have. It mentions wxPerl quite a bit and has a nice index of tools to help the wxWidgets GUI programmer, regardless of the language they are using.

Main Page

2025-01-15T06:07:41Z

104.181.193.235:

__NOTOC__

=== Welcome to the Perl Guilds Wiki ===
The '''Perl Guilds''' wiki is a community-driven resource designed to support '''freelance Perl programmers''' and help them thrive in their independent careers. This space is dedicated to Perl developers who want to enhance their skills, share knowledge, and collaborate with others to build sustainable, successful careers as freelancers in the world of Perl development. As a freelancer, you face unique challenges, but the Perl Guilds wiki offers resources and a supportive community to help you overcome them. Whether you're just starting or are an experienced Perl developer, you'll find valuable information here to help you refine your craft and build a business around your Perl expertise.

The original wiki concept was inspired by [https://wiki.freepascal.org FreePascal]'s community wiki. This wiki is maintained by myself, Brett Estrade ([https://metacpan.org/author/OODLER OODLER]) <[mailto:brett.estrade@gmail.com brett.estrade@gmail.com]>; I am an idependant Perl contractor based in Houston, Texas. If you found this page looking for a contract Perl programmer, you may reach me for a quote [https://brett.acutisdate.com here].

'''Disclaimer:''' Unless otherwise noted, the opinions and forms of expression on this site are my own own. Ill conceived and disordered Perl "standards of conduct" hold no dominion over me or this site - I reject the with my whole being; I also reject the traditional "3 virtues of Perl", rather I strive for the [https://www.youtube.com/watch?v=mEWfo9U3uTM rightly ordered virtue] originally intended by Perl's creator, Larry Wall; [[wikipedia:Seven_virtues|these]] are the things that hold sway over me and this site. If you don't like it, you do not have to be here. Similarly, if the idea of charging money to write Perl programs offends you, then you also do not need to be here (i.e., ''[[wikiquote:Davy_Crockett|you may go to hell and I will go to Texas]]''). This site is about creating a sustainable wage-earning culture that is based on the extremely powerful Perl programming language.

<div style="float:left; width:49%;”>
{| width="100%" class = "wikitable"
| valign="top" |
== Perl Beginners, Hobbyist, and Dabblers ==
This section is for anyone interested in Perl, learning Perl, or those tinkering with Perl. The point of this section is to move you over to become a professional Perl Craftsmen.

'''Official Website'''

'''Downloads'''

'''Community Participation'''

'''Email Lists and Communities:'''

'''Tutorials'''

'''Books and Magazines'''
|}

</div>

<div style="float:right; width:49%;”">

{| class="wikitable" width="100%"
| valign="top" |

== Perl Craftsmen and Professional Development ==

'''This section is for independent software professions''' '''who charge money for Perl-related services''' and use Perl as their secret weapon to make a living or those wishing to become one. It is not for "Jacks of all trades;" this section is for Perl craftsmen - journey men and true masters wishing to leverage their skills in Perl to put food in their kids' mouths and a roof over their head.

'''Official Website'''

'''(RAD), Rapid Application Development Tools, IDEs, Installer-Makers'''

* [https://sourceforge.net/projects/wxglade/ wxGlade] - written in Python, but can output Perl!

'''Using Perl for Making Window GUI Programs'''

* Cross-platform GUIs with wxPerl
* Windows Specific GUIs with Win32::GUI
* Cross-platform GUIs with GUIDeFATE

'''Using Perl for Creating a Commercial SaaS and Other Services'''

'''Monetization Strategies for Perl Programmers'''

'''Commerical Success Stories and Case Studies'''

'''Downloads'''

'''Community Participation'''

* [https://www.perl-guilds.net Perl Guilds Forum] - test forum to see if any activitiy is drawn to it

'''Tutorials'''

'''Books and Magazines'''

'''Related Sites'''

* https://perlclientdirectory.com/ - curated list of Perl clients for external APIs and services
* https://perlmodules.net - track changes to your favorite Perl Modules in CPAN
|}

</div>

<div style="float:left;margin-right:0.9em">

==Perl Guilds Wiki Portals==

Wiki Portals have been created for a selection of the platforms and topics that Perl and related tools support. The Portals gather together all the related information for the particular platform or topic in one place to make it easier to locate. The full list of supported platforms may be found [[Platform_list|here]].
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true">
File:NewUserLogo.png|link=Portal:New Users|[[Portal:New Users|New Users]]
File:SQLdb TSQLQuery.PNG|link=Portal:Databases|[[Portal:Databases|Database Development]]
File:GamesPortalLogo.png|link=Portal:Game Development|[[Portal:Game Development|Game Development]]
File:HardwarePortalLogo.png|link=Portal:Hardware and Robotics|[[Portal:Hardware and Robotics|Hardware and Robotics]]
File:HowTo.png|link=Portal:HowTo Demos|[[Portal:HowTo Demos|HowTo Demos]]
File:tachart getting started step6.png|link=Portal:SciTech|[[Portal:SciTech|Science and Technology]]
File:tdrawgrid.png|link=Portal:Web Development|[[Portal:SaaS and Web Development|Web Development]]
</gallery>

<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true">
File:Embedded.png|link=Portal:Embedded|[[Portal:Embedded|Embedded]]
File:FBSD Daemon.jpg|link=Portal:FreeBSD|[[Portal:FreeBSD|FreeBSD]]
File:tux.png|link=Portal:Linux|[[Portal:Linux|Linux]]
File:macOSlogo.png|link=Portal:Mac|[[Portal:Mac|macOS]]
File:Logo Windows 01.png|link=Portal:Windows|[[Portal:Windows|Windows]]
</gallery>

==In the News==

A summary of recent news stories about Perl can be found [[In the News|here]].

==Projects using Perl ==

Details and screenshots of an extensive number of applications created with Perl may be found [[Projects using Perl|here]]. There is also plenty of source code that can be found [[:category:Code|here]].

==Bug Tracker==

The [https://github.com/Perl/perl5/issues Perl Bug Tracker] and the [https://rt.perl.org/ Perl Request Tracker] (RT) are the places to go to check if the anomaly you have encountered has already been recorded as a Perl or Perl module bug and, if not, you can lodge a bug report (see [[How do I create a bug report]]) so that it can be fixed. Even better, lodge a patch if you can (see [[Creating A Patch]]) with the bug report.

<br />

Main Page

2025-01-15T05:59:13Z

104.181.193.235:

__NOTOC__

=== Welcome to the Perl Guilds Wiki ===
The '''Perl Guilds''' wiki is a community-driven resource designed to support '''freelance Perl programmers''' and help them thrive in their independent careers. This space is dedicated to Perl developers who want to enhance their skills, share knowledge, and collaborate with others to build sustainable, successful careers as freelancers in the world of Perl development. As a freelancer, you face unique challenges, but the Perl Guilds wiki offers resources and a supportive community to help you overcome them. Whether you're just starting or are an experienced Perl developer, you'll find valuable information here to help you refine your craft and build a business around your Perl expertise.

The original wiki concept was inspired by [https://wiki.freepascal.org FreePascal]'s community wiki. This wiki is maintained by myself, Brett Estrade ([https://metacpan.org/author/OODLER OODLER]) <[mailto:brett.estrade@gmail.com brett.estrade@gmail.com]>; I am an idependant Perl contractor based in Houston, Texas. If you found this page looking for a contract Perl programmer, you may reach me for a quote [https://brett.acutisdate.com here].

'''Disclaimer:''' Unless otherwise noted, the opinions and forms of expression on this site are my own own. Ill conceived and disordered Perl "standards of conduct" hold no dominion over me or this site - I reject the with my whole being; I also reject the traditional "3 virtues of Perl", rather I strive for the [https://www.youtube.com/watch?v=mEWfo9U3uTM rightly ordered virtue] originally intended by Perl's creator, Larry Wall; [[wikipedia:Seven_virtues|these]] are the things that hold sway over me and this site. If you don't like it, you do not have to be here. Similarly, if the idea of charging money to write Perl programs offends you, then you also do not need to be here. This site is about creating a sustainable wage-earning culture that is based on the extremely powerful Perl programming language.

<div style="float:left; width:49%;”>
{| width="100%" class = "wikitable"
| valign="top" |
== Perl Beginners, Hobbyist, and Dabblers ==
This section is for anyone interested in Perl, learning Perl, or those tinkering with Perl. The point of this section is to move you over to become a professional Perl Craftsmen.

'''Official Website'''

'''Downloads'''

'''Community Participation'''

'''Email Lists and Communities:'''

'''Tutorials'''

'''Books and Magazines'''
|}

</div>

<div style="float:right; width:49%;”">

{| class="wikitable" width="100%"
| valign="top" |

== Perl Craftsmen and Professional Development ==

'''This section is for independent software professions''' '''who charge money for Perl-related services''' and use Perl as their secret weapon to make a living or those wishing to become one. It is not for "Jacks of all trades;" this section is for Perl craftsmen - journey men and true masters wishing to leverage their skills in Perl to put food in their kids' mouths and a roof over their head.

'''Official Website'''

'''(RAD), Rapid Application Development Tools, IDEs, Installer-Makers'''

* [https://sourceforge.net/projects/wxglade/ wxGlade] - written in Python, but can output Perl!

'''Using Perl for Making Window GUI Programs'''

* Cross-platform GUIs with wxPerl
* Windows Specific GUIs with Win32::GUI
* Cross-platform GUIs with GUIDeFATE

'''Using Perl for Creating a Commercial SaaS and Other Services'''

'''Monetization Strategies for Perl Programmers'''

'''Commerical Success Stories and Case Studies'''

'''Downloads'''

'''Community Participation'''

* [https://www.perl-guilds.net Perl Guilds Forum] - test forum to see if any activitiy is drawn to it

'''Tutorials'''

'''Books and Magazines'''

'''Related Sites'''

* https://perlclientdirectory.com/ - curated list of Perl clients for external APIs and services
* https://perlmodules.net - track changes to your favorite Perl Modules in CPAN
|}

</div>

<div style="float:left;margin-right:0.9em">

==Perl Guilds Wiki Portals==

Wiki Portals have been created for a selection of the platforms and topics that Perl and related tools support. The Portals gather together all the related information for the particular platform or topic in one place to make it easier to locate. The full list of supported platforms may be found [[Platform_list|here]].
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true">
File:NewUserLogo.png|link=Portal:New Users|[[Portal:New Users|New Users]]
File:SQLdb TSQLQuery.PNG|link=Portal:Databases|[[Portal:Databases|Database Development]]
File:GamesPortalLogo.png|link=Portal:Game Development|[[Portal:Game Development|Game Development]]
File:HardwarePortalLogo.png|link=Portal:Hardware and Robotics|[[Portal:Hardware and Robotics|Hardware and Robotics]]
File:HowTo.png|link=Portal:HowTo Demos|[[Portal:HowTo Demos|HowTo Demos]]
File:tachart getting started step6.png|link=Portal:SciTech|[[Portal:SciTech|Science and Technology]]
File:tdrawgrid.png|link=Portal:Web Development|[[Portal:SaaS and Web Development|Web Development]]
</gallery>

<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true">
File:Embedded.png|link=Portal:Embedded|[[Portal:Embedded|Embedded]]
File:FBSD Daemon.jpg|link=Portal:FreeBSD|[[Portal:FreeBSD|FreeBSD]]
File:tux.png|link=Portal:Linux|[[Portal:Linux|Linux]]
File:macOSlogo.png|link=Portal:Mac|[[Portal:Mac|macOS]]
File:Logo Windows 01.png|link=Portal:Windows|[[Portal:Windows|Windows]]
</gallery>

==In the News==

A summary of recent news stories about Perl can be found [[In the News|here]].

==Projects using Perl ==

Details and screenshots of an extensive number of applications created with Perl may be found [[Projects using Perl|here]]. There is also plenty of source code that can be found [[:category:Code|here]].

==Bug Tracker==

The [https://github.com/Perl/perl5/issues Perl Bug Tracker] and the [https://rt.perl.org/ Perl Request Tracker] (RT) are the places to go to check if the anomaly you have encountered has already been recorded as a Perl or Perl module bug and, if not, you can lodge a bug report (see [[How do I create a bug report]]) so that it can be fixed. Even better, lodge a patch if you can (see [[Creating A Patch]]) with the bug report.

<br />