https://wiki.perl-guilds.net/api.php?action=feedcontributions&feedformat=atom&user=AdminPerl Guilds - Getting Medieval with Perl - User contributions [en]2026-07-31T23:50:10ZUser contributionsMediaWiki 1.44.2https://wiki.perl-guilds.net/index.php?title=Main_Page&diff=387Main Page2026-07-20T09:15:30Z<p>Admin: </p>
<hr />
<div>=== Welcome to the Perl Guilds Wiki ===<br />
The '''Perl Guilds''' wiki is a community-driven resource designed to support '''freelance and independent Perl programmers''' and help them thrive in their trades. The original wiki concept was inspired by [https://wiki.freepascal.org FreePascal]'s community wiki.<br />
<br />
This wiki is maintained by [[ServiceProviders|'''these people''']]. You may thank them for this resource by hiring them for something.<br />
<br />
{| style="width:100%; border:2px solid #6b4e2e; background:#fffaf0; margin:1em 0; padding:0.4em;"<br />
|-<br />
| style="width:100px; text-align:center; vertical-align:top; padding:0.7em;" | [[File:NewUserLogo.png|88px|link=Portal:Essays about The Virtuous Perl Programmer|alt=The Virtuous Perl Programmer essay series]]<br />
| style="vertical-align:top; padding:0.7em 1em;" |<br />
<big>'''Featured Series: [[Portal:Essays about The Virtuous Perl Programmer|The Virtuous Perl Programmer]]'''</big><br />
<br />
This long-form essay series follows the Perl programmer as craftsman: from the potentially weary journeyman or master seeking renewed work, to the prospective apprentice who has not yet discovered the trade. Its current technical journey develops a complete Windows wxPerl workshop and follows the work from a Perl idea to a graphical application, executable, installer, and supportable product.<br />
<br />
The essays apply '''Prudence''', '''Spiritedness''', and '''Good Order''' to real technical decisions without separating craftsmanship from truth, justice, the dignity of workers, service to users, or the proper use of talents received from God.<br />
<br />
'''Begin the journey:'''<br />
<br />
# [[The Perl Craftsman Returns to the Windows Desktop]]<br />
# [[The Perl Lazarus Workshop]]<br />
# [[Raising a Working wxPerl Shop on Windows]]<br />
# ''Forthcoming:'' [[From wxGlade Layout to Working Perl Application]]<br />
<br />
'''Series portal:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Living technical reference:''' [[Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
'''Related project:''' [[:Category:Perl Lazarus Project|Perl Lazarus Project]]<br />
|}<br />
<br />
=== Transforming Perl by Striving for Virtue ===<br />
The infamous three "virtues" of a Perl programmer are not what you have been led to believe. They are bad, very bad. Please [https://www.youtube.com/watch?v=mEWfo9U3uTM view this] to learn more about [[The Real 3 Virtues of Perl|'''the true virtues of Perl''']]: '''''Prudence''''', '''''Spiritedness''''', and '''''Good Order'''''.<br />
<br />
God is the Creator and the source of every good gift and talent. The programmer does not create from nothing; he receives intelligence, opportunity, tools, knowledge, and the labor of earlier craftsmen, and is responsible for developing these gifts and ordering them toward truthful service.<br />
<br />
Mastery therefore carries obligations. The apprentice, journeyman, master, customer, and user possess the same God-given dignity, while greater skill creates greater duties of justice, humility, patience, stewardship, and care.<br />
<br />
The [[Portal:Essays about The Virtuous Perl Programmer|Virtuous Perl Programmer essays]] apply these principles to the daily work of programming: choosing tools, forming apprentices, using AI, respecting licenses, protecting users, earning a just livelihood, and bringing software to completion.<br />
<br />
I hope to convey these ideals through this resource, and I hope you can help me.<br />
<br />
=== Site Feedback and Contributions ===<br />
Click [https://github.com/The-Perl-Cottage-Guild/wiki-requests/issues here] to report an issue with the content, suggest edits or additions, or request editor access.<br />
<br />
You may also [https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors '''join the editors email list'''] to provide feedback, volunteer, or discuss proposed changes. <u>'''''[https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors This may get you a quicker response].'''''</u><br />
<br />
Volunteers are eligible to create a listing [[ServiceProviders|here]].<br />
<br />
= Portals =<br />
<br />
<div style="float:left; width:49%;"><br />
<br />
{| class="wikitable" width="100%"<br />
| valign="top" |<br />
<br />
== General Audience Links ==<br />
<br />
Wiki portals have been created for a selection of the platforms and topics that Perl and related tools support. The portals gather related information for each platform or topic in one place to make it easier to locate. The full list of supported platforms may be found [[Platform_list|here]].<br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:NewUserLogo.png|link=Portal:Essays about The Virtuous Perl Programmer|[[Portal:Essays about The Virtuous Perl Programmer|Virtuous Perl Programmer]]<br />
File:wxPerl.png|link=Portal:GUIs with Perl|[[Portal:GUIs with Perl|GUIs with Perl]]<br />
File:Logo Windows 01.png|link=Portal:Windows|[[Portal:Windows|Windows]]<br />
File:Payment.jpeg|link=Portal:Payment Processing|[[Portal:Payment Processing|Getting Paid]]<br />
File:Money.jpeg|link=Portal:Perl for Profit|[[Portal:Perl for Profit|Perl for Profit]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Perlopenmp.jpeg|link=Portal:Perl+OpenMP|[[Portal:Perl+OpenMP|Perl+OpenMP]]<br />
File:Concurrency.png|link=Portal:Concurrency|[[Portal:Concurrency|Concurrency]]<br />
File:ToolBox.png|link=Portal:Software Development Tools|[[Portal:Software Development Tools|Development Tools]]<br />
File:perlCGI.jpg|link=Portal:Perl CGI Programming|[[Portal:Perl CGI Programming|Legacy Perl]]<br />
File:Camels.jpg|link=Portal:Perl Powered Programs (PPP)|[[Portal:Perl Powered Programs (PPP)|Perl Powered Programs (PPP)]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Perlcommunity.png|link=Portal:Perl Communities|[[Portal:Perl Communities|Communities]]<br />
File:XS.jpg|link=Portal:Embedding and Extending Perl|[[Portal:Embedding and Extending Perl|Embedding and Extending Perl]]<br />
File:History.gif|link=Portal:Perl History|[[Portal:Perl History|Perl History]]<br />
File:SQLdb TSQLQuery.PNG|link=Portal:Databases|[[Portal:Databases|Database Development]]<br />
File:GamesPortalLogo.png|link=Portal:Game Development|[[Portal:Game Development|Game Development]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:HowTo.png|link=Portal:HowTo Demos|[[Portal:HowTo Demos|HowTo Demos]]<br />
File:Rperl.jpeg|link=Portal:Alt. Perls|[[Portal:Alt. Perls|Alt. Perls]]<br />
File:Ai.jpeg|link=Portal:Artificial Intelligence|[[Portal:Artificial Intelligence|Artificial Intelligence]]<br />
File:Crypto.png|link=Portal:Crypto and Blockchain|[[Portal:Crypto and Blockchain|Blockchain]]<br />
File:Perlbooks.jpg|link=Portal:Ex Libris|[[Portal:Ex Libris|Ex Libris]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Embedded.png|link=Portal:Embedded|[[Portal:Embedded|Embedded]]<br />
File:FBSD Daemon.jpg|link=Portal:FreeBSD,OpenBSD,etc|[[Portal:FreeBSD,OpenBSD,etc|FreeBSD, OpenBSD, etc.]]<br />
File:tux.png|link=Portal:Linux|[[Portal:Linux|Linux]]<br />
File:macOSlogo.png|link=Portal:Mac|[[Portal:Mac|macOS]]<br />
File:HardwarePortalLogo.png|link=Portal:Hardware and Robotics|[[Portal:Hardware and Robotics|Hardware and Robotics]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Businessmodels.jpeg|link=Portal:Perl Business Models and Case Studies|[[Portal:Perl Business Models and Case Studies|Business Models and Case Studies]]<br />
File:ImageMagick.gif|link=Portal:Graphics Programming|[[Portal:Graphics Programming|Graphics Programming]]<br />
File:Hpc.jpg|link=Portal:HPC - High Performance Computing|[[Portal:HPC - High Performance Computing|HPC - High Performance Computing]]<br />
File:Bioperl.jpeg|link=Portal:Life Sciences|[[Portal:Life Sciences|Life Sciences]]<br />
File:tdrawgrid.png|link=Portal:SaaS and Web Development|[[Portal:SaaS and Web Development|SaaS and Web Development]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:tachart getting started step6.png|link=Portal:SciTech|[[Portal:SciTech|Science and Technology]]<br />
</gallery><br />
|}<br />
<br />
</div><br />
<br />
<div style="float:right; width:49%;"><br />
<br />
{| class="wikitable" width="100%"<br />
| valign="top" |<br />
<br />
== Perl Craftsmen and Professional Development ==<br />
<br />
'''This section is for independent software professionals who charge money for Perl-related services, and for those preparing to do so.''' Perl may be the visible product, the server-side foundation, or the craftsman's secret weapon.<br />
<br />
This is not a celebration of being a careless "jack of all trades." It is a place for apprentices, journeymen, and masters who wish to cultivate real specialties, serve users well, support their families, and earn a just and sustainable livelihood through useful labor.<br />
<br />
'''Featured Technical Journey'''<br />
<br />
* [[Portal:Essays about The Virtuous Perl Programmer|The Virtuous Perl Programmer]]<br />
** [[The Perl Craftsman Returns to the Windows Desktop]]<br />
** [[The Perl Lazarus Workshop]]<br />
** [[Raising a Working wxPerl Shop on Windows]]<br />
** ''Forthcoming:'' [[From wxGlade Layout to Working Perl Application]]<br />
* [[Developing and Distributing wxPerl Applications on Windows|Complete wxPerl-on-Windows technical reference]]<br />
* [[:Category:Perl Lazarus Project|Perl Lazarus Project category]]<br />
<br />
'''Quick Links'''<br />
<br />
* [[ServiceProviders|Perl service providers and craftsmen]]<br />
* [[Portal:Perl for Profit|Perl for Profit]]<br />
* [[Portal:Payment Processing|Getting Paid]]<br />
* [[Portal:Perl Business Models and Case Studies|Perl Business Models and Case Studies]]<br />
* [[Portal:Software Development Tools|Software Development Tools]]<br />
* [[Portal:HowTo Demos|HowTo Demos]]<br />
<br />
'''Notable Updates'''<br />
<br />
* [[Portal:GUIs with Perl|GUIs with Perl]]<br />
** [[Developing and Distributing wxPerl Applications on Windows]]<br />
** [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates wxPerl-wxGlade Templates]<br />
* [[Portal:Perl+OpenMP|Perl+OpenMP]]<br />
* [[Portal:Artificial Intelligence|Artificial Intelligence]]<br />
<br />
'''Email Lists'''<br />
<br />
* '''[https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors Perl-Guilds Wiki Contributors]''' listserv — join if you would like to contribute or offer regular feedback<br />
* '''[https://sourceforge.net/projects/perl-openmp/lists/perl-openmp-discuss Perl+OpenMP]''' listserv<br />
<br />
'''Note''': Yes, I encourage email lists for your project; and it turns out SourceForge.net is a great place to host reliable email lists!<br />
<br />
'''RAD, Rapid Application Development Tools, IDEs, and Installer-Makers'''<br />
<br />
* [https://strawberryperl.com/ Strawberry Perl] — native Perl and build environment for Windows<br />
* [https://sourceforge.net/projects/wxglade/ wxGlade] — written in Python, but can output Perl<br />
* [https://www.msys2.org/ MSYS2] — Unix-like editing, Git, SSH, and shell environment for Windows<br />
* [https://jrsoftware.org/isinfo.php Inno Setup] — professional Windows installer builder with reasonable commercial licensing terms<br />
* [[Perl and wxWidgets RAD on Windows|History of Perl and wxWidgets RAD tools on Windows]]<br />
<br />
'''Using Perl for Making Windows GUI Programs'''<br />
<br />
* Cross-platform GUIs with wxPerl<br />
** [[Developing and Distributing wxPerl Applications on Windows]]<br />
** [[GUI ideas for use with wxGlade]]<br />
* Windows-specific GUIs with Win32::GUI<br />
* Cross-platform GUIs with GUIDeFATE<br />
<br />
'''Using Perl for Creating Commercial SaaS and Other Services'''<br />
<br />
* [[Portal:SaaS and Web Development|SaaS and Web Development]]<br />
* [https://perlclientdirectory.com/ Perl Client Directory]<br />
* Desktop wxPerl clients may complement Perl web applications, APIs, databases, and hosted processing services.<br />
<br />
'''Monetization Strategies for Perl Programmers'''<br />
<br />
* [[Portal:Perl for Profit|Perl for Profit]]<br />
* [[Portal:Payment Processing|Payment Processing]]<br />
* [[Portal:Perl Business Models and Case Studies|Business Models and Case Studies]]<br />
* Application sales, site licenses, paid customization, migration, support, maintenance, training, hosting, and consulting<br />
<br />
'''Commercial Success Stories and Case Studies'''<br />
<br />
* [[Portal:Perl Business Models and Case Studies]]<br />
* [[Projects using Perl]]<br />
* [[Portal:Perl Powered Programs (PPP)|Perl Powered Programs]]<br />
<br />
'''Downloads and Source Code'''<br />
<br />
* [https://github.com/The-Perl-Cottage-Guild The Perl Cottage Guild on GitHub]<br />
* [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates wxPerl-wxGlade Templates]<br />
* [https://github.com/StormSurgeLive/nhc-advisory-gui NHC Advisory Explorer]<br />
* [[:Category:Code|Code on this wiki]]<br />
<br />
'''Community Participation'''<br />
<br />
* [https://www.perl-guilds.net Perl Guilds Forum] — test forum to see if any activity is drawn to it<br />
* [https://github.com/The-Perl-Cottage-Guild/wiki-requests/issues Wiki requests and issue tracker]<br />
* [[ServiceProviders|Service-provider listings]]<br />
<br />
'''Tutorials'''<br />
<br />
* [[Portal:HowTo Demos|HowTo Demos]]<br />
* [[Developing and Distributing wxPerl Applications on Windows]]<br />
* [[Raising a Working wxPerl Shop on Windows]]<br />
<br />
'''Books, Magazines, and Long-Form Writing'''<br />
<br />
* [[Portal:Ex Libris|Ex Libris]]<br />
* [[Portal:Essays about The Virtuous Perl Programmer|The Virtuous Perl Programmer essays]]<br />
* The essay series is being developed incrementally as a future book-length treatment of virtuous craftsmanship and marketable wxPerl application development.<br />
<br />
'''Related Sites'''<br />
<br />
* https://perlclientdirectory.com/ — curated list of Perl clients for external APIs and services<br />
* https://perlmodules.net — track changes to your favorite Perl modules in CPAN<br />
<br />
|}<br />
<br />
</div><br />
<br />
<div style="clear:both;"></div><br />
<br />
== In the News ==<br />
<br />
A summary of recent news stories about Perl can be found [[In the News|here]].<br />
<br />
== Projects using Perl ==<br />
<br />
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]].<br />
<br />
== Bug Tracker ==<br />
<br />
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. 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]].</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Category:Git&diff=386Category:Git2026-07-20T07:06:57Z<p>Admin: Created page with "{{DISPLAYTITLE:Category:Git}} This category contains pages concerning the use of '''Git''' in Perl projects. Within the wxPerl and wxGlade workflow, Git preserves generated and handwritten source, exposes changes made during code generation, provides recoverable checkpoints, and allows the craftsman to distinguish verified work from experimentation. '''Related workflow:''' Developing and Distributing wxPerl Applications on Windows Git C..."</p>
<hr />
<div>{{DISPLAYTITLE:Category:Git}}<br />
<br />
This category contains pages concerning the use of '''Git''' in Perl projects.<br />
<br />
Within the wxPerl and wxGlade workflow, Git preserves generated and handwritten source, exposes changes made during code generation, provides recoverable checkpoints, and allows the craftsman to distinguish verified work from experimentation.<br />
<br />
'''Related workflow:''' [[Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
[[Category:Perl Guilds|Git]]<br />
[[Category:Perl Lazarus Project|Git]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Category:MSYS2&diff=385Category:MSYS22026-07-20T07:06:39Z<p>Admin: Created page with "{{DISPLAYTITLE:Category:MSYS2}} This category contains pages discussing the use of '''MSYS2''' as a Unix-like editing, Git, SSH, and shell environment for Perl development on Windows. Within the Perl Lazarus workflow, MSYS2 complements rather than replaces Strawberry Perl. It may be used for vim, Git, source inspection, and familiar shell utilities, while wxPerl applications and packaging commands are run using the intended Strawberry Perl environment. '''Related work..."</p>
<hr />
<div>{{DISPLAYTITLE:Category:MSYS2}}<br />
<br />
This category contains pages discussing the use of '''MSYS2''' as a Unix-like editing, Git, SSH, and shell environment for Perl development on Windows.<br />
<br />
Within the Perl Lazarus workflow, MSYS2 complements rather than replaces Strawberry Perl. It may be used for vim, Git, source inspection, and familiar shell utilities, while wxPerl applications and packaging commands are run using the intended Strawberry Perl environment.<br />
<br />
'''Related workflow:''' [[Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
[[Category:Windows|MSYS2]]<br />
[[Category:Perl Lazarus Project|MSYS2]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Category:WxGlade&diff=384Category:WxGlade2026-07-20T07:06:25Z<p>Admin: Created page with "{{DISPLAYTITLE:Category:wxGlade}} This category contains pages about '''wxGlade''', a visual interface designer for wxWidgets applications. Within the Perl Lazarus workflow, wxGlade is used to save graphical interface projects as XML and emit Perl source code for wxPerl applications. Pages may cover installation, output settings, generated-code preservation, templates, interface ideas, event wiring, and efficient edit–emit–run workflows. '''GUI ideas and examples:..."</p>
<hr />
<div>{{DISPLAYTITLE:Category:wxGlade}}<br />
<br />
This category contains pages about '''wxGlade''', a visual interface designer for wxWidgets applications.<br />
<br />
Within the Perl Lazarus workflow, wxGlade is used to save graphical interface projects as XML and emit Perl source code for wxPerl applications. Pages may cover installation, output settings, generated-code preservation, templates, interface ideas, event wiring, and efficient edit–emit–run workflows.<br />
<br />
'''GUI ideas and examples:''' [[GUI ideas for use with wxGlade]]<br />
<br />
'''Windows wxPerl workflow:''' [[Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
'''Template repository:''' [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates wxPerl-wxGlade Templates]<br />
<br />
[[Category:Perl Lazarus Project|wxGlade]]<br />
[[Category:wxPerl|wxGlade]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Category:Strawberry_Perl&diff=383Category:Strawberry Perl2026-07-20T07:06:07Z<p>Admin: Created page with "{{DISPLAYTITLE:Category:Strawberry Perl}} This category contains pages about '''Strawberry Perl''', the native Perl distribution for Windows used as the principal Perl and build environment in the Perl Lazarus Project. Topics may include installation profiles, compilers, build tools, module installation, PDL distributions, environment verification, and compatibility with wxPerl and native libraries. '''Primary wxPerl installation guide:''' Developing and Distributin..."</p>
<hr />
<div>{{DISPLAYTITLE:Category:Strawberry Perl}}<br />
<br />
This category contains pages about '''Strawberry Perl''', the native Perl distribution for Windows used as the principal Perl and build environment in the Perl Lazarus Project.<br />
<br />
Topics may include installation profiles, compilers, build tools, module installation, PDL distributions, environment verification, and compatibility with wxPerl and native libraries.<br />
<br />
'''Primary wxPerl installation guide:''' [[Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
[[Category:Windows|Strawberry Perl]]<br />
[[Category:Perl Lazarus Project|Strawberry Perl]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Category:Windows&diff=382Category:Windows2026-07-20T07:05:14Z<p>Admin: Created page with "{{DISPLAYTITLE:Category:Windows}} This category contains pages concerning Perl development, deployment, compatibility, and application distribution on Microsoft Windows. Relevant topics include Strawberry Perl, wxPerl, GUI development, Windows executables, installers, native DLLs, backward compatibility, and historical experiments with older Windows systems. '''Primary wxPerl guide:''' Developing and Distributing wxPerl Applications on Windows Category:Perl Laz..."</p>
<hr />
<div>{{DISPLAYTITLE:Category:Windows}}<br />
<br />
This category contains pages concerning Perl development, deployment, compatibility, and application distribution on Microsoft Windows.<br />
<br />
Relevant topics include Strawberry Perl, wxPerl, GUI development, Windows executables, installers, native DLLs, backward compatibility, and historical experiments with older Windows systems.<br />
<br />
'''Primary wxPerl guide:''' [[Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
[[Category:Perl Lazarus Project|Windows]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Category:WxPerl&diff=381Category:WxPerl2026-07-20T07:04:58Z<p>Admin: Created page with "{{DISPLAYTITLE:Category:wxPerl}} This category contains pages about '''wxPerl''', the Perl bindings for the wxWidgets graphical application framework. Topics may include installation, controls, events, examples, wxGlade integration, Windows development, executable packaging, historical tools, and the creation of distributable desktop applications. '''Primary Windows guide:''' Developing and Distributing wxPerl Applications on Windows '''Related history:''' Perl..."</p>
<hr />
<div>{{DISPLAYTITLE:Category:wxPerl}}<br />
<br />
This category contains pages about '''wxPerl''', the Perl bindings for the wxWidgets graphical application framework.<br />
<br />
Topics may include installation, controls, events, examples, wxGlade integration, Windows development, executable packaging, historical tools, and the creation of distributable desktop applications.<br />
<br />
'''Primary Windows guide:''' [[Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
'''Related history:''' [[Perl and wxWidgets RAD on Windows]]<br />
<br />
[[Category:Perl Lazarus Project|wxPerl]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Category:Perl_Guilds&diff=380Category:Perl Guilds2026-07-20T07:04:44Z<p>Admin: Created page with "{{DISPLAYTITLE:Category:Perl Guilds}} This category contains pages related to '''Perl Guilds''': its purposes, essays, projects, guilds, and efforts to support independent Perl programmers in the practice of their trade. Perl Guilds draws upon the traditional idea of craftsmen learning, traveling, mastering a trade, forming apprentices, preserving knowledge, and supporting one another through useful work. Its purpose is not to impose a compulsory professional organiza..."</p>
<hr />
<div>{{DISPLAYTITLE:Category:Perl Guilds}}<br />
<br />
This category contains pages related to '''Perl Guilds''': its purposes, essays, projects, guilds, and efforts to support independent Perl programmers in the practice of their trade.<br />
<br />
Perl Guilds draws upon the traditional idea of craftsmen learning, traveling, mastering a trade, forming apprentices, preserving knowledge, and supporting one another through useful work.<br />
<br />
Its purpose is not to impose a compulsory professional organization or restrict entry into programming. It seeks to encourage voluntary associations through which Perl programmers can:<br />
<br />
* preserve and share practical knowledge;<br />
* develop marketable specialties;<br />
* form and encourage new programmers;<br />
* cooperate on projects;<br />
* serve users and communities;<br />
* and earn a just and sustainable livelihood through their labor.<br />
<br />
The Perl Lazarus Project and ''The Virtuous Perl Programmer'' essays are two expressions of this larger work.<br />
<br />
'''Main page:''' [[Main Page|Perl Guilds]]<br />
<br />
'''Virtuous Programmer essays:''' [[Portal:Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Perl Lazarus material:''' [[Category:Perl Lazarus Project]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Category:Perl_Lazarus_Project&diff=379Category:Perl Lazarus Project2026-07-20T07:04:28Z<p>Admin: Created page with "{{DISPLAYTITLE:Category:Perl Lazarus Project}} The '''Perl Lazarus Project''' is an effort arising from Perl Guilds to make practical Windows GUI development, packaging, and distribution available to Perl programmers through a clear and repeatable workflow. The project joins existing tools rather than attempting to replace them with a single monolithic development environment. Its principal stack includes: * Strawberry Perl; * wxWidgets and wxPerl; * wxGlade; * MSYS2,..."</p>
<hr />
<div>{{DISPLAYTITLE:Category:Perl Lazarus Project}}<br />
<br />
The '''Perl Lazarus Project''' is an effort arising from Perl Guilds to make practical Windows GUI development, packaging, and distribution available to Perl programmers through a clear and repeatable workflow.<br />
<br />
The project joins existing tools rather than attempting to replace them with a single monolithic development environment. Its principal stack includes:<br />
<br />
* Strawberry Perl;<br />
* wxWidgets and wxPerl;<br />
* wxGlade;<br />
* MSYS2, vim, and Git;<br />
* PAR-based executable packaging;<br />
* DLL-discovery tools;<br />
* and Inno Setup.<br />
<br />
The goal is to help a Perl programmer begin with existing Perl knowledge and end with a Windows application which an ordinary user can install, launch, and use without first reproducing the developer's environment.<br />
<br />
'''Primary technical guide:''' [[Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
'''Essay series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Historical background:''' [[Perl and wxWidgets RAD on Windows]]<br />
<br />
[[Category:Perl Guilds|Lazarus Project]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Category:The_Virtuous_Perl_Programmer&diff=378Category:The Virtuous Perl Programmer2026-07-20T07:04:07Z<p>Admin: Created page with "{{DISPLAYTITLE:Category:The Virtuous Perl Programmer}} This category contains essays in '''The Virtuous Perl Programmer''' series. The series considers programming as a human craft ordered toward truth, useful service, just exchange, and the common good. It applies the virtues developed through Perl Guilds to the practical work of designing, building, testing, distributing, selling, and supporting software. The current technical journey follows the Perl craftsman from..."</p>
<hr />
<div>{{DISPLAYTITLE:Category:The Virtuous Perl Programmer}}<br />
<br />
This category contains essays in '''The Virtuous Perl Programmer''' series.<br />
<br />
The series considers programming as a human craft ordered toward truth, useful service, just exchange, and the common good. It applies the virtues developed through Perl Guilds to the practical work of designing, building, testing, distributing, selling, and supporting software.<br />
<br />
The current technical journey follows the Perl craftsman from an existing knowledge of Perl toward the production of complete Windows desktop applications using Strawberry Perl, wxPerl, wxGlade, packaging tools, and Inno Setup.<br />
<br />
The essays are intended to serve both experienced Perl journeymen and masters who may be seeking a renewed field for their craft, and prospective apprentices who are only beginning to discover programming.<br />
<br />
'''Main portal:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Related project:''' [[Category:Perl Lazarus Project|Perl Lazarus Project]]<br />
<br />
[[Category:Perl Guilds|Virtuous Perl Programmer]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Raising_a_Working_wxPerl_Shop_on_Windows&diff=376Raising a Working wxPerl Shop on Windows2026-07-20T04:45:18Z<p>Admin: </p>
<hr />
<div>{{DISPLAYTITLE:Raising a Working wxPerl Shop on Windows}}<br />
<br />
''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.''<br />
<br />
A collection of tools is not yet a workshop.<br />
<br />
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.<br />
<br />
This essay will raise a practical wxPerl shop on Windows. By the end, the programmer should possess:<br />
<br />
* a known Strawberry Perl environment;<br />
* a working installation of <code>Alien::wxWidgets</code> and <code>Wx</code>;<br />
* a visible wxPerl demonstration;<br />
* wxGlade configured to emit Perl;<br />
* an MSYS2 terminal with vim and Git;<br />
* a small wxGlade project;<br />
* generated Perl source;<br />
* at least one working event;<br />
* and a Git commit preserving the first successful state of the shop.<br />
<br />
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.<br />
<br />
The distinction matters.<br />
<br />
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.<br />
<br />
The prudent craftsman proves each layer before placing the next one upon it.<br />
<br />
== What counts as a working shop? ==<br />
<br />
The shop is working when the entire development cycle can be repeated:<br />
<br />
# Open or create a wxGlade project.<br />
# Change the graphical design.<br />
# Emit Perl source code.<br />
# Inspect the generated changes.<br />
# Add or revise application behavior.<br />
# Run the application with the intended Strawberry Perl.<br />
# Correct the work.<br />
# Preserve a known-good state in Git.<br />
<br />
The goal is not merely to install several programs without error messages.<br />
<br />
The goal is to establish a rhythm of work.<br />
<br />
{| class="wikitable"<br />
|+ The daily wxPerl working cycle<br />
! Stage<br />
! Primary tool<br />
! Result<br />
|-<br />
| Design<br />
| wxGlade<br />
| A saved <code>.wxg</code> XML project<br />
|-<br />
| Emit<br />
| wxGlade<br />
| Perl source generated from the visual design<br />
|-<br />
| Inspect and edit<br />
| vim under MSYS2<br />
| Reviewed source and handwritten behavior<br />
|-<br />
| Run<br />
| Strawberry Perl terminal<br />
| The actual wxPerl application<br />
|-<br />
| Compare and preserve<br />
| Git under MSYS2<br />
| A diff and recoverable checkpoint<br />
|}<br />
<br />
The distinction between these environments will be repeated throughout this essay because it prevents one of the most confusing failures in the workflow:<br />
<br />
<blockquote><br />
Use MSYS2 to edit and manage the project, but run the wxPerl application using Strawberry Perl.<br />
</blockquote><br />
<br />
MSYS2 may have its own Perl. That Perl is not the Perl against which the selected wxPerl stack was built.<br />
<br />
== Begin with a tested profile ==<br />
<br />
A craftsman may enjoy experimenting with the newest tools, but he should first establish a known working reference point.<br />
<br />
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:<br />
<br />
{| class="wikitable"<br />
|+ Selected wxPerl installation profiles<br />
! Status<br />
! Strawberry Perl<br />
! <code>Alien::wxWidgets</code><br />
! <code>Wx</code><br />
! Use<br />
|-<br />
| Previously tested reference<br />
| 5.40.2.1, 64-bit UCRT MSI<br />
| 0.71<br />
| 3.008<br />
| The safer starting point for reproducing the established workflow<br />
|-<br />
| Newer PDL-oriented profile<br />
| 5.42.2.1, 64-bit UCRT PDL ZIP<br />
| 0.73<br />
| 3.009<br />
| A newer path which should be treated according to the current verification status on the wiki<br />
|-<br />
| Archived reference<br />
| 5.40.0.1, 64-bit UCRT MSI<br />
| 0.70<br />
| 3.005<br />
| Historical comparison and regression troubleshooting<br />
|}<br />
<br />
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.<br />
<br />
A tested profile is not a claim that newer software is bad.<br />
<br />
It is a statement about evidence.<br />
<br />
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.<br />
<br />
== Prepare a work record before installing anything ==<br />
<br />
Create a plain-text file named:<br />
<br />
<pre><br />
wxperl-environment.txt<br />
</pre><br />
<br />
Record:<br />
<br />
* the date;<br />
* Windows edition and version;<br />
* whether the system is 64-bit;<br />
* the selected Strawberry Perl profile;<br />
* the selected <code>Alien::wxWidgets</code> version;<br />
* the selected <code>Wx</code> version;<br />
* the wxGlade version;<br />
* the Python version used by wxGlade;<br />
* the MSYS2 installation date;<br />
* and links to the instructions followed.<br />
<br />
This file is not bureaucracy.<br />
<br />
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.<br />
<br />
Create a directory for installation logs as well:<br />
<br />
<pre><br />
C:\wxperl-shop\logs<br />
</pre><br />
<br />
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:<br />
<br />
# identify the selected profile;<br />
# run one installation stage;<br />
# preserve its output;<br />
# stop clearly when that stage fails;<br />
# verify the result;<br />
# and continue only when the layer beneath it is sound.<br />
<br />
The batch file should preserve successful labor. It should not turn the installation into an unknowable ritual.<br />
<br />
The manual steps remain important because they allow the craftsman to understand and repair the automated process.<br />
<br />
== Install Strawberry Perl ==<br />
<br />
For the previously tested profile, use the instructions at:<br />
<br />
* [[Wx 3.008, Alien::wxWidgets 0.71, Strawberry Perl 5.40.2.1]]<br />
<br />
The documented installer is the 64-bit UCRT MSI distribution of Strawberry Perl 5.40.2.1.<br />
<br />
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>.<br />
<br />
Open:<br />
<br />
<pre><br />
Start menu → Strawberry Perl → Perl (command line)<br />
</pre><br />
<br />
This should produce an ordinary Windows command prompt prepared for Strawberry Perl.<br />
<br />
Run:<br />
<br />
<pre><br />
where perl<br />
perl -v<br />
perl -V:archname<br />
perl -V:cc<br />
where gcc<br />
where gmake<br />
</pre><br />
<br />
The first <code>perl</code> reported by <code>where perl</code> should be the intended Strawberry Perl executable, normally under a path resembling:<br />
<br />
<pre><br />
C:\Strawberry\perl\bin\perl.exe<br />
</pre><br />
<br />
The exact compiler version is less important than proving that Strawberry Perl's compiler and build tools are available.<br />
<br />
Save the output:<br />
<br />
<pre><br />
where perl > C:\wxperl-shop\logs\strawberry-baseline.txt<br />
perl -v >> C:\wxperl-shop\logs\strawberry-baseline.txt<br />
perl -V:archname >> C:\wxperl-shop\logs\strawberry-baseline.txt<br />
perl -V:cc >> C:\wxperl-shop\logs\strawberry-baseline.txt<br />
where gcc >> C:\wxperl-shop\logs\strawberry-baseline.txt<br />
where gmake >> C:\wxperl-shop\logs\strawberry-baseline.txt<br />
</pre><br />
<br />
Do not proceed until the intended Perl is clear.<br />
<br />
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.<br />
<br />
== Install Alien::wxWidgets ==<br />
<br />
Remain in the Strawberry Perl command-line window.<br />
<br />
For the tested profile, run:<br />
<br />
<pre><br />
cpanm --verbose https://github.com/sciurius/perl-Alien-wxWidgets/releases/download/R0.71/Alien-wxWidgets-0.71.tar.gz<br />
</pre><br />
<br />
Preserve the output if practical:<br />
<br />
<pre><br />
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<br />
</pre><br />
<br />
This stage may require time. Native libraries and build configuration are involved.<br />
<br />
Do not mistake a quiet period for certain failure. Do not mistake a long stream of compiler output for success either.<br />
<br />
Wait for the final result.<br />
<br />
Then verify:<br />
<br />
<pre><br />
perl -MAlien::wxWidgets -e "print qq{Alien::wxWidgets $Alien::wxWidgets::VERSION\n}"<br />
</pre><br />
<br />
For this profile, the output should identify version 0.71.<br />
<br />
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.<br />
<br />
== Install Wx / wxPerl ==<br />
<br />
Once <code>Alien::wxWidgets</code> is installed and can be loaded, install the Perl binding:<br />
<br />
<pre><br />
cpanm --verbose https://github.com/sciurius/wxPerl/releases/download/R3.008/Wx-3.008.tar.gz<br />
</pre><br />
<br />
To preserve the complete output:<br />
<br />
<pre><br />
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<br />
</pre><br />
<br />
Then verify:<br />
<br />
<pre><br />
perl -MWx -e "print qq{Wx $Wx::VERSION\n}"<br />
</pre><br />
<br />
The selected profile should report:<br />
<br />
<pre><br />
Wx 3.008<br />
</pre><br />
<br />
Also verify both layers in one command:<br />
<br />
<pre><br />
perl -MAlien::wxWidgets -MWx -e "print qq{Alien::wxWidgets $Alien::wxWidgets::VERSION\nWx $Wx::VERSION\n}"<br />
</pre><br />
<br />
A successful module load is important, but it is not yet a complete graphical test.<br />
<br />
The binding must create an application and enter the Windows event loop.<br />
<br />
== Run a minimal hand-written wxPerl application ==<br />
<br />
Create:<br />
<br />
<pre><br />
C:\wxperl-shop\hello-wx.pl<br />
</pre><br />
<br />
with the following contents:<br />
<br />
<syntaxhighlight lang="perl"><br />
use strict;<br />
use warnings;<br />
use Wx;<br />
<br />
package HelloWxApp;<br />
use parent 'Wx::App';<br />
<br />
sub OnInit {<br />
my ($self) = @_;<br />
<br />
my $frame = Wx::Frame->new(<br />
undef,<br />
-1,<br />
'The Perl Lazarus Workshop',<br />
);<br />
<br />
$frame->SetSize(640, 360);<br />
$frame->Centre();<br />
$frame->Show(1);<br />
<br />
return 1;<br />
}<br />
<br />
package main;<br />
<br />
my $app = HelloWxApp->new();<br />
$app->MainLoop();<br />
</syntaxhighlight><br />
<br />
Run it from the Strawberry Perl terminal:<br />
<br />
<pre><br />
cd /d C:\wxperl-shop<br />
perl hello-wx.pl<br />
</pre><br />
<br />
A blank frame titled “The Perl Lazarus Workshop” should appear.<br />
<br />
This small program proves several things at once:<br />
<br />
* Strawberry Perl is active.<br />
* <code>Wx</code> can be loaded.<br />
* The native wxWidgets libraries can be found.<br />
* A Windows frame can be created.<br />
* The event loop can run.<br />
* The application can close normally.<br />
<br />
Do not dismiss the blank window as trivial.<br />
<br />
It is the first physical proof that the shop has been raised.<br />
<br />
== Install and run Wx::Demo ==<br />
<br />
The next verification is broader.<br />
<br />
From the Strawberry Perl terminal:<br />
<br />
<pre><br />
cpanm --verbose Wx::Demo<br />
</pre><br />
<br />
Then run:<br />
<br />
<pre><br />
wxperl_demo.pl<br />
</pre><br />
<br />
<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.<br />
<br />
Spend some time opening examples.<br />
<br />
Look at:<br />
<br />
* buttons and text controls;<br />
* list and tree controls;<br />
* notebooks;<br />
* menus;<br />
* dialogs;<br />
* drawing examples;<br />
* timers;<br />
* and event handling.<br />
<br />
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.<br />
<br />
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.<br />
<br />
This is why the craftsman tests in layers.<br />
<br />
== Install wxGlade ==<br />
<br />
[[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.]]<br />
<br />
wxGlade is a separate application. It is written using Python and wxPython, even though the application being developed will use Perl and wxPerl.<br />
<br />
That is not a contradiction.<br />
<br />
A tool need not be written in the same language as the work it helps produce.<br />
<br />
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:<br />
<br />
* Python 3.10.11;<br />
* wxPython installed through <code>pip</code>;<br />
* and wxGlade 1.1.1.<br />
<br />
Later Python combinations may work, but the living page should be consulted before replacing a tested profile merely because a newer Python release exists.<br />
<br />
Install Python 3.10.11 using the link in the maintained instructions. Enable the option to add Python to the Windows <code>PATH</code>.<br />
<br />
Open a normal Windows Command Prompt, not the Strawberry Perl terminal, and verify:<br />
<br />
<pre><br />
where python<br />
python --version<br />
python -m pip --version<br />
</pre><br />
<br />
Install wxPython:<br />
<br />
<pre><br />
python -m pip install wxPython<br />
</pre><br />
<br />
Download and unpack wxGlade 1.1.1. A reasonable location is:<br />
<br />
<pre><br />
C:\Tools\wxGlade-1.1.1<br />
</pre><br />
<br />
Change to that directory:<br />
<br />
<pre><br />
cd /d C:\Tools\wxGlade-1.1.1<br />
python wxglade.py<br />
</pre><br />
<br />
If the distribution provides <code>wxglade.pyw</code>, it can also be launched without retaining a console window.<br />
<br />
Create a small wrapper named:<br />
<br />
<pre><br />
C:\Tools\wxGlade-1.1.1\start-wxglade.cmd<br />
</pre><br />
<br />
with:<br />
<br />
<pre><br />
@echo off<br />
cd /d "C:\Tools\wxGlade-1.1.1"<br />
start "" pythonw wxglade.pyw<br />
</pre><br />
<br />
Adjust the path and filename to match the actual installation.<br />
<br />
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.<br />
<br />
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.<br />
<br />
<div style="clear:both;"></div><br />
<br />
== Install MSYS2, vim, and Git ==<br />
<br />
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><br />
<br />
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.<br />
<br />
Then install vim and Git:<br />
<br />
<pre><br />
pacman -S vim git<br />
</pre><br />
<br />
Verify:<br />
<br />
<pre><br />
vim --version<br />
git --version<br />
</pre><br />
<br />
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.<br />
<br />
A useful optional <code>~/.vimrc</code> for the author's preferred MSYS2 workflow is:<br />
<br />
<pre><br />
set mouse=<br />
set noautoindent<br />
set nosmartindent<br />
set nocindent<br />
</pre><br />
<br />
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.<br />
<br />
The critical check is:<br />
<br />
<pre><br />
which perl<br />
perl -v<br />
</pre><br />
<br />
Inside MSYS2, the reported Perl may be:<br />
<br />
<pre><br />
/usr/bin/perl<br />
</pre><br />
<br />
This is not Strawberry Perl.<br />
<br />
That is acceptable because MSYS2 is being used for vim, Git, shell navigation, and source inspection.<br />
<br />
Do not use that Perl to run the generated wxPerl application.<br />
<br />
Use the Strawberry Perl command-line window for:<br />
<br />
<pre><br />
perl your-application.pl<br />
</pre><br />
<br />
and later for:<br />
<br />
<pre><br />
cpanm<br />
wxpar<br />
pp_autolink<br />
gmake<br />
</pre><br />
<br />
The following table should remain mentally visible:<br />
<br />
{| class="wikitable"<br />
|+ Two terminals, two responsibilities<br />
! Environment<br />
! Use it for<br />
! Do not assume<br />
|-<br />
| MSYS2<br />
| vim, Git, SSH, diffs, shell navigation<br />
| That its <code>perl</code> is Strawberry Perl<br />
|-<br />
| Strawberry Perl command line<br />
| Perl modules, wxPerl execution, application tests, packaging<br />
| That Unix paths or MSYS2-specific shell behavior will apply<br />
|}<br />
<br />
A craftsman should know which shop he is standing in.<br />
<br />
== Create the first project directory ==<br />
<br />
Use a simple project for the first complete cycle.<br />
<br />
From the MSYS2 terminal:<br />
<br />
<pre><br />
mkdir -p /c/work/hello-wxperl/screenshots<br />
cd /c/work/hello-wxperl<br />
git init<br />
</pre><br />
<br />
Create a short <code>README.md</code>:<br />
<br />
<pre><br />
# Hello wxPerl<br />
<br />
First wxGlade-generated wxPerl project created while raising the<br />
Perl Lazarus development shop.<br />
</pre><br />
<br />
The directory will eventually contain:<br />
<br />
<pre><br />
hello-wxperl/<br />
├── hello-wxperl.wxg<br />
├── hello-wxperl.pl<br />
├── README.md<br />
└── screenshots/<br />
</pre><br />
<br />
This is intentionally smaller than the structure of a production application.<br />
<br />
The purpose is to prove the cycle before introducing application modules, tests, build directories, installer files, and documentation.<br />
<br />
== Design the first interface in wxGlade ==<br />
<br />
Open wxGlade.<br />
<br />
Create a new application containing:<br />
<br />
* one frame;<br />
* one panel;<br />
* one vertical box sizer;<br />
* one static-text control;<br />
* one button.<br />
<br />
Use names which communicate purpose:<br />
<br />
{| class="wikitable"<br />
! Object<br />
! Suggested name<br />
! Label<br />
|-<br />
| Frame<br />
| <code>MainFrame</code><br />
| The Perl Lazarus Workshop<br />
|-<br />
| Static text<br />
| <code>status_text</code><br />
| The shop is ready.<br />
|-<br />
| Button<br />
| <code>hello_button</code><br />
| Test wxPerl<br />
|}<br />
<br />
Select the root '''Application''' object in the wxGlade object tree.<br />
<br />
Set:<br />
<br />
* output language to '''Perl''';<br />
* wxWidgets compatibility to '''3.0''';<br />
* output path to the project Perl file;<br />
* code generation to '''Single file''';<br />
* and '''Keep user code''' to enabled.<br />
<br />
[[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.]]<br />
<br />
Save the wxGlade project as:<br />
<br />
<pre><br />
C:\work\hello-wxperl\hello-wxperl.wxg<br />
</pre><br />
<br />
Set the Perl output file to:<br />
<br />
<pre><br />
C:\work\hello-wxperl\hello-wxperl.pl<br />
</pre><br />
<br />
Press:<br />
<br />
<pre><br />
Ctrl-G<br />
</pre><br />
<br />
to generate the Perl source.<br />
<br />
The <code>.wxg</code> file is not the Perl program. It is the XML project describing the visual design.<br />
<br />
The <code>.pl</code> file is the code emitted from that design.<br />
<br />
Both are valuable source artifacts and both should be kept in Git.<br />
<br />
<div style="clear:both;"></div><br />
<br />
== Inspect what wxGlade emitted ==<br />
<br />
Return to the MSYS2 terminal:<br />
<br />
<pre><br />
cd /c/work/hello-wxperl<br />
ls -l<br />
vim hello-wxperl.pl<br />
</pre><br />
<br />
Do not immediately begin changing random portions of the generated code.<br />
<br />
First inspect:<br />
<br />
* the packages wxGlade created;<br />
* the frame constructor;<br />
* the controls;<br />
* the sizers;<br />
* the generated identifiers;<br />
* the event-handler placeholders;<br />
* the application class;<br />
* and the final call to the event loop.<br />
<br />
Look for wxGlade's generated-code markers. Their exact form may change among releases, but they identify sections which wxGlade owns and may regenerate.<br />
<br />
The '''Keep user code''' option is intended to preserve code outside those protected generation blocks.<br />
<br />
It is not permission to ignore source control.<br />
<br />
Before adding handwritten behavior, commit the generated baseline:<br />
<br />
<pre><br />
git add hello-wxperl.wxg hello-wxperl.pl README.md<br />
git commit -m "Generate initial wxGlade wxPerl application"<br />
</pre><br />
<br />
Now there is a recoverable point before the first manual edit.<br />
<br />
== Run the generated Perl with Strawberry Perl ==<br />
<br />
Open the Strawberry Perl command-line window.<br />
<br />
Run:<br />
<br />
<pre><br />
cd /d C:\work\hello-wxperl<br />
where perl<br />
perl hello-wxperl.pl<br />
</pre><br />
<br />
The frame should appear with the static text and button.<br />
<br />
The button may not yet perform useful work. That is expected.<br />
<br />
At this stage the entire visual generation path has been verified:<br />
<br />
```text<br />
wxGlade .wxg project<br />
↓<br />
Perl source emission<br />
↓<br />
Strawberry Perl<br />
↓<br />
wxPerl / wxWidgets<br />
↓<br />
Windows frame</div>Adminhttps://wiki.perl-guilds.net/index.php?title=The_Perl_Lazarus_Workshop&diff=375The Perl Lazarus Workshop2026-07-20T04:36:33Z<p>Admin: </p>
<hr />
<div>{{DISPLAYTITLE:The Perl Lazarus Workshop}}<br />
<br />
''This is the second essay in the series [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]. It follows [[The Perl Craftsman Returns to the Windows Desktop]] and explains the tools chosen for the Perl Lazarus Project.''<br />
<br />
A craftsman does not require every tool in his workshop to have been forged by the same smith.<br />
<br />
He requires tools which are sound, tools whose purposes he understands, and tools which can be arranged into a dependable way of working.<br />
<br />
The Perl programmer who wants to build a Windows desktop application already possesses the most important part of the workshop: Perl itself, together with the knowledge accumulated through years of writing scripts, maintaining systems, serving websites, transforming data, communicating with databases, and solving problems which did not arrive in a convenient form.<br />
<br />
What has often been missing is not ability. It is a clear path through the remaining tools.<br />
<br />
Perl has long had graphical toolkits, Windows modules, packaging systems, database drivers, networking libraries, and access to native code. Yet the programmer who asks a simple practical question—<br />
<br />
<blockquote><br />
How do I begin with Perl code and end with a Windows application which another person can install?<br />
</blockquote><br />
<br />
—may discover that the answer is distributed among old documentation, CPAN modules, build systems, archived projects, present-day tools, mailing-list discussions, source repositories, and hard-won experience.<br />
<br />
The [[Developing and Distributing wxPerl Applications on Windows|Perl Lazarus Project workflow]] does not attempt to hide these tools behind an enormous new integrated development environment. Its first objective is more modest and, for the present need, more useful: identify a modern combination which works, explain what each part contributes, and document a journey which another Perl programmer can repeat.<br />
<br />
The resulting workshop consists principally of:<br />
<br />
* Strawberry Perl;<br />
* wxWidgets;<br />
* <code>Alien::wxWidgets</code>;<br />
* wxPerl;<br />
* wxGlade;<br />
* MSYS2, vim, and Git;<br />
* PAR-based packaging tools;<br />
* DLL-discovery tools;<br />
* Inno Setup;<br />
* and a separate clean Windows environment in which the finished work can be tested.<br />
<br />
These tools do not all perform the same kind of work. They form layers.<br />
<br />
Understanding those layers is more valuable than memorizing a list of commands.<br />
<br />
== A workshop, not a monolith ==<br />
<br />
[[File:FreeAPIGUI.png|thumb|right|340px|alt=A wxPerl graphical application running as a Windows executable|The practical objective of the workshop is not merely a Perl script with a window, but a complete Windows application which users can run without installing the developer's toolchain.]]<br />
<br />
The Free Pascal Lazarus IDE provides part of the inspiration for the Perl Lazarus Project because it presents application development as a coherent activity.<br />
<br />
A Lazarus programmer can install an environment, create a project, place controls on a form, connect those controls to code, compile the application, and begin distributing the result. Around that process has grown a productive community of component authors, application developers, teachers, consultants, publishers, support providers, and specialist toolmakers.<br />
<br />
This is more significant than the presence of any one editor or form designer.<br />
<br />
The Lazarus and Free Pascal community demonstrates how a language community can support a practical micro-economy. The compiler may be freely available, but books still require authors. Components require maintainers. Applications require designers, testers, documenters, trainers, and support providers. Businesses and specialist communities still need programmers who understand their particular work.<br />
<br />
Shared tools do not abolish human labor. They make new forms of labor possible.<br />
<br />
Perl does not presently need to reproduce the entire Lazarus IDE in order to benefit from this example. The tools required for an effective Windows workshop already exist. The immediate need is to arrange them coherently.<br />
<br />
The Perl Lazarus Workshop is therefore deliberately plural. One program supplies the Perl environment. Another supplies the graphical library. Another generates the interface code. Another provides a familiar editing shell. Several tools cooperate to construct the executable. Another creates the installer.<br />
<br />
This arrangement may initially appear less elegant than a single commercial IDE. It also has advantages.<br />
<br />
Each tool can be understood independently. Each may be replaced when a better tool appears. The developer is not entirely dependent upon one vendor, one file format, or one abandoned product. The workflow can improve incrementally without requiring the whole workshop to be rebuilt at once.<br />
<br />
<div style="clear:both;"></div><br />
<br />
== Strawberry Perl: the foundation of the Windows shop ==<br />
<br />
The first layer is [https://strawberryperl.com/ Strawberry Perl].<br />
<br />
Strawberry Perl is not merely a Perl interpreter placed on Windows. It provides a native Perl distribution together with the compiler and build tools needed to install a broad range of CPAN modules, including modules containing XS or other native components.<ref>[https://strawberryperl.com/releases.html Strawberry Perl, “Releases”]</ref><br />
<br />
That distinction matters for wxPerl.<br />
<br />
A graphical binding to a substantial C++ library cannot be treated exactly like a small pure-Perl module. Native libraries must be built or supplied in compatible forms. Architectures must match. Compilers, DLLs, headers, and Perl configuration all matter.<br />
<br />
Strawberry Perl gives us a practical foundation upon which that native work can occur.<br />
<br />
It also provides tools which many Perl programmers already know how to use:<br />
<br />
* <code>perl</code>;<br />
* <code>cpan</code> and <code>cpanm</code>;<br />
* <code>gcc</code>;<br />
* <code>gmake</code>;<br />
* and the normal Perl library structure.<br />
<br />
This is one reason the Perl Lazarus Project emphasizes Strawberry Perl rather than requiring the user to construct a custom Perl environment from unrelated pieces.<br />
<br />
The chosen environment should still be treated as a tested combination rather than an abstract promise that every release will work with every other release. The maintained installation page records current, previously tested, experimental, and archived combinations:<br />
<br />
* [[Wx 3.008, Alien::wxWidgets 0.71, Strawberry Perl 5.40.2.1|a previously tested Strawberry Perl 5.40 and Wx 3.008 path]];<br />
* [[Wx 3.009, Alien::wxWidgets 0.73, Strawberry Perl 5.42.2.1 PDL|a newer PDL-oriented Strawberry Perl 5.42 and Wx 3.009 path]];<br />
* and older combinations which remain useful when investigating regressions.<br />
<br />
This distinction between a ''known working profile'' and the ''newest possible profile'' is an exercise in practical wisdom.<br />
<br />
A craftsman may experiment with newer tools. He should not confuse experimentation with a promise to users.<br />
<br />
== wxWidgets: a mature graphical foundation ==<br />
<br />
The graphical foundation beneath wxPerl is [https://wxwidgets.org/ wxWidgets].<br />
<br />
wxWidgets began as an effort to create portable graphical applications for Unix and Windows and later expanded to support additional operating systems and graphical back ends.<ref>[https://wxwidgets.org/about/ wxWidgets, “Overview”]</ref> It supplies windows, dialogs, menus, controls, event handling, drawing facilities, printing support, internationalization, networking helpers, and many other facilities required by desktop applications.<br />
<br />
Its architecture is important.<br />
<br />
wxWidgets does not generally seek to make every application display an entirely artificial set of controls which merely resemble the host operating system. It provides ports which use the facilities of the underlying environment. On Windows, the result can behave and appear like a Windows application rather than like a foreign interface transported unchanged from another platform.<br />
<br />
This supports two related goals.<br />
<br />
First, the application can be familiar to the Windows user.<br />
<br />
Second, the programmer is not necessarily imprisoned within Windows forever. wxWidgets has always been concerned with cross-platform application development, even though this series intentionally concentrates on producing and distributing the Windows version first.<br />
<br />
wxWidgets also has a long history of associated development tools. Its own historical record includes commercial dialog and RAD products such as wxDesigner, while its broader ecosystem has included interface builders, component libraries, language bindings, books, and commercial support.<ref>[https://wxwidgets.org/about/history/ wxWidgets, “History”]</ref><br />
<br />
Readers interested in that longer story should consult [[Perl and wxWidgets RAD on Windows]], which records earlier Perl-capable GUI builders, discontinued packaging environments, and related attempts to provide an integrated Windows application workflow.<br />
<br />
The history matters because the Perl Lazarus Project did not arise in an empty field. It receives working pieces from earlier craftsmen, learns from abandoned paths, and attempts to preserve what can still be used.<br />
<br />
== Alien::wxWidgets: locating and describing the native library ==<br />
<br />
Between wxWidgets and the Perl binding sits <code>Alien::wxWidgets</code>.<br />
<br />
The name “Alien” can sound more mysterious than the function it performs. In the Perl ecosystem, an Alien distribution generally helps locate, build, or describe a non-Perl library needed by Perl modules.<br />
<br />
In this workshop, <code>Alien::wxWidgets</code> provides the bridge between the native wxWidgets installation and the build of wxPerl. It records the information needed to compile and link the Perl binding against a suitable wxWidgets library.<br />
<br />
This layer is one reason version combinations matter.<br />
<br />
The relevant versions of:<br />
<br />
* Strawberry Perl;<br />
* its compiler and runtime;<br />
* wxWidgets;<br />
* <code>Alien::wxWidgets</code>;<br />
* and <code>Wx</code><br />
<br />
must agree sufficiently for the build to complete and the resulting programs to run.<br />
<br />
The installation script being developed for the Perl Lazarus Project exists to make this sequence repeatable. It does not abolish the need to understand the sequence.<br />
<br />
A good installation script should reveal:<br />
<br />
# which version is being installed;<br />
# where it was obtained;<br />
# which command is being run;<br />
# where its output is logged;<br />
# whether the stage succeeded;<br />
# and how the result can be verified.<br />
<br />
Automation is valuable when it preserves successful labor and allows another person to reproduce it. It becomes dangerous when it conceals the state of the workshop from the craftsman who must later repair it.<br />
<br />
== wxPerl: placing wxWidgets in Perl hands ==<br />
<br />
The Perl binding itself is distributed as <code>Wx</code> and is commonly called wxPerl.<br />
<br />
wxPerl allows a Perl program to create and control wxWidgets objects: applications, frames, panels, dialogs, buttons, text controls, lists, grids, notebooks, menus, status bars, timers, drawing contexts, and the many other facilities supplied by wxWidgets.<br />
<br />
This means the Perl programmer can bring existing Perl abilities directly into an event-driven desktop application.<br />
<br />
The database layer may still use DBI.<br />
<br />
The web client may still use familiar HTTP and JSON modules.<br />
<br />
The parser may still be the parser already tested in a command-line program or server process.<br />
<br />
The validation rules may still live in ordinary Perl modules.<br />
<br />
wxPerl does not require the craftsman to abandon the language in which the underlying work is already expressed. It gives that work a graphical point of contact with the user.<br />
<br />
The renewed ability to install and build wxPerl on current Windows environments owes much to the wxPerl revival work led by Johan Vromans and assisted by others who tested, corrected, and documented the modern build path.<ref>[https://dev.to/sciurius/wxperl-revival-5fde Johan Vromans, “wxPerl Revival”]</ref><br />
<br />
The Perl Lazarus Project builds on that labor. It is not a claim to have independently recreated wxPerl. It is an effort to carry the revived binding further into a repeatable development, packaging, and distribution practice.<br />
<br />
The first verification after installation should therefore be visible and concrete. <code>Wx::Demo</code> provides examples of many available controls and facilities, while a minimal application verifies that Perl can create a frame and enter the wxWidgets event loop.<br />
<br />
The third essay, [[Raising a Working wxPerl Shop on Windows]], will perform that verification in detail.<br />
<br />
== wxGlade: visual design which emits Perl ==<br />
<br />
[[File:WxgladeWinExample.png|thumb|left|380px|alt=wxGlade running on Windows while designing an interface for a wxPerl application|wxGlade is written using wxPython, but it can save the interface design as XML and emit Perl source code for a wxPerl application.]]<br />
<br />
wxPerl gives the programmer access to the graphical library, but constructing every interface entirely by hand can involve a large amount of mechanical work.<br />
<br />
Controls must be created, placed in sizers, connected to parent windows, assigned properties, and adjusted repeatedly as the layout develops.<br />
<br />
[https://wxglade.sourceforge.net/ wxGlade] provides a visual design environment for wxWidgets applications. It is written using wxPython, but this does not limit it to Python output. It can generate Python, C++, Perl, Lisp, and XRC.<ref>[https://wxglade.sourceforge.net/ wxGlade, project overview]</ref><br />
<br />
For the Perl Lazarus Workshop, the critical fact is simple:<br />
<br />
<blockquote><br />
wxGlade emits Perl.<br />
</blockquote><br />
<br />
The craftsman can arrange a window visually, save the wxGlade project as a <code>.wxg</code> XML file, and generate a Perl source file containing the corresponding wxPerl classes.<br />
<br />
This makes possible a RAD-like cycle:<br />
<br />
# Design or revise the interface in wxGlade.<br />
# Save the <code>.wxg</code> project.<br />
# Generate Perl.<br />
# Inspect the emitted changes.<br />
# Add or revise application behavior.<br />
# Run the program with Strawberry Perl.<br />
# Return to wxGlade when the visual design changes.<br />
<br />
The [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates wxPerl and wxGlade template repository] contains example interfaces intended as starting points for this process. The templates include familiar window patterns and historical interface recreations which can be opened in wxGlade, examined, changed, and emitted as Perl.<br />
<br />
AI tools have also been effective in producing first-draft wxGlade XML files from natural-language descriptions. Those drafts are not final designs. They are materials brought into the workshop.<br />
<br />
The proper process remains human:<br />
<br />
# describe the intended interface;<br />
# generate or obtain a first-draft <code>.wxg</code> file;<br />
# open it in wxGlade;<br />
# inspect the hierarchy and properties;<br />
# correct the layout;<br />
# emit Perl;<br />
# wire the application behavior;<br />
# review the code;<br />
# and test the result.<br />
<br />
AI may accelerate the preparation of material. It does not determine whether the interface serves the user, whether generated code is safe, or whether the application fulfills its promises.<br />
<br />
The craftsman remains responsible.<br />
<br />
Readers who need ideas for first projects may consult [[GUI ideas for use with wxGlade]].<br />
<br />
<div style="clear:both;"></div><br />
<br />
== MSYS2, vim, and Git: recovering a familiar working rhythm ==<br />
<br />
A Windows application should be built and tested against Strawberry Perl, but the craftsman does not need to abandon a familiar Unix-like editing workflow.<br />
<br />
[https://www.msys2.org/ MSYS2] supplies a Unix-like command-line environment and a package manager for Windows.<ref>[https://www.msys2.org/docs/what-is-msys2/ MSYS2, “What is MSYS2?”]</ref> Within its terminal, the programmer can install vim and Git:<br />
<br />
<pre><br />
pacman -S vim git<br />
</pre><br />
<br />
This creates a productive division of labor.<br />
<br />
The MSYS2 terminal can be used for:<br />
<br />
* editing with vim;<br />
* reviewing diffs;<br />
* committing changes;<br />
* managing branches;<br />
* using SSH keys;<br />
* navigating the project with familiar shell tools;<br />
* and performing the normal source-control work of a Unix-oriented Perl programmer.<br />
<br />
The Strawberry Perl terminal should be used for:<br />
<br />
* installing Perl modules;<br />
* running the wxPerl application;<br />
* executing Perl-oriented build commands;<br />
* creating the executable;<br />
* and verifying behavior against the actual Perl environment intended by the project.<br />
<br />
This separation is not merely a personal preference. Installing Git and related packages in MSYS2 may also install an MSYS2 Perl. Running the application from that shell without checking the active <code>PATH</code> can therefore invoke a different Perl than the Strawberry Perl for which wxPerl was built.<br />
<br />
The programmer should know which Perl is active.<br />
<br />
A workshop may contain two hammers. The craftsman must still know which one he has picked up.<br />
<br />
Git is particularly important when generated code is involved. wxGlade can preserve user code when configured properly, but configuration mistakes and generation changes can still damage handwritten work. A clean commit before generation gives the programmer a truthful record of what changed and a practical way to recover.<br />
<br />
The detailed edit–emit–wire–run workflow belongs to the next essay. Here it is enough to recognize that MSYS2 is not replacing Strawberry Perl. It restores a familiar editing and revision rhythm around it.<br />
<br />
== PAR, wxpar, and the hidden contents of an executable ==<br />
<br />
A working wxPerl script is not yet a distributable Windows product.<br />
<br />
The user should not be required to install Strawberry Perl, compile wxWidgets, install CPAN modules, configure environment variables, or reproduce the developer's workshop.<br />
<br />
PAR-based tools help collect the Perl interpreter, modules, and supporting material into a Windows executable.<br />
<br />
The current workshop uses:<br />
<br />
* <code>PAR::Packer</code>;<br />
* <code>Wx::Perl::Packager</code>, which provides <code>wxpar</code>;<br />
* and <code>App::PP::Autolink</code>, which provides <code>pp_autolink</code>.<br />
<br />
A minimal wxPerl packing command may look simple:<br />
<br />
<pre><br />
wxpar my-application.pl -o my-application.exe<br />
</pre><br />
<br />
The real difficulty is often not the command. It is discovering everything the application needs.<br />
<br />
A script which makes HTTPS requests may depend upon OpenSSL and compression DLLs which were present in Strawberry Perl's directories during development but are not automatically obvious to the packager. The program may work perfectly on the craftsman's computer and fail immediately on the customer's.<br />
<br />
This is why <code>pp_autolink</code> has proven especially valuable in the documented workflow. It helps discover native DLLs which must be linked explicitly into the packed application.<br />
<br />
The packaging layer therefore teaches an important lesson:<br />
<br />
<blockquote><br />
A dependency which is invisible to the developer is not invisible to the user's computer.<br />
</blockquote><br />
<br />
A professional result requires dependency discovery, a repeatable build command, and testing away from the development installation.<br />
<br />
The current [[Developing and Distributing wxPerl Applications on Windows#Creating Windows EXEs|executable-building notes]] preserve this still-developing body of experience, including special cases involving HTTPS and <code>Net::SSLeay</code>.<br />
<br />
== Martha: assistance at the difficult boundary ==<br />
<br />
The tool named Martha belongs near the far end of the workshop, not at its foundation.<br />
<br />
Martha does not replace Strawberry Perl, wxPerl, wxGlade, PAR, or Inno Setup. It is a wxPerl application created to assist with the difficult transition from a working Perl program to a package which can be installed and tested.<br />
<br />
Its present work includes assistance with:<br />
<br />
* discovering required DLLs;<br />
* generating a Makefile based on <code>wxpar</code>;<br />
* allowing that Makefile to be reviewed and adjusted;<br />
* running the executable build;<br />
* generating an Inno Setup configuration;<br />
* building the installer;<br />
* and testing the resulting stages.<br />
<br />
The name is related to Lazarus, but Martha's role is deliberately practical. The Perl Lazarus Project describes the larger revival and workflow. Martha helps with some of the work which is repetitive, error-prone, and easy to perform inconsistently.<br />
<br />
The important principle is that the helper should expose the process rather than make it unknowable. The programmer should be able to inspect the generated Makefile, see the DLL paths, read the Inno Setup script, and reproduce the command outside the GUI.<br />
<br />
A good tool assists judgment. It does not demand the surrender of judgment.<br />
<br />
For current details, see [[Developing and Distributing wxPerl Applications on Windows#Martha - A lightweight wxPerl helper for packaging Perl applications on Windows|Martha's role in the documented workflow]].<br />
<br />
== Inno Setup: placing the work into the user's hands ==<br />
<br />
The final major tool in the workshop is [https://jrsoftware.org/isinfo.php Inno Setup].<br />
<br />
A Windows executable can sometimes be distributed as a portable file, but ordinary Windows users commonly expect an installer. The installer can:<br />
<br />
* place program files in an appropriate directory;<br />
* create a Start menu entry;<br />
* create an optional desktop shortcut;<br />
* register an uninstaller;<br />
* preserve or update configuration;<br />
* install additional resources;<br />
* record version information;<br />
* and provide a familiar route for upgrades and removal.<br />
<br />
Inno Setup has existed since 1997 and provides a mature scriptable installer system for Windows.<ref>[https://jrsoftware.org/isinfo.php JRSoftware, “What is Inno Setup?”]</ref><br />
<br />
It also offers a good example of a tool which empowers apprentices, hobbyists, nonprofits, and small developers while reasonably asking commercial users to support the human labor behind it.<br />
<br />
The Inno Setup authors request that commercial users purchase a commercial license.<ref>[https://jrsoftware.org/isorder.php JRSoftware, “Inno Setup Commercial Licenses”]</ref> The request should be respected.<br />
<br />
A Perl craftsman who expects users to compensate his own labor should not treat the labor of toolmakers as though it appeared without cost or obligation.<br />
<br />
The license is not merely an administrative detail. It is part of a just relationship among craftsmen.<br />
<br />
Inno Setup lowers the barrier to professional Windows distribution. It allows a small developer to offer an installation experience which might otherwise require a substantial commercial packaging product or a large amount of custom engineering. When that tool contributes to commercial income, purchasing the requested license is an orderly acknowledgment of the value received.<br />
<br />
The installer itself must also respect the user.<br />
<br />
It should not request administrative privileges without need. It should not overwrite user-created data carelessly. It should not make removal intentionally difficult. It should not hide unrelated software in the package. It should explain what it is installing and preserve what the user has created.<br />
<br />
The installer is not wrapping placed around the “real application.”<br />
<br />
For the user, installation is the beginning of the application.<br />
<br />
== The living workshop and the written recipe ==<br />
<br />
The exact working version combination will change.<br />
<br />
Strawberry Perl will release new builds. wxWidgets will advance. <code>Alien::wxWidgets</code> and <code>Wx</code> will be updated. wxGlade will correct problems and add features. Packaging tools will discover new edge cases. Windows will alter security behavior.<br />
<br />
A book or essay cannot freeze the workshop forever.<br />
<br />
This is why the series and the technical wiki serve different but complementary purposes.<br />
<br />
The essays explain:<br />
<br />
* why the tools were selected;<br />
* how the layers relate;<br />
* what kind of work each tool performs;<br />
* and what virtues should govern their use.<br />
<br />
The living installation page records:<br />
<br />
* current download links;<br />
* tested version combinations;<br />
* experimental combinations;<br />
* archived combinations;<br />
* command lines;<br />
* known failures;<br />
* and corrections discovered through practice.<br />
<br />
The craftsman should consult both.<br />
<br />
A static essay without maintained instructions may become historically interesting but practically useless.<br />
<br />
A list of commands without an explanation of the workshop may work once while leaving the programmer unable to understand or repair it.<br />
<br />
Tradition requires both inherited wisdom and living application.<br />
<br />
== The craft and the virtue ==<br />
<br />
This stage of the journey is governed especially by practical wisdom, gratitude, justice, and humility.<br />
<br />
Practical wisdom asks what each tool is for.<br />
<br />
It prevents the programmer from selecting software merely because it is fashionable, entirely written in a preferred language, or advertised as capable of doing everything.<br />
<br />
Gratitude recognizes that the workshop is inherited.<br />
<br />
God is the source of creation, intelligence, talent, and opportunity. The programmer receives not only his own abilities, but also a world of prior human labor: operating systems, compilers, libraries, modules, editors, books, standards, and examples.<br />
<br />
<blockquote><br />
“For wisdom is better than all the most precious things: and whatsoever may be desired cannot be compared to it.”<br />
<br />— Proverbs 8:11, Douay-Rheims<br />
</blockquote><br />
<br />
Justice gives the human makers of those tools what is due to them.<br />
<br />
That may include:<br />
<br />
* obeying licenses;<br />
* preserving notices;<br />
* paying a reasonable commercial fee;<br />
* reporting defects honestly;<br />
* acknowledging authors;<br />
* contributing corrections;<br />
* supporting maintainers;<br />
* or teaching another person what one has learned.<br />
<br />
Humility acknowledges that no one programmer created the entire workshop.<br />
<br />
The experienced Perl programmer may know far more about databases or server operations than the author of a GUI builder. The GUI-tool author may know far more about layout engines and code generation. The installer author may understand Windows installation behavior which the application programmer has never had to consider.<br />
<br />
The guild-minded craftsman does not resent this dependence. Human beings are made to receive from and contribute to one another.<br />
<br />
The tools themselves must remain properly ordered.<br />
<br />
Strawberry Perl serves the Perl programmer.<br />
<br />
wxWidgets serves the graphical application.<br />
<br />
wxGlade serves the designer.<br />
<br />
MSYS2 and vim serve the editing process.<br />
<br />
Git serves truthful revision and recovery.<br />
<br />
PAR serves distribution.<br />
<br />
Inno Setup serves installation.<br />
<br />
AI may assist preparation, explanation, and first drafts.<br />
<br />
None of them is the master.<br />
<br />
The human craftsman remains responsible for choosing the purpose, judging the result, keeping promises, protecting the user, and directing the work toward the good.<br />
<br />
== At the workbench: draw your workshop map ==<br />
<br />
Before installing the full stack, prepare a workshop inventory.<br />
<br />
{| class="wikitable"<br />
|+ The Perl Lazarus Workshop<br />
! Layer<br />
! Selected tool<br />
! Work performed<br />
! Verification<br />
|-<br />
| Perl environment<br />
| Strawberry Perl<br />
| Runs Perl and supplies native build tools<br />
| Confirm the intended <code>perl.exe</code>, architecture, and compiler<br />
|-<br />
| Native GUI library<br />
| wxWidgets<br />
| Supplies windows, controls, events, and platform integration<br />
| Confirm the wxWidgets version used by wxPerl<br />
|-<br />
| Native-library bridge<br />
| <code>Alien::wxWidgets</code><br />
| Describes or supplies the wxWidgets build used by Perl<br />
| Query the installed module version and build configuration<br />
|-<br />
| Perl GUI binding<br />
| <code>Wx</code> / wxPerl<br />
| Makes wxWidgets available to Perl<br />
| Run a minimal frame and <code>Wx::Demo</code><br />
|-<br />
| Visual designer<br />
| wxGlade<br />
| Saves the visual design and emits Perl or XRC<br />
| Generate and run a small Perl interface<br />
|-<br />
| Editing environment<br />
| MSYS2 and vim<br />
| Supplies a familiar Unix-like editing shell<br />
| Confirm vim and the project paths<br />
|-<br />
| Revision control<br />
| Git<br />
| Preserves history, diffs, and recoverable checkpoints<br />
| Create a repository and commit the generated project<br />
|-<br />
| Executable packaging<br />
| PAR, <code>wxpar</code>, and <code>pp_autolink</code><br />
| Packages Perl and discovers native dependencies<br />
| Run the EXE outside the Strawberry Perl terminal<br />
|-<br />
| Installer<br />
| Inno Setup<br />
| Produces the Windows installation experience<br />
| Install, launch, upgrade, and uninstall on a clean machine<br />
|-<br />
| Independent test bench<br />
| Clean Windows virtual machine or physical system<br />
| Reveals dependencies accidentally supplied by the workshop<br />
| Test without Strawberry Perl or the development tools installed<br />
|}<br />
<br />
For each tool, answer:<br />
<br />
# What exact task does it perform?<br />
# Which other layer does it depend upon?<br />
# Which version has actually been tested?<br />
# How will success be verified?<br />
# Where will installation and build logs be kept?<br />
# What license governs its use?<br />
# What labor and knowledge did its authors contribute?<br />
# What would happen to the workflow if the tool disappeared?<br />
# Is the project data stored in an open or inspectable format?<br />
# Can the important build steps be reproduced without a graphical helper?<br />
<br />
The purpose is not to produce paperwork for its own sake.<br />
<br />
The map helps the craftsman understand his shop before something breaks.<br />
<br />
== Continue the journey ==<br />
<br />
The next essay, [[Raising a Working wxPerl Shop on Windows]], will assemble this workshop in practice.<br />
<br />
It will cover:<br />
<br />
* selecting a tested Strawberry Perl profile;<br />
* using the Perl Lazarus installation BAT file;<br />
* preserving installation logs;<br />
* verifying <code>Alien::wxWidgets</code> and <code>Wx</code>;<br />
* running <code>Wx::Demo</code>;<br />
* installing and launching wxGlade;<br />
* configuring MSYS2, vim, and Git;<br />
* generating the first Perl GUI;<br />
* wiring an event;<br />
* running it under Strawberry Perl;<br />
* and committing the result.<br />
<br />
At the end of that essay, the reader should possess more than a collection of installed programs.<br />
<br />
He should possess a working shop, a generated wxPerl application, a known active Perl environment, and the beginning of a repeatable craft.<br />
<br />
<references /><br />
<br />
{{DEFAULTSORT:Perl Lazarus Workshop}}<br />
<br />
'''Previous essay:''' [[The Perl Craftsman Returns to the Windows Desktop]]<br />
<br />
'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Next essay:''' [[Raising a Working wxPerl Shop on Windows]]<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]<br />
[[Category:Perl Guilds]]<br />
[[Category:Windows]]<br />
[[Category:Strawberry Perl]]<br />
[[Category:wxWidgets]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=The_Perl_Craftsman_Returns_to_the_Windows_Desktop&diff=374The Perl Craftsman Returns to the Windows Desktop2026-07-19T21:26:35Z<p>Admin: </p>
<hr />
<div>{{DISPLAYTITLE:The Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
''This is the first essay in the series [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]. The series follows the practical journey from Perl programmer to craftsman of complete, distributable Windows applications.''<br />
<br />
There comes a point in the life of a programmer when experience can become strangely tiring.<br />
<br />
The journeyman Perl programmer may have crossed many territories. He has repaired old systems, migrated databases, parsed uncooperative data, automated jobs, maintained web applications, connected APIs, managed servers, and rescued programs whose original authors disappeared years ago. He may have spent decades learning that the apparently simple problem is rarely simple, that data supplied by users never quite resembles the example, and that the machine which fails is usually not the machine on which the software was developed.<br />
<br />
The master Perl programmer may have done all of this while teaching others, supporting clients, maintaining community infrastructure, and carrying responsibility for systems which cannot simply be turned off and rewritten in the fashionable language of the year.<br />
<br />
Such a programmer is not obsolete. He may only be weary.<br />
<br />
The repeated announcement of Perl's death can become tiresome. So can working continually behind the scenes while newer communities rediscover techniques that Perl programmers have practiced for decades. The experienced Perl programmer may understandably ask whether there is any new territory worth crossing, or whether his remaining work consists only of maintaining what other people have abandoned.<br />
<br />
At the same time, a newer programmer may sit in front of a Windows computer and never encounter Perl at all. He may know that programs come from an application store, a game launcher, a download page, or a Git repository, but not yet understand that he can create those programs himself. He may be experimenting with game modifications, running a private server, editing configuration files, automating a repetitive task, or wondering how a favorite program works.<br />
<br />
He may, quite literally, be playing video games.<br />
<br />
Playing a game is not a lesser or shameful use of a computer. Recreation has its proper place. Yet games often place young people near modding, scripting, servers, digital art, online communities, hardware, configuration files, and technical curiosity. These can become entrances into a genuine craft.<br />
<br />
Some future Perl programmer is probably using a Windows computer right now without knowing that Perl exists.<br />
<br />
This series is addressed to both: the experienced craftsman who may need a new application for an old and powerful trade, and the prospective apprentice who has not yet discovered that programming can become his own craft.<br />
<br />
== The programmer as craftsman ==<br />
<br />
The language of the craftsman is useful because programming is not merely the manipulation of symbols. It is the application of knowledge, judgment, practiced skill, and responsibility to a human need.<br />
<br />
God is the Creator of the world, of the human person, and of every good thing upon which human work depends. The materials of the earth, the order discoverable within creation, the human capacity to reason, and the time and opportunity in which we work are not self-created possessions. They are gifts entrusted to us.<br />
<br />
Our talents also come from God. Intelligence, imagination, memory, patience, physical ability, experience, and the capacity to learn may be cultivated through discipline, but we did not first give these powers to ourselves.<br />
<br />
<blockquote><br />
“What hast thou that thou hast not received?”<br />
<br />— 1 Corinthians 4:7, Douay-Rheims<br />
</blockquote><br />
<br />
The programmer therefore creates only in a secondary and dependent sense. He does not create from nothing. He receives a world already made, abilities already given, knowledge preserved through the labor of others, and tools built by other craftsmen. Through his own labor he may then cultivate, combine, order, transform, and apply these gifts in ways which serve other persons.<br />
<br />
This dependence does not make human work insignificant. It gives work its proper dignity and purpose. Human labor is one of the means by which men and women develop the gifts of creation, provide for their families, serve their neighbors, form communities, and contribute to the common good.<br />
<br />
Work is ordered toward the good of persons because the human person is created by God and possesses a dignity which no employer, market, government, machine, or measure of productivity can bestow or remove. The programmer does not exist for the software, the company, or the market. Software, companies, and markets exist to serve human life and human communities.<br />
<br />
A technically impressive application which deceives its customers, degrades its workers, burdens its users, corrupts their work, or treats persons merely as sources of data and revenue cannot be considered excellent craftsmanship.<br />
<br />
The traditional progression from apprentice to journeyman to master should not be treated as a rigid credentialing system or as an excuse for excluding newcomers. It is a way of describing growth within a trade.<br />
<br />
* The '''apprentice''' learns the tools, vocabulary, habits, and established practices of the craft.<br />
* The '''journeyman''' can travel beyond the workshop in which he first learned and apply his skills to unfamiliar problems.<br />
* The '''master''' accepts responsibility for complete work, judges its quality, serves customers, preserves knowledge, and helps form other craftsmen.<br />
<br />
These names describe differences in skill, experience, and responsibility. They do not describe differences in human worth. The apprentice, journeyman, master, customer, and user possess the same God-given dignity.<br />
<br />
Mastery is achieved through the development of received talents, disciplined labor, experience, instruction, and grace. It gives the master greater responsibility, but it does not make him a higher kind of human being. Greater mastery creates greater obligations of honesty, patience, justice, humility, service, and care.<br />
<br />
The master should therefore receive the apprentice not merely as inexpensive labor, but as a person whose gifts should be discovered, cultivated, corrected, and encouraged.<br />
<br />
A journeyman is not merely someone who has memorized more syntax than an apprentice. He has learned how to proceed when the documentation is incomplete, the operating environment is unfamiliar, and the first solution does not work.<br />
<br />
A master is not someone who has stopped learning. He is someone whose experience has taught him the weight of a promise. When he says that a program can be installed, can preserve a user's data, or can be supported in a particular environment, he understands that another person's work may depend upon that claim.<br />
<br />
A master should also understand that knowledge is not diminished when it is handed on. The formation of an apprentice does not create a competitor who has stolen part of the master's trade. It strengthens the craft, preserves accumulated experience, and prepares another person to perform useful work.<br />
<br />
A masterwork is therefore not merely a clever algorithm, an ingenious regular expression, or an impressive piece of code. It is work brought to completion.<br />
<br />
For a Windows desktop application, that completion may include:<br />
<br />
* a useful and understandable graphical interface;<br />
* dependable handling of files and data;<br />
* communication with an existing Perl web service;<br />
* a Windows executable;<br />
* a familiar installer;<br />
* useful documentation;<br />
* testing on a computer other than the developer's;<br />
* a reasonable upgrade and uninstallation path;<br />
* and a plan for supporting the people who use it.<br />
<br />
The purpose of [[Main Page|Perl Guilds]] is to encourage this fuller understanding of the programmer's trade: independent programmers sharing knowledge, cultivating practical specialties, forming one another in the craft, and helping one another earn a living through useful work.<br />
<br />
== An invitation to the weary journeyman ==<br />
<br />
The experienced Perl programmer already possesses much of what is needed to build a valuable desktop application.<br />
<br />
He may know how to:<br />
<br />
* validate and transform data;<br />
* communicate with databases;<br />
* consume and publish APIs;<br />
* process text, images, or scientific data;<br />
* operate remote services;<br />
* automate complex workflows;<br />
* authenticate users;<br />
* generate reports;<br />
* maintain compatibility;<br />
* and diagnose failures in production.<br />
<br />
These abilities do not become irrelevant when a graphical interface is added. They become the substance behind the interface.<br />
<br />
The desktop is not a repudiation of the server work in which Perl programmers have excelled. It is another point at which that work can be placed into the hands of a user.<br />
<br />
A Perl programmer who has spent years building web applications may create a Windows client for one of those applications. A systems programmer may create an administrative console. A scientific programmer may package a model or data-analysis workflow for colleagues who will never use a command line. A collector, historian, translator, accountant, engineer, or small-business owner may need a specialized application which no large software company would consider profitable enough to build.<br />
<br />
The weary journeyman need not begin again as though his past experience counted for nothing. He must learn a new portion of the trade, but he brings his existing judgment with him.<br />
<br />
He already understands that a network can fail, that data must be validated, that an upgrade can damage a working system, and that a user who reports a problem is not necessarily mistaken. These lessons are harder to acquire than the syntax for creating a button.<br />
<br />
Learning wxPerl does not erase the journeyman's experience. It gives that experience another visible form.<br />
<br />
Perl is not the obstacle. Perl is the leverage.<br />
<br />
== An invitation to the future apprentice ==<br />
<br />
Perl also needs new programmers, and many potential programmers are sitting in front of Windows computers right now.<br />
<br />
It is impossible to count all future programmers before they discover the craft. We can, however, observe where ordinary desktop users are. Windows remains the dominant desktop operating-system family in worldwide usage measurements.<ref>[https://gs.statcounter.com/os-market-share/desktop/worldwide StatCounter Global Stats, “Desktop Operating System Market Share Worldwide”]</ref> It is also overwhelmingly prevalent among the participants in Valve's Steam hardware survey.<ref>[https://store.steampowered.com/hwsurvey/ Valve, “Steam Hardware &amp; Software Survey”]</ref><br />
<br />
Many of these users are playing games, installing modifications, running Discord communities, hosting servers, editing configuration files, experimenting with hardware, or trying to automate some irritating part of their digital lives. These activities are not programming apprenticeships by themselves, but they are often close to the doorway.<br />
<br />
A person who asks, “Can I change how this game behaves?” is already asking a programmer's question.<br />
<br />
A person who runs a private game server has begun to encounter networking, configuration, permissions, logs, backups, updates, and failure recovery.<br />
<br />
A person who installs a modification has begun to discover dependencies, version compatibility, file layouts, and the difference between a working installation and a broken one.<br />
<br />
A person who writes a small script to rename files or process game data has begun to discover that the computer can be instructed rather than merely consumed.<br />
<br />
If Perl wishes to recruit another generation, Perl programmers must be willing to meet prospective programmers where they are. That includes Windows.<br />
<br />
It is not enough to tell a Windows user that serious programmers eventually abandon his environment. It is better to show him that the computer he already owns can become a workshop; that Strawberry Perl gives him a native Perl environment; that wxPerl can create real graphical applications; and that the same language can later take him into web services, databases, systems work, scientific computing, graphics, automation, and many other fields.<br />
<br />
The route into the craft should not require the apprentice first to adopt the operating-system preferences of the master.<br />
<br />
A healthy guild does not merely preserve the techniques of its existing members. It invites new apprentices, gives them real work appropriate to their abilities, and allows them to grow into responsibility.<br />
<br />
== Why return to the desktop? ==<br />
<br />
Perl programmers have long been especially effective behind the scenes.<br />
<br />
Perl may collect the data, operate the website, maintain the database, run the scientific model, communicate with an outside service, or generate the report. The ordinary user may benefit from all of this without ever seeing Perl directly.<br />
<br />
That is not a defect. Invisible infrastructure is often excellent work.<br />
<br />
Nevertheless, the Windows desktop offers another place for the Perl craftsman to practice his trade: directly in front of the person whose work the software is intended to serve.<br />
<br />
A desktop application may:<br />
<br />
* organize files already stored on the user's computer;<br />
* provide a specialized editor or research interface;<br />
* display data from a remote Perl application;<br />
* upload images or documents for server-side processing;<br />
* present results from a database or API;<br />
* allow local work when the network is unavailable;<br />
* interact with devices or other applications installed on the computer;<br />
* or provide a richer companion to an existing website.<br />
<br />
A service such as [https://boyscoutpatch.info/ BoyScoutPatch.info], for example, may continue to perform centralized work for which a web application is well suited, while a desktop client could provide a more specialized workflow for collectors, researchers, or administrators.<br />
<br />
The desktop application and web application need not compete. Each can perform the work suited to it.<br />
<br />
The server may maintain shared data, perform expensive searches, coordinate users, apply centralized business rules, or execute processing which requires resources not available on the user's machine.<br />
<br />
The desktop application may manage local files, provide richer interaction, preserve partially completed work, integrate with the user's operating system, and continue performing some tasks when the network is unavailable.<br />
<br />
This is an application of subsidiarity. The server should perform work which genuinely belongs on the server. The desktop should perform work which is best placed in the user's hands. Larger systems should support the user, the independent programmer, and the local organization where their resources are genuinely needed, without unnecessarily taking away work and responsibility which can be competently exercised at the more immediate level.<br />
<br />
Subsidiarity does not require isolation. It must be joined to solidarity. The individual programmer, the guild, the toolmaker, the server operator, and the user may depend upon one another. The objective is not to abandon the smaller participant, but to strengthen him without absorbing every responsibility into a distant centralized system.<br />
<br />
The goal is not to replace every web application with a desktop program. It is to place each responsibility where it can be performed most effectively, while avoiding needless centralization and needless dependence upon a permanent network connection.<br />
<br />
== Why Windows? ==<br />
<br />
This series deliberately focuses on Windows.<br />
<br />
That does not imply that Windows is the only worthy platform, or that wxPerl cannot be useful elsewhere. It means that a craftsman must eventually choose a definite workshop and a definite group of users.<br />
<br />
Windows offers several practical advantages for this undertaking.<br />
<br />
First, Windows has a very large population of ordinary desktop users. That population includes customers, office workers, researchers, collectors, students, gamers, and prospective programmers.<br />
<br />
Second, specialized commercial desktop software is familiar on Windows. Users understand the idea of downloading an application, running an installer, finding the program in the Start menu, and paying for a tool which performs useful work.<br />
<br />
Third, Windows has an unusually strong culture of backward application compatibility. Microsoft describes application compatibility as an intentional design concern and recognizes that developers and customers expect applications in which they have invested to continue working.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/key-changes-since-windows-7-to-ensure-compatibility Microsoft Learn, “Key changes since Windows 7 to ensure compatibility”]</ref> Microsoft has also stated that it goes to great lengths to preserve application and device compatibility when operating-system versions change.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/windows-version-check Microsoft Learn, “Windows version check”]</ref><br />
<br />
Windows application manifests can even allow newer versions of the operating system to provide behaviors expected by software targeting earlier releases.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/application-executable-manifest Microsoft Learn, “App executable manifest”]</ref><br />
<br />
No compatibility promise is absolute. Security changes, removed components, architecture changes, obsolete drivers, unavailable libraries, and undocumented assumptions can still break old programs. Nevertheless, Windows demonstrates an unusually strong expectation that software written for an earlier generation should continue to function.<br />
<br />
At times, Windows' compatibility expectations appear even more extreme than Perl's own.<br />
<br />
That expectation matters to the independent craftsman.<br />
<br />
A specialized application may serve a modest community for many years. Its value may come from stability rather than constant reinvention. A program which continues working through several generations of hardware and operating systems can repay its development cost many times over.<br />
<br />
The author's own experiments with ActivePerl 5.8.8 on Windows 98 illustrate the remarkable historical reach of both ecosystems. This does not mean that new commercial software should target Windows 98. It means that the craftsman should recognize the strategic value of technologies which respect existing work.<br />
<br />
Fourth, Strawberry Perl provides a serious native Windows Perl environment. It includes Perl, a compiler, build utilities, and access to the CPAN ecosystem. The Windows programmer is not confined to a toy interpreter or an imitation of a Unix system.<br />
<br />
Finally, many Perl programmers already use Windows as a daily working environment, and many possible new Perl programmers begin there.<br />
<br />
The choice is therefore practical rather than ideological.<br />
<br />
The question is not, “Which operating system proves that I am a proper programmer?”<br />
<br />
The question is, “Where can existing Perl knowledge be turned into useful software, and where can new craftsmen be invited into the trade?”<br />
<br />
== Extreme compatibility creates an opportunity ==<br />
<br />
Windows' backward compatibility does more than preserve old software. It encourages a particular kind of small-scale production.<br />
<br />
A large vendor may prefer subscriptions, rapid replacement, cloud dependence, forced upgrades, and frequent redesign. An independent craftsman may instead produce a focused application which performs one job well and continues doing it for a long time.<br />
<br />
That application might serve only a few hundred users. It might serve a laboratory, a local company, a collecting community, a nonprofit, or a narrow professional field. Its market may be too small for a major software firm but large enough to support the person who understands the problem.<br />
<br />
Long-lived desktop software also creates continuing forms of useful labor:<br />
<br />
* installation;<br />
* customization;<br />
* data conversion;<br />
* training;<br />
* compatibility maintenance;<br />
* support;<br />
* integration with newer services;<br />
* and carefully managed upgrades.<br />
<br />
Backward compatibility does not eliminate this labor. It gives the labor a durable foundation.<br />
<br />
The programmer can improve the application without forcing every user to abandon previous work. The user can invest time learning a tool with some confidence that the tool will not disappear merely because an investor has changed direction or a remote service has been discontinued.<br />
<br />
This relationship between craftsman and user is especially important in a guild-minded approach to software. The programmer is not merely attempting to capture attention, collect data, or make cancellation difficult. He is accepting responsibility for an instrument another person may use in his own work.<br />
<br />
The user's investment matters. The user may have spent hours learning the software, entering data, developing procedures, training employees, or creating records which must be preserved. Backward compatibility is therefore not merely a technical convenience. It is a way of respecting labor already performed.<br />
<br />
== From a working script to a Windows product ==<br />
<br />
A Perl script and a Windows product may contain the same essential program logic, but the user's experience is very different.<br />
<br />
{| class="wikitable"<br />
|+ From the developer's program to the user's product<br />
! The developer may have<br />
! The Windows user reasonably expects<br />
|-<br />
| A <code>.pl</code> file<br />
| An application which starts from an icon<br />
|-<br />
| Installed CPAN modules<br />
| No requirement to install Perl or dependencies<br />
|-<br />
| Commands entered in a terminal<br />
| A graphical interface<br />
|-<br />
| Paths which work on the development computer<br />
| Correct installation and user-data directories<br />
|-<br />
| Diagnostic output in a console<br />
| Understandable errors and useful logs<br />
|-<br />
| A program which works in the workshop<br />
| A program which works on the user's computer<br />
|-<br />
| A collection of build commands<br />
| A repeatable installer and upgrade procedure<br />
|-<br />
| Personal knowledge of hidden dependencies<br />
| A package containing everything the application needs<br />
|}<br />
<br />
The difficult question is therefore not merely whether Perl can display a graphical window. It can.<br />
<br />
The difficult question is whether we can establish a clear and repeatable path from the Perl programmer's existing skills to software which an ordinary Windows user can install and use.<br />
<br />
That is the purpose of the [[Developing and Distributing wxPerl Applications on Windows|Perl Lazarus Project's documented Windows workflow]].<br />
<br />
== The Perl Lazarus journey ==<br />
<br />
[[File:perl-lazarus-project-workflow.png|thumb|right|420px|alt=Six-stage Perl Lazarus Project workflow from installing the development stack through testing the finished Windows application|The Perl Lazarus Project follows a complete path: install the stack, design the GUI, write the Perl code, package the executable, build the installer, and test the result on Windows.]]<br />
<br />
The Perl Lazarus Project builds upon the renewed wxPerl work associated with Johan Vromans and others in the wxPerl community.<ref>[https://dev.to/sciurius/wxperl-revival-5fde Johan Vromans, “wxPerl Revival”]</ref><br />
<br />
It comes out of the larger work of Perl Guilds: supporting independent Perl programmers who seek to make a living through their trade, preserve practical knowledge, and place powerful tools into the hands of individual craftsmen and smaller communities.<ref>Brett Estrade, “Perl Lazarus Project,” presentation for the Summer 2026 Perl Community Conference, Austin, Texas.</ref><br />
<br />
The name points first to Lazarus of the Bible, raised from the dead after four days. It is a fitting image for bringing renewed life to practical GUI development in Perl. The necessary modules and tools were not entirely gone, but the path among them had become difficult to see and difficult to follow.<br />
<br />
The name also acknowledges the example of the [https://www.lazarus-ide.org/ Lazarus IDE and Free Pascal community]. Lazarus demonstrates what can happen when a programming community joins a language, a visual designer, component libraries, documentation, packaging practices, examples, books, support, consulting, and application development.<br />
<br />
The deeper inspiration is not merely the interface of an integrated development environment. It is the presence of a complete culture of application production.<br />
<br />
Perl does not necessarily need a single enormous Lazarus-like IDE. It needs a clear path which craftsmen can follow:<br />
<br />
# Install a known working development stack.<br />
# Design the interface.<br />
# Generate and write Perl code.<br />
# Package the application as an executable.<br />
# Build a Windows installer.<br />
# Test the installed program on a clean Windows system.<br />
<br />
The significance of this path is not that any individual step is unknown. Perl already has a native Windows distribution, graphical bindings, interface-design tools, packaging modules, and installer technology. The missing element has been a coherent and repeatable journey connecting them.<br />
<br />
The present stack joins Strawberry Perl, wxWidgets, wxPerl, wxGlade, PAR-based packaging tools, and Inno Setup. The next essay, [[The Perl Lazarus Workshop]], will explain why these tools belong together and what role each one performs in the craftsman's workshop.<br />
<br />
The series will then proceed through installation, visual design, the wxGlade-to-Perl development cycle, application structure, local data, communication with Perl web services, executable creation, installer construction, testing, support, and the possibility of earning a livable wage through useful applications.<br />
<br />
<div style="clear:both;"></div><br />
<br />
[[File:nhc-advisory-explorer-windows.png|thumb|left|380px|alt=NHC Advisory Explorer running as a packaged Windows desktop application|The NHC Advisory Explorer demonstrates the practical result: a wxPerl program packaged for ordinary Windows users.]]<br />
<br />
This is not merely a theoretical possibility. The [https://github.com/StormSurgeLive/nhc-advisory-gui NHC Advisory Explorer] is one example of a wxPerl program packaged for Windows users.<ref>[https://github.com/StormSurgeLive/nhc-advisory-gui StormSurgeLive, “NHC Advisory Explorer”]</ref><br />
<br />
The program retrieves and presents National Hurricane Center advisory information through a familiar desktop interface. More importantly for this series, it demonstrates that the complete path can be followed: a Perl application can be given a graphical interface, packaged as a Windows executable, placed into an installer, and distributed to users who do not need to install Perl or understand the application's dependencies.<br />
<br />
That final point is essential.<br />
<br />
The Perl programmer may know that the application depends upon Strawberry Perl, wxPerl, wxWidgets, CPAN modules, native DLLs, and packaging tools. The user should ordinarily experience only a Windows application which installs and runs in the expected way.<br />
<br />
The language remains the craftsman's advantage. It does not need to become the customer's burden.<br />
<br />
Readers who want to examine earlier tools and historical attempts at wxWidgets rapid application development in Perl may also consult [[Perl and wxWidgets RAD on Windows]].<br />
<br />
<div style="clear:both;"></div><br />
<br />
== The craft and the virtue ==<br />
<br />
The virtues themselves are discussed elsewhere in the [[Portal:Essays about The Virtuous Perl Programmer|Virtuous Perl Programmer]] material. Here our concern is how they direct the work at hand.<br />
<br />
'''Practical wisdom, or prudence, not laziness''' asks the craftsman to identify a genuine human good and choose fitting means of attaining it.<br />
<br />
For the weary journeyman or master, prudence may require learning a new part of the trade rather than endlessly repeating familiar server-side work. Existing Perl experience is not discarded. It is redirected and extended.<br />
<br />
For the apprentice, prudence means refusing the temptation to skip directly to a polished commercial product without first learning the underlying tools and workflow.<br />
<br />
<blockquote><br />
“Wherefore I wished, and understanding was given me: and I called upon God, and the spirit of wisdom came upon me.”<br />
<br />— Wisdom 7:7, Douay-Rheims<br />
</blockquote><br />
<br />
Automation does not eliminate the importance of labor, but neither is human labor the first cause of creation or goodness.<br />
<br />
God alone is Creator in the proper sense. The earth and its materials, the natural order, the human person, reason, imagination, skill, time, opportunity, and the capacity to work are gifts from Him. Human beings create none of these things from nothing.<br />
<br />
Within that created order, however, the earthly goods which human society cultivates, fashions, organizes, preserves, repairs, and exchanges depend upon human labor acting upon gifts received from God. Labor adds form, usefulness, knowledge, order, accessibility, and service to what has been given.<br />
<br />
The programmer's abilities are therefore neither meaningless accidents nor entirely self-made possessions. They are talents entrusted to him. He has a duty to develop them, use them honestly, and direct them toward good purposes.<br />
<br />
<blockquote><br />
“Every best gift, and every perfect gift, is from above, coming down from the Father of lights.”<br />
<br />— James 1:17, Douay-Rheims<br />
</blockquote><br />
<br />
A tool preserves earlier labor and allows new labor to be applied more effectively, but the tool does not give itself a worthy purpose. It does not recognize the user's dignity, determine what justice requires, accept responsibility for an error, repent of deception, or choose to serve the common good.<br />
<br />
A compiler contains the accumulated labor of its authors and maintainers.<br />
<br />
A GUI designer preserves knowledge about widgets, layouts, serialization, and code generation.<br />
<br />
A Perl module contains work which another programmer has made reusable.<br />
<br />
An installer builder embodies years of experience with Windows installation, upgrades, shortcuts, permissions, and uninstallation.<br />
<br />
A body of documentation preserves the labor of those who discovered, tested, explained, and corrected the workflow before us.<br />
<br />
The virtuous programmer receives all of this with gratitude. He gives thanks first to God, from whom every talent and every good ultimately comes. He also gives human creators what is due to them: attribution, obedience to licenses, payment when reasonably requested, helpful correction, support, and respect for their work.<br />
<br />
The programmer who hopes to receive just compensation for his own labor should respect the labor which makes his work possible.<br />
<br />
The same order applies to artificial intelligence.<br />
<br />
An AI system is a tool produced through human labor and trained through the use of humanly created materials, technical infrastructure, and natural resources. It is not a person, a craftsman, a moral agent, or the source of wisdom. It does not possess the dignity of the apprentice whose work it may assist, nor does it assume the responsibility of the master who chooses to employ it.<br />
<br />
AI may help the programmer produce a first draft of a wxGlade XML file, suggest Perl code, identify an error, or explain an unfamiliar API. The human programmer must still judge the purpose, verify the output, respect the rights and labor of others, protect the user, and accept responsibility for the finished application.<br />
<br />
The tool may assist the craftsman. It cannot replace the craftsman's moral agency.<br />
<br />
The aim of the virtuous programmer is therefore not to avoid work. It is to avoid wasting work.<br />
<br />
A repeatable installation procedure preserves labor.<br />
<br />
A visual GUI builder reduces unnecessary mechanical effort.<br />
<br />
Reusable Perl modules preserve tested knowledge.<br />
<br />
An installer saves every user from recreating the developer's environment.<br />
<br />
Backward compatibility protects work already performed by programmers and users.<br />
<br />
Good tools allow the craftsman to direct more effort toward understanding the user and completing the work.<br />
<br />
The purpose of this series is therefore larger than the recovery of a neglected technical workflow. A craft forms the craftsman. The habits by which we design, build, test, sell, and support software shape the kind of people we become.<br />
<br />
A programmer who learns to see users as persons rather than abstractions, to give fellow workers their due, to admit error, to keep promises, to restrain ambition, and to place skill at the service of genuine human needs is learning more than application development.<br />
<br />
Technical mastery is good, but it is not the highest good.<br />
<br />
Profit can be good when it sustains useful work, supports a family, allows continued maintenance, and makes service possible. It becomes disordered when users, workers, customers, or communities are treated merely as instruments for obtaining it.<br />
<br />
Likewise, open-source and freely available tools are good, but their availability does not mean that no human labor stands behind them. A sustainable guild economy depends upon mutual recognition: craftsmen receive tools, instruction, examples, testing, and support from others, and they contribute labor, knowledge, payment, encouragement, or maintenance in return.<br />
<br />
Good craftsmanship joins competence with justice.<br />
<br />
The craft reaches its proper earthly end when knowledge, tools, talents, and labor are received with gratitude and ordered toward truthful service of persons, families, and communities.<br />
<br />
Its final measure is not technical mastery, money, reputation, or even the survival of a particular programming language. The craftsman must ask whether he has used the gifts entrusted to him faithfully, treated others justly, served genuine human needs, and returned good fruit from the talents he received.<br />
<br />
== At the workbench: propose a masterwork ==<br />
<br />
Before installing anything, describe one possible application.<br />
<br />
Write down:<br />
<br />
# Who will use it?<br />
# What work are they doing now?<br />
# What burden, error, or unmet need does the application address?<br />
# What part of that work belongs on the desktop?<br />
# What part, if any, belongs on a Perl-powered server?<br />
# What files or data will the user provide?<br />
# What result will the application produce?<br />
# What is the smallest version which would be genuinely useful?<br />
# Why would someone install it?<br />
# Why might someone reasonably pay for it?<br />
# What continuing responsibility will you accept after delivering it?<br />
# How will the application respect the user's data and previous labor?<br />
# Could an apprentice learn something useful by helping with it?<br />
# Could the application remain useful for five or ten years?<br />
# Would the price, support arrangement, or business model allow the programmer to continue serving its users without harming his family or neglecting other obligations?<br />
# What talents, opportunities, inherited knowledge, and tools has God entrusted to you for this work, and how will you use them faithfully?<br />
<br />
The proposal need not describe a large product.<br />
<br />
A narrow tool completed well is a better masterwork than an ambitious system which never leaves the developer's computer.<br />
<br />
The first project might be:<br />
<br />
* a specialized file converter;<br />
* a research tool;<br />
* a desktop client for an existing Perl web application;<br />
* a database front end;<br />
* an image-processing utility;<br />
* a scientific data viewer;<br />
* an administrative console;<br />
* a report generator;<br />
* a collecting application;<br />
* or a tool created for one profession, organization, or community.<br />
<br />
The value of a project does not depend upon millions of users. A tool may create substantial value by serving a small number of people whose work is important and whose needs are poorly understood by larger software vendors.<br />
<br />
The craftsman should begin close to the problem.<br />
<br />
Talk to the prospective user. Observe the existing work. Learn the vocabulary. Ask where mistakes occur, what consumes time, what information must be preserved, and what happens when the current process fails.<br />
<br />
The application should emerge from service to a real need, not from the desire to display technical cleverness.<br />
<br />
== Continue the journey ==<br />
<br />
The next essay, [[The Perl Lazarus Workshop]], examines the tools selected for this work: Strawberry Perl, wxWidgets, wxPerl, wxGlade, MSYS2, PAR-based packaging, and Inno Setup.<br />
<br />
The purpose will not be to present a random collection of software. It will be to understand how each tool contributes to one coherent craftsman's workshop, how the labor embodied in those tools makes new work possible, and why the chosen stack provides a practical route from Perl knowledge to a complete Windows application.<br />
<br />
The third essay, [[Raising a Working wxPerl Shop on Windows]], will then move from explanation to practice: installing the development environment, verifying wxPerl, adding wxGlade, establishing an efficient MSYS2 and vim workflow, generating Perl code, wiring an event, running the program under Strawberry Perl, and preserving the result in Git.<br />
<br />
The journey begins with an existing trade, a real human need, gifts received from God, and the decision to bring useful work to completion.<br />
<br />
<references /><br />
<br />
{{DEFAULTSORT:Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Next essay:''' [[The Perl Lazarus Workshop]]<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]<br />
[[Category:Perl Guilds]]<br />
[[Category:Windows]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=The_Perl_Craftsman_Returns_to_the_Windows_Desktop&diff=373The Perl Craftsman Returns to the Windows Desktop2026-07-19T21:19:44Z<p>Admin: </p>
<hr />
<div>{{DISPLAYTITLE:The Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
''This is the first essay in the series [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]. The series follows the practical journey from Perl programmer to craftsman of complete, distributable Windows applications.''<br />
<br />
There comes a point in the life of a programmer when experience can become strangely tiring.<br />
<br />
The journeyman Perl programmer may have crossed many territories. He has repaired old systems, migrated databases, parsed uncooperative data, automated jobs, maintained web applications, connected APIs, managed servers, and rescued programs whose original authors disappeared years ago. He may have spent decades learning that the apparently simple problem is rarely simple, that data supplied by users never quite resembles the example, and that the machine which fails is usually not the machine on which the software was developed.<br />
<br />
The master Perl programmer may have done all of this while teaching others, supporting clients, maintaining community infrastructure, and carrying responsibility for systems which cannot simply be turned off and rewritten in the fashionable language of the year.<br />
<br />
Such a programmer is not obsolete. He may only be weary.<br />
<br />
The repeated announcement of Perl's death can become tiresome. So can working continually behind the scenes while newer communities rediscover techniques that Perl programmers have practiced for decades. The experienced Perl programmer may understandably ask whether there is any new territory worth crossing, or whether his remaining work consists only of maintaining what other people have abandoned.<br />
<br />
At the same time, a newer programmer may sit in front of a Windows computer and never encounter Perl at all. He may know that programs come from an application store, a game launcher, a download page, or a Git repository, but not yet understand that he can create those programs himself. He may be experimenting with game modifications, running a private server, editing configuration files, automating a repetitive task, or wondering how a favorite program works.<br />
<br />
He may, quite literally, be playing video games.<br />
<br />
Playing a game is not a lesser or shameful use of a computer. Recreation has its proper place. Yet games often place young people near modding, scripting, servers, digital art, online communities, hardware, configuration files, and technical curiosity. These can become entrances into a genuine craft.<br />
<br />
Some future Perl programmer is probably using a Windows computer right now without knowing that Perl exists.<br />
<br />
This series is addressed to both: the experienced craftsman who may need a new application for an old and powerful trade, and the prospective apprentice who has not yet discovered that programming can become his own craft.<br />
<br />
== The programmer as craftsman ==<br />
<br />
The language of the craftsman is useful because programming is not merely the manipulation of symbols. It is the application of knowledge, judgment, practiced skill, and responsibility to a human need.<br />
<br />
Work is ordered toward the good of persons. The programmer does not exist for the software, the company, or the market. Software, companies, and markets exist to serve human life and human communities. A technically impressive application which deceives its customers, degrades its workers, burdens its users, or treats persons merely as sources of data and revenue cannot be considered excellent craftsmanship.<br />
<br />
The traditional progression from apprentice to journeyman to master should not be treated as a rigid credentialing system or as an excuse for excluding newcomers. It is a way of describing growth within a trade.<br />
<br />
* The '''apprentice''' learns the tools, vocabulary, habits, and established practices of the craft.<br />
* The '''journeyman''' can travel beyond the workshop in which he first learned and apply his skills to unfamiliar problems.<br />
* The '''master''' accepts responsibility for complete work, judges its quality, serves customers, preserves knowledge, and helps form other craftsmen.<br />
<br />
These names describe differences in skill, experience, and responsibility. They do not describe differences in human worth. The apprentice, journeyman, master, customer, and user possess the same inherent dignity. Greater mastery creates greater obligations of honesty, patience, justice, service, and care. It does not make one person more valuable than another.<br />
<br />
A journeyman is not merely someone who has memorized more syntax than an apprentice. He has learned how to proceed when the documentation is incomplete, the operating environment is unfamiliar, and the first solution does not work.<br />
<br />
A master is not someone who has stopped learning. He is someone whose experience has taught him the weight of a promise. When he says that a program can be installed, can preserve a user's data, or can be supported in a particular environment, he understands that another person's work may depend upon that claim.<br />
<br />
A master should also understand that knowledge is not diminished when it is handed on. The formation of an apprentice does not create a competitor who has stolen part of the master's trade. It strengthens the craft, preserves accumulated experience, and prepares another person to perform useful work.<br />
<br />
A masterwork is therefore not merely a clever algorithm, an ingenious regular expression, or an impressive piece of code. It is work brought to completion.<br />
<br />
For a Windows desktop application, that completion may include:<br />
<br />
* a useful and understandable graphical interface;<br />
* dependable handling of files and data;<br />
* communication with an existing Perl web service;<br />
* a Windows executable;<br />
* a familiar installer;<br />
* useful documentation;<br />
* testing on a computer other than the developer's;<br />
* a reasonable upgrade and uninstallation path;<br />
* and a plan for supporting the people who use it.<br />
<br />
The purpose of [[Main Page|Perl Guilds]] is to encourage this fuller understanding of the programmer's trade: independent programmers sharing knowledge, cultivating practical specialties, forming one another in the craft, and helping one another earn a living through useful work.<br />
<br />
== An invitation to the weary journeyman ==<br />
<br />
The experienced Perl programmer already possesses much of what is needed to build a valuable desktop application.<br />
<br />
He may know how to:<br />
<br />
* validate and transform data;<br />
* communicate with databases;<br />
* consume and publish APIs;<br />
* process text, images, or scientific data;<br />
* operate remote services;<br />
* automate complex workflows;<br />
* authenticate users;<br />
* generate reports;<br />
* maintain compatibility;<br />
* and diagnose failures in production.<br />
<br />
These abilities do not become irrelevant when a graphical interface is added. They become the substance behind the interface.<br />
<br />
The desktop is not a repudiation of the server work in which Perl programmers have excelled. It is another point at which that work can be placed into the hands of a user.<br />
<br />
A Perl programmer who has spent years building web applications may create a Windows client for one of those applications. A systems programmer may create an administrative console. A scientific programmer may package a model or data-analysis workflow for colleagues who will never use a command line. A collector, historian, translator, accountant, engineer, or small-business owner may need a specialized application which no large software company would consider profitable enough to build.<br />
<br />
The weary journeyman need not begin again as though his past experience counted for nothing. He must learn a new portion of the trade, but he brings his existing judgment with him.<br />
<br />
He already understands that a network can fail, that data must be validated, that an upgrade can damage a working system, and that a user who reports a problem is not necessarily mistaken. These lessons are harder to acquire than the syntax for creating a button.<br />
<br />
Learning wxPerl does not erase the journeyman's experience. It gives that experience another visible form.<br />
<br />
Perl is not the obstacle. Perl is the leverage.<br />
<br />
== An invitation to the future apprentice ==<br />
<br />
Perl also needs new programmers, and many potential programmers are sitting in front of Windows computers right now.<br />
<br />
It is impossible to count all future programmers before they discover the craft. We can, however, observe where ordinary desktop users are. Windows remains the dominant desktop operating-system family in worldwide usage measurements.<ref>[https://gs.statcounter.com/os-market-share/desktop/worldwide StatCounter Global Stats, “Desktop Operating System Market Share Worldwide”]</ref> It is also overwhelmingly prevalent among the participants in Valve's Steam hardware survey.<ref>[https://store.steampowered.com/hwsurvey/ Valve, “Steam Hardware &amp; Software Survey”]</ref><br />
<br />
Many of these users are playing games, installing modifications, running Discord communities, hosting servers, editing configuration files, experimenting with hardware, or trying to automate some irritating part of their digital lives. These activities are not programming apprenticeships by themselves, but they are often close to the doorway.<br />
<br />
A person who asks, “Can I change how this game behaves?” is already asking a programmer's question.<br />
<br />
A person who runs a private game server has begun to encounter networking, configuration, permissions, logs, backups, updates, and failure recovery.<br />
<br />
A person who installs a mod has begun to discover dependencies, version compatibility, file layouts, and the difference between a working installation and a broken one.<br />
<br />
A person who writes a small script to rename files or process game data has begun to discover that the computer can be instructed rather than merely consumed.<br />
<br />
If Perl wishes to recruit another generation, Perl programmers must be willing to meet prospective programmers where they are. That includes Windows.<br />
<br />
It is not enough to tell a Windows user that serious programmers eventually abandon his environment. It is better to show him that the computer he already owns can become a workshop; that Strawberry Perl gives him a native Perl environment; that wxPerl can create real graphical applications; and that the same language can later take him into web services, databases, systems work, scientific computing, graphics, automation, and many other fields.<br />
<br />
The route into the craft should not require the apprentice first to adopt the operating-system preferences of the master.<br />
<br />
A healthy guild does not merely preserve the techniques of its existing members. It invites new apprentices, gives them real work appropriate to their abilities, and allows them to grow into responsibility.<br />
<br />
== Why return to the desktop? ==<br />
<br />
Perl programmers have long been especially effective behind the scenes.<br />
<br />
Perl may collect the data, operate the website, maintain the database, run the scientific model, communicate with an outside service, or generate the report. The ordinary user may benefit from all of this without ever seeing Perl directly.<br />
<br />
That is not a defect. Invisible infrastructure is often excellent work.<br />
<br />
Nevertheless, the Windows desktop offers another place for the Perl craftsman to practice his trade: directly in front of the person whose work the software is intended to serve.<br />
<br />
A desktop application may:<br />
<br />
* organize files already stored on the user's computer;<br />
* provide a specialized editor or research interface;<br />
* display data from a remote Perl application;<br />
* upload images or documents for server-side processing;<br />
* present results from a database or API;<br />
* allow local work when the network is unavailable;<br />
* interact with devices or other applications installed on the computer;<br />
* or provide a richer companion to an existing website.<br />
<br />
A service such as [https://boyscoutpatch.info/ BoyScoutPatch.info], for example, may continue to perform centralized work for which a web application is well suited, while a desktop client could provide a more specialized workflow for collectors, researchers, or administrators.<br />
<br />
The desktop application and web application need not compete. Each can perform the work suited to it.<br />
<br />
The server may maintain shared data, perform expensive searches, coordinate users, apply centralized business rules, or execute processing which requires resources not available on the user's machine.<br />
<br />
The desktop application may manage local files, provide richer interaction, preserve partially completed work, integrate with the user's operating system, and continue performing some tasks when the network is unavailable.<br />
<br />
This is an application of subsidiarity. The server should perform work which genuinely belongs on the server. The desktop should perform work which is best placed in the user's hands. Larger systems should support the user, the independent programmer, and the local organization where their resources are genuinely needed, without unnecessarily taking away work and responsibility which can be competently exercised at the more immediate level.<br />
<br />
Subsidiarity does not require isolation. It must be joined to solidarity. The individual programmer, the guild, the toolmaker, the server operator, and the user may depend upon one another. The objective is not to abandon the smaller participant, but to strengthen him without absorbing every responsibility into a distant centralized system.<br />
<br />
The goal is not to replace every web application with a desktop program. It is to place each responsibility where it can be performed most effectively, while avoiding needless centralization and needless dependence upon a permanent network connection.<br />
<br />
== Why Windows? ==<br />
<br />
This series deliberately focuses on Windows.<br />
<br />
That does not imply that Windows is the only worthy platform, or that wxPerl cannot be useful elsewhere. It means that a craftsman must eventually choose a definite workshop and a definite group of users.<br />
<br />
Windows offers several practical advantages for this undertaking.<br />
<br />
First, Windows has a very large population of ordinary desktop users. That population includes customers, office workers, researchers, collectors, students, gamers, and prospective programmers.<br />
<br />
Second, specialized commercial desktop software is familiar on Windows. Users understand the idea of downloading an application, running an installer, finding the program in the Start menu, and paying for a tool which performs useful work.<br />
<br />
Third, Windows has an unusually strong culture of backward application compatibility. Microsoft describes application compatibility as an intentional design concern and states that developers and customers expect applications they have invested in to continue working.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/key-changes-since-windows-7-to-ensure-compatibility Microsoft Learn, “Key changes since Windows 7 to ensure compatibility”]</ref> Microsoft has also stated that it goes to great lengths to preserve application and device compatibility when operating-system versions change.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/windows-version-check Microsoft Learn, “Windows version check”]</ref><br />
<br />
Windows application manifests can even allow newer versions of the operating system to provide behaviors expected by software targeting earlier releases.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/application-executable-manifest Microsoft Learn, “App executable manifest”]</ref><br />
<br />
No compatibility promise is absolute. Security changes, removed components, architecture changes, obsolete drivers, unavailable libraries, and undocumented assumptions can still break old programs. Nevertheless, Windows demonstrates an unusually strong expectation that software written for an earlier generation should continue to function.<br />
<br />
At times, Windows' compatibility expectations appear even more extreme than Perl's own.<br />
<br />
That expectation matters to the independent craftsman.<br />
<br />
A specialized application may serve a modest community for many years. Its value may come from stability rather than constant reinvention. A program which continues working through several generations of hardware and operating systems can repay its development cost many times over.<br />
<br />
The author's own experiments with ActivePerl 5.8.8 on Windows 98 illustrate the remarkable historical reach of both ecosystems. This does not mean that new commercial software should target Windows 98. It means that the craftsman should recognize the strategic value of technologies which respect existing work.<br />
<br />
Fourth, Strawberry Perl provides a serious native Windows Perl environment. It includes Perl, a compiler, build utilities, and access to the CPAN ecosystem. The Windows programmer is not confined to a toy interpreter or an imitation of a Unix system.<br />
<br />
Finally, many Perl programmers already use Windows as a daily working environment, and many possible new Perl programmers begin there.<br />
<br />
The choice is therefore practical rather than ideological.<br />
<br />
The question is not, “Which operating system proves that I am a proper programmer?”<br />
<br />
The question is, “Where can existing Perl knowledge be turned into useful software, and where can new craftsmen be invited into the trade?”<br />
<br />
== Extreme compatibility creates an opportunity ==<br />
<br />
Windows' backward compatibility does more than preserve old software. It encourages a particular kind of small-scale production.<br />
<br />
A large vendor may prefer subscriptions, rapid replacement, cloud dependence, forced upgrades, and frequent redesign. An independent craftsman may instead produce a focused application which performs one job well and continues doing it for a long time.<br />
<br />
That application might serve only a few hundred users. It might serve a laboratory, a local company, a collecting community, a nonprofit, or a narrow professional field. Its market may be too small for a major software firm but large enough to support the person who understands the problem.<br />
<br />
Long-lived desktop software also creates continuing forms of useful labor:<br />
<br />
* installation;<br />
* customization;<br />
* data conversion;<br />
* training;<br />
* compatibility maintenance;<br />
* support;<br />
* integration with newer services;<br />
* and carefully managed upgrades.<br />
<br />
Backward compatibility does not eliminate this labor. It gives the labor a durable foundation.<br />
<br />
The programmer can improve the application without forcing every user to abandon previous work. The user can invest time learning a tool with some confidence that the tool will not disappear merely because an investor has changed direction or a remote service has been discontinued.<br />
<br />
This relationship between craftsman and user is especially important in a guild-minded approach to software. The programmer is not merely attempting to capture attention, collect data, or make cancellation difficult. He is accepting responsibility for an instrument another person may use in his own work.<br />
<br />
The user's investment matters. The user may have spent hours learning the software, entering data, developing procedures, training employees, or creating records which must be preserved. Backward compatibility is therefore not merely a technical convenience. It is a way of respecting labor already performed.<br />
<br />
== From a working script to a Windows product ==<br />
<br />
A Perl script and a Windows product may contain the same essential program logic, but the user's experience is very different.<br />
<br />
{| class="wikitable"<br />
|+ From the developer's program to the user's product<br />
! The developer may have<br />
! The Windows user reasonably expects<br />
|-<br />
| A <code>.pl</code> file<br />
| An application which starts from an icon<br />
|-<br />
| Installed CPAN modules<br />
| No requirement to install Perl or dependencies<br />
|-<br />
| Commands entered in a terminal<br />
| A graphical interface<br />
|-<br />
| Paths which work on the development computer<br />
| Correct installation and user-data directories<br />
|-<br />
| Diagnostic output in a console<br />
| Understandable errors and useful logs<br />
|-<br />
| A program which works in the workshop<br />
| A program which works on the user's computer<br />
|-<br />
| A collection of build commands<br />
| A repeatable installer and upgrade procedure<br />
|-<br />
| Personal knowledge of hidden dependencies<br />
| A package containing everything the application needs<br />
|}<br />
<br />
The difficult question is therefore not merely whether Perl can display a graphical window. It can.<br />
<br />
The difficult question is whether we can establish a clear and repeatable path from the Perl programmer's existing skills to software which an ordinary Windows user can install and use.<br />
<br />
That is the purpose of the [[Developing and Distributing wxPerl Applications on Windows|Perl Lazarus Project's documented Windows workflow]].<br />
<br />
== The Perl Lazarus journey ==<br />
<br />
[[File:perl-lazarus-project-workflow.png|thumb|right|420px|alt=Six-stage Perl Lazarus Project workflow from installing the development stack through testing the finished Windows application|The Perl Lazarus Project follows a complete path: install the stack, design the GUI, write the Perl code, package the executable, build the installer, and test the result on Windows.]]<br />
<br />
The Perl Lazarus Project builds upon the renewed wxPerl work associated with Johan Vromans and others in the wxPerl community.<ref>[https://dev.to/sciurius/wxperl-revival-5fde Johan Vromans, “wxPerl Revival”]</ref><br />
<br />
It comes out of the larger work of Perl Guilds: supporting independent Perl programmers who seek to make a living through their trade, preserve practical knowledge, and place powerful tools into the hands of individual craftsmen and smaller communities.<ref>Brett Estrade, “Perl Lazarus Project,” presentation prepared for the Summer 2026 Perl Community Conference, Austin, Texas.</ref><br />
<br />
The name points first to Lazarus of the Bible, raised from the dead after four days. It is a fitting image for bringing renewed life to practical GUI development in Perl. The necessary modules and tools were not entirely gone, but the path among them had become difficult to see and difficult to follow.<br />
<br />
The name also acknowledges the example of the [https://www.lazarus-ide.org/ Lazarus IDE and Free Pascal community]. Lazarus demonstrates what can happen when a programming community joins a language, a visual designer, component libraries, documentation, packaging practices, examples, books, support, consulting, and application development.<br />
<br />
The deeper inspiration is not merely the interface of an integrated development environment. It is the presence of a complete culture of application production.<br />
<br />
Perl does not necessarily need a single enormous Lazarus-like IDE. It needs a clear path which craftsmen can follow:<br />
<br />
# Install a known working development stack.<br />
# Design the interface.<br />
# Generate and write Perl code.<br />
# Package the application as an executable.<br />
# Build a Windows installer.<br />
# Test the installed program on a clean Windows system.<br />
<br />
The significance of this path is not that any individual step is unknown. Perl already has a native Windows distribution, graphical bindings, interface-design tools, packaging modules, and installer technology. The missing element has been a coherent and repeatable journey connecting them.<br />
<br />
The present stack joins Strawberry Perl, wxWidgets, wxPerl, wxGlade, PAR-based packaging tools, and Inno Setup. The next essay, [[The Perl Lazarus Workshop]], will explain why these tools belong together and what role each one performs in the craftsman's workshop.<br />
<br />
The series will then proceed through installation, visual design, the wxGlade-to-Perl development cycle, application structure, local data, communication with Perl web services, executable creation, installer construction, testing, support, and the possibility of earning a livable wage through useful applications.<br />
<br />
<div style="clear:both;"></div><br />
<br />
[[File:nhc-advisory-explorer-windows.png|thumb|left|380px|alt=NHC Advisory Explorer running as a packaged Windows desktop application|The NHC Advisory Explorer demonstrates the practical result: a wxPerl program packaged for ordinary Windows users.]]<br />
<br />
This is not merely a theoretical possibility. The [https://github.com/StormSurgeLive/nhc-advisory-gui NHC Advisory Explorer] is one example of a wxPerl program packaged for Windows users.<ref>[https://github.com/StormSurgeLive/nhc-advisory-gui StormSurgeLive, “NHC Advisory Explorer”]</ref><br />
<br />
The program retrieves and presents National Hurricane Center advisory information through a familiar desktop interface. More importantly for this series, it demonstrates that the complete path can be followed: a Perl application can be given a graphical interface, packaged as a Windows executable, placed into an installer, and distributed to users who do not need to install Perl or understand the application's dependencies.<br />
<br />
That final point is essential.<br />
<br />
The Perl programmer may know that the application depends upon Strawberry Perl, wxPerl, wxWidgets, CPAN modules, native DLLs, and packaging tools. The user should ordinarily experience only a Windows application which installs and runs in the expected way.<br />
<br />
The language remains the craftsman's advantage. It does not need to become the customer's burden.<br />
<br />
Readers who want to examine earlier tools and historical attempts at wxWidgets rapid application development in Perl may also consult [[Perl and wxWidgets RAD on Windows]].<br />
<br />
<div style="clear:both;"></div><br />
<br />
== The craft and the virtue ==<br />
<br />
The virtues themselves are discussed elsewhere in the [[Portal:Essays about The Virtuous Perl Programmer|Virtuous Perl Programmer]] material. Here our concern is how they direct the work at hand.<br />
<br />
'''Practical wisdom, or prudence, not laziness''' asks the craftsman to identify a genuine human good and choose fitting means of attaining it.<br />
<br />
For the weary journeyman or master, prudence may require learning a new part of the trade rather than endlessly repeating familiar server-side work. Existing Perl experience is not discarded. It is redirected and extended.<br />
<br />
For the apprentice, prudence means refusing the temptation to skip directly to a polished commercial product without first learning the underlying tools and workflow.<br />
<br />
<blockquote><br />
“Wherefore I wished, and understanding was given me: and I called upon God, and the spirit of wisdom came upon me.”<br />
<br />— Wisdom 7:7, Douay-Rheims<br />
</blockquote><br />
<br />
Automation does not eliminate the importance of labor. All earthly economic value added by human society is created through human labor acting upon the gifts of creation. A tool preserves earlier labor and allows new labor to be applied more effectively, but it does not recognize the user's need, exercise judgment, accept responsibility, or provide service by itself.<br />
<br />
A compiler contains the accumulated labor of its authors and maintainers.<br />
<br />
A GUI designer preserves knowledge about widgets, layouts, serialization, and code generation.<br />
<br />
A Perl module contains work which another programmer has made reusable.<br />
<br />
An installer builder embodies years of experience with Windows installation, upgrades, shortcuts, permissions, and uninstallation.<br />
<br />
The virtuous programmer receives this earlier labor with gratitude, learns the terms under which it is offered, and gives its creators what is due to them. When a tool requests a reasonable commercial license, acknowledgment, contribution, or other form of support, the programmer should not ask only what he can legally avoid.<br />
<br />
The programmer who hopes to receive just compensation for his own labor should respect the labor which makes his work possible.<br />
<br />
The aim of the virtuous programmer is therefore not to avoid work. It is to avoid wasting work.<br />
<br />
A repeatable installation procedure preserves labor.<br />
<br />
A visual GUI builder reduces unnecessary mechanical effort.<br />
<br />
Reusable Perl modules preserve tested knowledge.<br />
<br />
An installer saves every user from recreating the developer's environment.<br />
<br />
Backward compatibility protects work already performed by programmers and users.<br />
<br />
Good tools allow the craftsman to direct more effort toward understanding the user and completing the work.<br />
<br />
The purpose of this series is therefore larger than the recovery of a neglected technical workflow. A craft forms the craftsman. The habits by which we design, build, test, sell, and support software shape the kind of people we become.<br />
<br />
A programmer who learns to see users as persons rather than abstractions, to give fellow workers their due, to admit error, to keep promises, to restrain ambition, and to place skill at the service of genuine human needs is learning more than application development.<br />
<br />
Technical mastery is good, but it is not the highest good.<br />
<br />
Profit can be good when it sustains useful work, supports a family, allows continued maintenance, and makes service possible. It becomes disordered when users, workers, customers, or communities are treated merely as instruments for obtaining it.<br />
<br />
Likewise, open-source and freely available tools are good, but their availability does not mean that no human labor stands behind them. A sustainable guild economy depends upon mutual recognition: craftsmen receive tools, instruction, examples, testing, and support from others, and they contribute labor, knowledge, payment, encouragement, or maintenance in return.<br />
<br />
Good craftsmanship joins competence with justice.<br />
<br />
The craft reaches its proper end when knowledge, tools, and labor are ordered toward truthful service of persons and communities.<br />
<br />
== At the workbench: propose a masterwork ==<br />
<br />
Before installing anything, describe one possible application.<br />
<br />
Write down:<br />
<br />
# Who will use it?<br />
# What work are they doing now?<br />
# What burden, error, or unmet need does the application address?<br />
# What part of that work belongs on the desktop?<br />
# What part, if any, belongs on a Perl-powered server?<br />
# What files or data will the user provide?<br />
# What result will the application produce?<br />
# What is the smallest version which would be genuinely useful?<br />
# Why would someone install it?<br />
# Why might someone reasonably pay for it?<br />
# What continuing responsibility will you accept after delivering it?<br />
# How will the application respect the user's data and previous labor?<br />
# Could an apprentice learn something useful by helping with it?<br />
# Could the application remain useful for five or ten years?<br />
# Would the price, support arrangement, or business model allow the programmer to continue serving its users without harming his family or neglecting other obligations?<br />
<br />
The proposal need not describe a large product.<br />
<br />
A narrow tool completed well is a better masterwork than an ambitious system which never leaves the developer's computer.<br />
<br />
The first project might be:<br />
<br />
* a specialized file converter;<br />
* a research tool;<br />
* a desktop client for an existing Perl web application;<br />
* a database front end;<br />
* an image-processing utility;<br />
* a scientific data viewer;<br />
* an administrative console;<br />
* a report generator;<br />
* a collecting application;<br />
* or a tool created for one profession, organization, or community.<br />
<br />
The value of a project does not depend upon millions of users. A tool may create substantial value by serving a small number of people whose work is important and whose needs are poorly understood by larger software vendors.<br />
<br />
The craftsman should begin close to the problem.<br />
<br />
Talk to the prospective user. Observe the existing work. Learn the vocabulary. Ask where mistakes occur, what consumes time, what information must be preserved, and what happens when the current process fails.<br />
<br />
The application should emerge from service to a real need, not from the desire to display technical cleverness.<br />
<br />
== Continue the journey ==<br />
<br />
The next essay, [[The Perl Lazarus Workshop]], examines the tools selected for this work: Strawberry Perl, wxWidgets, wxPerl, wxGlade, MSYS2, PAR-based packaging, and Inno Setup.<br />
<br />
The purpose will not be to present a random collection of software. It will be to understand how each tool contributes to one coherent craftsman's workshop, how the labor embodied in those tools makes new work possible, and why the chosen stack provides a practical route from Perl knowledge to a complete Windows application.<br />
<br />
The third essay, [[Raising a Working wxPerl Shop on Windows]], will then move from explanation to practice: installing the development environment, verifying wxPerl, adding wxGlade, establishing an efficient MSYS2 and vim workflow, generating Perl code, wiring an event, running the program under Strawberry Perl, and preserving the result in Git.<br />
<br />
The journey begins with an existing trade, a real human need, and the decision to bring useful work to completion.<br />
<br />
<references /><br />
<br />
{{DEFAULTSORT:Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Next essay:''' [[The Perl Lazarus Workshop]]<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]<br />
[[Category:Perl Guilds]]<br />
[[Category:Windows]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=The_Perl_Craftsman_Returns_to_the_Windows_Desktop&diff=372The Perl Craftsman Returns to the Windows Desktop2026-07-19T21:13:58Z<p>Admin: /* The craft and the virtue */</p>
<hr />
<div>{{DISPLAYTITLE:The Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
''This is the first essay in the series [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]. The series follows the practical journey from Perl programmer to craftsman of complete, distributable Windows applications.''<br />
<br />
There comes a point in the life of a programmer when experience can become strangely tiring.<br />
<br />
The journeyman Perl programmer may have crossed many territories. He has repaired old systems, migrated databases, parsed uncooperative data, automated jobs, maintained web applications, connected APIs, managed servers, and rescued programs whose original authors disappeared years ago. He may have spent decades learning that the apparently simple problem is rarely simple, that data supplied by users never quite resembles the example, and that the machine which fails is usually not the machine on which the software was developed.<br />
<br />
The master Perl programmer may have done all of this while teaching others, supporting clients, maintaining community infrastructure, and carrying responsibility for systems which cannot simply be turned off and rewritten in the fashionable language of the year.<br />
<br />
Such a programmer is not obsolete. He may only be weary.<br />
<br />
The repeated announcement of Perl's death can become tiresome. So can working continually behind the scenes while newer communities rediscover techniques that Perl programmers have practiced for decades. The experienced Perl programmer may understandably ask whether there is any new territory worth crossing, or whether his remaining work consists only of maintaining what other people have abandoned.<br />
<br />
At the same time, a newer programmer may sit in front of a Windows computer and never encounter Perl at all. He may know that programs come from an application store, a game launcher, a download page, or a Git repository, but not yet understand that he can create those programs himself. He may be experimenting with game modifications, running a private server, editing configuration files, automating a repetitive task, or wondering how a favorite program works.<br />
<br />
He may, quite literally, be playing video games.<br />
<br />
This series is addressed to both programmers: the experienced craftsman who may need a new application for an old and powerful trade, and the prospective apprentice who has not yet discovered that programming can become his own craft.<br />
<br />
== The programmer as craftsman ==<br />
<br />
The language of the craftsman is useful because programming is not merely the manipulation of symbols. It is the application of knowledge, judgment, practiced skill, and responsibility to a human need.<br />
<br />
The traditional progression from apprentice to journeyman to master should not be treated as a rigid credentialing system or as an excuse for excluding newcomers. It is a way of describing growth within a trade.<br />
<br />
* The '''apprentice''' learns the tools, vocabulary, habits, and established practices of the craft.<br />
* The '''journeyman''' can travel beyond the workshop in which he first learned and apply his skills to unfamiliar problems.<br />
* The '''master''' accepts responsibility for complete work, judges its quality, serves customers, preserves knowledge, and helps form other craftsmen.<br />
<br />
A journeyman is not merely someone who has memorized more syntax than an apprentice. He has learned how to proceed when the documentation is incomplete, the operating environment is unfamiliar, and the first solution does not work.<br />
<br />
A master is not someone who has stopped learning. He is someone whose experience has taught him the weight of a promise. When he says that a program can be installed, can preserve a user's data, or can be supported in a particular environment, he understands that another person's work may depend upon that claim.<br />
<br />
A masterwork is therefore not merely a clever algorithm, an ingenious regular expression, or an impressive piece of code. It is work brought to completion.<br />
<br />
For a Windows desktop application, that completion may include:<br />
<br />
* a useful and understandable graphical interface;<br />
* dependable handling of files and data;<br />
* communication with an existing Perl web service;<br />
* a Windows executable;<br />
* a familiar installer;<br />
* useful documentation;<br />
* testing on a computer other than the developer's;<br />
* a reasonable upgrade and uninstallation path;<br />
* and a plan for supporting the people who use it.<br />
<br />
The purpose of [[Main Page|Perl Guilds]] is to encourage this fuller understanding of the programmer's trade: independent programmers sharing knowledge, cultivating practical specialties, forming one another in the craft, and helping one another earn a living through useful work.<br />
<br />
== An invitation to the weary journeyman ==<br />
<br />
The experienced Perl programmer already possesses much of what is needed to build a valuable desktop application.<br />
<br />
He may know how to:<br />
<br />
* validate and transform data;<br />
* communicate with databases;<br />
* consume and publish APIs;<br />
* process text, images, or scientific data;<br />
* operate remote services;<br />
* automate complex workflows;<br />
* authenticate users;<br />
* generate reports;<br />
* maintain compatibility;<br />
* and diagnose failures in production.<br />
<br />
These abilities do not become irrelevant when a graphical interface is added. They become the substance behind the interface.<br />
<br />
The desktop is not a repudiation of the server work in which Perl programmers have excelled. It is another point at which that work can be placed into the hands of a user.<br />
<br />
A Perl programmer who has spent years building web applications may create a Windows client for one of those applications. A systems programmer may create an administrative console. A scientific programmer may package a model or data-analysis workflow for colleagues who will never use a command line. A collector, historian, translator, accountant, engineer, or small-business owner may need a specialized application that no large software company would consider profitable enough to build.<br />
<br />
The weary journeyman need not begin again as though his past experience counted for nothing. He must learn a new portion of the trade, but he brings his existing judgment with him.<br />
<br />
Perl is not the obstacle. Perl is the leverage.<br />
<br />
== An invitation to the future apprentice ==<br />
<br />
Perl also needs new programmers, and many potential programmers are sitting in front of Windows computers right now.<br />
<br />
It would be impossible to count all future programmers before they discover the craft. We can, however, observe where ordinary desktop users are. Windows remains the largest desktop operating-system family in worldwide usage measurements.<ref>[https://gs.statcounter.com/os-market-share/desktop/ StatCounter Global Stats, “Desktop Operating System Market Share Worldwide”]</ref> It also remains the overwhelmingly prevalent operating-system environment among people participating in the Steam hardware survey.<ref>[https://store.steampowered.com/hwsurvey/ Valve, “Steam Hardware & Software Survey”]</ref><br />
<br />
Many of these users are playing games, installing modifications, running Discord communities, hosting servers, editing files, experimenting with hardware, or trying to automate some irritating part of their digital lives. These activities are not programming apprenticeships by themselves, but they are often close to the doorway.<br />
<br />
A person who asks, “Can I change how this game behaves?” is already asking a programmer's question.<br />
<br />
A person who runs a private game server has begun to encounter networking, configuration, permissions, logs, and failure recovery.<br />
<br />
A person who writes a small script to rename files or process game data has begun to discover that the computer can be instructed rather than merely consumed.<br />
<br />
If Perl wishes to recruit another generation, Perl programmers must be willing to meet prospective programmers where they are. That includes Windows.<br />
<br />
It is not enough to tell a Windows user that serious programmers eventually abandon his environment. It is better to show him that the computer he already owns can become a workshop; that Strawberry Perl gives him a native Perl environment; that wxPerl can create real graphical applications; and that the same language can later take him into web services, databases, systems work, scientific computing, and many other fields.<br />
<br />
The route into the craft should not require the apprentice first to adopt the operating-system preferences of the master.<br />
<br />
== Why return to the desktop? ==<br />
<br />
Perl programmers have long been especially effective behind the scenes.<br />
<br />
Perl may collect the data, operate the website, maintain the database, run the scientific model, communicate with an outside service, or generate the report. The ordinary user may benefit from all of this without ever seeing Perl directly.<br />
<br />
That is not a defect. Invisible infrastructure is often excellent work.<br />
<br />
Nevertheless, the Windows desktop offers another place for the Perl craftsman to practice his trade: directly in front of the person whose work the software is intended to serve.<br />
<br />
A desktop application may:<br />
<br />
* organize files already stored on the user's computer;<br />
* provide a specialized editor or research interface;<br />
* display data from a remote Perl application;<br />
* upload images or documents for server-side processing;<br />
* present results from a database or API;<br />
* allow local work when the network is unavailable;<br />
* interact with devices or applications installed on the computer;<br />
* or provide a richer companion to an existing website.<br />
<br />
A service such as [https://boyscoutpatch.info/ BoyScoutPatch.info], for example, may continue to perform centralized work for which a web application is well suited, while a desktop client could provide a more specialized workflow for collectors, researchers, or administrators.<br />
<br />
This is an application of subsidiarity. The server should perform work which genuinely belongs on the server. The desktop should perform work which is best placed in the user's hands.<br />
<br />
The objective is not to replace every web application with a desktop program. It is to place each responsibility where it can be performed most effectively, while avoiding needless centralization and needless dependence upon a permanent network connection.<br />
<br />
== Why Windows? ==<br />
<br />
This series deliberately focuses on Windows.<br />
<br />
That does not imply that Windows is the only worthy platform, or that wxPerl cannot be useful elsewhere. It means that a craftsman must eventually choose a definite workshop and a definite group of users.<br />
<br />
Windows offers several practical advantages for this undertaking.<br />
<br />
First, Windows has a very large population of ordinary desktop users. That population includes customers, office workers, researchers, collectors, students, gamers, and prospective programmers.<br />
<br />
Second, specialized commercial desktop software is familiar on Windows. Users understand the idea of downloading an application, running an installer, finding the program in the Start menu, and paying for a tool which performs useful work.<br />
<br />
Third, Windows is unusually committed to backward application compatibility. Microsoft states that it goes to great lengths to maintain application and device compatibility across operating-system version changes, especially for ordinary applications without kernel dependencies.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/windows-version-check Microsoft Learn, “Windows version check”]</ref> Windows application manifests even allow newer versions of Windows to preserve behaviors expected by applications targeting older releases.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/application-executable-manifest Microsoft Learn, “App executable manifest”]</ref><br />
<br />
No compatibility promise is absolute. Security changes, removed components, architecture changes, obsolete drivers, and undocumented assumptions can still break old programs. Nevertheless, Windows demonstrates an unusually strong expectation that software written for an earlier generation should continue to function.<br />
<br />
That expectation matters to the independent craftsman.<br />
<br />
A specialized application may serve a modest community for many years. Its value may come from stability rather than constant reinvention. A program which continues working through several generations of hardware and operating systems can repay its development cost many times over.<br />
<br />
Perl's own concern for compatibility belongs naturally in such an environment. Experiments with ActivePerl 5.8.8 on Windows 98 illustrate the extraordinary historical reach of both ecosystems. That does not mean new commercial software should target Windows 98. It means the craftsman should recognize the strategic value of technologies which respect existing work.<br />
<br />
Fourth, Strawberry Perl provides a serious native Windows Perl environment. It includes Perl, a compiler, build utilities, and access to the CPAN ecosystem. The Windows programmer is not confined to a toy interpreter or an imitation of a Unix system.<br />
<br />
Finally, many Perl programmers already use Windows as a daily working environment, and many possible new Perl programmers begin there.<br />
<br />
The choice is therefore practical rather than ideological.<br />
<br />
The question is not, “Which operating system proves that I am a proper programmer?”<br />
<br />
The question is, “Where can existing Perl knowledge be turned into useful software, and where can new craftsmen be invited into the trade?”<br />
<br />
== Extreme compatibility creates an opportunity ==<br />
<br />
Windows' backward compatibility does more than preserve old software. It encourages a particular kind of small-scale production.<br />
<br />
A large vendor may prefer subscriptions, rapid replacement, cloud dependence, and frequent redesign. An independent craftsman may instead produce a focused application which performs one job well and continues doing it for a long time.<br />
<br />
That application might serve only a few hundred users. It might serve a laboratory, a local company, a collecting community, a nonprofit, or a narrow professional field. Its market may be too small for a major software firm but large enough to support the person who understands the problem.<br />
<br />
Long-lived desktop software also creates continuing forms of useful labor:<br />
<br />
* installation;<br />
* customization;<br />
* data conversion;<br />
* training;<br />
* compatibility maintenance;<br />
* support;<br />
* integration with newer services;<br />
* and carefully managed upgrades.<br />
<br />
Backward compatibility does not eliminate this labor. It gives the labor a durable foundation.<br />
<br />
The programmer can improve the application without forcing every user to abandon previous work. The user can invest time learning a tool with some confidence that the tool will not disappear merely because an investor has changed direction.<br />
<br />
This relationship between craftsman and user is especially important in a guild-minded approach to software. The programmer is not merely attempting to capture attention. He is accepting responsibility for an instrument another person may use in his own work.<br />
<br />
== From a working script to a Windows product ==<br />
<br />
A Perl script and a Windows product may contain the same essential program logic, but the user's experience is very different.<br />
<br />
{| class="wikitable"<br />
|+ From the developer's program to the user's product<br />
! The developer may have<br />
! The Windows user reasonably expects<br />
|-<br />
| A <code>.pl</code> file<br />
| An application that starts from an icon<br />
|-<br />
| Installed CPAN modules<br />
| No requirement to install Perl or dependencies<br />
|-<br />
| Commands entered in a terminal<br />
| A graphical interface<br />
|-<br />
| Paths that work on the development computer<br />
| Correct installation and user-data directories<br />
|-<br />
| Diagnostic output in a console<br />
| Understandable errors and useful logs<br />
|-<br />
| A program that works in the workshop<br />
| A program that works on the user's computer<br />
|-<br />
| A collection of build commands<br />
| A repeatable installer and upgrade procedure<br />
|}<br />
<br />
The difficult question is therefore not merely whether Perl can display a graphical window. It can.<br />
<br />
The difficult question is whether we can establish a clear and repeatable path from the Perl programmer's existing skills to software which an ordinary Windows user can install and use.<br />
<br />
That is the purpose of the [[Developing and Distributing wxPerl Applications on Windows|Perl Lazarus Project's documented Windows workflow]].<br />
<br />
== The Perl Lazarus journey ==<br />
<br />
[[File:perl-lazarus-project-workflow.png|thumb|right|420px|alt=Six-stage Perl Lazarus Project workflow from installing the development stack through testing the finished Windows application|The Perl Lazarus Project follows a complete path: install the stack, design the GUI, write the Perl code, package the executable, build the installer, and test the result on Windows.]]<br />
<br />
The Perl Lazarus Project builds upon the renewed wxPerl work associated with Johan Vromans and others in the wxPerl community.<ref>[https://dev.to/sciurius/wxperl-revival-5fde Johan Vromans, “wxPerl Revival”]</ref><br />
<br />
Its name also acknowledges the example of the [https://www.lazarus-ide.org/ Lazarus IDE and Free Pascal community]. Lazarus demonstrates what can happen when a programming community joins a language, a visual designer, components, documentation, packaging practices, and an economy of books, support, consulting, and application development.<br />
<br />
Perl does not necessarily need a single enormous Lazarus-like IDE. It needs a clear path which craftsmen can follow:<br />
<br />
# Install a known working development stack.<br />
# Design the interface.<br />
# Generate and write Perl code.<br />
# Package the application as an executable.<br />
# Build a Windows installer.<br />
# Test the installed program on a clean Windows system.<br />
<br />
The significance of this path is not that any individual step is unknown. Perl already has a native Windows distribution, graphical bindings, interface-design tools, packaging modules, and installer technology. The missing element has been a coherent and repeatable journey connecting them.<br />
<br />
The present stack joins Strawberry Perl, wxWidgets, wxPerl, wxGlade, PAR-based packaging tools, and Inno Setup. The next essay, [[The Perl Lazarus Workshop]], will explain why these tools belong together and what role each one performs in the craftsman’s workshop.<br />
<br />
The series will then proceed through installation, visual design, the wxGlade-to-Perl development cycle, application structure, local data, communication with Perl web services, executable creation, installer construction, testing, and support.<br />
<br />
{{clear}}<br />
<br />
[[File:nhc-advisory-explorer-windows.png|thumb|left|380px|alt=NHC Advisory Explorer running as a packaged Windows desktop application|The NHC Advisory Explorer demonstrates the practical result: a wxPerl program packaged for ordinary Windows users.]]<br />
<br />
This is not merely a theoretical possibility. The [https://github.com/StormSurgeLive/nhc-advisory-gui NHC Advisory Explorer] is one example of a wxPerl program packaged for Windows users.<ref>[https://github.com/StormSurgeLive/nhc-advisory-gui StormSurgeLive, “NHC Advisory Explorer”]</ref><br />
<br />
The program retrieves and presents National Hurricane Center advisory information through a familiar desktop interface. More importantly for this series, it demonstrates that the complete path can be followed: a Perl application can be given a graphical interface, packaged as a Windows executable, placed into an installer, and distributed to users who do not need to install Perl or understand the application’s dependencies.<br />
<br />
That final point is essential. The Perl programmer may know that the application depends upon Strawberry Perl, wxPerl, wxWidgets, CPAN modules, native DLLs, and packaging tools. The user should ordinarily experience only a Windows application which installs and runs in the expected way.<br />
<br />
Readers who want to examine earlier tools and historical attempts at wxWidgets rapid application development in Perl may also consult [[Perl and wxWidgets RAD on Windows]].<br />
<br />
{{clear}}<br />
<br />
== The craft and the virtue ==<br />
<br />
The virtues themselves are discussed elsewhere on Perl Guilds. Here our concern is how they direct the work at hand.<br />
<br />
'''Practical wisdom, or prudence, not laziness''' asks the craftsman to identify a genuine human good and choose fitting means of attaining it.<br />
<br />
For the weary journeyman or master, prudence may require learning a new part of the trade rather than endlessly repeating familiar server-side work. Existing Perl experience is not discarded. It is redirected and extended.<br />
<br />
For the apprentice, prudence means refusing the temptation to skip directly to a polished commercial product without first learning the underlying tools and workflow.<br />
<br />
Automation does not eliminate the importance of labor. All earthly economic value added by human society is created through human labor acting upon the gifts of creation. A tool preserves earlier labor and allows new labor to be applied more effectively, but it does not recognize the user's need, exercise judgment, accept responsibility, or provide service by itself.<br />
<br />
The aim of the virtuous programmer is therefore not to avoid work. It is to avoid wasting work.<br />
<br />
A repeatable installation procedure preserves labor.<br />
<br />
A visual GUI builder reduces unnecessary mechanical effort.<br />
<br />
Reusable Perl modules preserve tested knowledge.<br />
<br />
An installer saves every user from recreating the developer's environment.<br />
<br />
Backward compatibility protects work already performed by programmers and users.<br />
<br />
Good tools allow the craftsman to direct more effort toward understanding the user and completing the work. The final measure of the work is not merely technical efficiency or profit, but whether it truthfully and justly serves the persons and communities for whom it was made.<br />
<br />
The purpose of this series is therefore larger than the recovery of a neglected technical workflow. A craft forms the craftsman. The habits by which we design, build, test, sell, and support software shape the kind of people we become.<br />
<br />
A programmer who learns to see users as persons rather than abstractions, to give fellow workers their due, to admit error, to keep promises, to restrain ambition, and to place skill at the service of genuine human needs is learning more than application development.<br />
<br />
Technical mastery is good, but it is not the highest good. The craft reaches its proper end when knowledge, tools, and labor are ordered toward truthful service of persons and communities.<br />
<br />
== At the workbench: propose a masterwork ==<br />
<br />
Before installing anything, describe one possible application.<br />
<br />
Write down:<br />
<br />
# Who will use it?<br />
# What work are they doing now?<br />
# What part of that work belongs on the desktop?<br />
# What part, if any, belongs on a Perl-powered server?<br />
# What files or data will the user provide?<br />
# What result will the application produce?<br />
# What is the smallest version that would be genuinely useful?<br />
# Why would someone install it?<br />
# Why might someone reasonably pay for it?<br />
# What responsibility will you accept after delivering it?<br />
# Could an apprentice learn something by helping with it?<br />
# Could the application remain useful for five or ten years?<br />
<br />
The proposal need not describe a large product. A narrow tool completed well is a better masterwork than an ambitious system which never leaves the developer's computer.<br />
<br />
== Continue the journey ==<br />
<br />
The next essay, [[The Perl Lazarus Workshop]], examines the tools selected for this work: Strawberry Perl, wxWidgets, wxPerl, wxGlade, MSYS2, PAR-based packaging, and Inno Setup.<br />
<br />
The purpose will not be to present a random collection of software. It will be to understand how each tool contributes to one coherent craftsman's workshop, and how the labor embodied in these tools allows a Perl programmer to perform new work of his own.<br />
<br />
<references /><br />
<br />
{{DEFAULTSORT:Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Next essay:''' [[The Perl Lazarus Workshop]]<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]<br />
[[Category:Perl Guilds]]<br />
[[Category:Windows]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Template:Clear&diff=371Template:Clear2026-07-19T21:08:53Z<p>Admin: Created page with "<div style="clear:both;"></div>"</p>
<hr />
<div><div style="clear:both;"></div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=The_Perl_Craftsman_Returns_to_the_Windows_Desktop&diff=370The Perl Craftsman Returns to the Windows Desktop2026-07-19T21:08:30Z<p>Admin: /* The Perl Lazarus journey */</p>
<hr />
<div>{{DISPLAYTITLE:The Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
''This is the first essay in the series [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]. The series follows the practical journey from Perl programmer to craftsman of complete, distributable Windows applications.''<br />
<br />
There comes a point in the life of a programmer when experience can become strangely tiring.<br />
<br />
The journeyman Perl programmer may have crossed many territories. He has repaired old systems, migrated databases, parsed uncooperative data, automated jobs, maintained web applications, connected APIs, managed servers, and rescued programs whose original authors disappeared years ago. He may have spent decades learning that the apparently simple problem is rarely simple, that data supplied by users never quite resembles the example, and that the machine which fails is usually not the machine on which the software was developed.<br />
<br />
The master Perl programmer may have done all of this while teaching others, supporting clients, maintaining community infrastructure, and carrying responsibility for systems which cannot simply be turned off and rewritten in the fashionable language of the year.<br />
<br />
Such a programmer is not obsolete. He may only be weary.<br />
<br />
The repeated announcement of Perl's death can become tiresome. So can working continually behind the scenes while newer communities rediscover techniques that Perl programmers have practiced for decades. The experienced Perl programmer may understandably ask whether there is any new territory worth crossing, or whether his remaining work consists only of maintaining what other people have abandoned.<br />
<br />
At the same time, a newer programmer may sit in front of a Windows computer and never encounter Perl at all. He may know that programs come from an application store, a game launcher, a download page, or a Git repository, but not yet understand that he can create those programs himself. He may be experimenting with game modifications, running a private server, editing configuration files, automating a repetitive task, or wondering how a favorite program works.<br />
<br />
He may, quite literally, be playing video games.<br />
<br />
This series is addressed to both programmers: the experienced craftsman who may need a new application for an old and powerful trade, and the prospective apprentice who has not yet discovered that programming can become his own craft.<br />
<br />
== The programmer as craftsman ==<br />
<br />
The language of the craftsman is useful because programming is not merely the manipulation of symbols. It is the application of knowledge, judgment, practiced skill, and responsibility to a human need.<br />
<br />
The traditional progression from apprentice to journeyman to master should not be treated as a rigid credentialing system or as an excuse for excluding newcomers. It is a way of describing growth within a trade.<br />
<br />
* The '''apprentice''' learns the tools, vocabulary, habits, and established practices of the craft.<br />
* The '''journeyman''' can travel beyond the workshop in which he first learned and apply his skills to unfamiliar problems.<br />
* The '''master''' accepts responsibility for complete work, judges its quality, serves customers, preserves knowledge, and helps form other craftsmen.<br />
<br />
A journeyman is not merely someone who has memorized more syntax than an apprentice. He has learned how to proceed when the documentation is incomplete, the operating environment is unfamiliar, and the first solution does not work.<br />
<br />
A master is not someone who has stopped learning. He is someone whose experience has taught him the weight of a promise. When he says that a program can be installed, can preserve a user's data, or can be supported in a particular environment, he understands that another person's work may depend upon that claim.<br />
<br />
A masterwork is therefore not merely a clever algorithm, an ingenious regular expression, or an impressive piece of code. It is work brought to completion.<br />
<br />
For a Windows desktop application, that completion may include:<br />
<br />
* a useful and understandable graphical interface;<br />
* dependable handling of files and data;<br />
* communication with an existing Perl web service;<br />
* a Windows executable;<br />
* a familiar installer;<br />
* useful documentation;<br />
* testing on a computer other than the developer's;<br />
* a reasonable upgrade and uninstallation path;<br />
* and a plan for supporting the people who use it.<br />
<br />
The purpose of [[Main Page|Perl Guilds]] is to encourage this fuller understanding of the programmer's trade: independent programmers sharing knowledge, cultivating practical specialties, forming one another in the craft, and helping one another earn a living through useful work.<br />
<br />
== An invitation to the weary journeyman ==<br />
<br />
The experienced Perl programmer already possesses much of what is needed to build a valuable desktop application.<br />
<br />
He may know how to:<br />
<br />
* validate and transform data;<br />
* communicate with databases;<br />
* consume and publish APIs;<br />
* process text, images, or scientific data;<br />
* operate remote services;<br />
* automate complex workflows;<br />
* authenticate users;<br />
* generate reports;<br />
* maintain compatibility;<br />
* and diagnose failures in production.<br />
<br />
These abilities do not become irrelevant when a graphical interface is added. They become the substance behind the interface.<br />
<br />
The desktop is not a repudiation of the server work in which Perl programmers have excelled. It is another point at which that work can be placed into the hands of a user.<br />
<br />
A Perl programmer who has spent years building web applications may create a Windows client for one of those applications. A systems programmer may create an administrative console. A scientific programmer may package a model or data-analysis workflow for colleagues who will never use a command line. A collector, historian, translator, accountant, engineer, or small-business owner may need a specialized application that no large software company would consider profitable enough to build.<br />
<br />
The weary journeyman need not begin again as though his past experience counted for nothing. He must learn a new portion of the trade, but he brings his existing judgment with him.<br />
<br />
Perl is not the obstacle. Perl is the leverage.<br />
<br />
== An invitation to the future apprentice ==<br />
<br />
Perl also needs new programmers, and many potential programmers are sitting in front of Windows computers right now.<br />
<br />
It would be impossible to count all future programmers before they discover the craft. We can, however, observe where ordinary desktop users are. Windows remains the largest desktop operating-system family in worldwide usage measurements.<ref>[https://gs.statcounter.com/os-market-share/desktop/ StatCounter Global Stats, “Desktop Operating System Market Share Worldwide”]</ref> It also remains the overwhelmingly prevalent operating-system environment among people participating in the Steam hardware survey.<ref>[https://store.steampowered.com/hwsurvey/ Valve, “Steam Hardware & Software Survey”]</ref><br />
<br />
Many of these users are playing games, installing modifications, running Discord communities, hosting servers, editing files, experimenting with hardware, or trying to automate some irritating part of their digital lives. These activities are not programming apprenticeships by themselves, but they are often close to the doorway.<br />
<br />
A person who asks, “Can I change how this game behaves?” is already asking a programmer's question.<br />
<br />
A person who runs a private game server has begun to encounter networking, configuration, permissions, logs, and failure recovery.<br />
<br />
A person who writes a small script to rename files or process game data has begun to discover that the computer can be instructed rather than merely consumed.<br />
<br />
If Perl wishes to recruit another generation, Perl programmers must be willing to meet prospective programmers where they are. That includes Windows.<br />
<br />
It is not enough to tell a Windows user that serious programmers eventually abandon his environment. It is better to show him that the computer he already owns can become a workshop; that Strawberry Perl gives him a native Perl environment; that wxPerl can create real graphical applications; and that the same language can later take him into web services, databases, systems work, scientific computing, and many other fields.<br />
<br />
The route into the craft should not require the apprentice first to adopt the operating-system preferences of the master.<br />
<br />
== Why return to the desktop? ==<br />
<br />
Perl programmers have long been especially effective behind the scenes.<br />
<br />
Perl may collect the data, operate the website, maintain the database, run the scientific model, communicate with an outside service, or generate the report. The ordinary user may benefit from all of this without ever seeing Perl directly.<br />
<br />
That is not a defect. Invisible infrastructure is often excellent work.<br />
<br />
Nevertheless, the Windows desktop offers another place for the Perl craftsman to practice his trade: directly in front of the person whose work the software is intended to serve.<br />
<br />
A desktop application may:<br />
<br />
* organize files already stored on the user's computer;<br />
* provide a specialized editor or research interface;<br />
* display data from a remote Perl application;<br />
* upload images or documents for server-side processing;<br />
* present results from a database or API;<br />
* allow local work when the network is unavailable;<br />
* interact with devices or applications installed on the computer;<br />
* or provide a richer companion to an existing website.<br />
<br />
A service such as [https://boyscoutpatch.info/ BoyScoutPatch.info], for example, may continue to perform centralized work for which a web application is well suited, while a desktop client could provide a more specialized workflow for collectors, researchers, or administrators.<br />
<br />
This is an application of subsidiarity. The server should perform work which genuinely belongs on the server. The desktop should perform work which is best placed in the user's hands.<br />
<br />
The objective is not to replace every web application with a desktop program. It is to place each responsibility where it can be performed most effectively, while avoiding needless centralization and needless dependence upon a permanent network connection.<br />
<br />
== Why Windows? ==<br />
<br />
This series deliberately focuses on Windows.<br />
<br />
That does not imply that Windows is the only worthy platform, or that wxPerl cannot be useful elsewhere. It means that a craftsman must eventually choose a definite workshop and a definite group of users.<br />
<br />
Windows offers several practical advantages for this undertaking.<br />
<br />
First, Windows has a very large population of ordinary desktop users. That population includes customers, office workers, researchers, collectors, students, gamers, and prospective programmers.<br />
<br />
Second, specialized commercial desktop software is familiar on Windows. Users understand the idea of downloading an application, running an installer, finding the program in the Start menu, and paying for a tool which performs useful work.<br />
<br />
Third, Windows is unusually committed to backward application compatibility. Microsoft states that it goes to great lengths to maintain application and device compatibility across operating-system version changes, especially for ordinary applications without kernel dependencies.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/windows-version-check Microsoft Learn, “Windows version check”]</ref> Windows application manifests even allow newer versions of Windows to preserve behaviors expected by applications targeting older releases.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/application-executable-manifest Microsoft Learn, “App executable manifest”]</ref><br />
<br />
No compatibility promise is absolute. Security changes, removed components, architecture changes, obsolete drivers, and undocumented assumptions can still break old programs. Nevertheless, Windows demonstrates an unusually strong expectation that software written for an earlier generation should continue to function.<br />
<br />
That expectation matters to the independent craftsman.<br />
<br />
A specialized application may serve a modest community for many years. Its value may come from stability rather than constant reinvention. A program which continues working through several generations of hardware and operating systems can repay its development cost many times over.<br />
<br />
Perl's own concern for compatibility belongs naturally in such an environment. Experiments with ActivePerl 5.8.8 on Windows 98 illustrate the extraordinary historical reach of both ecosystems. That does not mean new commercial software should target Windows 98. It means the craftsman should recognize the strategic value of technologies which respect existing work.<br />
<br />
Fourth, Strawberry Perl provides a serious native Windows Perl environment. It includes Perl, a compiler, build utilities, and access to the CPAN ecosystem. The Windows programmer is not confined to a toy interpreter or an imitation of a Unix system.<br />
<br />
Finally, many Perl programmers already use Windows as a daily working environment, and many possible new Perl programmers begin there.<br />
<br />
The choice is therefore practical rather than ideological.<br />
<br />
The question is not, “Which operating system proves that I am a proper programmer?”<br />
<br />
The question is, “Where can existing Perl knowledge be turned into useful software, and where can new craftsmen be invited into the trade?”<br />
<br />
== Extreme compatibility creates an opportunity ==<br />
<br />
Windows' backward compatibility does more than preserve old software. It encourages a particular kind of small-scale production.<br />
<br />
A large vendor may prefer subscriptions, rapid replacement, cloud dependence, and frequent redesign. An independent craftsman may instead produce a focused application which performs one job well and continues doing it for a long time.<br />
<br />
That application might serve only a few hundred users. It might serve a laboratory, a local company, a collecting community, a nonprofit, or a narrow professional field. Its market may be too small for a major software firm but large enough to support the person who understands the problem.<br />
<br />
Long-lived desktop software also creates continuing forms of useful labor:<br />
<br />
* installation;<br />
* customization;<br />
* data conversion;<br />
* training;<br />
* compatibility maintenance;<br />
* support;<br />
* integration with newer services;<br />
* and carefully managed upgrades.<br />
<br />
Backward compatibility does not eliminate this labor. It gives the labor a durable foundation.<br />
<br />
The programmer can improve the application without forcing every user to abandon previous work. The user can invest time learning a tool with some confidence that the tool will not disappear merely because an investor has changed direction.<br />
<br />
This relationship between craftsman and user is especially important in a guild-minded approach to software. The programmer is not merely attempting to capture attention. He is accepting responsibility for an instrument another person may use in his own work.<br />
<br />
== From a working script to a Windows product ==<br />
<br />
A Perl script and a Windows product may contain the same essential program logic, but the user's experience is very different.<br />
<br />
{| class="wikitable"<br />
|+ From the developer's program to the user's product<br />
! The developer may have<br />
! The Windows user reasonably expects<br />
|-<br />
| A <code>.pl</code> file<br />
| An application that starts from an icon<br />
|-<br />
| Installed CPAN modules<br />
| No requirement to install Perl or dependencies<br />
|-<br />
| Commands entered in a terminal<br />
| A graphical interface<br />
|-<br />
| Paths that work on the development computer<br />
| Correct installation and user-data directories<br />
|-<br />
| Diagnostic output in a console<br />
| Understandable errors and useful logs<br />
|-<br />
| A program that works in the workshop<br />
| A program that works on the user's computer<br />
|-<br />
| A collection of build commands<br />
| A repeatable installer and upgrade procedure<br />
|}<br />
<br />
The difficult question is therefore not merely whether Perl can display a graphical window. It can.<br />
<br />
The difficult question is whether we can establish a clear and repeatable path from the Perl programmer's existing skills to software which an ordinary Windows user can install and use.<br />
<br />
That is the purpose of the [[Developing and Distributing wxPerl Applications on Windows|Perl Lazarus Project's documented Windows workflow]].<br />
<br />
== The Perl Lazarus journey ==<br />
<br />
[[File:perl-lazarus-project-workflow.png|thumb|right|420px|alt=Six-stage Perl Lazarus Project workflow from installing the development stack through testing the finished Windows application|The Perl Lazarus Project follows a complete path: install the stack, design the GUI, write the Perl code, package the executable, build the installer, and test the result on Windows.]]<br />
<br />
The Perl Lazarus Project builds upon the renewed wxPerl work associated with Johan Vromans and others in the wxPerl community.<ref>[https://dev.to/sciurius/wxperl-revival-5fde Johan Vromans, “wxPerl Revival”]</ref><br />
<br />
Its name also acknowledges the example of the [https://www.lazarus-ide.org/ Lazarus IDE and Free Pascal community]. Lazarus demonstrates what can happen when a programming community joins a language, a visual designer, components, documentation, packaging practices, and an economy of books, support, consulting, and application development.<br />
<br />
Perl does not necessarily need a single enormous Lazarus-like IDE. It needs a clear path which craftsmen can follow:<br />
<br />
# Install a known working development stack.<br />
# Design the interface.<br />
# Generate and write Perl code.<br />
# Package the application as an executable.<br />
# Build a Windows installer.<br />
# Test the installed program on a clean Windows system.<br />
<br />
The significance of this path is not that any individual step is unknown. Perl already has a native Windows distribution, graphical bindings, interface-design tools, packaging modules, and installer technology. The missing element has been a coherent and repeatable journey connecting them.<br />
<br />
The present stack joins Strawberry Perl, wxWidgets, wxPerl, wxGlade, PAR-based packaging tools, and Inno Setup. The next essay, [[The Perl Lazarus Workshop]], will explain why these tools belong together and what role each one performs in the craftsman’s workshop.<br />
<br />
The series will then proceed through installation, visual design, the wxGlade-to-Perl development cycle, application structure, local data, communication with Perl web services, executable creation, installer construction, testing, and support.<br />
<br />
{{clear}}<br />
<br />
[[File:nhc-advisory-explorer-windows.png|thumb|left|380px|alt=NHC Advisory Explorer running as a packaged Windows desktop application|The NHC Advisory Explorer demonstrates the practical result: a wxPerl program packaged for ordinary Windows users.]]<br />
<br />
This is not merely a theoretical possibility. The [https://github.com/StormSurgeLive/nhc-advisory-gui NHC Advisory Explorer] is one example of a wxPerl program packaged for Windows users.<ref>[https://github.com/StormSurgeLive/nhc-advisory-gui StormSurgeLive, “NHC Advisory Explorer”]</ref><br />
<br />
The program retrieves and presents National Hurricane Center advisory information through a familiar desktop interface. More importantly for this series, it demonstrates that the complete path can be followed: a Perl application can be given a graphical interface, packaged as a Windows executable, placed into an installer, and distributed to users who do not need to install Perl or understand the application’s dependencies.<br />
<br />
That final point is essential. The Perl programmer may know that the application depends upon Strawberry Perl, wxPerl, wxWidgets, CPAN modules, native DLLs, and packaging tools. The user should ordinarily experience only a Windows application which installs and runs in the expected way.<br />
<br />
Readers who want to examine earlier tools and historical attempts at wxWidgets rapid application development in Perl may also consult [[Perl and wxWidgets RAD on Windows]].<br />
<br />
{{clear}}<br />
<br />
== The craft and the virtue ==<br />
<br />
The virtues themselves are discussed elsewhere on Perl Guilds. Here our concern is how they direct the work at hand.<br />
<br />
'''Practical wisdom, or prudence, not laziness''' asks the craftsman to choose tools and markets according to the work which genuinely needs to be done.<br />
<br />
For the weary journeyman or master, prudence may require learning a new part of the trade rather than endlessly repeating familiar server-side work. Existing Perl experience is not discarded. It is redirected and extended.<br />
<br />
For the apprentice, prudence means refusing the temptation to skip directly to a polished commercial product without first learning the underlying tools and workflow.<br />
<br />
Automation does not eliminate the importance of labor. All earthly value is created by human labor. A tool preserves earlier labor and allows new labor to be applied more effectively, but the tool does not recognize the user's need, exercise judgment, accept responsibility, or provide service by itself.<br />
<br />
The aim of the virtuous programmer is therefore not to avoid work. It is to avoid wasting work.<br />
<br />
A repeatable installation procedure preserves labor.<br />
<br />
A visual GUI builder reduces unnecessary mechanical effort.<br />
<br />
Reusable Perl modules preserve tested knowledge.<br />
<br />
An installer saves every user from recreating the developer's environment.<br />
<br />
Backward compatibility protects work already performed by programmers and users.<br />
<br />
Good tools allow the craftsman to direct more effort toward understanding the user and completing the work.<br />
<br />
== At the workbench: propose a masterwork ==<br />
<br />
Before installing anything, describe one possible application.<br />
<br />
Write down:<br />
<br />
# Who will use it?<br />
# What work are they doing now?<br />
# What part of that work belongs on the desktop?<br />
# What part, if any, belongs on a Perl-powered server?<br />
# What files or data will the user provide?<br />
# What result will the application produce?<br />
# What is the smallest version that would be genuinely useful?<br />
# Why would someone install it?<br />
# Why might someone reasonably pay for it?<br />
# What responsibility will you accept after delivering it?<br />
# Could an apprentice learn something by helping with it?<br />
# Could the application remain useful for five or ten years?<br />
<br />
The proposal need not describe a large product. A narrow tool completed well is a better masterwork than an ambitious system which never leaves the developer's computer.<br />
<br />
== Continue the journey ==<br />
<br />
The next essay, [[The Perl Lazarus Workshop]], examines the tools selected for this work: Strawberry Perl, wxWidgets, wxPerl, wxGlade, MSYS2, PAR-based packaging, and Inno Setup.<br />
<br />
The purpose will not be to present a random collection of software. It will be to understand how each tool contributes to one coherent craftsman's workshop, and how the labor embodied in these tools allows a Perl programmer to perform new work of his own.<br />
<br />
<references /><br />
<br />
{{DEFAULTSORT:Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Next essay:''' [[The Perl Lazarus Workshop]]<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]<br />
[[Category:Perl Guilds]]<br />
[[Category:Windows]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=The_Perl_Craftsman_Returns_to_the_Windows_Desktop&diff=369The Perl Craftsman Returns to the Windows Desktop2026-07-19T21:06:46Z<p>Admin: /* The Perl Lazarus journey */</p>
<hr />
<div>{{DISPLAYTITLE:The Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
''This is the first essay in the series [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]. The series follows the practical journey from Perl programmer to craftsman of complete, distributable Windows applications.''<br />
<br />
There comes a point in the life of a programmer when experience can become strangely tiring.<br />
<br />
The journeyman Perl programmer may have crossed many territories. He has repaired old systems, migrated databases, parsed uncooperative data, automated jobs, maintained web applications, connected APIs, managed servers, and rescued programs whose original authors disappeared years ago. He may have spent decades learning that the apparently simple problem is rarely simple, that data supplied by users never quite resembles the example, and that the machine which fails is usually not the machine on which the software was developed.<br />
<br />
The master Perl programmer may have done all of this while teaching others, supporting clients, maintaining community infrastructure, and carrying responsibility for systems which cannot simply be turned off and rewritten in the fashionable language of the year.<br />
<br />
Such a programmer is not obsolete. He may only be weary.<br />
<br />
The repeated announcement of Perl's death can become tiresome. So can working continually behind the scenes while newer communities rediscover techniques that Perl programmers have practiced for decades. The experienced Perl programmer may understandably ask whether there is any new territory worth crossing, or whether his remaining work consists only of maintaining what other people have abandoned.<br />
<br />
At the same time, a newer programmer may sit in front of a Windows computer and never encounter Perl at all. He may know that programs come from an application store, a game launcher, a download page, or a Git repository, but not yet understand that he can create those programs himself. He may be experimenting with game modifications, running a private server, editing configuration files, automating a repetitive task, or wondering how a favorite program works.<br />
<br />
He may, quite literally, be playing video games.<br />
<br />
This series is addressed to both programmers: the experienced craftsman who may need a new application for an old and powerful trade, and the prospective apprentice who has not yet discovered that programming can become his own craft.<br />
<br />
== The programmer as craftsman ==<br />
<br />
The language of the craftsman is useful because programming is not merely the manipulation of symbols. It is the application of knowledge, judgment, practiced skill, and responsibility to a human need.<br />
<br />
The traditional progression from apprentice to journeyman to master should not be treated as a rigid credentialing system or as an excuse for excluding newcomers. It is a way of describing growth within a trade.<br />
<br />
* The '''apprentice''' learns the tools, vocabulary, habits, and established practices of the craft.<br />
* The '''journeyman''' can travel beyond the workshop in which he first learned and apply his skills to unfamiliar problems.<br />
* The '''master''' accepts responsibility for complete work, judges its quality, serves customers, preserves knowledge, and helps form other craftsmen.<br />
<br />
A journeyman is not merely someone who has memorized more syntax than an apprentice. He has learned how to proceed when the documentation is incomplete, the operating environment is unfamiliar, and the first solution does not work.<br />
<br />
A master is not someone who has stopped learning. He is someone whose experience has taught him the weight of a promise. When he says that a program can be installed, can preserve a user's data, or can be supported in a particular environment, he understands that another person's work may depend upon that claim.<br />
<br />
A masterwork is therefore not merely a clever algorithm, an ingenious regular expression, or an impressive piece of code. It is work brought to completion.<br />
<br />
For a Windows desktop application, that completion may include:<br />
<br />
* a useful and understandable graphical interface;<br />
* dependable handling of files and data;<br />
* communication with an existing Perl web service;<br />
* a Windows executable;<br />
* a familiar installer;<br />
* useful documentation;<br />
* testing on a computer other than the developer's;<br />
* a reasonable upgrade and uninstallation path;<br />
* and a plan for supporting the people who use it.<br />
<br />
The purpose of [[Main Page|Perl Guilds]] is to encourage this fuller understanding of the programmer's trade: independent programmers sharing knowledge, cultivating practical specialties, forming one another in the craft, and helping one another earn a living through useful work.<br />
<br />
== An invitation to the weary journeyman ==<br />
<br />
The experienced Perl programmer already possesses much of what is needed to build a valuable desktop application.<br />
<br />
He may know how to:<br />
<br />
* validate and transform data;<br />
* communicate with databases;<br />
* consume and publish APIs;<br />
* process text, images, or scientific data;<br />
* operate remote services;<br />
* automate complex workflows;<br />
* authenticate users;<br />
* generate reports;<br />
* maintain compatibility;<br />
* and diagnose failures in production.<br />
<br />
These abilities do not become irrelevant when a graphical interface is added. They become the substance behind the interface.<br />
<br />
The desktop is not a repudiation of the server work in which Perl programmers have excelled. It is another point at which that work can be placed into the hands of a user.<br />
<br />
A Perl programmer who has spent years building web applications may create a Windows client for one of those applications. A systems programmer may create an administrative console. A scientific programmer may package a model or data-analysis workflow for colleagues who will never use a command line. A collector, historian, translator, accountant, engineer, or small-business owner may need a specialized application that no large software company would consider profitable enough to build.<br />
<br />
The weary journeyman need not begin again as though his past experience counted for nothing. He must learn a new portion of the trade, but he brings his existing judgment with him.<br />
<br />
Perl is not the obstacle. Perl is the leverage.<br />
<br />
== An invitation to the future apprentice ==<br />
<br />
Perl also needs new programmers, and many potential programmers are sitting in front of Windows computers right now.<br />
<br />
It would be impossible to count all future programmers before they discover the craft. We can, however, observe where ordinary desktop users are. Windows remains the largest desktop operating-system family in worldwide usage measurements.<ref>[https://gs.statcounter.com/os-market-share/desktop/ StatCounter Global Stats, “Desktop Operating System Market Share Worldwide”]</ref> It also remains the overwhelmingly prevalent operating-system environment among people participating in the Steam hardware survey.<ref>[https://store.steampowered.com/hwsurvey/ Valve, “Steam Hardware & Software Survey”]</ref><br />
<br />
Many of these users are playing games, installing modifications, running Discord communities, hosting servers, editing files, experimenting with hardware, or trying to automate some irritating part of their digital lives. These activities are not programming apprenticeships by themselves, but they are often close to the doorway.<br />
<br />
A person who asks, “Can I change how this game behaves?” is already asking a programmer's question.<br />
<br />
A person who runs a private game server has begun to encounter networking, configuration, permissions, logs, and failure recovery.<br />
<br />
A person who writes a small script to rename files or process game data has begun to discover that the computer can be instructed rather than merely consumed.<br />
<br />
If Perl wishes to recruit another generation, Perl programmers must be willing to meet prospective programmers where they are. That includes Windows.<br />
<br />
It is not enough to tell a Windows user that serious programmers eventually abandon his environment. It is better to show him that the computer he already owns can become a workshop; that Strawberry Perl gives him a native Perl environment; that wxPerl can create real graphical applications; and that the same language can later take him into web services, databases, systems work, scientific computing, and many other fields.<br />
<br />
The route into the craft should not require the apprentice first to adopt the operating-system preferences of the master.<br />
<br />
== Why return to the desktop? ==<br />
<br />
Perl programmers have long been especially effective behind the scenes.<br />
<br />
Perl may collect the data, operate the website, maintain the database, run the scientific model, communicate with an outside service, or generate the report. The ordinary user may benefit from all of this without ever seeing Perl directly.<br />
<br />
That is not a defect. Invisible infrastructure is often excellent work.<br />
<br />
Nevertheless, the Windows desktop offers another place for the Perl craftsman to practice his trade: directly in front of the person whose work the software is intended to serve.<br />
<br />
A desktop application may:<br />
<br />
* organize files already stored on the user's computer;<br />
* provide a specialized editor or research interface;<br />
* display data from a remote Perl application;<br />
* upload images or documents for server-side processing;<br />
* present results from a database or API;<br />
* allow local work when the network is unavailable;<br />
* interact with devices or applications installed on the computer;<br />
* or provide a richer companion to an existing website.<br />
<br />
A service such as [https://boyscoutpatch.info/ BoyScoutPatch.info], for example, may continue to perform centralized work for which a web application is well suited, while a desktop client could provide a more specialized workflow for collectors, researchers, or administrators.<br />
<br />
This is an application of subsidiarity. The server should perform work which genuinely belongs on the server. The desktop should perform work which is best placed in the user's hands.<br />
<br />
The objective is not to replace every web application with a desktop program. It is to place each responsibility where it can be performed most effectively, while avoiding needless centralization and needless dependence upon a permanent network connection.<br />
<br />
== Why Windows? ==<br />
<br />
This series deliberately focuses on Windows.<br />
<br />
That does not imply that Windows is the only worthy platform, or that wxPerl cannot be useful elsewhere. It means that a craftsman must eventually choose a definite workshop and a definite group of users.<br />
<br />
Windows offers several practical advantages for this undertaking.<br />
<br />
First, Windows has a very large population of ordinary desktop users. That population includes customers, office workers, researchers, collectors, students, gamers, and prospective programmers.<br />
<br />
Second, specialized commercial desktop software is familiar on Windows. Users understand the idea of downloading an application, running an installer, finding the program in the Start menu, and paying for a tool which performs useful work.<br />
<br />
Third, Windows is unusually committed to backward application compatibility. Microsoft states that it goes to great lengths to maintain application and device compatibility across operating-system version changes, especially for ordinary applications without kernel dependencies.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/windows-version-check Microsoft Learn, “Windows version check”]</ref> Windows application manifests even allow newer versions of Windows to preserve behaviors expected by applications targeting older releases.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/application-executable-manifest Microsoft Learn, “App executable manifest”]</ref><br />
<br />
No compatibility promise is absolute. Security changes, removed components, architecture changes, obsolete drivers, and undocumented assumptions can still break old programs. Nevertheless, Windows demonstrates an unusually strong expectation that software written for an earlier generation should continue to function.<br />
<br />
That expectation matters to the independent craftsman.<br />
<br />
A specialized application may serve a modest community for many years. Its value may come from stability rather than constant reinvention. A program which continues working through several generations of hardware and operating systems can repay its development cost many times over.<br />
<br />
Perl's own concern for compatibility belongs naturally in such an environment. Experiments with ActivePerl 5.8.8 on Windows 98 illustrate the extraordinary historical reach of both ecosystems. That does not mean new commercial software should target Windows 98. It means the craftsman should recognize the strategic value of technologies which respect existing work.<br />
<br />
Fourth, Strawberry Perl provides a serious native Windows Perl environment. It includes Perl, a compiler, build utilities, and access to the CPAN ecosystem. The Windows programmer is not confined to a toy interpreter or an imitation of a Unix system.<br />
<br />
Finally, many Perl programmers already use Windows as a daily working environment, and many possible new Perl programmers begin there.<br />
<br />
The choice is therefore practical rather than ideological.<br />
<br />
The question is not, “Which operating system proves that I am a proper programmer?”<br />
<br />
The question is, “Where can existing Perl knowledge be turned into useful software, and where can new craftsmen be invited into the trade?”<br />
<br />
== Extreme compatibility creates an opportunity ==<br />
<br />
Windows' backward compatibility does more than preserve old software. It encourages a particular kind of small-scale production.<br />
<br />
A large vendor may prefer subscriptions, rapid replacement, cloud dependence, and frequent redesign. An independent craftsman may instead produce a focused application which performs one job well and continues doing it for a long time.<br />
<br />
That application might serve only a few hundred users. It might serve a laboratory, a local company, a collecting community, a nonprofit, or a narrow professional field. Its market may be too small for a major software firm but large enough to support the person who understands the problem.<br />
<br />
Long-lived desktop software also creates continuing forms of useful labor:<br />
<br />
* installation;<br />
* customization;<br />
* data conversion;<br />
* training;<br />
* compatibility maintenance;<br />
* support;<br />
* integration with newer services;<br />
* and carefully managed upgrades.<br />
<br />
Backward compatibility does not eliminate this labor. It gives the labor a durable foundation.<br />
<br />
The programmer can improve the application without forcing every user to abandon previous work. The user can invest time learning a tool with some confidence that the tool will not disappear merely because an investor has changed direction.<br />
<br />
This relationship between craftsman and user is especially important in a guild-minded approach to software. The programmer is not merely attempting to capture attention. He is accepting responsibility for an instrument another person may use in his own work.<br />
<br />
== From a working script to a Windows product ==<br />
<br />
A Perl script and a Windows product may contain the same essential program logic, but the user's experience is very different.<br />
<br />
{| class="wikitable"<br />
|+ From the developer's program to the user's product<br />
! The developer may have<br />
! The Windows user reasonably expects<br />
|-<br />
| A <code>.pl</code> file<br />
| An application that starts from an icon<br />
|-<br />
| Installed CPAN modules<br />
| No requirement to install Perl or dependencies<br />
|-<br />
| Commands entered in a terminal<br />
| A graphical interface<br />
|-<br />
| Paths that work on the development computer<br />
| Correct installation and user-data directories<br />
|-<br />
| Diagnostic output in a console<br />
| Understandable errors and useful logs<br />
|-<br />
| A program that works in the workshop<br />
| A program that works on the user's computer<br />
|-<br />
| A collection of build commands<br />
| A repeatable installer and upgrade procedure<br />
|}<br />
<br />
The difficult question is therefore not merely whether Perl can display a graphical window. It can.<br />
<br />
The difficult question is whether we can establish a clear and repeatable path from the Perl programmer's existing skills to software which an ordinary Windows user can install and use.<br />
<br />
That is the purpose of the [[Developing and Distributing wxPerl Applications on Windows|Perl Lazarus Project's documented Windows workflow]].<br />
<br />
== The Perl Lazarus journey ==<br />
<br />
[[File:perl-lazarus-project-workflow.png<br />
|thumb<br />
|right<br />
|420px<br />
|alt=Six-stage Perl Lazarus Project workflow from installing the development stack through testing the finished Windows application<br />
|The Perl Lazarus Project follows a complete path: install the stack, design the GUI, write the Perl code, package the executable, build the installer, and test the result on Windows.<br />
]]<br />
<br />
The Perl Lazarus Project builds upon the renewed wxPerl work associated with Johan Vromans and others in the wxPerl community.<ref>[https://dev.to/sciurius/wxperl-revival-5fde Johan Vromans, “wxPerl Revival”]</ref><br />
<br />
Its name also acknowledges the example of the [https://www.lazarus-ide.org/ Lazarus IDE and Free Pascal community]. Lazarus demonstrates what can happen when a programming community joins a language, a visual designer, components, documentation, packaging practices, and an economy of books, support, consulting, and application development.<br />
<br />
Perl does not necessarily need a single enormous Lazarus-like IDE. It needs a clear path which craftsmen can follow:<br />
<br />
# Install a known working development stack.<br />
# Design the interface.<br />
# Generate and write Perl code.<br />
# Package the application as an executable.<br />
# Build a Windows installer.<br />
# Test the installed program on a clean Windows system.<br />
<br />
The significance of this path is not that any individual step is unknown. Perl already has a native Windows distribution, graphical bindings, interface-design tools, packaging modules, and installer technology. The missing element has been a coherent and repeatable journey connecting them.<br />
<br />
The present stack joins Strawberry Perl, wxWidgets, wxPerl, wxGlade, PAR-based packaging tools, and Inno Setup. The next essay, [[The Perl Lazarus Workshop]], will explain why these tools belong together and what role each one performs in the craftsman’s workshop.<br />
<br />
The series will then proceed through installation, visual design, the wxGlade-to-Perl development cycle, application structure, local data, communication with Perl web services, executable creation, installer construction, testing, and support.<br />
<br />
{{clear}}<br />
<br />
[[File:nhc-advisory-explorer-windows.png<br />
|thumb<br />
|left<br />
|380px<br />
|alt=NHC Advisory Explorer running as a packaged Windows desktop application<br />
|The NHC Advisory Explorer demonstrates the practical result: a wxPerl program packaged for ordinary Windows users.<br />
]]<br />
<br />
This is not merely a theoretical possibility. The [https://github.com/StormSurgeLive/nhc-advisory-gui NHC Advisory Explorer] is one example of a wxPerl program packaged for Windows users.<ref>[https://github.com/StormSurgeLive/nhc-advisory-gui StormSurgeLive, “NHC Advisory Explorer”]</ref><br />
<br />
The program retrieves and presents National Hurricane Center advisory information through a familiar desktop interface. More importantly for this series, it demonstrates that the complete path can be followed: a Perl application can be given a graphical interface, packaged as a Windows executable, placed into an installer, and distributed to users who do not need to install Perl or understand the application’s dependencies.<br />
<br />
That final point is essential. The Perl programmer may know that the application depends upon Strawberry Perl, wxPerl, wxWidgets, CPAN modules, native DLLs, and packaging tools. The user should ordinarily experience only a Windows application which installs and runs in the expected way.<br />
<br />
Readers who want to examine earlier tools and historical attempts at wxWidgets rapid application development in Perl may also consult [[Perl and wxWidgets RAD on Windows]].<br />
<br />
{{clear}}<br />
<br />
== The craft and the virtue ==<br />
<br />
The virtues themselves are discussed elsewhere on Perl Guilds. Here our concern is how they direct the work at hand.<br />
<br />
'''Practical wisdom, or prudence, not laziness''' asks the craftsman to choose tools and markets according to the work which genuinely needs to be done.<br />
<br />
For the weary journeyman or master, prudence may require learning a new part of the trade rather than endlessly repeating familiar server-side work. Existing Perl experience is not discarded. It is redirected and extended.<br />
<br />
For the apprentice, prudence means refusing the temptation to skip directly to a polished commercial product without first learning the underlying tools and workflow.<br />
<br />
Automation does not eliminate the importance of labor. All earthly value is created by human labor. A tool preserves earlier labor and allows new labor to be applied more effectively, but the tool does not recognize the user's need, exercise judgment, accept responsibility, or provide service by itself.<br />
<br />
The aim of the virtuous programmer is therefore not to avoid work. It is to avoid wasting work.<br />
<br />
A repeatable installation procedure preserves labor.<br />
<br />
A visual GUI builder reduces unnecessary mechanical effort.<br />
<br />
Reusable Perl modules preserve tested knowledge.<br />
<br />
An installer saves every user from recreating the developer's environment.<br />
<br />
Backward compatibility protects work already performed by programmers and users.<br />
<br />
Good tools allow the craftsman to direct more effort toward understanding the user and completing the work.<br />
<br />
== At the workbench: propose a masterwork ==<br />
<br />
Before installing anything, describe one possible application.<br />
<br />
Write down:<br />
<br />
# Who will use it?<br />
# What work are they doing now?<br />
# What part of that work belongs on the desktop?<br />
# What part, if any, belongs on a Perl-powered server?<br />
# What files or data will the user provide?<br />
# What result will the application produce?<br />
# What is the smallest version that would be genuinely useful?<br />
# Why would someone install it?<br />
# Why might someone reasonably pay for it?<br />
# What responsibility will you accept after delivering it?<br />
# Could an apprentice learn something by helping with it?<br />
# Could the application remain useful for five or ten years?<br />
<br />
The proposal need not describe a large product. A narrow tool completed well is a better masterwork than an ambitious system which never leaves the developer's computer.<br />
<br />
== Continue the journey ==<br />
<br />
The next essay, [[The Perl Lazarus Workshop]], examines the tools selected for this work: Strawberry Perl, wxWidgets, wxPerl, wxGlade, MSYS2, PAR-based packaging, and Inno Setup.<br />
<br />
The purpose will not be to present a random collection of software. It will be to understand how each tool contributes to one coherent craftsman's workshop, and how the labor embodied in these tools allows a Perl programmer to perform new work of his own.<br />
<br />
<references /><br />
<br />
{{DEFAULTSORT:Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Next essay:''' [[The Perl Lazarus Workshop]]<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]<br />
[[Category:Perl Guilds]]<br />
[[Category:Windows]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=File:Nhc-advisory-explorer-windows.png&diff=368File:Nhc-advisory-explorer-windows.png2026-07-19T21:04:34Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=File:Perl-lazarus-project-workflow.png&diff=367File:Perl-lazarus-project-workflow.png2026-07-19T21:04:01Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=The_Perl_Craftsman_Returns_to_the_Windows_Desktop&diff=366The Perl Craftsman Returns to the Windows Desktop2026-07-19T20:55:24Z<p>Admin: </p>
<hr />
<div>{{DISPLAYTITLE:The Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
''This is the first essay in the series [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]. The series follows the practical journey from Perl programmer to craftsman of complete, distributable Windows applications.''<br />
<br />
There comes a point in the life of a programmer when experience can become strangely tiring.<br />
<br />
The journeyman Perl programmer may have crossed many territories. He has repaired old systems, migrated databases, parsed uncooperative data, automated jobs, maintained web applications, connected APIs, managed servers, and rescued programs whose original authors disappeared years ago. He may have spent decades learning that the apparently simple problem is rarely simple, that data supplied by users never quite resembles the example, and that the machine which fails is usually not the machine on which the software was developed.<br />
<br />
The master Perl programmer may have done all of this while teaching others, supporting clients, maintaining community infrastructure, and carrying responsibility for systems which cannot simply be turned off and rewritten in the fashionable language of the year.<br />
<br />
Such a programmer is not obsolete. He may only be weary.<br />
<br />
The repeated announcement of Perl's death can become tiresome. So can working continually behind the scenes while newer communities rediscover techniques that Perl programmers have practiced for decades. The experienced Perl programmer may understandably ask whether there is any new territory worth crossing, or whether his remaining work consists only of maintaining what other people have abandoned.<br />
<br />
At the same time, a newer programmer may sit in front of a Windows computer and never encounter Perl at all. He may know that programs come from an application store, a game launcher, a download page, or a Git repository, but not yet understand that he can create those programs himself. He may be experimenting with game modifications, running a private server, editing configuration files, automating a repetitive task, or wondering how a favorite program works.<br />
<br />
He may, quite literally, be playing video games.<br />
<br />
This series is addressed to both programmers: the experienced craftsman who may need a new application for an old and powerful trade, and the prospective apprentice who has not yet discovered that programming can become his own craft.<br />
<br />
== The programmer as craftsman ==<br />
<br />
The language of the craftsman is useful because programming is not merely the manipulation of symbols. It is the application of knowledge, judgment, practiced skill, and responsibility to a human need.<br />
<br />
The traditional progression from apprentice to journeyman to master should not be treated as a rigid credentialing system or as an excuse for excluding newcomers. It is a way of describing growth within a trade.<br />
<br />
* The '''apprentice''' learns the tools, vocabulary, habits, and established practices of the craft.<br />
* The '''journeyman''' can travel beyond the workshop in which he first learned and apply his skills to unfamiliar problems.<br />
* The '''master''' accepts responsibility for complete work, judges its quality, serves customers, preserves knowledge, and helps form other craftsmen.<br />
<br />
A journeyman is not merely someone who has memorized more syntax than an apprentice. He has learned how to proceed when the documentation is incomplete, the operating environment is unfamiliar, and the first solution does not work.<br />
<br />
A master is not someone who has stopped learning. He is someone whose experience has taught him the weight of a promise. When he says that a program can be installed, can preserve a user's data, or can be supported in a particular environment, he understands that another person's work may depend upon that claim.<br />
<br />
A masterwork is therefore not merely a clever algorithm, an ingenious regular expression, or an impressive piece of code. It is work brought to completion.<br />
<br />
For a Windows desktop application, that completion may include:<br />
<br />
* a useful and understandable graphical interface;<br />
* dependable handling of files and data;<br />
* communication with an existing Perl web service;<br />
* a Windows executable;<br />
* a familiar installer;<br />
* useful documentation;<br />
* testing on a computer other than the developer's;<br />
* a reasonable upgrade and uninstallation path;<br />
* and a plan for supporting the people who use it.<br />
<br />
The purpose of [[Main Page|Perl Guilds]] is to encourage this fuller understanding of the programmer's trade: independent programmers sharing knowledge, cultivating practical specialties, forming one another in the craft, and helping one another earn a living through useful work.<br />
<br />
== An invitation to the weary journeyman ==<br />
<br />
The experienced Perl programmer already possesses much of what is needed to build a valuable desktop application.<br />
<br />
He may know how to:<br />
<br />
* validate and transform data;<br />
* communicate with databases;<br />
* consume and publish APIs;<br />
* process text, images, or scientific data;<br />
* operate remote services;<br />
* automate complex workflows;<br />
* authenticate users;<br />
* generate reports;<br />
* maintain compatibility;<br />
* and diagnose failures in production.<br />
<br />
These abilities do not become irrelevant when a graphical interface is added. They become the substance behind the interface.<br />
<br />
The desktop is not a repudiation of the server work in which Perl programmers have excelled. It is another point at which that work can be placed into the hands of a user.<br />
<br />
A Perl programmer who has spent years building web applications may create a Windows client for one of those applications. A systems programmer may create an administrative console. A scientific programmer may package a model or data-analysis workflow for colleagues who will never use a command line. A collector, historian, translator, accountant, engineer, or small-business owner may need a specialized application that no large software company would consider profitable enough to build.<br />
<br />
The weary journeyman need not begin again as though his past experience counted for nothing. He must learn a new portion of the trade, but he brings his existing judgment with him.<br />
<br />
Perl is not the obstacle. Perl is the leverage.<br />
<br />
== An invitation to the future apprentice ==<br />
<br />
Perl also needs new programmers, and many potential programmers are sitting in front of Windows computers right now.<br />
<br />
It would be impossible to count all future programmers before they discover the craft. We can, however, observe where ordinary desktop users are. Windows remains the largest desktop operating-system family in worldwide usage measurements.<ref>[https://gs.statcounter.com/os-market-share/desktop/ StatCounter Global Stats, “Desktop Operating System Market Share Worldwide”]</ref> It also remains the overwhelmingly prevalent operating-system environment among people participating in the Steam hardware survey.<ref>[https://store.steampowered.com/hwsurvey/ Valve, “Steam Hardware & Software Survey”]</ref><br />
<br />
Many of these users are playing games, installing modifications, running Discord communities, hosting servers, editing files, experimenting with hardware, or trying to automate some irritating part of their digital lives. These activities are not programming apprenticeships by themselves, but they are often close to the doorway.<br />
<br />
A person who asks, “Can I change how this game behaves?” is already asking a programmer's question.<br />
<br />
A person who runs a private game server has begun to encounter networking, configuration, permissions, logs, and failure recovery.<br />
<br />
A person who writes a small script to rename files or process game data has begun to discover that the computer can be instructed rather than merely consumed.<br />
<br />
If Perl wishes to recruit another generation, Perl programmers must be willing to meet prospective programmers where they are. That includes Windows.<br />
<br />
It is not enough to tell a Windows user that serious programmers eventually abandon his environment. It is better to show him that the computer he already owns can become a workshop; that Strawberry Perl gives him a native Perl environment; that wxPerl can create real graphical applications; and that the same language can later take him into web services, databases, systems work, scientific computing, and many other fields.<br />
<br />
The route into the craft should not require the apprentice first to adopt the operating-system preferences of the master.<br />
<br />
== Why return to the desktop? ==<br />
<br />
Perl programmers have long been especially effective behind the scenes.<br />
<br />
Perl may collect the data, operate the website, maintain the database, run the scientific model, communicate with an outside service, or generate the report. The ordinary user may benefit from all of this without ever seeing Perl directly.<br />
<br />
That is not a defect. Invisible infrastructure is often excellent work.<br />
<br />
Nevertheless, the Windows desktop offers another place for the Perl craftsman to practice his trade: directly in front of the person whose work the software is intended to serve.<br />
<br />
A desktop application may:<br />
<br />
* organize files already stored on the user's computer;<br />
* provide a specialized editor or research interface;<br />
* display data from a remote Perl application;<br />
* upload images or documents for server-side processing;<br />
* present results from a database or API;<br />
* allow local work when the network is unavailable;<br />
* interact with devices or applications installed on the computer;<br />
* or provide a richer companion to an existing website.<br />
<br />
A service such as [https://boyscoutpatch.info/ BoyScoutPatch.info], for example, may continue to perform centralized work for which a web application is well suited, while a desktop client could provide a more specialized workflow for collectors, researchers, or administrators.<br />
<br />
This is an application of subsidiarity. The server should perform work which genuinely belongs on the server. The desktop should perform work which is best placed in the user's hands.<br />
<br />
The objective is not to replace every web application with a desktop program. It is to place each responsibility where it can be performed most effectively, while avoiding needless centralization and needless dependence upon a permanent network connection.<br />
<br />
== Why Windows? ==<br />
<br />
This series deliberately focuses on Windows.<br />
<br />
That does not imply that Windows is the only worthy platform, or that wxPerl cannot be useful elsewhere. It means that a craftsman must eventually choose a definite workshop and a definite group of users.<br />
<br />
Windows offers several practical advantages for this undertaking.<br />
<br />
First, Windows has a very large population of ordinary desktop users. That population includes customers, office workers, researchers, collectors, students, gamers, and prospective programmers.<br />
<br />
Second, specialized commercial desktop software is familiar on Windows. Users understand the idea of downloading an application, running an installer, finding the program in the Start menu, and paying for a tool which performs useful work.<br />
<br />
Third, Windows is unusually committed to backward application compatibility. Microsoft states that it goes to great lengths to maintain application and device compatibility across operating-system version changes, especially for ordinary applications without kernel dependencies.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/windows-version-check Microsoft Learn, “Windows version check”]</ref> Windows application manifests even allow newer versions of Windows to preserve behaviors expected by applications targeting older releases.<ref>[https://learn.microsoft.com/en-us/windows/compatibility/application-executable-manifest Microsoft Learn, “App executable manifest”]</ref><br />
<br />
No compatibility promise is absolute. Security changes, removed components, architecture changes, obsolete drivers, and undocumented assumptions can still break old programs. Nevertheless, Windows demonstrates an unusually strong expectation that software written for an earlier generation should continue to function.<br />
<br />
That expectation matters to the independent craftsman.<br />
<br />
A specialized application may serve a modest community for many years. Its value may come from stability rather than constant reinvention. A program which continues working through several generations of hardware and operating systems can repay its development cost many times over.<br />
<br />
Perl's own concern for compatibility belongs naturally in such an environment. Experiments with ActivePerl 5.8.8 on Windows 98 illustrate the extraordinary historical reach of both ecosystems. That does not mean new commercial software should target Windows 98. It means the craftsman should recognize the strategic value of technologies which respect existing work.<br />
<br />
Fourth, Strawberry Perl provides a serious native Windows Perl environment. It includes Perl, a compiler, build utilities, and access to the CPAN ecosystem. The Windows programmer is not confined to a toy interpreter or an imitation of a Unix system.<br />
<br />
Finally, many Perl programmers already use Windows as a daily working environment, and many possible new Perl programmers begin there.<br />
<br />
The choice is therefore practical rather than ideological.<br />
<br />
The question is not, “Which operating system proves that I am a proper programmer?”<br />
<br />
The question is, “Where can existing Perl knowledge be turned into useful software, and where can new craftsmen be invited into the trade?”<br />
<br />
== Extreme compatibility creates an opportunity ==<br />
<br />
Windows' backward compatibility does more than preserve old software. It encourages a particular kind of small-scale production.<br />
<br />
A large vendor may prefer subscriptions, rapid replacement, cloud dependence, and frequent redesign. An independent craftsman may instead produce a focused application which performs one job well and continues doing it for a long time.<br />
<br />
That application might serve only a few hundred users. It might serve a laboratory, a local company, a collecting community, a nonprofit, or a narrow professional field. Its market may be too small for a major software firm but large enough to support the person who understands the problem.<br />
<br />
Long-lived desktop software also creates continuing forms of useful labor:<br />
<br />
* installation;<br />
* customization;<br />
* data conversion;<br />
* training;<br />
* compatibility maintenance;<br />
* support;<br />
* integration with newer services;<br />
* and carefully managed upgrades.<br />
<br />
Backward compatibility does not eliminate this labor. It gives the labor a durable foundation.<br />
<br />
The programmer can improve the application without forcing every user to abandon previous work. The user can invest time learning a tool with some confidence that the tool will not disappear merely because an investor has changed direction.<br />
<br />
This relationship between craftsman and user is especially important in a guild-minded approach to software. The programmer is not merely attempting to capture attention. He is accepting responsibility for an instrument another person may use in his own work.<br />
<br />
== From a working script to a Windows product ==<br />
<br />
A Perl script and a Windows product may contain the same essential program logic, but the user's experience is very different.<br />
<br />
{| class="wikitable"<br />
|+ From the developer's program to the user's product<br />
! The developer may have<br />
! The Windows user reasonably expects<br />
|-<br />
| A <code>.pl</code> file<br />
| An application that starts from an icon<br />
|-<br />
| Installed CPAN modules<br />
| No requirement to install Perl or dependencies<br />
|-<br />
| Commands entered in a terminal<br />
| A graphical interface<br />
|-<br />
| Paths that work on the development computer<br />
| Correct installation and user-data directories<br />
|-<br />
| Diagnostic output in a console<br />
| Understandable errors and useful logs<br />
|-<br />
| A program that works in the workshop<br />
| A program that works on the user's computer<br />
|-<br />
| A collection of build commands<br />
| A repeatable installer and upgrade procedure<br />
|}<br />
<br />
The difficult question is therefore not merely whether Perl can display a graphical window. It can.<br />
<br />
The difficult question is whether we can establish a clear and repeatable path from the Perl programmer's existing skills to software which an ordinary Windows user can install and use.<br />
<br />
That is the purpose of the [[Developing and Distributing wxPerl Applications on Windows|Perl Lazarus Project's documented Windows workflow]].<br />
<br />
== The Perl Lazarus journey ==<br />
<br />
The Perl Lazarus Project builds upon the renewed wxPerl work associated with Johan Vromans and others in the wxPerl community.<ref>[https://dev.to/sciurius/wxperl-revival-5fde Johan Vromans, “wxPerl Revival”]</ref><br />
<br />
Its name also acknowledges the example of the [https://www.lazarus-ide.org/ Lazarus IDE and Free Pascal community]. Lazarus demonstrates what can happen when a programming community joins a language, a visual designer, components, documentation, packaging practices, and an economy of books, support, consulting, and application development.<br />
<br />
Perl does not necessarily need a single enormous Lazarus-like IDE. It needs a path which craftsmen can follow.<br />
<br />
[[File:perl-lazarus-project-workflow.png|thumb|center|900px|alt=Workflow from installing the wxPerl stack through testing an installed Windows application|The Perl Lazarus Project follows the complete journey from installing the stack to testing an installed Windows application.]]<br />
<br />
# Install a known working development stack.<br />
# Design the interface.<br />
# Generate and write Perl code.<br />
# Package the application as an executable.<br />
# Build a Windows installer.<br />
# Test the installed program on a clean Windows system.<br />
<br />
The present stack joins Strawberry Perl, wxWidgets, wxPerl, wxGlade, PAR-based packaging tools, and Inno Setup. The next essay, [[The Perl Lazarus Workshop]], will explain why these tools belong together.<br />
<br />
The series will then proceed through installation, visual design, the wxGlade-to-Perl development cycle, application structure, local data, communication with Perl web services, executable creation, installer construction, testing, and support.<br />
<br />
This is not merely a theoretical possibility. The [https://github.com/StormSurgeLive/nhc-advisory-gui NHC Advisory Explorer] is one example of a wxPerl program packaged for Windows users.<ref>[https://github.com/StormSurgeLive/nhc-advisory-gui StormSurgeLive, “NHC Advisory Explorer”]</ref><br />
<br />
Readers who want to examine earlier tools and historical attempts at wxWidgets rapid application development in Perl may also consult [[Perl and wxWidgets RAD on Windows]].<br />
<br />
[[File:nhc-advisory-explorer-windows.png|thumb|center|850px|alt=NHC Advisory Explorer running as a Windows desktop application|The NHC Advisory Explorer demonstrates a wxPerl application distributed for ordinary Windows use.]]<br />
<br />
== The craft and the virtue ==<br />
<br />
The virtues themselves are discussed elsewhere on Perl Guilds. Here our concern is how they direct the work at hand.<br />
<br />
'''Practical wisdom, or prudence, not laziness''' asks the craftsman to choose tools and markets according to the work which genuinely needs to be done.<br />
<br />
For the weary journeyman or master, prudence may require learning a new part of the trade rather than endlessly repeating familiar server-side work. Existing Perl experience is not discarded. It is redirected and extended.<br />
<br />
For the apprentice, prudence means refusing the temptation to skip directly to a polished commercial product without first learning the underlying tools and workflow.<br />
<br />
Automation does not eliminate the importance of labor. All earthly value is created by human labor. A tool preserves earlier labor and allows new labor to be applied more effectively, but the tool does not recognize the user's need, exercise judgment, accept responsibility, or provide service by itself.<br />
<br />
The aim of the virtuous programmer is therefore not to avoid work. It is to avoid wasting work.<br />
<br />
A repeatable installation procedure preserves labor.<br />
<br />
A visual GUI builder reduces unnecessary mechanical effort.<br />
<br />
Reusable Perl modules preserve tested knowledge.<br />
<br />
An installer saves every user from recreating the developer's environment.<br />
<br />
Backward compatibility protects work already performed by programmers and users.<br />
<br />
Good tools allow the craftsman to direct more effort toward understanding the user and completing the work.<br />
<br />
== At the workbench: propose a masterwork ==<br />
<br />
Before installing anything, describe one possible application.<br />
<br />
Write down:<br />
<br />
# Who will use it?<br />
# What work are they doing now?<br />
# What part of that work belongs on the desktop?<br />
# What part, if any, belongs on a Perl-powered server?<br />
# What files or data will the user provide?<br />
# What result will the application produce?<br />
# What is the smallest version that would be genuinely useful?<br />
# Why would someone install it?<br />
# Why might someone reasonably pay for it?<br />
# What responsibility will you accept after delivering it?<br />
# Could an apprentice learn something by helping with it?<br />
# Could the application remain useful for five or ten years?<br />
<br />
The proposal need not describe a large product. A narrow tool completed well is a better masterwork than an ambitious system which never leaves the developer's computer.<br />
<br />
== Continue the journey ==<br />
<br />
The next essay, [[The Perl Lazarus Workshop]], examines the tools selected for this work: Strawberry Perl, wxWidgets, wxPerl, wxGlade, MSYS2, PAR-based packaging, and Inno Setup.<br />
<br />
The purpose will not be to present a random collection of software. It will be to understand how each tool contributes to one coherent craftsman's workshop, and how the labor embodied in these tools allows a Perl programmer to perform new work of his own.<br />
<br />
<references /><br />
<br />
{{DEFAULTSORT:Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Next essay:''' [[The Perl Lazarus Workshop]]<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]<br />
[[Category:Perl Guilds]]<br />
[[Category:Windows]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Portal:Essays_about_The_Virtuous_Perl_Programmer&diff=365Portal:Essays about The Virtuous Perl Programmer2026-07-19T20:41:24Z<p>Admin: /* The Technical Journey */</p>
<hr />
<div>== The Technical Journey ==<br />
<br />
1 [[The Perl Craftsman Returns to the Windows Desktop|The Perl Craftsman Returns to the Windows Desktop]]<br />
*: ''Why the journeyman, master, and aspiring Perl programmer should learn to build complete Windows applications.''<br />
<br />
2 [[The Perl Lazarus Workshop|The Perl Lazarus Workshop]]<br />
*: ''Why Strawberry Perl, wxWidgets, wxPerl, wxGlade, MSYS2, PAR, and Inno Setup belong in one practical workshop.''<br />
<br />
3 [[Raising a Working wxPerl Shop on Windows|Raising a Working wxPerl Shop on Windows]]<br />
*: ''Installing the toolchain and establishing an efficient edit–emit–wire–run workflow.''<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Portal:Essays_about_The_Virtuous_Perl_Programmer&diff=364Portal:Essays about The Virtuous Perl Programmer2026-07-19T20:40:56Z<p>Admin: /* The Technical Journey */</p>
<hr />
<div>== The Technical Journey ==<br />
<br />
1 [[The Perl Craftsman Returns to the Windows Desktop|The Perl Craftsman Returns to the Windows Desktop]]<br />
#: ''Why the journeyman, master, and aspiring Perl programmer should learn to build complete Windows applications.''<br />
<br />
2 [[The Perl Lazarus Workshop|The Perl Lazarus Workshop]]<br />
#: ''Why Strawberry Perl, wxWidgets, wxPerl, wxGlade, MSYS2, PAR, and Inno Setup belong in one practical workshop.''<br />
<br />
3 [[Raising a Working wxPerl Shop on Windows|Raising a Working wxPerl Shop on Windows]]<br />
#: ''Installing the toolchain and establishing an efficient edit–emit–wire–run workflow.''<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Raising_a_Working_wxPerl_Shop_on_Windows&diff=363Raising a Working wxPerl Shop on Windows2026-07-19T20:39:40Z<p>Admin: Created page with "'''Previous essay:''' The Perl Lazarus Workshop '''Series:''' Essays about The Virtuous Perl Programmer Category:The Virtuous Perl Programmer Category:Perl Lazarus Project Category:wxPerl"</p>
<hr />
<div>'''Previous essay:''' [[The Perl Lazarus Workshop]]<br />
<br />
'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=The_Perl_Lazarus_Workshop&diff=362The Perl Lazarus Workshop2026-07-19T20:39:19Z<p>Admin: Created page with "'''Previous essay:''' The Perl Craftsman Returns to the Windows Desktop '''Series:''' Essays about The Virtuous Perl Programmer '''Next essay:''' Raising a Working wxPerl Shop on Windows Category:The Virtuous Perl Programmer Category:Perl Lazarus Project Category:wxPerl"</p>
<hr />
<div>'''Previous essay:''' [[The Perl Craftsman Returns to the Windows Desktop]]<br />
<br />
'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Next essay:''' [[Raising a Working wxPerl Shop on Windows]]<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=The_Perl_Craftsman_Returns_to_the_Windows_Desktop&diff=361The Perl Craftsman Returns to the Windows Desktop2026-07-19T20:39:00Z<p>Admin: </p>
<hr />
<div>{{DEFAULTSORT:Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Next essay:''' [[The Perl Lazarus Workshop]]<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=The_Perl_Craftsman_Returns_to_the_Windows_Desktop&diff=360The Perl Craftsman Returns to the Windows Desktop2026-07-19T20:38:45Z<p>Admin: Created page with "{{DEFAULTSORT:Perl Craftsman Returns to the Windows Desktop}} '''Series:''' Essays about The Virtuous Perl Programmer '''Next essay:''' The Perl Lazarus Workshop"</p>
<hr />
<div>{{DEFAULTSORT:Perl Craftsman Returns to the Windows Desktop}}<br />
<br />
'''Series:''' [[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
<br />
'''Next essay:''' [[The Perl Lazarus Workshop]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Portal:Essays_about_The_Virtuous_Perl_Programmer&diff=359Portal:Essays about The Virtuous Perl Programmer2026-07-19T20:38:21Z<p>Admin: Created page with "== The Technical Journey == # The Perl Craftsman Returns to the Windows Desktop #: ''Why the journeyman, master, and aspiring Perl programmer should learn to build complete Windows applications.'' # The Perl Lazarus Workshop #: ''Why Strawberry Perl, wxWidgets, wxPerl, wxGlade, MSYS2, PAR, and Inno Setup belong in one practical workshop.'' # Raising a Working wxPerl Shop on Windows|R..."</p>
<hr />
<div>== The Technical Journey ==<br />
<br />
# [[The Perl Craftsman Returns to the Windows Desktop|The Perl Craftsman Returns to the Windows Desktop]]<br />
#: ''Why the journeyman, master, and aspiring Perl programmer should learn to build complete Windows applications.''<br />
<br />
# [[The Perl Lazarus Workshop|The Perl Lazarus Workshop]]<br />
#: ''Why Strawberry Perl, wxWidgets, wxPerl, wxGlade, MSYS2, PAR, and Inno Setup belong in one practical workshop.''<br />
<br />
# [[Raising a Working wxPerl Shop on Windows|Raising a Working wxPerl Shop on Windows]]<br />
#: ''Installing the toolchain and establishing an efficient edit–emit–wire–run workflow.''<br />
<br />
[[Category:The Virtuous Perl Programmer]]<br />
[[Category:Perl Lazarus Project]]<br />
[[Category:wxPerl]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Main_Page&diff=358Main Page2026-07-19T20:27:30Z<p>Admin: /* General Audience Links */</p>
<hr />
<div>=== Welcome to the Perl Guilds Wiki ===<br />
The '''Perl Guilds''' wiki is a community-driven resource designed to support '''freelance Perl programmers''' and help them thrive in their independent careers. The original wiki concept was inspired by [https://wiki.freepascal.org FreePascal]'s community wiki.<br />
<br />
This wiki is maintained by [[ServiceProviders|'''these people''']]. You may thank them for this resource by hiring them for something.<br />
<br />
=== Transforming Perl by Striving for Virtue ===<br />
The infamous three "virtues" of a Perl programmer are not what you have been led to believe. They are bad, very bad. Please [https://www.youtube.com/watch?v=mEWfo9U3uTM view this] to learn more about [[The Real 3 Virtues of Perl|'''the true virtues of Perl''']]: '''''Prudence''''', '''''Spiritedness''''', and '''''Good Order'''''.<br />
<br />
I hope to convey these ideals through this resource, and I hope you can help me.<br />
<br />
=== Site Feedback and Contributions ===<br />
Click [https://github.com/The-Perl-Cottage-Guild/wiki-requests/issues here] to report an issue with the content, suggest edits or additions, or request editor access.<br />
<br />
You may also [https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors '''join the editors email list'''] to provide feedback, volunteer, or discuss proposed changes. <u>'''''[https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors This may get you a quicker response].'''''</u><br />
<br />
Volunteers are eligible to create a listing [[ServiceProviders|here]].<br />
<br />
= Portals =<br />
<br />
<div style="float:left; width:49%;"><br />
<br />
{| class="wikitable" width="100%"<br />
| valign="top" |<br />
<br />
== General Audience Links ==<br />
<br />
Wiki portals have been created for a selection of the platforms and topics that Perl and related tools support. The portals gather related information for each platform or topic in one place to make it easier to locate. The full list of supported platforms may be found [[Platform_list|here]].<br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:wxPerl.png|link=Portal:GUIs with Perl|[[Portal:GUIs with Perl|GUIs with Perl]]<br />
File:Logo Windows 01.png|link=Portal:Windows|[[Portal:Windows|Windows]]<br />
File:Payment.jpeg|link=Portal:Payment Processing|[[Portal:Payment Processing|Getting Paid]]<br />
File:Perlopenmp.jpeg|link=Portal:Perl+OpenMP|[[Portal:Perl+OpenMP|Perl+OpenMP]]<br />
File:Concurrency.png|link=Portal:Concurrency|[[Portal:Concurrency|Concurrency]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:ToolBox.png|link=Portal:Software Development Tools|[[Portal:Software Development Tools|Development Tools]]<br />
File:perlCGI.jpg|link=Portal:Perl CGI Programming|[[Portal:Perl CGI Programming|Legacy Perl]]<br />
File:Camels.jpg|link=Portal:Perl Powered Programs (PPP)|[[Portal:Perl Powered Programs (PPP)|Perl Powered Programs (PPP)]]<br />
File:Perlcommunity.png|link=Portal:Perl Communities|[[Portal:Perl Communities|Communities]]<br />
File:XS.jpg|link=Portal:Embedding and Extending Perl|[[Portal:Embedding and Extending Perl|Embedding and Extending Perl]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Money.jpeg|link=Portal:Perl for Profit|[[Portal:Perl for Profit|Perl for Profit]]<br />
File:History.gif|link=Portal:Perl History|[[Portal:Perl History|Perl History]]<br />
File:SQLdb TSQLQuery.PNG|link=Portal:Databases|[[Portal:Databases|Database Development]]<br />
File:GamesPortalLogo.png|link=Portal:Game Development|[[Portal:Game Development|Game Development]]<br />
File:HowTo.png|link=Portal:HowTo Demos|[[Portal:HowTo Demos|HowTo Demos]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Rperl.jpeg|link=Portal:Alt. Perls|[[Portal:Alt. Perls|Alt. Perls]]<br />
File:Ai.jpeg|link=Portal:Artificial Intelligence|[[Portal:Artificial Intelligence|Artificial Intelligence]]<br />
File:Crypto.png|link=Portal:Crypto and Blockchain|[[Portal:Crypto and Blockchain|Blockchain]]<br />
File:Perlbooks.jpg|link=Portal:Ex Libris|[[Portal:Ex Libris|Ex Libris]]<br />
File:Embedded.png|link=Portal:Embedded|[[Portal:Embedded|Embedded]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:FBSD Daemon.jpg|link=Portal:FreeBSD,OpenBSD,etc|[[Portal:FreeBSD,OpenBSD,etc|FreeBSD, OpenBSD, etc.]]<br />
File:tux.png|link=Portal:Linux|[[Portal:Linux|Linux]]<br />
File:macOSlogo.png|link=Portal:Mac|[[Portal:Mac|macOS]]<br />
File:HardwarePortalLogo.png|link=Portal:Hardware and Robotics|[[Portal:Hardware and Robotics|Hardware and Robotics]]<br />
File:Businessmodels.jpeg|link=Portal:Perl Business Models and Case Studies|[[Portal:Perl Business Models and Case Studies|Perl Business Models and Case Studies]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:ImageMagick.gif|link=Portal:Graphics Programming|[[Portal:Graphics Programming|Graphics Programming]]<br />
File:Hpc.jpg|link=Portal:HPC - High Performance Computing|[[Portal:HPC - High Performance Computing|HPC - High Performance Computing]]<br />
File:Bioperl.jpeg|link=Portal:Life Sciences|[[Portal:Life Sciences|Life Sciences]]<br />
File:tdrawgrid.png|link=Portal:SaaS and Web Development|[[Portal:SaaS and Web Development|SaaS and Web Development]]<br />
File:tachart getting started step6.png|link=Portal:SciTech|[[Portal:SciTech|Science and Technology]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:NewUserLogo.png|link=Portal:New Users|[[Portal:Essays about The Virtuous Perl Programmer|Essays about The Virtuous Perl Programmer]]<br />
</gallery><br />
|}<br />
<br />
</div><br />
<br />
<div style="float:right; width:49%;"><br />
<br />
{| class="wikitable" width="100%"<br />
| valign="top" |<br />
<br />
== Perl Craftsmen and Professional Development ==<br />
<br />
'''This section is for independent software professionals''' '''who charge money for Perl-related services''' and use Perl as their secret weapon to make a living, or for those wishing to become one.<br />
<br />
It is not for "jacks of all trades." This section is for Perl craftsmen: journeymen and true masters who wish to leverage their Perl skills to put food in their kids' mouths and a roof over their heads.<br />
<br />
'''Quick Links'''<br />
<br />
* [[Developing and Distributing wxPerl Applications on Windows|wxPerl on Windows: developing and distributing wxPerl applications]]<br />
<br />
'''Notable Updates'''<br />
<br />
* [[Portal:GUIs with Perl|GUIs with Perl]]<br />
** [[Developing and Distributing wxPerl Applications on Windows]]<br />
* [[Portal:Perl+OpenMP|Perl+OpenMP]]<br />
<br />
'''Email Lists'''<br />
<br />
* '''[https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors Perl-Guilds Wiki Contributors]''' listserv - join if you would like to contribute or offer regular feedback<br />
* '''[https://sourceforge.net/projects/perl-openmp/lists/perl-openmp-discuss Perl+OpenMP]''' listserv<br />
<br />
'''Note''': Yes, I encourage email lists for your project; and it turns out SourceForge.net is a great place to host reliable email lists!<br />
<br />
'''RAD, Rapid Application Development Tools, IDEs, and Installer-Makers'''<br />
<br />
* [https://sourceforge.net/projects/wxglade/ wxGlade] - written in Python, but can output Perl<br />
<br />
'''Using Perl for Making Windows GUI Programs'''<br />
<br />
* Cross-platform GUIs with wxPerl<br />
** [[Developing and Distributing wxPerl Applications on Windows]]<br />
* Windows-specific GUIs with Win32::GUI<br />
* Cross-platform GUIs with GUIDeFATE<br />
<br />
'''Using Perl for Creating a Commercial SaaS and Other Services'''<br />
<br />
'''Monetization Strategies for Perl Programmers'''<br />
<br />
'''Commercial Success Stories and Case Studies'''<br />
<br />
'''Downloads'''<br />
<br />
'''Community Participation'''<br />
<br />
* [https://www.perl-guilds.net Perl Guilds Forum] - test forum to see if any activity is drawn to it<br />
<br />
'''Tutorials'''<br />
<br />
'''Books and Magazines'''<br />
<br />
'''Related Sites'''<br />
<br />
* https://perlclientdirectory.com/ - curated list of Perl clients for external APIs and services<br />
* https://perlmodules.net - track changes to your favorite Perl modules in CPAN<br />
<br />
|}<br />
<br />
</div><br />
<br />
<div style="float:left; margin-right:0.9em;"><br />
<br />
== In the News ==<br />
<br />
A summary of recent news stories about Perl can be found [[In the News|here]].<br />
<br />
== Projects using Perl ==<br />
<br />
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]].<br />
<br />
== Bug Tracker ==<br />
<br />
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. 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]].<br />
<br />
<br /><br />
</div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=Main_Page&diff=357Main Page2026-07-19T20:27:01Z<p>Admin: /* General Audience Links */</p>
<hr />
<div>=== Welcome to the Perl Guilds Wiki ===<br />
The '''Perl Guilds''' wiki is a community-driven resource designed to support '''freelance Perl programmers''' and help them thrive in their independent careers. The original wiki concept was inspired by [https://wiki.freepascal.org FreePascal]'s community wiki.<br />
<br />
This wiki is maintained by [[ServiceProviders|'''these people''']]. You may thank them for this resource by hiring them for something.<br />
<br />
=== Transforming Perl by Striving for Virtue ===<br />
The infamous three "virtues" of a Perl programmer are not what you have been led to believe. They are bad, very bad. Please [https://www.youtube.com/watch?v=mEWfo9U3uTM view this] to learn more about [[The Real 3 Virtues of Perl|'''the true virtues of Perl''']]: '''''Prudence''''', '''''Spiritedness''''', and '''''Good Order'''''.<br />
<br />
I hope to convey these ideals through this resource, and I hope you can help me.<br />
<br />
=== Site Feedback and Contributions ===<br />
Click [https://github.com/The-Perl-Cottage-Guild/wiki-requests/issues here] to report an issue with the content, suggest edits or additions, or request editor access.<br />
<br />
You may also [https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors '''join the editors email list'''] to provide feedback, volunteer, or discuss proposed changes. <u>'''''[https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors This may get you a quicker response].'''''</u><br />
<br />
Volunteers are eligible to create a listing [[ServiceProviders|here]].<br />
<br />
= Portals =<br />
<br />
<div style="float:left; width:49%;"><br />
<br />
{| class="wikitable" width="100%"<br />
| valign="top" |<br />
<br />
== General Audience Links ==<br />
<br />
Wiki portals have been created for a selection of the platforms and topics that Perl and related tools support. The portals gather related information for each platform or topic in one place to make it easier to locate. The full list of supported platforms may be found [[Platform_list|here]].<br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:wxPerl.png|link=Portal:GUIs with Perl|[[Portal:GUIs with Perl|GUIs with Perl]]<br />
File:Logo Windows 01.png|link=Portal:Windows|[[Portal:Windows|Windows]]<br />
File:Payment.jpeg|link=Portal:Payment Processing|[[Portal:Payment Processing|Getting Paid]]<br />
File:Perlopenmp.jpeg|link=Portal:Perl+OpenMP|[[Portal:Perl+OpenMP|Perl+OpenMP]]<br />
File:Concurrency.png|link=Portal:Concurrency|[[Portal:Concurrency|Concurrency]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:ToolBox.png|link=Portal:Software Development Tools|[[Portal:Software Development Tools|Development Tools]]<br />
File:perlCGI.jpg|link=Portal:Perl CGI Programming|[[Portal:Perl CGI Programming|Legacy Perl]]<br />
File:Camels.jpg|link=Portal:Perl Powered Programs (PPP)|[[Portal:Perl Powered Programs (PPP)|Perl Powered Programs (PPP)]]<br />
File:Perlcommunity.png|link=Portal:Perl Communities|[[Portal:Perl Communities|Communities]]<br />
File:XS.jpg|link=Portal:Embedding and Extending Perl|[[Portal:Embedding and Extending Perl|Embedding and Extending Perl]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Money.jpeg|link=Portal:Perl for Profit|[[Portal:Perl for Profit|Perl for Profit]]<br />
File:History.gif|link=Portal:Perl History|[[Portal:Perl History|Perl History]]<br />
File:SQLdb TSQLQuery.PNG|link=Portal:Databases|[[Portal:Databases|Database Development]]<br />
File:GamesPortalLogo.png|link=Portal:Game Development|[[Portal:Game Development|Game Development]]<br />
File:HowTo.png|link=Portal:HowTo Demos|[[Portal:HowTo Demos|HowTo Demos]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Rperl.jpeg|link=Portal:Alt. Perls|[[Portal:Alt. Perls|Alt. Perls]]<br />
File:Ai.jpeg|link=Portal:Artificial Intelligence|[[Portal:Artificial Intelligence|Artificial Intelligence]]<br />
File:Crypto.png|link=Portal:Crypto and Blockchain|[[Portal:Crypto and Blockchain|Blockchain]]<br />
File:Perlbooks.jpg|link=Portal:Ex Libris|[[Portal:Ex Libris|Ex Libris]]<br />
File:Embedded.png|link=Portal:Embedded|[[Portal:Embedded|Embedded]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:FBSD Daemon.jpg|link=Portal:FreeBSD,OpenBSD,etc|[[Portal:FreeBSD,OpenBSD,etc|FreeBSD, OpenBSD, etc.]]<br />
File:tux.png|link=Portal:Linux|[[Portal:Linux|Linux]]<br />
File:macOSlogo.png|link=Portal:Mac|[[Portal:Mac|macOS]]<br />
File:HardwarePortalLogo.png|link=Portal:Hardware and Robotics|[[Portal:Hardware and Robotics|Hardware and Robotics]]<br />
File:Businessmodels.jpeg|link=Portal:Perl Business Models and Case Studies|[[Portal:Perl Business Models and Case Studies|Perl Business Models and Case Studies]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:ImageMagick.gif|link=Portal:Graphics Programming|[[Portal:Graphics Programming|Graphics Programming]]<br />
File:Hpc.jpg|link=Portal:HPC - High Performance Computing|[[Portal:HPC - High Performance Computing|HPC - High Performance Computing]]<br />
File:Bioperl.jpeg|link=Portal:Life Sciences|[[Portal:Life Sciences|Life Sciences]]<br />
File:tdrawgrid.png|link=Portal:SaaS and Web Development|[[Portal:SaaS and Web Development|SaaS and Web Development]]<br />
File:tachart getting started step6.png|link=Portal:SciTech|[[Portal:SciTech|Science and Technology]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:NewUserLogo.png|link=Portal:New Users|[[Portal:Essays on The Virtuous Perl Programmer|Essays on The Virtuous Perl Programmer]]<br />
</gallery><br />
|}<br />
<br />
</div><br />
<br />
<div style="float:right; width:49%;"><br />
<br />
{| class="wikitable" width="100%"<br />
| valign="top" |<br />
<br />
== Perl Craftsmen and Professional Development ==<br />
<br />
'''This section is for independent software professionals''' '''who charge money for Perl-related services''' and use Perl as their secret weapon to make a living, or for those wishing to become one.<br />
<br />
It is not for "jacks of all trades." This section is for Perl craftsmen: journeymen and true masters who wish to leverage their Perl skills to put food in their kids' mouths and a roof over their heads.<br />
<br />
'''Quick Links'''<br />
<br />
* [[Developing and Distributing wxPerl Applications on Windows|wxPerl on Windows: developing and distributing wxPerl applications]]<br />
<br />
'''Notable Updates'''<br />
<br />
* [[Portal:GUIs with Perl|GUIs with Perl]]<br />
** [[Developing and Distributing wxPerl Applications on Windows]]<br />
* [[Portal:Perl+OpenMP|Perl+OpenMP]]<br />
<br />
'''Email Lists'''<br />
<br />
* '''[https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors Perl-Guilds Wiki Contributors]''' listserv - join if you would like to contribute or offer regular feedback<br />
* '''[https://sourceforge.net/projects/perl-openmp/lists/perl-openmp-discuss Perl+OpenMP]''' listserv<br />
<br />
'''Note''': Yes, I encourage email lists for your project; and it turns out SourceForge.net is a great place to host reliable email lists!<br />
<br />
'''RAD, Rapid Application Development Tools, IDEs, and Installer-Makers'''<br />
<br />
* [https://sourceforge.net/projects/wxglade/ wxGlade] - written in Python, but can output Perl<br />
<br />
'''Using Perl for Making Windows GUI Programs'''<br />
<br />
* Cross-platform GUIs with wxPerl<br />
** [[Developing and Distributing wxPerl Applications on Windows]]<br />
* Windows-specific GUIs with Win32::GUI<br />
* Cross-platform GUIs with GUIDeFATE<br />
<br />
'''Using Perl for Creating a Commercial SaaS and Other Services'''<br />
<br />
'''Monetization Strategies for Perl Programmers'''<br />
<br />
'''Commercial Success Stories and Case Studies'''<br />
<br />
'''Downloads'''<br />
<br />
'''Community Participation'''<br />
<br />
* [https://www.perl-guilds.net Perl Guilds Forum] - test forum to see if any activity is drawn to it<br />
<br />
'''Tutorials'''<br />
<br />
'''Books and Magazines'''<br />
<br />
'''Related Sites'''<br />
<br />
* https://perlclientdirectory.com/ - curated list of Perl clients for external APIs and services<br />
* https://perlmodules.net - track changes to your favorite Perl modules in CPAN<br />
<br />
|}<br />
<br />
</div><br />
<br />
<div style="float:left; margin-right:0.9em;"><br />
<br />
== In the News ==<br />
<br />
A summary of recent news stories about Perl can be found [[In the News|here]].<br />
<br />
== Projects using Perl ==<br />
<br />
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]].<br />
<br />
== Bug Tracker ==<br />
<br />
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. 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]].<br />
<br />
<br /><br />
</div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=Main_Page&diff=356Main Page2026-07-10T16:25:33Z<p>Admin: </p>
<hr />
<div>=== Welcome to the Perl Guilds Wiki ===<br />
The '''Perl Guilds''' wiki is a community-driven resource designed to support '''freelance Perl programmers''' and help them thrive in their independent careers. The original wiki concept was inspired by [https://wiki.freepascal.org FreePascal]'s community wiki.<br />
<br />
This wiki is maintained by [[ServiceProviders|'''these people''']]. You may thank them for this resource by hiring them for something.<br />
<br />
=== Transforming Perl by Striving for Virtue ===<br />
The infamous three "virtues" of a Perl programmer are not what you have been led to believe. They are bad, very bad. Please [https://www.youtube.com/watch?v=mEWfo9U3uTM view this] to learn more about [[The Real 3 Virtues of Perl|'''the true virtues of Perl''']]: '''''Prudence''''', '''''Spiritedness''''', and '''''Good Order'''''.<br />
<br />
I hope to convey these ideals through this resource, and I hope you can help me.<br />
<br />
=== Site Feedback and Contributions ===<br />
Click [https://github.com/The-Perl-Cottage-Guild/wiki-requests/issues here] to report an issue with the content, suggest edits or additions, or request editor access.<br />
<br />
You may also [https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors '''join the editors email list'''] to provide feedback, volunteer, or discuss proposed changes. <u>'''''[https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors This may get you a quicker response].'''''</u><br />
<br />
Volunteers are eligible to create a listing [[ServiceProviders|here]].<br />
<br />
= Portals =<br />
<br />
<div style="float:left; width:49%;"><br />
<br />
{| class="wikitable" width="100%"<br />
| valign="top" |<br />
<br />
== General Audience Links ==<br />
<br />
Wiki portals have been created for a selection of the platforms and topics that Perl and related tools support. The portals gather related information for each platform or topic in one place to make it easier to locate. The full list of supported platforms may be found [[Platform_list|here]].<br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:wxPerl.png|link=Portal:GUIs with Perl|[[Portal:GUIs with Perl|GUIs with Perl]]<br />
File:Logo Windows 01.png|link=Portal:Windows|[[Portal:Windows|Windows]]<br />
File:Payment.jpeg|link=Portal:Payment Processing|[[Portal:Payment Processing|Getting Paid]]<br />
File:Perlopenmp.jpeg|link=Portal:Perl+OpenMP|[[Portal:Perl+OpenMP|Perl+OpenMP]]<br />
File:Concurrency.png|link=Portal:Concurrency|[[Portal:Concurrency|Concurrency]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:ToolBox.png|link=Portal:Software Development Tools|[[Portal:Software Development Tools|Development Tools]]<br />
File:perlCGI.jpg|link=Portal:Perl CGI Programming|[[Portal:Perl CGI Programming|Legacy Perl]]<br />
File:Camels.jpg|link=Portal:Perl Powered Programs (PPP)|[[Portal:Perl Powered Programs (PPP)|Perl Powered Programs (PPP)]]<br />
File:Perlcommunity.png|link=Portal:Perl Communities|[[Portal:Perl Communities|Communities]]<br />
File:XS.jpg|link=Portal:Embedding and Extending Perl|[[Portal:Embedding and Extending Perl|Embedding and Extending Perl]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Money.jpeg|link=Portal:Perl for Profit|[[Portal:Perl for Profit|Perl for Profit]]<br />
File:History.gif|link=Portal:Perl History|[[Portal:Perl History|Perl History]]<br />
File:SQLdb TSQLQuery.PNG|link=Portal:Databases|[[Portal:Databases|Database Development]]<br />
File:GamesPortalLogo.png|link=Portal:Game Development|[[Portal:Game Development|Game Development]]<br />
File:HowTo.png|link=Portal:HowTo Demos|[[Portal:HowTo Demos|HowTo Demos]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Rperl.jpeg|link=Portal:Alt. Perls|[[Portal:Alt. Perls|Alt. Perls]]<br />
File:Ai.jpeg|link=Portal:Artificial Intelligence|[[Portal:Artificial Intelligence|Artificial Intelligence]]<br />
File:Crypto.png|link=Portal:Crypto and Blockchain|[[Portal:Crypto and Blockchain|Blockchain]]<br />
File:Perlbooks.jpg|link=Portal:Ex Libris|[[Portal:Ex Libris|Ex Libris]]<br />
File:Embedded.png|link=Portal:Embedded|[[Portal:Embedded|Embedded]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:FBSD Daemon.jpg|link=Portal:FreeBSD,OpenBSD,etc|[[Portal:FreeBSD,OpenBSD,etc|FreeBSD, OpenBSD, etc.]]<br />
File:tux.png|link=Portal:Linux|[[Portal:Linux|Linux]]<br />
File:macOSlogo.png|link=Portal:Mac|[[Portal:Mac|macOS]]<br />
File:HardwarePortalLogo.png|link=Portal:Hardware and Robotics|[[Portal:Hardware and Robotics|Hardware and Robotics]]<br />
File:Businessmodels.jpeg|link=Portal:Perl Business Models and Case Studies|[[Portal:Perl Business Models and Case Studies|Perl Business Models and Case Studies]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:ImageMagick.gif|link=Portal:Graphics Programming|[[Portal:Graphics Programming|Graphics Programming]]<br />
File:Hpc.jpg|link=Portal:HPC - High Performance Computing|[[Portal:HPC - High Performance Computing|HPC - High Performance Computing]]<br />
File:Bioperl.jpeg|link=Portal:Life Sciences|[[Portal:Life Sciences|Life Sciences]]<br />
File:tdrawgrid.png|link=Portal:SaaS and Web Development|[[Portal:SaaS and Web Development|SaaS and Web Development]]<br />
File:tachart getting started step6.png|link=Portal:SciTech|[[Portal:SciTech|Science and Technology]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:NewUserLogo.png|link=Portal:New Users|[[Portal:New Users|New Users]]<br />
</gallery><br />
|}<br />
<br />
</div><br />
<br />
<div style="float:right; width:49%;"><br />
<br />
{| class="wikitable" width="100%"<br />
| valign="top" |<br />
<br />
== Perl Craftsmen and Professional Development ==<br />
<br />
'''This section is for independent software professionals''' '''who charge money for Perl-related services''' and use Perl as their secret weapon to make a living, or for those wishing to become one.<br />
<br />
It is not for "jacks of all trades." This section is for Perl craftsmen: journeymen and true masters who wish to leverage their Perl skills to put food in their kids' mouths and a roof over their heads.<br />
<br />
'''Quick Links'''<br />
<br />
* [[Developing and Distributing wxPerl Applications on Windows|wxPerl on Windows: developing and distributing wxPerl applications]]<br />
<br />
'''Notable Updates'''<br />
<br />
* [[Portal:GUIs with Perl|GUIs with Perl]]<br />
** [[Developing and Distributing wxPerl Applications on Windows]]<br />
* [[Portal:Perl+OpenMP|Perl+OpenMP]]<br />
<br />
'''Email Lists'''<br />
<br />
* '''[https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors Perl-Guilds Wiki Contributors]''' listserv - join if you would like to contribute or offer regular feedback<br />
* '''[https://sourceforge.net/projects/perl-openmp/lists/perl-openmp-discuss Perl+OpenMP]''' listserv<br />
<br />
'''Note''': Yes, I encourage email lists for your project; and it turns out SourceForge.net is a great place to host reliable email lists!<br />
<br />
'''RAD, Rapid Application Development Tools, IDEs, and Installer-Makers'''<br />
<br />
* [https://sourceforge.net/projects/wxglade/ wxGlade] - written in Python, but can output Perl<br />
<br />
'''Using Perl for Making Windows GUI Programs'''<br />
<br />
* Cross-platform GUIs with wxPerl<br />
** [[Developing and Distributing wxPerl Applications on Windows]]<br />
* Windows-specific GUIs with Win32::GUI<br />
* Cross-platform GUIs with GUIDeFATE<br />
<br />
'''Using Perl for Creating a Commercial SaaS and Other Services'''<br />
<br />
'''Monetization Strategies for Perl Programmers'''<br />
<br />
'''Commercial Success Stories and Case Studies'''<br />
<br />
'''Downloads'''<br />
<br />
'''Community Participation'''<br />
<br />
* [https://www.perl-guilds.net Perl Guilds Forum] - test forum to see if any activity is drawn to it<br />
<br />
'''Tutorials'''<br />
<br />
'''Books and Magazines'''<br />
<br />
'''Related Sites'''<br />
<br />
* https://perlclientdirectory.com/ - curated list of Perl clients for external APIs and services<br />
* https://perlmodules.net - track changes to your favorite Perl modules in CPAN<br />
<br />
|}<br />
<br />
</div><br />
<br />
<div style="float:left; margin-right:0.9em;"><br />
<br />
== In the News ==<br />
<br />
A summary of recent news stories about Perl can be found [[In the News|here]].<br />
<br />
== Projects using Perl ==<br />
<br />
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]].<br />
<br />
== Bug Tracker ==<br />
<br />
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. 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]].<br />
<br />
<br /><br />
</div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=File:Wxglade-nhc-advisory-explorer-3.png&diff=355File:Wxglade-nhc-advisory-explorer-3.png2026-07-06T05:53:39Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=File:Wxglade-nhc-advisory-explorer-2.png&diff=354File:Wxglade-nhc-advisory-explorer-2.png2026-07-06T05:53:11Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=File:Wxglade-nhc-advisory-explorer-1.png&diff=353File:Wxglade-nhc-advisory-explorer-1.png2026-07-06T05:52:40Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=File:Wxglade-netcdf-explorer.png&diff=352File:Wxglade-netcdf-explorer.png2026-07-06T05:50:29Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=File:Wxglade-limewire-style-interface.png&diff=351File:Wxglade-limewire-style-interface.png2026-07-06T05:50:03Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=File:Wxglade-wsftp-clone.png&diff=350File:Wxglade-wsftp-clone.png2026-07-05T07:27:50Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=File:Wxglade-putty-configuration-pane.png&diff=349File:Wxglade-putty-configuration-pane.png2026-07-05T07:27:16Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=File:Wxglade-netscape-clone.png&diff=348File:Wxglade-netscape-clone.png2026-07-05T07:26:48Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=File:Wxglade-windows-help-gui.png&diff=347File:Wxglade-windows-help-gui.png2026-07-05T07:26:03Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=GUI_ideas_for_use_with_wxGlade&diff=346GUI ideas for use with wxGlade2026-07-05T07:23:00Z<p>Admin: </p>
<hr />
<div>__NOTOC__<br />
<br />
= wxPerl / wxGlade Application Template Catalog =<br />
<br />
This page catalogs GUI mockups, template applications, and app ideas from the [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates wxPerl-wxGlade-Templates] repository.<br />
<br />
The repository collects [https://sourceforge.net/projects/wxglade/ wxGlade] <code>.wxg</code> project files and working Perl driver scripts that generate wxPerl GUIs directly from wxGlade output. These examples are intended to serve as starting points for real wxPerl desktop applications.<br />
<br />
For setup instructions, see:<br />
<br />
* [[Developing and Distributing wxPerl Applications on Windows|Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
== Purpose ==<br />
<br />
The goal of this catalog is to make it easier for Perl programmers to find practical wxGlade GUI ideas that can be copied, studied, modified, and eventually turned into working wxPerl desktop applications.<br />
<br />
These examples are especially useful for:<br />
<br />
* learning wxGlade layout techniques<br />
* testing wxPerl widgets on Windows<br />
* building simple commercial desktop utilities<br />
* creating GUI front ends for existing Perl scripts<br />
* prototyping Windows-style applications with Perl<br />
* preserving classic desktop UI patterns that still work well<br />
<br />
== Repository ==<br />
<br />
* Repository: [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates]<br />
* Main setup guide: [[Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
== AI-Assisted wxGlade Template Generation ==<br />
<br />
ChatGPT and similar AI tools can be useful for generating first-draft wxGlade XML files. This can be especially helpful when starting from a description such as:<br />
<br />
* "make a two-pane FTP client layout"<br />
* "make a PuTTY-style configuration dialog"<br />
* "make a Windows 95-style help viewer"<br />
* "make a tabbed search interface with a results grid"<br />
* "make a scientific data browser with a tree view, metadata pane, and plot area"<br />
<br />
The generated XML should be treated as a starting point, not a finished application. Always open the file in wxGlade, inspect the widget tree, fix layout issues, and test the generated Perl code.<br />
<br />
AI-generated wxGlade files are most useful for:<br />
<br />
* quickly prototyping an interface idea<br />
* creating a rough widget hierarchy<br />
* experimenting with sizers and panels<br />
* generating repetitive boilerplate layouts<br />
* turning a hand-drawn mockup or written app idea into a first editable <code>.wxg</code> file<br />
<br />
A practical workflow is:<br />
<br />
<pre><br />
Describe the desired GUI → Generate wxGlade XML → Open in wxGlade → Fix layout/details → Generate Perl code → Add real Perl logic<br />
</pre><br />
<br />
This does not replace wxGlade. It gives Perl programmers a faster way to get an initial layout into wxGlade so they can continue refining it visually.<br />
<br />
== Application Ideas and Templates ==<br />
<br />
=== Windows Help GUI ===<br />
<br />
[[File:Wxglade-windows-help-gui.png|900px|Windows Help GUI wxGlade template screenshot]]<br />
<br />
A classic Windows 95/98-style help viewer layout.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* menu-driven application layout<br />
* help/document viewer style<br />
* navigation pane plus content pane<br />
* classic Windows desktop design<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* local documentation viewer<br />
* offline manual reader<br />
* FAQ browser<br />
* product support utility<br />
* help system for a packaged Perl application<br />
<br />
=== Netscape 2.0 Clone ===<br />
<br />
[[File:Wxglade-netscape-clone.png|900px|Netscape 2.0 style wxGlade template screenshot]]<br />
<br />
A retro browser-style interface inspired by early Netscape.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* menu bar<br />
* toolbar buttons<br />
* location/address field<br />
* large content area<br />
* status bar<br />
* classic browser-style workflow<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* HTML documentation shell<br />
* internal web viewer<br />
* archive browser<br />
* local content navigator<br />
* kiosk-style viewer<br />
<br />
=== PuTTY Configuration Pane ===<br />
<br />
[[File:Wxglade-putty-configuration-pane.png|900px|PuTTY configuration pane wxGlade template screenshot]]<br />
<br />
A configuration dialog inspired by PuTTY's familiar settings layout.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* category tree<br />
* grouped settings panels<br />
* form controls<br />
* dialog buttons<br />
* configuration-heavy application design<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* SSH profile manager<br />
* rsync/SFTP launcher<br />
* server connection manager<br />
* backup configuration tool<br />
* cluster login helper<br />
* settings editor for a Perl utility<br />
<br />
=== WS-FTP Clone ===<br />
<br />
[[File:Wxglade-wsftp-clone.png|900px|WS-FTP style wxGlade template screenshot]]<br />
<br />
A classic two-pane file transfer client layout.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* dual-pane file manager interface<br />
* connection controls<br />
* list views<br />
* transfer queue area<br />
* old-school but still-useful desktop file workflow<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* FTP/SFTP client<br />
* deployment tool<br />
* file sync GUI<br />
* webhost upload utility<br />
* batch transfer manager<br />
* local/remote file comparison tool<br />
<br />
=== LimeWire-Style Interface ===<br />
<br />
[[File:Wxglade-limewire-style-interface.png|900px|LimeWire style wxGlade template screenshot]]<br />
<br />
A search-and-results interface inspired by classic peer-to-peer software.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* search field<br />
* results grid<br />
* tabs<br />
* sidebar navigation<br />
* progress/list panes<br />
* search-driven desktop workflow<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* archive search tool<br />
* CPAN package browser<br />
* media catalog<br />
* dataset searcher<br />
* internal document finder<br />
* OCR search front end<br />
* eBay/archive research tool<br />
<br />
=== NetCDF Explorer ===<br />
<br />
[[File:Wxglade-netcdf-explorer.png|900px|NetCDF Explorer wxGlade template screenshot]]<br />
<br />
A scientific data browser idea intended to pair well with Strawberry Perl, PDL, and scientific Perl tooling.<br />
<br />
'''Status:''' Template / app idea<br />
<br />
'''What it demonstrates:'''<br />
<br />
* scientific data browser layout<br />
* dataset navigation<br />
* variable lists<br />
* metadata panes<br />
* plotting/viewer area<br />
* workflow for technical users<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* NetCDF viewer<br />
* PDL-based data explorer<br />
* ADCIRC/ASGS result browser<br />
* HDF/NetCDF inspection utility<br />
* CSV/SQLite scientific data viewer<br />
* teaching tool for scientific Perl<br />
<br />
=== NHC Advisory Explorer ===<br />
<br />
[[File:Wxglade-nhc-advisory-explorer-1.png|900px|NHC Advisory Explorer screenshot 1]]<br />
<br />
[[File:Wxglade-nhc-advisory-explorer-2.png|900px|NHC Advisory Explorer screenshot 2]]<br />
<br />
[[File:Wxglade-nhc-advisory-explorer-3.png|900px|NHC Advisory Explorer screenshot 3]]<br />
<br />
The NHC Advisory Explorer is a real wxPerl application rather than just a mockup. It has an available Windows executable release.<br />
<br />
* Release page: [https://github.com/StormSurgeLive/nhc-advisory-gui/releases NHC Advisory GUI releases]<br />
<br />
'''Status:''' Implemented; Windows EXE release available<br />
<br />
'''What it demonstrates:'''<br />
<br />
* real wxPerl application workflow<br />
* advisory navigation<br />
* weather text/data display<br />
* practical desktop packaging<br />
* turning a wxGlade layout into a useful application<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* hurricane advisory browser<br />
* emergency-management tool<br />
* weather data front end<br />
* wxPerl packaging example<br />
* example of shipping a Perl GUI as a normal Windows executable<br />
<br />
== Suggested Template Categories ==<br />
<br />
=== Classic Windows Utilities ===<br />
<br />
Good examples:<br />
<br />
* Windows Help GUI<br />
* PuTTY Configuration Pane<br />
* WS-FTP Clone<br />
<br />
These are useful because they model familiar desktop patterns that ordinary Windows users already understand.<br />
<br />
Possible apps:<br />
<br />
* configuration editors<br />
* log viewers<br />
* backup managers<br />
* system inventory tools<br />
* connection/profile managers<br />
* installer front ends<br />
* INI / YAML / JSON editors<br />
<br />
=== Internet and Network Tools ===<br />
<br />
Good examples:<br />
<br />
* Netscape 2.0 Clone<br />
* PuTTY Configuration Pane<br />
* WS-FTP Clone<br />
* LimeWire-style Interface<br />
<br />
Possible apps:<br />
<br />
* SSH/SFTP launcher<br />
* website deployment GUI<br />
* CPAN mirror browser<br />
* FTP/SFTP batch uploader<br />
* network scanner front end<br />
* API test client<br />
* simple web archive browser<br />
<br />
=== Search, Archive, and Catalog Tools ===<br />
<br />
Good examples:<br />
<br />
* LimeWire-style Interface<br />
* Netscape 2.0 Clone<br />
* Windows Help GUI<br />
<br />
Possible apps:<br />
<br />
* local document search<br />
* eBay/archive search front end<br />
* image OCR search tool<br />
* CPAN module browser<br />
* source-code search tool<br />
* PDF/manual index browser<br />
<br />
=== Scientific and Engineering Tools ===<br />
<br />
Good examples:<br />
<br />
* NetCDF Explorer<br />
* NHC Advisory Explorer<br />
<br />
Possible apps:<br />
<br />
* NetCDF/HDF data explorer<br />
* PDL plotting front end<br />
* ADCIRC/ASGS results viewer<br />
* meteorological data browser<br />
* CSV/SQLite data inspector<br />
* sensor log viewer<br />
* engineering calculator collection<br />
<br />
=== Commercial Desktop Utilities ===<br />
<br />
These are simple programs that could realistically be sold, bundled, or used internally by small businesses.<br />
<br />
Possible apps:<br />
<br />
* invoice helper<br />
* customer lookup tool<br />
* report generator<br />
* file renamer<br />
* batch image processor<br />
* shipping label assistant<br />
* data cleanup tool<br />
* small SQLite-backed business app<br />
* upload/deployment utility<br />
* quote/order tracker<br />
<br />
== Suggested Repository Layout ==<br />
<br />
A useful structure for each template would be:<br />
<br />
<pre><br />
template-name/<br />
README.md<br />
screenshot.png<br />
template.wxg<br />
generated/<br />
MyFrame.pm<br />
driver.pl<br />
dist/<br />
build-notes.md<br />
</pre><br />
<br />
Recommended files:<br />
<br />
* <code>README.md</code> - what the template demonstrates<br />
* <code>template.wxg</code> - wxGlade project file<br />
* <code>driver.pl</code> - minimal runnable Perl script<br />
* <code>screenshot.png</code> - current screenshot<br />
* <code>build-notes.md</code> - notes about Strawberry Perl, wxPerl, DLLs, packaging, or installer creation<br />
<br />
== Suggested README Fields for Each Template ==<br />
<br />
Each template should ideally document:<br />
<br />
; Name<br />
: Human-readable name of the template or application idea.<br />
<br />
; Status<br />
: Mockup, partial implementation, working prototype, packaged release, abandoned, etc.<br />
<br />
; Purpose<br />
: What kind of application this layout is good for.<br />
<br />
; Widgets Used<br />
: Major wxWidgets/wxPerl controls demonstrated.<br />
<br />
; Perl Modules<br />
: Useful Perl modules that pair well with the template.<br />
<br />
; Tested On<br />
: Strawberry Perl version, wxPerl version, Windows version, etc.<br />
<br />
; Packaging Notes<br />
: Any notes about building an EXE or installer.<br />
<br />
; Screenshot<br />
: Link or local file reference.<br />
<br />
== Widget Patterns to Demonstrate ==<br />
<br />
Future templates should try to cover common wxPerl/wxGlade patterns such as:<br />
<br />
* main frame with menu bar and status bar<br />
* toolbar-driven application<br />
* tabbed notebook interface<br />
* split-pane application<br />
* tree navigation plus detail panel<br />
* dual-pane file manager<br />
* modal configuration dialog<br />
* wizard-style workflow<br />
* searchable list/grid interface<br />
* log viewer with controls<br />
* progress dialog for long-running Perl tasks<br />
* system tray utility<br />
* SQLite-backed data-entry form<br />
* plot/image viewer shell<br />
<br />
== Notes on Clone-Style Templates ==<br />
<br />
Some templates intentionally resemble well-known classic applications. These should be treated as UI studies and educational examples, not as trademarked product replacements.<br />
<br />
When turning a template into a real application:<br />
<br />
* use your own application name<br />
* use your own icons and artwork<br />
* avoid copying trademarks<br />
* keep the useful layout pattern<br />
* replace mockup controls with real Perl logic<br />
<br />
== Why This Matters ==<br />
<br />
wxPerl and wxGlade give Perl programmers a practical path to creating normal-looking desktop applications, especially on Windows. A good collection of templates lowers the barrier to entry by giving programmers something visual and runnable to start from.<br />
<br />
The real advantage is simple:<br />
<br />
'''Use wxGlade to design the interface. Use Perl to make it useful. Package it so users never need to know it was Perl.'''<br />
<br />
== See Also ==<br />
<br />
* [[Portal:GUIs with Perl]]<br />
* [[Portal:Windows]]<br />
* [[Developing and Distributing wxPerl Applications on Windows]]<br />
* [[Portal:Perl for Profit]]<br />
* [[Portal:Software Development Tools]]<br />
* [[Portal:SciTech]]<br />
* [[Portal:Perl Powered Programs (PPP)]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=GUI_ideas_for_use_with_wxGlade&diff=345GUI ideas for use with wxGlade2026-07-05T07:21:19Z<p>Admin: </p>
<hr />
<div>**NOTOC**<br />
<br />
= wxPerl / wxGlade Application Template Catalog =<br />
<br />
This page catalogs GUI mockups, template applications, and app ideas from the [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates wxPerl-wxGlade-Templates] repository.<br />
<br />
The repository collects [https://sourceforge.net/projects/wxglade/ wxGlade] <code>.wxg</code> project files and working Perl driver scripts that generate wxPerl GUIs directly from wxGlade output. These examples are intended to serve as starting points for real wxPerl desktop applications.<br />
<br />
For setup instructions, see:<br />
<br />
* [[Developing and Distributing wxPerl Applications on Windows|Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
== Purpose ==<br />
<br />
The goal of this catalog is to make it easier for Perl programmers to find practical wxGlade GUI ideas that can be copied, studied, modified, and eventually turned into working wxPerl desktop applications.<br />
<br />
These examples are especially useful for:<br />
<br />
* learning wxGlade layout techniques<br />
* testing wxPerl widgets on Windows<br />
* building simple commercial desktop utilities<br />
* creating GUI front ends for existing Perl scripts<br />
* prototyping Windows-style applications with Perl<br />
* preserving classic desktop UI patterns that still work well<br />
<br />
== Repository ==<br />
<br />
* Repository: [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates]<br />
* Main setup guide: [[Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
== AI-Assisted wxGlade Template Generation ==<br />
<br />
ChatGPT and similar AI tools can be useful for generating first-draft wxGlade XML files. This can be especially helpful when starting from a description such as:<br />
<br />
* "make a two-pane FTP client layout"<br />
* "make a PuTTY-style configuration dialog"<br />
* "make a Windows 95-style help viewer"<br />
* "make a tabbed search interface with a results grid"<br />
* "make a scientific data browser with a tree view, metadata pane, and plot area"<br />
<br />
The generated XML should be treated as a starting point, not a finished application. Always open the file in wxGlade, inspect the widget tree, fix layout issues, and test the generated Perl code.<br />
<br />
AI-generated wxGlade files are most useful for:<br />
<br />
* quickly prototyping an interface idea<br />
* creating a rough widget hierarchy<br />
* experimenting with sizers and panels<br />
* generating repetitive boilerplate layouts<br />
* turning a hand-drawn mockup or written app idea into a first editable <code>.wxg</code> file<br />
<br />
A practical workflow is:<br />
<br />
<pre><br />
Describe the desired GUI → Generate wxGlade XML → Open in wxGlade → Fix layout/details → Generate Perl code → Add real Perl logic<br />
</pre><br />
<br />
This does not replace wxGlade. It gives Perl programmers a faster way to get an initial layout into wxGlade so they can continue refining it visually.<br />
<br />
== Application Ideas and Templates ==<br />
<br />
=== Windows Help GUI ===<br />
<br />
<div style="max-width: 900px; margin: 0 0 1em 0;"><br />
<img src="https://github.com/user-attachments/assets/041716c6-c4ab-4e21-93e1-117f58ffe0c0" alt="Windows Help GUI wxGlade template screenshot" style="max-width:100%; height:auto; border:1px solid #cccccc;" /><br />
</div><br />
<br />
A classic Windows 95/98-style help viewer layout.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* menu-driven application layout<br />
* help/document viewer style<br />
* navigation pane plus content pane<br />
* classic Windows desktop design<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* local documentation viewer<br />
* offline manual reader<br />
* FAQ browser<br />
* product support utility<br />
* help system for a packaged Perl application<br />
<br />
=== Netscape 2.0 Clone ===<br />
<br />
<div style="max-width: 900px; margin: 0 0 1em 0;"><br />
<img src="https://github.com/user-attachments/assets/c572a291-9a77-4c48-bf9f-c4823d04ba8f" alt="Netscape 2.0 style wxGlade template screenshot" style="max-width:100%; height:auto; border:1px solid #cccccc;" /><br />
</div><br />
<br />
A retro browser-style interface inspired by early Netscape.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* menu bar<br />
* toolbar buttons<br />
* location/address field<br />
* large content area<br />
* status bar<br />
* classic browser-style workflow<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* HTML documentation shell<br />
* internal web viewer<br />
* archive browser<br />
* local content navigator<br />
* kiosk-style viewer<br />
<br />
=== PuTTY Configuration Pane ===<br />
<br />
<div style="max-width: 900px; margin: 0 0 1em 0;"><br />
<img src="https://github.com/user-attachments/assets/c2e41b87-48d2-4269-8d8e-75a4861a78f7" alt="PuTTY configuration pane wxGlade template screenshot" style="max-width:100%; height:auto; border:1px solid #cccccc;" /><br />
</div><br />
<br />
A configuration dialog inspired by PuTTY's familiar settings layout.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* category tree<br />
* grouped settings panels<br />
* form controls<br />
* dialog buttons<br />
* configuration-heavy application design<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* SSH profile manager<br />
* rsync/SFTP launcher<br />
* server connection manager<br />
* backup configuration tool<br />
* cluster login helper<br />
* settings editor for a Perl utility<br />
<br />
=== WS-FTP Clone ===<br />
<br />
<div style="max-width: 900px; margin: 0 0 1em 0;"><br />
<img src="https://github.com/user-attachments/assets/0082bccb-7731-4d4b-bb55-de2c0b12f49a" alt="WS-FTP style wxGlade template screenshot" style="max-width:100%; height:auto; border:1px solid #cccccc;" /><br />
</div><br />
<br />
A classic two-pane file transfer client layout.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* dual-pane file manager interface<br />
* connection controls<br />
* list views<br />
* transfer queue area<br />
* old-school but still-useful desktop file workflow<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* FTP/SFTP client<br />
* deployment tool<br />
* file sync GUI<br />
* webhost upload utility<br />
* batch transfer manager<br />
* local/remote file comparison tool<br />
<br />
=== LimeWire-Style Interface ===<br />
<br />
<div style="max-width: 900px; margin: 0 0 1em 0;"><br />
<img src="https://github.com/user-attachments/assets/8d65a2e5-0472-4bb0-8c64-f87ddea9ec1b" alt="LimeWire style wxGlade template screenshot" style="max-width:100%; height:auto; border:1px solid #cccccc;" /><br />
</div><br />
<br />
A search-and-results interface inspired by classic peer-to-peer software.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* search field<br />
* results grid<br />
* tabs<br />
* sidebar navigation<br />
* progress/list panes<br />
* search-driven desktop workflow<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* archive search tool<br />
* CPAN package browser<br />
* media catalog<br />
* dataset searcher<br />
* internal document finder<br />
* OCR search front end<br />
* eBay/archive research tool<br />
<br />
=== NetCDF Explorer ===<br />
<br />
<div style="max-width: 900px; margin: 0 0 1em 0;"><br />
<img src="https://github.com/user-attachments/assets/da42b521-1b7a-491b-afb2-cd1f7f35c386" alt="NetCDF Explorer wxGlade template screenshot" style="max-width:100%; height:auto; border:1px solid #cccccc;" /><br />
</div><br />
<br />
A scientific data browser idea intended to pair well with Strawberry Perl, PDL, and scientific Perl tooling.<br />
<br />
'''Status:''' Template / app idea<br />
<br />
'''What it demonstrates:'''<br />
<br />
* scientific data browser layout<br />
* dataset navigation<br />
* variable lists<br />
* metadata panes<br />
* plotting/viewer area<br />
* workflow for technical users<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* NetCDF viewer<br />
* PDL-based data explorer<br />
* ADCIRC/ASGS result browser<br />
* HDF/NetCDF inspection utility<br />
* CSV/SQLite scientific data viewer<br />
* teaching tool for scientific Perl<br />
<br />
=== NHC Advisory Explorer ===<br />
<br />
<div style="max-width: 900px; margin: 0 0 1em 0;"><br />
<img src="https://github.com/user-attachments/assets/0ef50655-841f-420f-be33-60c26a7cf721" alt="NHC Advisory Explorer screenshot 1" style="max-width:100%; height:auto; border:1px solid #cccccc;" /><br />
</div><br />
<br />
<div style="max-width: 900px; margin: 0 0 1em 0;"><br />
<img src="https://github.com/user-attachments/assets/377eb242-a17c-46f1-8ceb-5f2a4593c553" alt="NHC Advisory Explorer screenshot 2" style="max-width:100%; height:auto; border:1px solid #cccccc;" /><br />
</div><br />
<br />
<div style="max-width: 900px; margin: 0 0 1em 0;"><br />
<img src="https://github.com/user-attachments/assets/5813887a-8116-41da-bdc5-7340316b6999" alt="NHC Advisory Explorer screenshot 3" style="max-width:100%; height:auto; border:1px solid #cccccc;" /><br />
</div><br />
<br />
The NHC Advisory Explorer is a real wxPerl application rather than just a mockup. It has an available Windows executable release.<br />
<br />
* Release page: [https://github.com/StormSurgeLive/nhc-advisory-gui/releases NHC Advisory GUI releases]<br />
<br />
'''Status:''' Implemented; Windows EXE release available<br />
<br />
'''What it demonstrates:'''<br />
<br />
* real wxPerl application workflow<br />
* advisory navigation<br />
* weather text/data display<br />
* practical desktop packaging<br />
* turning a wxGlade layout into a useful application<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* hurricane advisory browser<br />
* emergency-management tool<br />
* weather data front end<br />
* wxPerl packaging example<br />
* example of shipping a Perl GUI as a normal Windows executable<br />
<br />
== Suggested Template Categories ==<br />
<br />
=== Classic Windows Utilities ===<br />
<br />
Good examples:<br />
<br />
* Windows Help GUI<br />
* PuTTY Configuration Pane<br />
* WS-FTP Clone<br />
<br />
These are useful because they model familiar desktop patterns that ordinary Windows users already understand.<br />
<br />
Possible apps:<br />
<br />
* configuration editors<br />
* log viewers<br />
* backup managers<br />
* system inventory tools<br />
* connection/profile managers<br />
* installer front ends<br />
* INI / YAML / JSON editors<br />
<br />
=== Internet and Network Tools ===<br />
<br />
Good examples:<br />
<br />
* Netscape 2.0 Clone<br />
* PuTTY Configuration Pane<br />
* WS-FTP Clone<br />
* LimeWire-style Interface<br />
<br />
Possible apps:<br />
<br />
* SSH/SFTP launcher<br />
* website deployment GUI<br />
* CPAN mirror browser<br />
* FTP/SFTP batch uploader<br />
* network scanner front end<br />
* API test client<br />
* simple web archive browser<br />
<br />
=== Search, Archive, and Catalog Tools ===<br />
<br />
Good examples:<br />
<br />
* LimeWire-style Interface<br />
* Netscape 2.0 Clone<br />
* Windows Help GUI<br />
<br />
Possible apps:<br />
<br />
* local document search<br />
* eBay/archive search front end<br />
* image OCR search tool<br />
* CPAN module browser<br />
* source-code search tool<br />
* PDF/manual index browser<br />
<br />
=== Scientific and Engineering Tools ===<br />
<br />
Good examples:<br />
<br />
* NetCDF Explorer<br />
* NHC Advisory Explorer<br />
<br />
Possible apps:<br />
<br />
* NetCDF/HDF data explorer<br />
* PDL plotting front end<br />
* ADCIRC/ASGS results viewer<br />
* meteorological data browser<br />
* CSV/SQLite data inspector<br />
* sensor log viewer<br />
* engineering calculator collection<br />
<br />
=== Commercial Desktop Utilities ===<br />
<br />
These are simple programs that could realistically be sold, bundled, or used internally by small businesses.<br />
<br />
Possible apps:<br />
<br />
* invoice helper<br />
* customer lookup tool<br />
* report generator<br />
* file renamer<br />
* batch image processor<br />
* shipping label assistant<br />
* data cleanup tool<br />
* small SQLite-backed business app<br />
* upload/deployment utility<br />
* quote/order tracker<br />
<br />
== Suggested Repository Layout ==<br />
<br />
A useful structure for each template would be:<br />
<br />
<pre><br />
template-name/<br />
README.md<br />
screenshot.png<br />
template.wxg<br />
generated/<br />
MyFrame.pm<br />
driver.pl<br />
dist/<br />
build-notes.md<br />
</pre><br />
<br />
Recommended files:<br />
<br />
* <code>README.md</code> - what the template demonstrates<br />
* <code>template.wxg</code> - wxGlade project file<br />
* <code>driver.pl</code> - minimal runnable Perl script<br />
* <code>screenshot.png</code> - current screenshot<br />
* <code>build-notes.md</code> - notes about Strawberry Perl, wxPerl, DLLs, packaging, or installer creation<br />
<br />
== Suggested README Fields for Each Template ==<br />
<br />
Each template should ideally document:<br />
<br />
; Name<br />
: Human-readable name of the template or application idea.<br />
<br />
; Status<br />
: Mockup, partial implementation, working prototype, packaged release, abandoned, etc.<br />
<br />
; Purpose<br />
: What kind of application this layout is good for.<br />
<br />
; Widgets Used<br />
: Major wxWidgets/wxPerl controls demonstrated.<br />
<br />
; Perl Modules<br />
: Useful Perl modules that pair well with the template.<br />
<br />
; Tested On<br />
: Strawberry Perl version, wxPerl version, Windows version, etc.<br />
<br />
; Packaging Notes<br />
: Any notes about building an EXE or installer.<br />
<br />
; Screenshot<br />
: Link or local file reference.<br />
<br />
== Widget Patterns to Demonstrate ==<br />
<br />
Future templates should try to cover common wxPerl/wxGlade patterns such as:<br />
<br />
* main frame with menu bar and status bar<br />
* toolbar-driven application<br />
* tabbed notebook interface<br />
* split-pane application<br />
* tree navigation plus detail panel<br />
* dual-pane file manager<br />
* modal configuration dialog<br />
* wizard-style workflow<br />
* searchable list/grid interface<br />
* log viewer with controls<br />
* progress dialog for long-running Perl tasks<br />
* system tray utility<br />
* SQLite-backed data-entry form<br />
* plot/image viewer shell<br />
<br />
== Notes on Clone-Style Templates ==<br />
<br />
Some templates intentionally resemble well-known classic applications. These should be treated as UI studies and educational examples, not as trademarked product replacements.<br />
<br />
When turning a template into a real application:<br />
<br />
* use your own application name<br />
* use your own icons and artwork<br />
* avoid copying trademarks<br />
* keep the useful layout pattern<br />
* replace mockup controls with real Perl logic<br />
<br />
== Why This Matters ==<br />
<br />
wxPerl and wxGlade give Perl programmers a practical path to creating normal-looking desktop applications, especially on Windows. A good collection of templates lowers the barrier to entry by giving programmers something visual and runnable to start from.<br />
<br />
The real advantage is simple:<br />
<br />
'''Use wxGlade to design the interface. Use Perl to make it useful. Package it so users never need to know it was Perl.'''<br />
<br />
== See Also ==<br />
<br />
* [[Portal:GUIs with Perl]]<br />
* [[Portal:Windows]]<br />
* [[Developing and Distributing wxPerl Applications on Windows]]<br />
* [[Portal:Perl for Profit]]<br />
* [[Portal:Software Development Tools]]<br />
* [[Portal:SciTech]]<br />
* [[Portal:Perl Powered Programs (PPP)]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=GUI_ideas_for_use_with_wxGlade&diff=344GUI ideas for use with wxGlade2026-07-05T07:19:21Z<p>Admin: </p>
<hr />
<div>**NOTOC**<br />
<br />
= wxPerl / wxGlade Application Template Catalog =<br />
<br />
This page catalogs GUI mockups, template applications, and app ideas from the [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates wxPerl-wxGlade-Templates] repository.<br />
<br />
The repository collects [https://sourceforge.net/projects/wxglade/ wxGlade] <code>.wxg</code> project files and working Perl driver scripts that generate wxPerl GUIs directly from wxGlade output. These examples are intended to serve as starting points for real wxPerl desktop applications.<br />
<br />
For setup instructions, see:<br />
<br />
* [[Developing and Distributing wxPerl Applications on Windows|Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
== Purpose ==<br />
<br />
The goal of this catalog is to make it easier for Perl programmers to find practical wxGlade GUI ideas that can be copied, studied, modified, and eventually turned into working wxPerl desktop applications.<br />
<br />
These examples are especially useful for:<br />
<br />
* learning wxGlade layout techniques<br />
* testing wxPerl widgets on Windows<br />
* building simple commercial desktop utilities<br />
* creating GUI front ends for existing Perl scripts<br />
* prototyping Windows-style applications with Perl<br />
* preserving classic desktop UI patterns that still work well<br />
<br />
== Repository ==<br />
<br />
* Repository: [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates]<br />
* Main setup guide: [[Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
== Application Ideas and Templates ==<br />
<br />
=== Windows Help GUI ===<br />
<br />
[https://github.com/user-attachments/assets/041716c6-c4ab-4e21-93e1-117f58ffe0c0 Screenshot]<br />
<br />
A classic Windows 95/98-style help viewer layout.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* menu-driven application layout<br />
* help/document viewer style<br />
* navigation pane plus content pane<br />
* classic Windows desktop design<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* local documentation viewer<br />
* offline manual reader<br />
* FAQ browser<br />
* product support utility<br />
* help system for a packaged Perl application<br />
<br />
=== Netscape 2.0 Clone ===<br />
<br />
[https://github.com/user-attachments/assets/c572a291-9a77-4c48-bf9f-c4823d04ba8f Screenshot]<br />
<br />
A retro browser-style interface inspired by early Netscape.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* menu bar<br />
* toolbar buttons<br />
* location/address field<br />
* large content area<br />
* status bar<br />
* classic browser-style workflow<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* HTML documentation shell<br />
* internal web viewer<br />
* archive browser<br />
* local content navigator<br />
* kiosk-style viewer<br />
<br />
=== PuTTY Configuration Pane ===<br />
<br />
[https://github.com/user-attachments/assets/c2e41b87-48d2-4269-8d8e-75a4861a78f7 Screenshot]<br />
<br />
A configuration dialog inspired by PuTTY's familiar settings layout.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* category tree<br />
* grouped settings panels<br />
* form controls<br />
* dialog buttons<br />
* configuration-heavy application design<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* SSH profile manager<br />
* rsync/SFTP launcher<br />
* server connection manager<br />
* backup configuration tool<br />
* cluster login helper<br />
* settings editor for a Perl utility<br />
<br />
=== WS-FTP Clone ===<br />
<br />
[https://github.com/user-attachments/assets/0082bccb-7731-4d4b-bb55-de2c0b12f49a Screenshot]<br />
<br />
A classic two-pane file transfer client layout.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* dual-pane file manager interface<br />
* connection controls<br />
* list views<br />
* transfer queue area<br />
* old-school but still-useful desktop file workflow<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* FTP/SFTP client<br />
* deployment tool<br />
* file sync GUI<br />
* webhost upload utility<br />
* batch transfer manager<br />
* local/remote file comparison tool<br />
<br />
=== LimeWire-Style Interface ===<br />
<br />
[https://github.com/user-attachments/assets/8d65a2e5-0472-4bb0-8c64-f87ddea9ec1b Screenshot]<br />
<br />
A search-and-results interface inspired by classic peer-to-peer software.<br />
<br />
'''Status:''' Template / mockup<br />
<br />
'''What it demonstrates:'''<br />
<br />
* search field<br />
* results grid<br />
* tabs<br />
* sidebar navigation<br />
* progress/list panes<br />
* search-driven desktop workflow<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* archive search tool<br />
* CPAN package browser<br />
* media catalog<br />
* dataset searcher<br />
* internal document finder<br />
* OCR search front end<br />
* eBay/archive research tool<br />
<br />
=== NetCDF Explorer ===<br />
<br />
[https://github.com/user-attachments/assets/da42b521-1b7a-491b-afb2-cd1f7f35c386 Screenshot]<br />
<br />
A scientific data browser idea intended to pair well with Strawberry Perl, PDL, and scientific Perl tooling.<br />
<br />
'''Status:''' Template / app idea<br />
<br />
'''What it demonstrates:'''<br />
<br />
* scientific data browser layout<br />
* dataset navigation<br />
* variable lists<br />
* metadata panes<br />
* plotting/viewer area<br />
* workflow for technical users<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* NetCDF viewer<br />
* PDL-based data explorer<br />
* ADCIRC/ASGS result browser<br />
* HDF/NetCDF inspection utility<br />
* CSV/SQLite scientific data viewer<br />
* teaching tool for scientific Perl<br />
<br />
=== NHC Advisory Explorer ===<br />
<br />
[https://github.com/user-attachments/assets/0ef50655-841f-420f-be33-60c26a7cf721 Screenshot 1]<br />
<br />
[https://github.com/user-attachments/assets/377eb242-a17c-46f1-8ceb-5f2a4593c553 Screenshot 2]<br />
<br />
[https://github.com/user-attachments/assets/5813887a-8116-41da-bdc5-7340316b6999 Screenshot 3]<br />
<br />
The NHC Advisory Explorer is a real wxPerl application rather than just a mockup. It has an available Windows executable release.<br />
<br />
* Release page: [https://github.com/StormSurgeLive/nhc-advisory-gui/releases NHC Advisory GUI releases]<br />
<br />
'''Status:''' Implemented; Windows EXE release available<br />
<br />
'''What it demonstrates:'''<br />
<br />
* real wxPerl application workflow<br />
* advisory navigation<br />
* weather text/data display<br />
* practical desktop packaging<br />
* turning a wxGlade layout into a useful application<br />
<br />
'''Possible Perl uses:'''<br />
<br />
* hurricane advisory browser<br />
* emergency-management tool<br />
* weather data front end<br />
* wxPerl packaging example<br />
* example of shipping a Perl GUI as a normal Windows executable<br />
<br />
== Suggested Template Categories ==<br />
<br />
=== Classic Windows Utilities ===<br />
<br />
Good examples:<br />
<br />
* Windows Help GUI<br />
* PuTTY Configuration Pane<br />
* WS-FTP Clone<br />
<br />
These are useful because they model familiar desktop patterns that ordinary Windows users already understand.<br />
<br />
Possible apps:<br />
<br />
* configuration editors<br />
* log viewers<br />
* backup managers<br />
* system inventory tools<br />
* connection/profile managers<br />
* installer front ends<br />
* INI / YAML / JSON editors<br />
<br />
=== Internet and Network Tools ===<br />
<br />
Good examples:<br />
<br />
* Netscape 2.0 Clone<br />
* PuTTY Configuration Pane<br />
* WS-FTP Clone<br />
* LimeWire-style Interface<br />
<br />
Possible apps:<br />
<br />
* SSH/SFTP launcher<br />
* website deployment GUI<br />
* CPAN mirror browser<br />
* FTP/SFTP batch uploader<br />
* network scanner front end<br />
* API test client<br />
* simple web archive browser<br />
<br />
=== Search, Archive, and Catalog Tools ===<br />
<br />
Good examples:<br />
<br />
* LimeWire-style Interface<br />
* Netscape 2.0 Clone<br />
* Windows Help GUI<br />
<br />
Possible apps:<br />
<br />
* local document search<br />
* eBay/archive search front end<br />
* image OCR search tool<br />
* CPAN module browser<br />
* source-code search tool<br />
* PDF/manual index browser<br />
<br />
=== Scientific and Engineering Tools ===<br />
<br />
Good examples:<br />
<br />
* NetCDF Explorer<br />
* NHC Advisory Explorer<br />
<br />
Possible apps:<br />
<br />
* NetCDF/HDF data explorer<br />
* PDL plotting front end<br />
* ADCIRC/ASGS results viewer<br />
* meteorological data browser<br />
* CSV/SQLite data inspector<br />
* sensor log viewer<br />
* engineering calculator collection<br />
<br />
=== Commercial Desktop Utilities ===<br />
<br />
These are simple programs that could realistically be sold, bundled, or used internally by small businesses.<br />
<br />
Possible apps:<br />
<br />
* invoice helper<br />
* customer lookup tool<br />
* report generator<br />
* file renamer<br />
* batch image processor<br />
* shipping label assistant<br />
* data cleanup tool<br />
* small SQLite-backed business app<br />
* upload/deployment utility<br />
* quote/order tracker<br />
<br />
== Suggested Repository Layout ==<br />
<br />
A useful structure for each template would be:<br />
<br />
<pre><br />
template-name/<br />
README.md<br />
screenshot.png<br />
template.wxg<br />
generated/<br />
MyFrame.pm<br />
driver.pl<br />
dist/<br />
build-notes.md<br />
</pre><br />
<br />
Recommended files:<br />
<br />
* <code>README.md</code> - what the template demonstrates<br />
* <code>template.wxg</code> - wxGlade project file<br />
* <code>driver.pl</code> - minimal runnable Perl script<br />
* <code>screenshot.png</code> - current screenshot<br />
* <code>build-notes.md</code> - notes about Strawberry Perl, wxPerl, DLLs, packaging, or installer creation<br />
<br />
== Suggested README Fields for Each Template ==<br />
<br />
Each template should ideally document:<br />
<br />
; Name<br />
: Human-readable name of the template or application idea.<br />
<br />
; Status<br />
: Mockup, partial implementation, working prototype, packaged release, abandoned, etc.<br />
<br />
; Purpose<br />
: What kind of application this layout is good for.<br />
<br />
; Widgets Used<br />
: Major wxWidgets/wxPerl controls demonstrated.<br />
<br />
; Perl Modules<br />
: Useful Perl modules that pair well with the template.<br />
<br />
; Tested On<br />
: Strawberry Perl version, wxPerl version, Windows version, etc.<br />
<br />
; Packaging Notes<br />
: Any notes about building an EXE or installer.<br />
<br />
; Screenshot<br />
: Link or local file reference.<br />
<br />
== Widget Patterns to Demonstrate ==<br />
<br />
Future templates should try to cover common wxPerl/wxGlade patterns such as:<br />
<br />
* main frame with menu bar and status bar<br />
* toolbar-driven application<br />
* tabbed notebook interface<br />
* split-pane application<br />
* tree navigation plus detail panel<br />
* dual-pane file manager<br />
* modal configuration dialog<br />
* wizard-style workflow<br />
* searchable list/grid interface<br />
* log viewer with controls<br />
* progress dialog for long-running Perl tasks<br />
* system tray utility<br />
* SQLite-backed data-entry form<br />
* plot/image viewer shell<br />
<br />
== Notes on Clone-Style Templates ==<br />
<br />
Some templates intentionally resemble well-known classic applications. These should be treated as UI studies and educational examples, not as trademarked product replacements.<br />
<br />
When turning a template into a real application:<br />
<br />
* use your own application name<br />
* use your own icons and artwork<br />
* avoid copying trademarks<br />
* keep the useful layout pattern<br />
* replace mockup controls with real Perl logic<br />
<br />
== Why This Matters ==<br />
<br />
wxPerl and wxGlade give Perl programmers a practical path to creating normal-looking desktop applications, especially on Windows. A good collection of templates lowers the barrier to entry by giving programmers something visual and runnable to start from.<br />
<br />
The real advantage is simple:<br />
<br />
'''Use wxGlade to design the interface. Use Perl to make it useful. Package it so users never need to know it was Perl.'''<br />
<br />
== AI-Assisted wxGlade Template Generation ==<br />
<br />
ChatGPT and similar AI tools can be useful for generating first-draft wxGlade XML files. This can be especially helpful when starting from a description such as:<br />
<br />
* "make a two-pane FTP client layout"<br />
* "make a PuTTY-style configuration dialog"<br />
* "make a Windows 95-style help viewer"<br />
* "make a tabbed search interface with a results grid"<br />
* "make a scientific data browser with a tree view, metadata pane, and plot area"<br />
<br />
The generated XML should be treated as a starting point, not a finished application. Always open the file in wxGlade, inspect the widget tree, fix layout issues, and test the generated Perl code.<br />
<br />
AI-generated wxGlade files are most useful for:<br />
<br />
* quickly prototyping an interface idea<br />
* creating a rough widget hierarchy<br />
* experimenting with sizers and panels<br />
* generating repetitive boilerplate layouts<br />
* turning a hand-drawn mockup or written app idea into a first editable <code>.wxg</code> file<br />
<br />
A practical workflow is:<br />
<br />
<pre><br />
Describe the desired GUI → Generate wxGlade XML → Open in wxGlade → Fix layout/details → Generate Perl code → Add real Perl logic<br />
</pre><br />
<br />
This does not replace wxGlade. It gives Perl programmers a faster way to get an initial layout into wxGlade so they can continue refining it visually.<br />
<br />
== See Also ==<br />
<br />
* [[Portal:GUIs with Perl]]<br />
* [[Portal:Windows]]<br />
* [[Developing and Distributing wxPerl Applications on Windows]]<br />
* [[Portal:Perl for Profit]]<br />
* [[Portal:Software Development Tools]]<br />
* [[Portal:SciTech]]<br />
* [[Portal:Perl Powered Programs (PPP)]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=GUI_ideas_for_use_with_wxGlade&diff=343GUI ideas for use with wxGlade2026-07-05T07:16:46Z<p>Admin: Created page with "**NOTOC** = wxPerl / wxGlade Application Template Catalog = This page catalogs GUI mockups, template applications, and app ideas from the [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates wxPerl-wxGlade-Templates] repository. The repository is intended as a place to collect [https://sourceforge.net/projects/wxglade/ wxGlade] <code>.wxg</code> project files and working Perl driver scripts that generate wxPerl GUIs directly from wxGlade output. These e..."</p>
<hr />
<div>**NOTOC**<br />
<br />
= wxPerl / wxGlade Application Template Catalog =<br />
<br />
This page catalogs GUI mockups, template applications, and app ideas from the [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates wxPerl-wxGlade-Templates] repository.<br />
<br />
The repository is intended as a place to collect [https://sourceforge.net/projects/wxglade/ wxGlade] <code>.wxg</code> project files and working Perl driver scripts that generate wxPerl GUIs directly from wxGlade output. These examples are meant to serve as starting points for real wxPerl applications.<br />
<br />
For setup instructions, see:<br />
<br />
* [[Developing and Distributing wxPerl Applications on Windows|Developing and Distributing wxPerl Applications on Windows]]<br />
<br />
== Purpose ==<br />
<br />
The goal of this catalog is to make it easier for Perl programmers to find practical wxGlade GUI ideas that can be copied, studied, modified, and eventually turned into working wxPerl desktop applications.<br />
<br />
These examples are especially useful for:<br />
<br />
* learning wxGlade layout techniques<br />
* testing wxPerl widgets on Windows<br />
* building simple commercial desktop utilities<br />
* creating GUI front ends for existing Perl scripts<br />
* prototyping Windows-style applications with Perl<br />
* preserving classic desktop UI patterns that still work well<br />
<br />
== Repository ==<br />
<br />
* Repository: [https://github.com/The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates The-Perl-Cottage-Guild/wxPerl-wxGlade-Templates]<br />
* Main setup guide: [[Developing and Distributing wxPerl Applications on Windows]]<br />
* Intended files:<br />
** wxGlade <code>.wxg</code> XML project files<br />
** generated Perl GUI code<br />
** Perl driver scripts<br />
** screenshots<br />
** notes on packaging or distribution, where applicable<br />
<br />
== Template and Application Idea Gallery ==<br />
<br />
{| class="wikitable sortable" width="100%"<br />
! Application / Template<br />
! Screenshot<br />
! Type<br />
! Status<br />
! What It Demonstrates<br />
<br />
| ! Possible Perl Uses |<br />
| ------------------------------------------------------------------------------------------------------------------------------------ |<br />
| '''Windows Help GUI''' |<br />
| [https://github.com/user-attachments/assets/041716c6-c4ab-4e21-93e1-117f58ffe0c0 Screenshot] |<br />
| Classic Windows-style help viewer |<br />
| Template / mockup |<br />
| Menus, toolbar-like navigation, tree/list navigation, document pane, classic Windows 95/98-style layout |<br />
| Documentation viewer, local help browser, offline manual reader, FAQ viewer, product support utility |<br />
| - |<br />
| '''Netscape 2.0 Clone''' |<br />
| [https://github.com/user-attachments/assets/c572a291-9a77-4c48-bf9f-c4823d04ba8f Screenshot] |<br />
| Retro web browser UI study |<br />
| Template / mockup |<br />
| Menu bar, toolbar buttons, location field, large content area, status bar, classic browser layout |<br />
| HTML documentation shell, internal web viewer, archive browser, kiosk-style viewer, local content navigator |<br />
| - |<br />
| '''PuTTY Configuration Pane''' |<br />
| [https://github.com/user-attachments/assets/c2e41b87-48d2-4269-8d8e-75a4861a78f7 Screenshot] |<br />
| Configuration dialog |<br />
| Template / mockup |<br />
| Category tree, settings panels, grouped options, form controls, dialog buttons |<br />
| SSH profile manager, rsync/SFTP launcher, server connection manager, backup configuration tool, cluster login helper |<br />
| - |<br />
| '''WS-FTP Clone''' |<br />
| [https://github.com/user-attachments/assets/0082bccb-7731-4d4b-bb55-de2c0b12f49a Screenshot] |<br />
| File transfer client UI |<br />
| Template / mockup |<br />
| Dual-pane file manager layout, connection controls, list views, transfer queue area |<br />
| FTP/SFTP client, deployment tool, file sync GUI, webhost upload utility, batch transfer manager |<br />
| - |<br />
| '''LimeWire-Style Interface''' |<br />
| [https://github.com/user-attachments/assets/8d65a2e5-0472-4bb0-8c64-f87ddea9ec1b Screenshot] |<br />
| Search/download manager UI |<br />
| Template / mockup |<br />
| Search field, results grid, tabs, sidebar navigation, progress/list panes |<br />
| Archive search tool, CPAN package browser, media catalog, dataset searcher, internal document finder |<br />
| - |<br />
| '''NetCDF Explorer''' |<br />
| [https://github.com/user-attachments/assets/da42b521-1b7a-491b-afb2-cd1f7f35c386 Screenshot] |<br />
| Scientific data browser |<br />
| Template / app idea |<br />
| Dataset navigation, variable lists, metadata panes, plotting/viewer layout, scientific workflow UI |<br />
| NetCDF viewer, PDL-based data explorer, ADCIRC/ASGS result browser, HDF/NetCDF inspection utility, teaching tool for scientific Perl |<br />
| - |<br />
| '''NHC Advisory Explorer''' |<br />
| [https://github.com/user-attachments/assets/0ef50655-841f-420f-be33-60c26a7cf721 Screenshot 1]<br /> |<br />
| [https://github.com/user-attachments/assets/377eb242-a17c-46f1-8ceb-5f2a4593c553 Screenshot 2]<br /> |<br />
| [https://github.com/user-attachments/assets/5813887a-8116-41da-bdc5-7340316b6999 Screenshot 3] |<br />
| Weather / hurricane advisory viewer |<br />
| Implemented; Windows EXE release available |<br />
| Real-world wxPerl application, advisory navigation, text display, data retrieval, desktop packaging |<br />
| Hurricane advisory browser, emergency-management tool, weather data front end, example of shipping a wxPerl Windows executable |<br />
| } |<br />
<br />
== Implemented Example ==<br />
<br />
=== NHC Advisory Explorer ===<br />
<br />
The '''NHC Advisory Explorer''' is currently the strongest example in the collection because it has moved beyond a mockup and has an actual Windows executable release.<br />
<br />
* Project release: [https://github.com/StormSurgeLive/nhc-advisory-gui/releases NHC Advisory GUI releases]<br />
* Useful as an example of:<br />
** turning a wxGlade layout into a working wxPerl application<br />
** packaging a Perl GUI for Windows users<br />
** building a practical domain-specific desktop tool<br />
** using Perl as the hidden implementation advantage behind a normal-looking Windows application<br />
<br />
== Suggested Template Categories ==<br />
<br />
As the repository grows, templates can be grouped into the following categories.<br />
<br />
=== Classic Windows Utilities ===<br />
<br />
Good examples:<br />
<br />
* Windows Help GUI<br />
* PuTTY Configuration Pane<br />
* WS-FTP Clone<br />
<br />
These are useful because they model familiar desktop patterns that ordinary Windows users already understand.<br />
<br />
Possible apps:<br />
<br />
* configuration editors<br />
* log viewers<br />
* backup managers<br />
* system inventory tools<br />
* connection/profile managers<br />
* installer front ends<br />
* INI / YAML / JSON editors<br />
<br />
=== Internet and Network Tools ===<br />
<br />
Good examples:<br />
<br />
* Netscape 2.0 Clone<br />
* PuTTY Configuration Pane<br />
* WS-FTP Clone<br />
* LimeWire-style Interface<br />
<br />
Possible apps:<br />
<br />
* SSH/SFTP launcher<br />
* website deployment GUI<br />
* CPAN mirror browser<br />
* FTP/SFTP batch uploader<br />
* network scanner front end<br />
* API test client<br />
* simple web archive browser<br />
<br />
=== Search, Archive, and Catalog Tools ===<br />
<br />
Good examples:<br />
<br />
* LimeWire-style Interface<br />
* Netscape 2.0 Clone<br />
* Windows Help GUI<br />
<br />
Possible apps:<br />
<br />
* local document search<br />
* eBay/archive search front end<br />
* image OCR search tool<br />
* CPAN module browser<br />
* source-code search tool<br />
* PDF/manual index browser<br />
<br />
=== Scientific and Engineering Tools ===<br />
<br />
Good examples:<br />
<br />
* NetCDF Explorer<br />
* NHC Advisory Explorer<br />
<br />
Possible apps:<br />
<br />
* NetCDF/HDF data explorer<br />
* PDL plotting front end<br />
* ADCIRC/ASGS results viewer<br />
* meteorological data browser<br />
* CSV/SQLite data inspector<br />
* sensor log viewer<br />
* engineering calculator collection<br />
<br />
=== Commercial Desktop Utilities ===<br />
<br />
These are simple programs that could realistically be sold, bundled, or used internally by small businesses.<br />
<br />
Possible apps:<br />
<br />
* invoice helper<br />
* customer lookup tool<br />
* report generator<br />
* file renamer<br />
* batch image processor<br />
* shipping label assistant<br />
* data cleanup tool<br />
* small SQLite-backed business app<br />
* upload/deployment utility<br />
* quote/order tracker<br />
<br />
== Suggested Repository Layout ==<br />
<br />
A useful structure for each template would be:<br />
<br />
<pre><br />
template-name/<br />
README.md<br />
screenshot.png<br />
template.wxg<br />
generated/<br />
MyFrame.pm<br />
driver.pl<br />
dist/<br />
build-notes.md<br />
</pre><br />
<br />
Recommended files:<br />
<br />
* <code>README.md</code> - what the template demonstrates<br />
* <code>template.wxg</code> - wxGlade project file<br />
* <code>driver.pl</code> - minimal runnable Perl script<br />
* <code>screenshot.png</code> - current screenshot<br />
* <code>build-notes.md</code> - notes about Strawberry Perl, wxPerl, DLLs, packaging, or installer creation<br />
<br />
== Suggested README Fields for Each Template ==<br />
<br />
Each template should ideally document:<br />
<br />
{| class="wikitable" width="100%"<br />
! Field<br />
<br />
| ! Description |<br />
| ------------------------------------------------------------------------------------ |<br />
| '''Name''' |<br />
| Human-readable name of the template or application idea |<br />
| - |<br />
| '''Status''' |<br />
| Mockup, partial implementation, working prototype, packaged release, abandoned, etc. |<br />
| - |<br />
| '''Purpose''' |<br />
| What kind of application this layout is good for |<br />
| - |<br />
| '''Widgets Used''' |<br />
| Major wxWidgets/wxPerl controls demonstrated |<br />
| - |<br />
| '''Perl Modules''' |<br />
| Useful Perl modules that pair well with the template |<br />
| - |<br />
| '''Tested On''' |<br />
| Strawberry Perl version, wxPerl version, Windows version, etc. |<br />
| - |<br />
| '''Packaging Notes''' |<br />
| Any notes about building an EXE or installer |<br />
| - |<br />
| '''Screenshot''' |<br />
| Link or local file reference |<br />
| } |<br />
<br />
== Widget Patterns to Demonstrate ==<br />
<br />
Future templates should try to cover common wxPerl/wxGlade patterns such as:<br />
<br />
* main frame with menu bar and status bar<br />
* toolbar-driven application<br />
* tabbed notebook interface<br />
* split-pane application<br />
* tree navigation plus detail panel<br />
* dual-pane file manager<br />
* modal configuration dialog<br />
* wizard-style workflow<br />
* searchable list/grid interface<br />
* log viewer with controls<br />
* progress dialog for long-running Perl tasks<br />
* system tray utility<br />
* SQLite-backed data-entry form<br />
* plot/image viewer shell<br />
<br />
== Notes on Clone-Style Templates ==<br />
<br />
Some templates intentionally resemble well-known classic applications. These should be treated as UI studies and educational examples, not as trademarked product replacements.<br />
<br />
When turning a template into a real application:<br />
<br />
* use your own application name<br />
* use your own icons and artwork<br />
* avoid copying trademarks<br />
* keep the useful layout pattern<br />
* replace mockup controls with real Perl logic<br />
<br />
== Why This Matters ==<br />
<br />
wxPerl and wxGlade give Perl programmers a practical path to creating normal-looking desktop applications, especially on Windows. A good collection of templates lowers the barrier to entry by giving programmers something visual and runnable to start from.<br />
<br />
The real advantage is simple:<br />
<br />
'''Use wxGlade to design the interface. Use Perl to make it useful. Package it so users never need to know it was Perl.'''<br />
<br />
== See Also ==<br />
<br />
* [[Portal:GUIs with Perl]]<br />
* [[Portal:Windows]]<br />
* [[Developing and Distributing wxPerl Applications on Windows]]<br />
* [[Portal:Perl for Profit]]<br />
* [[Portal:Software Development Tools]]<br />
* [[Portal:SciTech]]<br />
* [[Portal:Perl Powered Programs (PPP)]]</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Developing_and_Distributing_wxPerl_Applications_on_Windows&diff=342Developing and Distributing wxPerl Applications on Windows2026-07-05T07:16:37Z<p>Admin: /* Getting wxGlade Help */</p>
<hr />
<div>== Introduction ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
This page is about installing wxPerl under Strawberry Perl for application development and distribution as a Windows executable.<br />
<br />
=== Why Perl GUIs, why Windows? ===<br />
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.<br />
[[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.]]<br />
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.<br />
<br />
=== [https://dev.to/sciurius/wxperl-revival-5fde See] the original call for a [https://dev.to/sciurius/wxperl-revival-5fde wxPerl Revival]! ===<br />
<br />
=== Git Repository of wxGlade / wxPerl Examples ===<br />
https://github.com/The-Perl-Cottage-Guild/wxPerl-Templates<br />
== Installing wxPerl on Windows for Development ==<br />
<br />
These instructions are for you, not your customers! Give them a clickable installer like Windows users expect (see how here!)<br />
<br />
=== General Steps ===<br />
<br />
{| class="wikitable"<br />
! Step<br />
! Component<br />
! Link<br />
! Notes<br />
|-<br />
| 1<br />
| Strawberry Perl<br />
| [https://strawberryperl.com/releases.html releases]<br />
| Install Strawberry Perl first. For the newer PDL-based build, use the PDL ZIP edition rather than the standard MSI.<br />
|-<br />
| 2<br />
| Alien::wxWidgets<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/ github]<br />
| Install after Strawberry Perl and wxWidgets are available.<br />
|-<br />
| 3<br />
| Wx / wxPerl<br />
| [https://github.com/sciurius/wxPerl/releases github]<br />
| Install last; this is the Perl binding used by wxPerl applications.<br />
|}<br />
<br />
=== More Specific Version Combinations with Detailed Instructions & Links ===<br />
<br />
{| class="wikitable"<br />
! Status<br />
! Strawberry Perl<br />
! wxWidgets<br />
! Alien::wxWidgets<br />
! Wx / wxPerl<br />
! Detailed Instructions / Links<br />
! Notes<br />
|-<br />
| Latest / Experimental PDL Build<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54221_64bit 5.42.2.1 64-bit UCRT, PDL ZIP edition]<br />
| [https://github.com/wxWidgets/wxWidgets/releases/tag/v3.2.9 3.2.9]<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.73 0.73]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.009 3.009]<br />
| [[Wx 3.009, Alien::wxWidgets 0.73, Strawberry Perl 5.42.2.1 PDL]]<br />
| Newer PDL-based build path. 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>. This combination should be treated as experimental until the full build and packaging workflow is verified.<br />
|-<br />
| Upstream PowerShell Helper Script<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54201_64bit 5.42.0.1 64-bit portable, by default]<br />
| [https://github.com/wxWidgets/wxWidgets/releases/tag/v3.2.9 3.2.9]<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.73 0.73]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.009 3.009]<br />
| [https://github.com/sciurius/wxGitHubAction/blob/main/script/wxPerl-Windows.ps1 wxPerl-Windows.ps1]<br />
| Read the script carefully before running it. As written, it installs portable Strawberry Perl, builds wxWidgets from source, manually installs Alien::wxWidgets configuration, then builds Wx. It does not use the PDL ZIP by default, so the script needs adjustment for the <code>C:\sw\pdl</code> PDL layout. It is best treated as an upstream build recipe or advanced helper, not as the primary beginner installation path.<br />
|-<br />
| Previously Tested<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54021_64bit_UCRT 5.40.2.1 64-bit UCRT MSI]<br />
| See detailed instructions page<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.71 0.71]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.008 3.008]<br />
| [[Wx 3.008, Alien::wxWidgets 0.71, Strawberry Perl 5.40.2.1]]<br />
| Previously documented working combination. This is the safer reference path until the newer PDL build is fully verified.<br />
|-<br />
| Archive<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54001_64bit_UCRT 5.40.0.1 64-bit UCRT MSI]<br />
| See detailed instructions page<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.70 0.70]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.005 3.005]<br />
| [[Wx 3.005, Alien::wxWidgets 0.70, Strawberry Perl 5.40.0.1]]<br />
| Earlier archived working combination. Keep this entry for historical reference and troubleshooting regressions.<br />
|}<br />
<br />
== Verify Installation ==<br />
The information provided in this section ought to be unrelated to the verified version combination outlined in the Installation section above. <br />
<br />
=== Install Wx::Demo ===<br />
Wx::Demo is nice demonstration application, highlight many (if not all) of the wxWidget features available via xPerl.<br />
<br />
<big><code>C:\> cpanm --verbose Wx::Demo</code></big><br />
<br />
.. then once installed, run it with this command (which is available in the PATH already),<br />
<br />
<big><code>C:\> wxperl_demo.pl</code></big><br />
<br />
== wxGlade - a Perl Friendly Cross-Platform GUI Builder ==<br />
<br />
=== Trigger Warning: wxGlade is written in wxPython, so you must install it if you want to use wxGlade to build your GUI. ===<br />
Totally worth it!<br />
<br />
=== Install wxGlade ===<br />
[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.<br />
<br />
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.<br />
=== Step 1 - Install Python 3.10.11 for Windows ===<br />
Install via following link,<br />
<br />
https://www.python.org/ftp/python/3.10.11/python-3.10.11-amd64.exe ([https://www.python.org/downloads/windows/ linked here])<br />
<br />
'''Notes''':<br />
<br />
# 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<br />
# install as admin (checkbox should be already checked; also opt'd to add "python" to the PATH)<br />
<br />
=== Step 2 - Install wxPython ===<br />
<br />
# open up the Windows CMD window<br />
# use pip,<br />
<br />
<big><code>C:\> pip install wxPython</code></big><br />
<br />
'''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.<br />
<br />
=== Step 3 - Download and unzip wxGlade ===<br />
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.)<br />
[[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!]]<br />
Via Windows CMD terminal, navigate to the unzipped directory and run the command,<br />
<br />
<big><code>C:\> python wxglade.py</code></big><br />
<br />
=== Getting wxGlade Help ===<br />
''wxGlade''<nowiki/>'s developer is responsive on Github and there is a semi-active email list on SourceForge,<br />
<br />
* Github repo - https://github.com/wxGlade/wxGlade<br />
* email list - https://sourceforge.net/p/wxglade/mailman/wxglade-general/<br />
* See [[GUI ideas for use with wxGlade]] if you don't know where to start!<br />
<br />
== Development Workflow Notes ==<br />
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.<br />
[[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.]]<br />
<br />
=== Editor and <code>git</code> Options on Windows ===<br />
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>:<br />
<br />
<big><code>pacman -S vim git</code></big><br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Pro Tip: Turn Off MSYS2's <code>vim</code> Mouse Support and Auto/Smart Indenting ====<br />
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.<br />
<br />
To turn all that off, put the following lines in your <code>~/.vimrc</code> file:<br />
<br />
<pre><br />
set mouse=<br />
set noautoindent<br />
set nosmartindent<br />
set nocindent<br />
</pre><br />
=== Using wxGlade's "Single file" + "''Keep user code''" Options ===<br />
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:<br />
<br />
# start a new project (or open an existing one)<br />
# click on the root "Application" object in the object viewer<br />
# find the output pane, set the output to be "'''Perl'''"<br />
# set version of wxWidgets to be "'''3.0'''"<br />
# [[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<br />
<br />
=== Using wxGlade's "''Separate file for each class''" Option ===<br />
... to do<br />
<br />
== Creating Windows EXEs ==<br />
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.<br />
<br />
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.<br />
<br />
=== PAR::Package, App::PP::Autolink, and Wx::Perl::Packager ===<br />
<br />
==== Step 1 - Install PAR::Package, App::PP::Autolink, and Wx::Perl::Packager ====<br />
<big><code>C:\> cpanm --verbose PAR::Package App::PP::Autolink Wx::Perl::Packager</code></big><br />
<br />
'''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.<br />
<br />
==== Step 2 - Generate the EXE ====<br />
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:<br />
<br />
<big><code>C:\> wxpar YOURPROGRAM.pl -o YOURPROGRAM.exe</code></big><br />
<br />
===== Important Notes About wxGlade Generated Code =====<br />
# 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.]<br />
# Earlier versions of wxGlade also used a non-Exporter import tag that wxpar could not properly follow; see the code "before" and "after" below:<br />
<br />
<pre><br />
use Wx qw[:allclasses];<br />
use strict;<br />
<br />
...<br />
<br />
package main;<br />
<br />
unless(caller){<br />
my $local = Wx::Locale->new("English", "en", "en"); # replace with ??<br />
$local->AddCatalog("app"); # replace with the appropriate catalog name<br />
<br />
my $app = MyApp->new();<br />
$app->MainLoop();<br />
}<br />
</pre><br />
<br />
Should be modified to look like the following:<br />
<br />
<pre><br />
use Wx;<br />
use strict;<br />
<br />
...<br />
<br />
package main;<br />
<br />
my $local = Wx::Locale->new("English", "en", "en"); # replace with ??<br />
$local->AddCatalog("app"); # replace with the appropriate catalog name<br />
<br />
my $app = MyApp->new();<br />
$app->MainLoop();<br />
</pre><br />
<br />
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.<br />
<br />
==== Special Cases ====<br />
<br />
===== <code>Makefile</code> for an Application uses HTTP::Tiny and calls out to SSL-enabled sites =====<br />
Example - [https://github.com/StormSurgeLive/nhc-advisory-gui/blob/master/asgs-storm-bug.pl https://github.com/StormSurgeLive/nhc-advisory-gui/]<br />
<br />
(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!)<br />
<br />
<pre><br />
all:<br />
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<br />
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<br />
<br />
# It was an adventure finding all the dependencies related to the wxpar command,<br />
# particularly those around what was needed. The basic process entailed:<br />
# 1. use wxpar, which generates an options file with all the Wx DLLs<br />
# 2. install App::PP::Autolink, which provides the utility "pp_autolink"; this<br />
# utility scans the .pl file you're packing, in this case, "asgs-storm-bug.pl",<br />
# for DLLs - lo' and behold, it found the ones I needed; in particular the critical<br />
# one that was not getting picked up by pp or wxpar, "libcrypto-3-x64___.dll!"<br />
# 3. run the "wxpar" command above<br />
# 4. test in a non-Strawberry Perl window, such as the MSYS2 terminal, using the command:<br />
#<br />
# PERL_DL_DEBUG=5 dist/nhc-explorer.exe<br />
#<br />
# I learned about this command while searching, here:<br />
#<br />
# https://stackoverflow.com/questions/423330/why-cant-dynaloader-pm-load-ssleay-dll-for-netssleay-and-cryptssleay<br />
</pre><br />
==== Important Note About Finding all DLLs ====<br />
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.<br />
<br />
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.<br />
<br />
=== Martha - ''A lightweight wxPerl helper for packaging Perl applications on Windows'' ===<br />
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:<br />
<br />
* automatically finds required DLLs<br />
* generates Makefile, based on using wxpar (a pp wrapper)<br />
* user can tweak and save the Makefile<br />
* user can load an existing Makefile<br />
* user can run the Makefile to create the executable<br />
* user can run the executable<br />
* user can configure an Inno Setup provided it is installed<br />
* run the Inno Setup file to generate an installer for their program<br />
* finally, they may test the installer directly from the GUI<br />
<br />
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.<br />
<br />
For more information and updates on the project, visit the Github repo [https://github.com/The-Perl-Cottage-Guild/wxPerl-Helper here].<br />
<br />
=== Background: Perl, wxWidgets, and RAD on Windows ===<br />
<br />
For historical context on earlier Perl/wxWidgets GUI builders, RAD tools, and discontinued Windows application-building efforts, see [[Perl and wxWidgets RAD on Windows]].<br />
<br />
== Creating Installers for Windows EXEs ==<br />
Professional Windows programs are expected to provide installers. This section will be developed as I figure out how to do this. A few notes:<br />
<br />
* 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])<br />
* '''[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].<br />
* 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<br />
* [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.''<br />
* [https://www.revenera.com/install/products/installshield InstallShield] (commercial - software monetization services)<br />
<br />
=== Using Inno Setup ===<br />
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.<br />
<br />
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.<br />
<br />
[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.<br />
<br />
[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.<br />
== Underdeveloped Sections ==<br />
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.<br />
<br />
=== Distributing EXEs to other Windows Machines ===<br />
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.<br />
<br />
=== Maintaining Perl Applications using XRC ===<br />
[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.<br />
[[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.]]<br />
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.<br />
<br />
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.<br />
<br />
=== Frequently Asked Questions ===<br />
Nobody actually contacts me to ask these questions, but they seem to be important.<br />
<br />
==== Q: Can these wxPerl applications using Strawberry Perl make ''https'' requests? ====<br />
A: Yes! Strawberry Perl comes with HTTP::Tiny (a core Perl module) and Net::SSLeay (used by HTTP::Tiny for https requests).<br />
<br />
== Additional Resources ==<br />
<br />
=== Printed Books ===<br />
[[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.]]<br />
'''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.<br />
<br />
=== Longer List of RAD Tools and GUI Builders* ===<br />
<br />
<br />
* [[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''')<br />
* [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''')<br />
** outputs Perl code<br />
** archived but a trial is downloadable [https://web.archive.org/web/20131020024033/http://www.wxdesigner-software.de/download.html here] (archive.org)<br />
** Reliable contact for license: ''undetermined at this time''<br />
* [http://www.anthemion.co.uk/dialogblocks/download.htm DialogBlocks] - '''('''''Latest at this time'', '''Version 5.18, August 21st, 2024)'''<br />
** can export C++, XRC, which wxGlade should be able to import<br />
** No Perl export (see XRC)<br />
** Cross Platform (Windows, Mac, Linux)<br />
** Registration required, but support is discontinued - email support@anthemion.co.uk, they may just give you a free key if you are nice :-)<br />
<br />
''*You may want to also check this duplicated internal [[Portal:Software Development Tools#wxPerl (wxWidgets wrapper)|page]].''</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Developing_and_Distributing_wxPerl_Applications_on_Windows&diff=341Developing and Distributing wxPerl Applications on Windows2026-07-05T07:16:10Z<p>Admin: /* wxGlade - a Perl Friendly Cross-Platform GUI Builder */</p>
<hr />
<div>== Introduction ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
This page is about installing wxPerl under Strawberry Perl for application development and distribution as a Windows executable.<br />
<br />
=== Why Perl GUIs, why Windows? ===<br />
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.<br />
[[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.]]<br />
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.<br />
<br />
=== [https://dev.to/sciurius/wxperl-revival-5fde See] the original call for a [https://dev.to/sciurius/wxperl-revival-5fde wxPerl Revival]! ===<br />
<br />
=== Git Repository of wxGlade / wxPerl Examples ===<br />
https://github.com/The-Perl-Cottage-Guild/wxPerl-Templates<br />
== Installing wxPerl on Windows for Development ==<br />
<br />
These instructions are for you, not your customers! Give them a clickable installer like Windows users expect (see how here!)<br />
<br />
=== General Steps ===<br />
<br />
{| class="wikitable"<br />
! Step<br />
! Component<br />
! Link<br />
! Notes<br />
|-<br />
| 1<br />
| Strawberry Perl<br />
| [https://strawberryperl.com/releases.html releases]<br />
| Install Strawberry Perl first. For the newer PDL-based build, use the PDL ZIP edition rather than the standard MSI.<br />
|-<br />
| 2<br />
| Alien::wxWidgets<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/ github]<br />
| Install after Strawberry Perl and wxWidgets are available.<br />
|-<br />
| 3<br />
| Wx / wxPerl<br />
| [https://github.com/sciurius/wxPerl/releases github]<br />
| Install last; this is the Perl binding used by wxPerl applications.<br />
|}<br />
<br />
=== More Specific Version Combinations with Detailed Instructions & Links ===<br />
<br />
{| class="wikitable"<br />
! Status<br />
! Strawberry Perl<br />
! wxWidgets<br />
! Alien::wxWidgets<br />
! Wx / wxPerl<br />
! Detailed Instructions / Links<br />
! Notes<br />
|-<br />
| Latest / Experimental PDL Build<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54221_64bit 5.42.2.1 64-bit UCRT, PDL ZIP edition]<br />
| [https://github.com/wxWidgets/wxWidgets/releases/tag/v3.2.9 3.2.9]<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.73 0.73]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.009 3.009]<br />
| [[Wx 3.009, Alien::wxWidgets 0.73, Strawberry Perl 5.42.2.1 PDL]]<br />
| Newer PDL-based build path. 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>. This combination should be treated as experimental until the full build and packaging workflow is verified.<br />
|-<br />
| Upstream PowerShell Helper Script<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54201_64bit 5.42.0.1 64-bit portable, by default]<br />
| [https://github.com/wxWidgets/wxWidgets/releases/tag/v3.2.9 3.2.9]<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.73 0.73]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.009 3.009]<br />
| [https://github.com/sciurius/wxGitHubAction/blob/main/script/wxPerl-Windows.ps1 wxPerl-Windows.ps1]<br />
| Read the script carefully before running it. As written, it installs portable Strawberry Perl, builds wxWidgets from source, manually installs Alien::wxWidgets configuration, then builds Wx. It does not use the PDL ZIP by default, so the script needs adjustment for the <code>C:\sw\pdl</code> PDL layout. It is best treated as an upstream build recipe or advanced helper, not as the primary beginner installation path.<br />
|-<br />
| Previously Tested<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54021_64bit_UCRT 5.40.2.1 64-bit UCRT MSI]<br />
| See detailed instructions page<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.71 0.71]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.008 3.008]<br />
| [[Wx 3.008, Alien::wxWidgets 0.71, Strawberry Perl 5.40.2.1]]<br />
| Previously documented working combination. This is the safer reference path until the newer PDL build is fully verified.<br />
|-<br />
| Archive<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54001_64bit_UCRT 5.40.0.1 64-bit UCRT MSI]<br />
| See detailed instructions page<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.70 0.70]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.005 3.005]<br />
| [[Wx 3.005, Alien::wxWidgets 0.70, Strawberry Perl 5.40.0.1]]<br />
| Earlier archived working combination. Keep this entry for historical reference and troubleshooting regressions.<br />
|}<br />
<br />
== Verify Installation ==<br />
The information provided in this section ought to be unrelated to the verified version combination outlined in the Installation section above. <br />
<br />
=== Install Wx::Demo ===<br />
Wx::Demo is nice demonstration application, highlight many (if not all) of the wxWidget features available via xPerl.<br />
<br />
<big><code>C:\> cpanm --verbose Wx::Demo</code></big><br />
<br />
.. then once installed, run it with this command (which is available in the PATH already),<br />
<br />
<big><code>C:\> wxperl_demo.pl</code></big><br />
<br />
== wxGlade - a Perl Friendly Cross-Platform GUI Builder ==<br />
<br />
=== Trigger Warning: wxGlade is written in wxPython, so you must install it if you want to use wxGlade to build your GUI. ===<br />
Totally worth it!<br />
<br />
=== Install wxGlade ===<br />
[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.<br />
<br />
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.<br />
=== Step 1 - Install Python 3.10.11 for Windows ===<br />
Install via following link,<br />
<br />
https://www.python.org/ftp/python/3.10.11/python-3.10.11-amd64.exe ([https://www.python.org/downloads/windows/ linked here])<br />
<br />
'''Notes''':<br />
<br />
# 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<br />
# install as admin (checkbox should be already checked; also opt'd to add "python" to the PATH)<br />
<br />
=== Step 2 - Install wxPython ===<br />
<br />
# open up the Windows CMD window<br />
# use pip,<br />
<br />
<big><code>C:\> pip install wxPython</code></big><br />
<br />
'''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.<br />
<br />
=== Step 3 - Download and unzip wxGlade ===<br />
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.)<br />
[[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!]]<br />
Via Windows CMD terminal, navigate to the unzipped directory and run the command,<br />
<br />
<big><code>C:\> python wxglade.py</code></big><br />
<br />
=== Getting wxGlade Help ===<br />
''wxGlade''<nowiki/>'s developer is responsive on Github and there is a semi-active email list on SourceForge,<br />
<br />
* Github repo - https://github.com/wxGlade/wxGlade<br />
* email list - https://sourceforge.net/p/wxglade/mailman/wxglade-general/<br />
* See [GUI ideas for use with wxGlade] if you don't know where to start!<br />
<br />
== Development Workflow Notes ==<br />
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.<br />
[[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.]]<br />
<br />
=== Editor and <code>git</code> Options on Windows ===<br />
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>:<br />
<br />
<big><code>pacman -S vim git</code></big><br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Pro Tip: Turn Off MSYS2's <code>vim</code> Mouse Support and Auto/Smart Indenting ====<br />
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.<br />
<br />
To turn all that off, put the following lines in your <code>~/.vimrc</code> file:<br />
<br />
<pre><br />
set mouse=<br />
set noautoindent<br />
set nosmartindent<br />
set nocindent<br />
</pre><br />
=== Using wxGlade's "Single file" + "''Keep user code''" Options ===<br />
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:<br />
<br />
# start a new project (or open an existing one)<br />
# click on the root "Application" object in the object viewer<br />
# find the output pane, set the output to be "'''Perl'''"<br />
# set version of wxWidgets to be "'''3.0'''"<br />
# [[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<br />
<br />
=== Using wxGlade's "''Separate file for each class''" Option ===<br />
... to do<br />
<br />
== Creating Windows EXEs ==<br />
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.<br />
<br />
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.<br />
<br />
=== PAR::Package, App::PP::Autolink, and Wx::Perl::Packager ===<br />
<br />
==== Step 1 - Install PAR::Package, App::PP::Autolink, and Wx::Perl::Packager ====<br />
<big><code>C:\> cpanm --verbose PAR::Package App::PP::Autolink Wx::Perl::Packager</code></big><br />
<br />
'''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.<br />
<br />
==== Step 2 - Generate the EXE ====<br />
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:<br />
<br />
<big><code>C:\> wxpar YOURPROGRAM.pl -o YOURPROGRAM.exe</code></big><br />
<br />
===== Important Notes About wxGlade Generated Code =====<br />
# 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.]<br />
# Earlier versions of wxGlade also used a non-Exporter import tag that wxpar could not properly follow; see the code "before" and "after" below:<br />
<br />
<pre><br />
use Wx qw[:allclasses];<br />
use strict;<br />
<br />
...<br />
<br />
package main;<br />
<br />
unless(caller){<br />
my $local = Wx::Locale->new("English", "en", "en"); # replace with ??<br />
$local->AddCatalog("app"); # replace with the appropriate catalog name<br />
<br />
my $app = MyApp->new();<br />
$app->MainLoop();<br />
}<br />
</pre><br />
<br />
Should be modified to look like the following:<br />
<br />
<pre><br />
use Wx;<br />
use strict;<br />
<br />
...<br />
<br />
package main;<br />
<br />
my $local = Wx::Locale->new("English", "en", "en"); # replace with ??<br />
$local->AddCatalog("app"); # replace with the appropriate catalog name<br />
<br />
my $app = MyApp->new();<br />
$app->MainLoop();<br />
</pre><br />
<br />
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.<br />
<br />
==== Special Cases ====<br />
<br />
===== <code>Makefile</code> for an Application uses HTTP::Tiny and calls out to SSL-enabled sites =====<br />
Example - [https://github.com/StormSurgeLive/nhc-advisory-gui/blob/master/asgs-storm-bug.pl https://github.com/StormSurgeLive/nhc-advisory-gui/]<br />
<br />
(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!)<br />
<br />
<pre><br />
all:<br />
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<br />
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<br />
<br />
# It was an adventure finding all the dependencies related to the wxpar command,<br />
# particularly those around what was needed. The basic process entailed:<br />
# 1. use wxpar, which generates an options file with all the Wx DLLs<br />
# 2. install App::PP::Autolink, which provides the utility "pp_autolink"; this<br />
# utility scans the .pl file you're packing, in this case, "asgs-storm-bug.pl",<br />
# for DLLs - lo' and behold, it found the ones I needed; in particular the critical<br />
# one that was not getting picked up by pp or wxpar, "libcrypto-3-x64___.dll!"<br />
# 3. run the "wxpar" command above<br />
# 4. test in a non-Strawberry Perl window, such as the MSYS2 terminal, using the command:<br />
#<br />
# PERL_DL_DEBUG=5 dist/nhc-explorer.exe<br />
#<br />
# I learned about this command while searching, here:<br />
#<br />
# https://stackoverflow.com/questions/423330/why-cant-dynaloader-pm-load-ssleay-dll-for-netssleay-and-cryptssleay<br />
</pre><br />
==== Important Note About Finding all DLLs ====<br />
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.<br />
<br />
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.<br />
<br />
=== Martha - ''A lightweight wxPerl helper for packaging Perl applications on Windows'' ===<br />
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:<br />
<br />
* automatically finds required DLLs<br />
* generates Makefile, based on using wxpar (a pp wrapper)<br />
* user can tweak and save the Makefile<br />
* user can load an existing Makefile<br />
* user can run the Makefile to create the executable<br />
* user can run the executable<br />
* user can configure an Inno Setup provided it is installed<br />
* run the Inno Setup file to generate an installer for their program<br />
* finally, they may test the installer directly from the GUI<br />
<br />
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.<br />
<br />
For more information and updates on the project, visit the Github repo [https://github.com/The-Perl-Cottage-Guild/wxPerl-Helper here].<br />
<br />
=== Background: Perl, wxWidgets, and RAD on Windows ===<br />
<br />
For historical context on earlier Perl/wxWidgets GUI builders, RAD tools, and discontinued Windows application-building efforts, see [[Perl and wxWidgets RAD on Windows]].<br />
<br />
== Creating Installers for Windows EXEs ==<br />
Professional Windows programs are expected to provide installers. This section will be developed as I figure out how to do this. A few notes:<br />
<br />
* 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])<br />
* '''[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].<br />
* 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<br />
* [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.''<br />
* [https://www.revenera.com/install/products/installshield InstallShield] (commercial - software monetization services)<br />
<br />
=== Using Inno Setup ===<br />
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.<br />
<br />
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.<br />
<br />
[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.<br />
<br />
[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.<br />
== Underdeveloped Sections ==<br />
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.<br />
<br />
=== Distributing EXEs to other Windows Machines ===<br />
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.<br />
<br />
=== Maintaining Perl Applications using XRC ===<br />
[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.<br />
[[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.]]<br />
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.<br />
<br />
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.<br />
<br />
=== Frequently Asked Questions ===<br />
Nobody actually contacts me to ask these questions, but they seem to be important.<br />
<br />
==== Q: Can these wxPerl applications using Strawberry Perl make ''https'' requests? ====<br />
A: Yes! Strawberry Perl comes with HTTP::Tiny (a core Perl module) and Net::SSLeay (used by HTTP::Tiny for https requests).<br />
<br />
== Additional Resources ==<br />
<br />
=== Printed Books ===<br />
[[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.]]<br />
'''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.<br />
<br />
=== Longer List of RAD Tools and GUI Builders* ===<br />
<br />
<br />
* [[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''')<br />
* [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''')<br />
** outputs Perl code<br />
** archived but a trial is downloadable [https://web.archive.org/web/20131020024033/http://www.wxdesigner-software.de/download.html here] (archive.org)<br />
** Reliable contact for license: ''undetermined at this time''<br />
* [http://www.anthemion.co.uk/dialogblocks/download.htm DialogBlocks] - '''('''''Latest at this time'', '''Version 5.18, August 21st, 2024)'''<br />
** can export C++, XRC, which wxGlade should be able to import<br />
** No Perl export (see XRC)<br />
** Cross Platform (Windows, Mac, Linux)<br />
** Registration required, but support is discontinued - email support@anthemion.co.uk, they may just give you a free key if you are nice :-)<br />
<br />
''*You may want to also check this duplicated internal [[Portal:Software Development Tools#wxPerl (wxWidgets wrapper)|page]].''</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Developing_and_Distributing_wxPerl_Applications_on_Windows&diff=340Developing and Distributing wxPerl Applications on Windows2026-07-05T06:54:13Z<p>Admin: /* Installation */</p>
<hr />
<div>== Introduction ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
This page is about installing wxPerl under Strawberry Perl for application development and distribution as a Windows executable.<br />
<br />
=== Why Perl GUIs, why Windows? ===<br />
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.<br />
[[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.]]<br />
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.<br />
<br />
=== [https://dev.to/sciurius/wxperl-revival-5fde See] the original call for a [https://dev.to/sciurius/wxperl-revival-5fde wxPerl Revival]! ===<br />
<br />
=== Git Repository of wxGlade / wxPerl Examples ===<br />
https://github.com/The-Perl-Cottage-Guild/wxPerl-Templates<br />
== Installing wxPerl on Windows for Development ==<br />
<br />
These instructions are for you, not your customers! Give them a clickable installer like Windows users expect (see how here!)<br />
<br />
=== General Steps ===<br />
<br />
{| class="wikitable"<br />
! Step<br />
! Component<br />
! Link<br />
! Notes<br />
|-<br />
| 1<br />
| Strawberry Perl<br />
| [https://strawberryperl.com/releases.html releases]<br />
| Install Strawberry Perl first. For the newer PDL-based build, use the PDL ZIP edition rather than the standard MSI.<br />
|-<br />
| 2<br />
| Alien::wxWidgets<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/ github]<br />
| Install after Strawberry Perl and wxWidgets are available.<br />
|-<br />
| 3<br />
| Wx / wxPerl<br />
| [https://github.com/sciurius/wxPerl/releases github]<br />
| Install last; this is the Perl binding used by wxPerl applications.<br />
|}<br />
<br />
=== More Specific Version Combinations with Detailed Instructions & Links ===<br />
<br />
{| class="wikitable"<br />
! Status<br />
! Strawberry Perl<br />
! wxWidgets<br />
! Alien::wxWidgets<br />
! Wx / wxPerl<br />
! Detailed Instructions / Links<br />
! Notes<br />
|-<br />
| Latest / Experimental PDL Build<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54221_64bit 5.42.2.1 64-bit UCRT, PDL ZIP edition]<br />
| [https://github.com/wxWidgets/wxWidgets/releases/tag/v3.2.9 3.2.9]<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.73 0.73]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.009 3.009]<br />
| [[Wx 3.009, Alien::wxWidgets 0.73, Strawberry Perl 5.42.2.1 PDL]]<br />
| Newer PDL-based build path. 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>. This combination should be treated as experimental until the full build and packaging workflow is verified.<br />
|-<br />
| Upstream PowerShell Helper Script<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54201_64bit 5.42.0.1 64-bit portable, by default]<br />
| [https://github.com/wxWidgets/wxWidgets/releases/tag/v3.2.9 3.2.9]<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.73 0.73]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.009 3.009]<br />
| [https://github.com/sciurius/wxGitHubAction/blob/main/script/wxPerl-Windows.ps1 wxPerl-Windows.ps1]<br />
| Read the script carefully before running it. As written, it installs portable Strawberry Perl, builds wxWidgets from source, manually installs Alien::wxWidgets configuration, then builds Wx. It does not use the PDL ZIP by default, so the script needs adjustment for the <code>C:\sw\pdl</code> PDL layout. It is best treated as an upstream build recipe or advanced helper, not as the primary beginner installation path.<br />
|-<br />
| Previously Tested<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54021_64bit_UCRT 5.40.2.1 64-bit UCRT MSI]<br />
| See detailed instructions page<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.71 0.71]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.008 3.008]<br />
| [[Wx 3.008, Alien::wxWidgets 0.71, Strawberry Perl 5.40.2.1]]<br />
| Previously documented working combination. This is the safer reference path until the newer PDL build is fully verified.<br />
|-<br />
| Archive<br />
| [https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_54001_64bit_UCRT 5.40.0.1 64-bit UCRT MSI]<br />
| See detailed instructions page<br />
| [https://github.com/sciurius/perl-Alien-wxWidgets/releases/tag/R0.70 0.70]<br />
| [https://github.com/sciurius/wxPerl/releases/tag/R3.005 3.005]<br />
| [[Wx 3.005, Alien::wxWidgets 0.70, Strawberry Perl 5.40.0.1]]<br />
| Earlier archived working combination. Keep this entry for historical reference and troubleshooting regressions.<br />
|}<br />
<br />
== Verify Installation ==<br />
The information provided in this section ought to be unrelated to the verified version combination outlined in the Installation section above. <br />
<br />
=== Install Wx::Demo ===<br />
Wx::Demo is nice demonstration application, highlight many (if not all) of the wxWidget features available via xPerl.<br />
<br />
<big><code>C:\> cpanm --verbose Wx::Demo</code></big><br />
<br />
.. then once installed, run it with this command (which is available in the PATH already),<br />
<br />
<big><code>C:\> wxperl_demo.pl</code></big><br />
<br />
== wxGlade - a Perl Friendly Cross-Platform GUI Builder ==<br />
<br />
=== Trigger Warning: wxGlade is written in wxPython, so you must install it if you want to use wxGlade to build your GUI. ===<br />
Totally worth it!<br />
<br />
=== Install wxGlade ===<br />
[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.<br />
<br />
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.<br />
=== Step 1 - Install Python 3.10.11 for Windows ===<br />
Install via following link,<br />
<br />
https://www.python.org/ftp/python/3.10.11/python-3.10.11-amd64.exe ([https://www.python.org/downloads/windows/ linked here])<br />
<br />
'''Notes''':<br />
<br />
# 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<br />
# install as admin (checkbox should be already checked; also opt'd to add "python" to the PATH)<br />
<br />
=== Step 2 - Install wxPython ===<br />
<br />
# open up the Windows CMD window<br />
# use pip,<br />
<br />
<big><code>C:\> pip install wxPython</code></big><br />
<br />
'''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.<br />
<br />
=== Step 3 - Download and unzip wxGlade ===<br />
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.)<br />
[[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!]]<br />
Via Windows CMD terminal, navigate to the unzipped directory and run the command,<br />
<br />
<big><code>C:\> python wxglade.py</code></big><br />
<br />
=== Getting wxGlade Help ===<br />
''wxGlade''<nowiki/>'s developer is responsive on Github and there is a semi-active email list on SourceForge,<br />
<br />
* Github repo - https://github.com/wxGlade/wxGlade<br />
* email list - https://sourceforge.net/p/wxglade/mailman/wxglade-general/<br />
<br />
== Development Workflow Notes ==<br />
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.<br />
[[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.]]<br />
<br />
=== Editor and <code>git</code> Options on Windows ===<br />
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>:<br />
<br />
<big><code>pacman -S vim git</code></big><br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Pro Tip: Turn Off MSYS2's <code>vim</code> Mouse Support and Auto/Smart Indenting ====<br />
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.<br />
<br />
To turn all that off, put the following lines in your <code>~/.vimrc</code> file:<br />
<br />
<pre><br />
set mouse=<br />
set noautoindent<br />
set nosmartindent<br />
set nocindent<br />
</pre><br />
=== Using wxGlade's "Single file" + "''Keep user code''" Options ===<br />
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:<br />
<br />
# start a new project (or open an existing one)<br />
# click on the root "Application" object in the object viewer<br />
# find the output pane, set the output to be "'''Perl'''"<br />
# set version of wxWidgets to be "'''3.0'''"<br />
# [[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<br />
<br />
=== Using wxGlade's "''Separate file for each class''" Option ===<br />
... to do<br />
<br />
== Creating Windows EXEs ==<br />
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.<br />
<br />
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.<br />
<br />
=== PAR::Package, App::PP::Autolink, and Wx::Perl::Packager ===<br />
<br />
==== Step 1 - Install PAR::Package, App::PP::Autolink, and Wx::Perl::Packager ====<br />
<big><code>C:\> cpanm --verbose PAR::Package App::PP::Autolink Wx::Perl::Packager</code></big><br />
<br />
'''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.<br />
<br />
==== Step 2 - Generate the EXE ====<br />
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:<br />
<br />
<big><code>C:\> wxpar YOURPROGRAM.pl -o YOURPROGRAM.exe</code></big><br />
<br />
===== Important Notes About wxGlade Generated Code =====<br />
# 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.]<br />
# Earlier versions of wxGlade also used a non-Exporter import tag that wxpar could not properly follow; see the code "before" and "after" below:<br />
<br />
<pre><br />
use Wx qw[:allclasses];<br />
use strict;<br />
<br />
...<br />
<br />
package main;<br />
<br />
unless(caller){<br />
my $local = Wx::Locale->new("English", "en", "en"); # replace with ??<br />
$local->AddCatalog("app"); # replace with the appropriate catalog name<br />
<br />
my $app = MyApp->new();<br />
$app->MainLoop();<br />
}<br />
</pre><br />
<br />
Should be modified to look like the following:<br />
<br />
<pre><br />
use Wx;<br />
use strict;<br />
<br />
...<br />
<br />
package main;<br />
<br />
my $local = Wx::Locale->new("English", "en", "en"); # replace with ??<br />
$local->AddCatalog("app"); # replace with the appropriate catalog name<br />
<br />
my $app = MyApp->new();<br />
$app->MainLoop();<br />
</pre><br />
<br />
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.<br />
<br />
==== Special Cases ====<br />
<br />
===== <code>Makefile</code> for an Application uses HTTP::Tiny and calls out to SSL-enabled sites =====<br />
Example - [https://github.com/StormSurgeLive/nhc-advisory-gui/blob/master/asgs-storm-bug.pl https://github.com/StormSurgeLive/nhc-advisory-gui/]<br />
<br />
(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!)<br />
<br />
<pre><br />
all:<br />
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<br />
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<br />
<br />
# It was an adventure finding all the dependencies related to the wxpar command,<br />
# particularly those around what was needed. The basic process entailed:<br />
# 1. use wxpar, which generates an options file with all the Wx DLLs<br />
# 2. install App::PP::Autolink, which provides the utility "pp_autolink"; this<br />
# utility scans the .pl file you're packing, in this case, "asgs-storm-bug.pl",<br />
# for DLLs - lo' and behold, it found the ones I needed; in particular the critical<br />
# one that was not getting picked up by pp or wxpar, "libcrypto-3-x64___.dll!"<br />
# 3. run the "wxpar" command above<br />
# 4. test in a non-Strawberry Perl window, such as the MSYS2 terminal, using the command:<br />
#<br />
# PERL_DL_DEBUG=5 dist/nhc-explorer.exe<br />
#<br />
# I learned about this command while searching, here:<br />
#<br />
# https://stackoverflow.com/questions/423330/why-cant-dynaloader-pm-load-ssleay-dll-for-netssleay-and-cryptssleay<br />
</pre><br />
==== Important Note About Finding all DLLs ====<br />
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.<br />
<br />
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.<br />
<br />
=== Martha - ''A lightweight wxPerl helper for packaging Perl applications on Windows'' ===<br />
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:<br />
<br />
* automatically finds required DLLs<br />
* generates Makefile, based on using wxpar (a pp wrapper)<br />
* user can tweak and save the Makefile<br />
* user can load an existing Makefile<br />
* user can run the Makefile to create the executable<br />
* user can run the executable<br />
* user can configure an Inno Setup provided it is installed<br />
* run the Inno Setup file to generate an installer for their program<br />
* finally, they may test the installer directly from the GUI<br />
<br />
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.<br />
<br />
For more information and updates on the project, visit the Github repo [https://github.com/The-Perl-Cottage-Guild/wxPerl-Helper here].<br />
<br />
=== Background: Perl, wxWidgets, and RAD on Windows ===<br />
<br />
For historical context on earlier Perl/wxWidgets GUI builders, RAD tools, and discontinued Windows application-building efforts, see [[Perl and wxWidgets RAD on Windows]].<br />
<br />
== Creating Installers for Windows EXEs ==<br />
Professional Windows programs are expected to provide installers. This section will be developed as I figure out how to do this. A few notes:<br />
<br />
* 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])<br />
* '''[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].<br />
* 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<br />
* [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.''<br />
* [https://www.revenera.com/install/products/installshield InstallShield] (commercial - software monetization services)<br />
<br />
=== Using Inno Setup ===<br />
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.<br />
<br />
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.<br />
<br />
[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.<br />
<br />
[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.<br />
== Underdeveloped Sections ==<br />
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.<br />
<br />
=== Distributing EXEs to other Windows Machines ===<br />
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.<br />
<br />
=== Maintaining Perl Applications using XRC ===<br />
[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.<br />
[[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.]]<br />
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.<br />
<br />
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.<br />
<br />
=== Frequently Asked Questions ===<br />
Nobody actually contacts me to ask these questions, but they seem to be important.<br />
<br />
==== Q: Can these wxPerl applications using Strawberry Perl make ''https'' requests? ====<br />
A: Yes! Strawberry Perl comes with HTTP::Tiny (a core Perl module) and Net::SSLeay (used by HTTP::Tiny for https requests).<br />
<br />
== Additional Resources ==<br />
<br />
=== Printed Books ===<br />
[[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.]]<br />
'''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.<br />
<br />
=== Longer List of RAD Tools and GUI Builders* ===<br />
<br />
<br />
* [[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''')<br />
* [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''')<br />
** outputs Perl code<br />
** archived but a trial is downloadable [https://web.archive.org/web/20131020024033/http://www.wxdesigner-software.de/download.html here] (archive.org)<br />
** Reliable contact for license: ''undetermined at this time''<br />
* [http://www.anthemion.co.uk/dialogblocks/download.htm DialogBlocks] - '''('''''Latest at this time'', '''Version 5.18, August 21st, 2024)'''<br />
** can export C++, XRC, which wxGlade should be able to import<br />
** No Perl export (see XRC)<br />
** Cross Platform (Windows, Mac, Linux)<br />
** Registration required, but support is discontinued - email support@anthemion.co.uk, they may just give you a free key if you are nice :-)<br />
<br />
''*You may want to also check this duplicated internal [[Portal:Software Development Tools#wxPerl (wxWidgets wrapper)|page]].''</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Main_Page&diff=339Main Page2026-07-05T06:51:34Z<p>Admin: </p>
<hr />
<div>**NOTOC**<br />
<br />
=== Welcome to the Perl Guilds Wiki ===<br />
The '''Perl Guilds''' wiki is a community-driven resource designed to support '''freelance Perl programmers''' and help them thrive in their independent careers. The original wiki concept was inspired by [https://wiki.freepascal.org FreePascal]'s community wiki.<br />
<br />
This wiki is maintained by [[ServiceProviders|'''these people''']]. You may thank them for this resource by hiring them for something.<br />
<br />
=== Transforming Perl by Striving for Virtue ===<br />
The infamous three "virtues" of a Perl programmer are not what you have been led to believe. They are bad, very bad. Please [https://www.youtube.com/watch?v=mEWfo9U3uTM view this] to learn more about [[The Real 3 Virtues of Perl|'''the true virtues of Perl''']]: '''''Prudence''''', '''''Spiritedness''''', and '''''Good Order'''''.<br />
<br />
I hope to convey these ideals through this resource, and I hope you can help me.<br />
<br />
=== Site Feedback and Contributions ===<br />
Click [https://github.com/The-Perl-Cottage-Guild/wiki-requests/issues here] to report an issue with the content, suggest edits or additions, or request editor access.<br />
<br />
You may also [https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors '''join the editors email list'''] to provide feedback, volunteer, or discuss proposed changes. <u>'''''[https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors This may get you a quicker response].'''''</u><br />
<br />
Volunteers are eligible to create a listing [[ServiceProviders|here]].<br />
<br />
= Portals =<br />
<br />
<div style="float:left; width:49%;"><br />
<br />
{| class="wikitable" width="100%"<br />
| valign="top" |<br />
<br />
== General Audience Links ==<br />
<br />
Wiki portals have been created for a selection of the platforms and topics that Perl and related tools support. The portals gather related information for each platform or topic in one place to make it easier to locate. The full list of supported platforms may be found [[Platform_list|here]].<br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:wxPerl.png|link=Portal:GUIs with Perl|[[Portal:GUIs with Perl|GUIs with Perl]]<br />
File:Logo Windows 01.png|link=Portal:Windows|[[Portal:Windows|Windows]]<br />
File:Payment.jpeg|link=Portal:Payment Processing|[[Portal:Payment Processing|Getting Paid]]<br />
File:Perlopenmp.jpeg|link=Portal:Perl+OpenMP|[[Portal:Perl+OpenMP|Perl+OpenMP]]<br />
File:Concurrency.png|link=Portal:Concurrency|[[Portal:Concurrency|Concurrency]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:ToolBox.png|link=Portal:Software Development Tools|[[Portal:Software Development Tools|Development Tools]]<br />
File:perlCGI.jpg|link=Portal:Perl CGI Programming|[[Portal:Perl CGI Programming|Legacy Perl]]<br />
File:Camels.jpg|link=Portal:Perl Powered Programs (PPP)|[[Portal:Perl Powered Programs (PPP)|Perl Powered Programs (PPP)]]<br />
File:Perlcommunity.png|link=Portal:Perl Communities|[[Portal:Perl Communities|Communities]]<br />
File:XS.jpg|link=Portal:Embedding and Extending Perl|[[Portal:Embedding and Extending Perl|Embedding and Extending Perl]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Money.jpeg|link=Portal:Perl for Profit|[[Portal:Perl for Profit|Perl for Profit]]<br />
File:History.gif|link=Portal:Perl History|[[Portal:Perl History|Perl History]]<br />
File:SQLdb TSQLQuery.PNG|link=Portal:Databases|[[Portal:Databases|Database Development]]<br />
File:GamesPortalLogo.png|link=Portal:Game Development|[[Portal:Game Development|Game Development]]<br />
File:HowTo.png|link=Portal:HowTo Demos|[[Portal:HowTo Demos|HowTo Demos]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:Rperl.jpeg|link=Portal:Alt. Perls|[[Portal:Alt. Perls|Alt. Perls]]<br />
File:Ai.jpeg|link=Portal:Artificial Intelligence|[[Portal:Artificial Intelligence|Artificial Intelligence]]<br />
File:Crypto.png|link=Portal:Crypto and Blockchain|[[Portal:Crypto and Blockchain|Blockchain]]<br />
File:Perlbooks.jpg|link=Portal:Ex Libris|[[Portal:Ex Libris|Ex Libris]]<br />
File:Embedded.png|link=Portal:Embedded|[[Portal:Embedded|Embedded]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:FBSD Daemon.jpg|link=Portal:FreeBSD,OpenBSD,etc|[[Portal:FreeBSD,OpenBSD,etc|FreeBSD, OpenBSD, etc.]]<br />
File:tux.png|link=Portal:Linux|[[Portal:Linux|Linux]]<br />
File:macOSlogo.png|link=Portal:Mac|[[Portal:Mac|macOS]]<br />
File:HardwarePortalLogo.png|link=Portal:Hardware and Robotics|[[Portal:Hardware and Robotics|Hardware and Robotics]]<br />
File:Businessmodels.jpeg|link=Portal:Perl Business Models and Case Studies|[[Portal:Perl Business Models and Case Studies|Perl Business Models and Case Studies]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:ImageMagick.gif|link=Portal:Graphics Programming|[[Portal:Graphics Programming|Graphics Programming]]<br />
File:Hpc.jpg|link=Portal:HPC - High Performance Computing|[[Portal:HPC - High Performance Computing|HPC - High Performance Computing]]<br />
File:Bioperl.jpeg|link=Portal:Life Sciences|[[Portal:Life Sciences|Life Sciences]]<br />
File:tdrawgrid.png|link=Portal:SaaS and Web Development|[[Portal:SaaS and Web Development|SaaS and Web Development]]<br />
File:tachart getting started step6.png|link=Portal:SciTech|[[Portal:SciTech|Science and Technology]]<br />
</gallery><br />
<br />
<gallery spacing="small" captionalign="center" position="center" widths="64" heights="64" hideaddbutton="true" navigation="true"><br />
File:NewUserLogo.png|link=Portal:New Users|[[Portal:New Users|New Users]]<br />
</gallery><br />
|}<br />
<br />
</div><br />
<br />
<div style="float:right; width:49%;"><br />
<br />
{| class="wikitable" width="100%"<br />
| valign="top" |<br />
<br />
== Perl Craftsmen and Professional Development ==<br />
<br />
'''This section is for independent software professionals''' '''who charge money for Perl-related services''' and use Perl as their secret weapon to make a living, or for those wishing to become one.<br />
<br />
It is not for "jacks of all trades." This section is for Perl craftsmen: journeymen and true masters who wish to leverage their Perl skills to put food in their kids' mouths and a roof over their heads.<br />
<br />
'''Quick Links'''<br />
<br />
* [[Developing and Distributing wxPerl Applications on Windows|wxPerl on Windows: developing and distributing wxPerl applications]]<br />
<br />
'''Notable Updates'''<br />
<br />
* [[Portal:GUIs with Perl|GUIs with Perl]]<br />
** [[Developing and Distributing wxPerl Applications on Windows]]<br />
* [[Portal:Perl+OpenMP|Perl+OpenMP]]<br />
<br />
'''Email Lists'''<br />
<br />
* '''[https://sourceforge.net/projects/perl-guilds/lists/perl-guilds-editors Perl-Guilds Wiki Contributors]''' listserv - join if you would like to contribute or offer regular feedback<br />
* '''[https://sourceforge.net/projects/perl-openmp/lists/perl-openmp-discuss Perl+OpenMP]''' listserv<br />
<br />
'''Note''': Yes, I encourage email lists for your project; and it turns out SourceForge.net is a great place to host reliable email lists!<br />
<br />
'''RAD, Rapid Application Development Tools, IDEs, and Installer-Makers'''<br />
<br />
* [https://sourceforge.net/projects/wxglade/ wxGlade] - written in Python, but can output Perl<br />
<br />
'''Using Perl for Making Windows GUI Programs'''<br />
<br />
* Cross-platform GUIs with wxPerl<br />
** [[Developing and Distributing wxPerl Applications on Windows]]<br />
* Windows-specific GUIs with Win32::GUI<br />
* Cross-platform GUIs with GUIDeFATE<br />
<br />
'''Using Perl for Creating a Commercial SaaS and Other Services'''<br />
<br />
'''Monetization Strategies for Perl Programmers'''<br />
<br />
'''Commercial Success Stories and Case Studies'''<br />
<br />
'''Downloads'''<br />
<br />
'''Community Participation'''<br />
<br />
* [https://www.perl-guilds.net Perl Guilds Forum] - test forum to see if any activity is drawn to it<br />
<br />
'''Tutorials'''<br />
<br />
'''Books and Magazines'''<br />
<br />
'''Related Sites'''<br />
<br />
* https://perlclientdirectory.com/ - curated list of Perl clients for external APIs and services<br />
* https://perlmodules.net - track changes to your favorite Perl modules in CPAN<br />
<br />
|}<br />
<br />
</div><br />
<br />
<div style="float:left; margin-right:0.9em;"><br />
<br />
== In the News ==<br />
<br />
A summary of recent news stories about Perl can be found [[In the News|here]].<br />
<br />
== Projects using Perl ==<br />
<br />
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]].<br />
<br />
== Bug Tracker ==<br />
<br />
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. 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]].<br />
<br />
<br /><br />
</div></div>Adminhttps://wiki.perl-guilds.net/index.php?title=Portal:Perl_Powered_Programs_(PPP)&diff=338Portal:Perl Powered Programs (PPP)2026-07-05T06:46:36Z<p>Admin: /* Moved / Not Perl-Based */</p>
<hr />
<div>=Introduction=<br />
<br />
This portal catalogs programs that are written in Perl, integrate Perl, use Perl heavily, or support Perl programmers.<br />
<br />
This is not the place for code that is strictly modules or libraries. You may [mailto:brett[.estrade@gmail.com](mailto:.estrade@gmail.com) email me] to get your program listed here after verification.<br />
<br />
=Written in Perl or Perl-Heavy=<br />
<br />
== GUI / Web Applications ==<br />
<br />
=== Blogging / Publishing ===<br />
<br />
* Movable Type (https://movabletype.org/) - long-running commercial blogging and publishing system built around Perl<br />
* Dada Mail (https://dadamailproject.com/) - web-based mailing list manager written in Perl<br />
<br />
=== Content Management Systems / Wikis / Collaboration ===<br />
<br />
* ShinyCMS (https://github.com/denny/ShinyCMS) - CMS built in Perl using Catalyst<br />
* Foswiki (https://foswiki.org/About/WebHome) - Perl-based enterprise wiki and collaboration platform<br />
* IkiWiki (https://ikiwiki.info/) - wiki compiler / static site generator written in Perl<br />
* Bugzilla (https://www.bugzilla.org/) - long-running bug tracking system, historically important and still maintained<br />
* Request Tracker / RT (https://bestpractical.com/request-tracker) - enterprise ticketing and workflow system<br />
* OTRS / ((OTRS)) Community Edition (https://otrs.com/) - historically important Perl-based help desk, customer service, and IT service management ticketing system. The former open source Community Edition ended after the 6.x line; modern open source continuation is mainly through forks such as Znuny and OTOBO.<br />
* Znuny (https://www.znuny.org/) - Perl-based help desk / ITSM system descended from the OTRS ecosystem<br />
<br />
=== Business / Institutional Systems ===<br />
<br />
* Koha (https://koha-community.org/) - open source integrated library system used by libraries<br />
* LedgerSMB (https://ledgersmb.org/) - open source accounting / ERP system for small and medium businesses<br />
<br />
=== Dev/Ops / System Administration ===<br />
<br />
* Rex (https://www.rexify.org/<nowiki/>) - use instead of Terraform, Puppet, Ansible, etc. for some automation workflows<br />
* Webmin (https://webmin.com/) - web-based Unix/Linux system administration panel<br />
* Virtualmin (https://www.virtualmin.com/) - hosting control panel built on the Webmin ecosystem<br />
* Usermin (https://www.usermin.com/) - web-based user account / mail / shell management from the Webmin family<br />
* Proxmox VE (https://github.com/proxmox) - major open source virtualization platform; the backend uses Perl heavily alongside Rust, JavaScript, and C<br />
* Netdisco (https://netdisco.org/) - web-based network discovery and management tool using SNMP, CLI, and device APIs<br />
* MySQLTuner (https://github.com/major/MySQLTuner-perl) - widely used MySQL/MariaDB/Percona tuning and diagnostics script written in Perl<br />
<br />
=== Email / Mail Filtering / Mail Archives ===<br />
<br />
* Apache SpamAssassin (https://spamassassin.apache.org/) - widely deployed anti-spam platform written in Perl<br />
* Sympa (https://www.sympa.community/) - scalable mailing list manager<br />
* MHonArc (https://mhonarc.org/) - Perl mail-to-HTML converter and mail archive generator<br />
* Dada Mail (https://dadamailproject.com/) - mailing list manager for announcement and discussion lists<br />
<br />
=== Monitoring / Logging / Statistics ===<br />
<br />
* AWStats (https://awstats.sourceforge.io/) - web, streaming, FTP, and mail log analyzer<br />
* Munin (https://munin-monitoring.org/) - networked resource monitoring and graphing tool<br />
* SmokePing (https://oss.oetiker.ch/smokeping/) - latency measurement and graphing tool<br />
* MRTG (https://oss.oetiker.ch/mrtg/) - Multi Router Traffic Grapher; classic network traffic graphing tool written in Perl and C<br />
<br />
=== Editors & IDEs ===<br />
<br />
* Kephra (https://kephra.sourceforge.net/site/en/home_news.shtml) - wxPerl-based editor<br />
* Padre (https://padre.perlide.org/) - Perl IDE<br />
<br />
=== Link Aggregation ===<br />
<br />
* Links (https://codeberg.org/gandalf/Links)<br />
<br />
=== Virtualization / VPS / Hosting Control Panels ===<br />
<br />
* Proxmox VE (https://github.com/proxmox) - open source virtualization and container platform with a Perl-heavy backend<br />
* cPanel/WHM (https://cpanel.net) - commercial webhosting control panel; historically Perl-heavy and still ships/supports Perl environments<br />
* Webmin / Virtualmin (https://webmin.com/) - web-based server administration and hosting management<br />
<br />
=== Scientific / Visualization Tools ===<br />
<br />
* Circos (https://circos.ca/) - visualization tool widely used for genomics and circular data visualization<br />
<br />
== Perl-Based Command-Line Tools ==<br />
<br />
* ack (https://beyondgrep.com/) - a better grep for programmers, written in Perl<br />
* cloc (https://github.com/AlDanial/cloc) - counts lines of code, comments, and whitespace; written entirely in Perl<br />
* cpanm / App::cpanminus (https://cpanmin.us/) - modern Perl module installer<br />
* dzil / Dist::Zilla (https://dzil.org/) - release/build automation for CPAN distributions<br />
* perlcritic (https://metacpan.org/dist/Perl-Critic) - judges Perl code against best practices and idiomatic traditions<br />
* perltidy (https://metacpan.org/dist/Perl-Tidy) - formats Perl code<br />
* perlbrew (https://perlbrew.pl/) - install and manage multiple Perl versions in user space<br />
* plenv (https://github.com/tokuhirom/plenv) - another Perl version manager<br />
* Carton (https://metacpan.org/pod/Carton) - dependency manager for Perl applications<br />
* Devel::Cover (https://metacpan.org/pod/Devel::Cover) - Perl code coverage tool<br />
* prove (https://perldoc.perl.org/prove) - TAP-based test runner included with Perl tooling<br />
* GNU Parallel (https://www.gnu.org/software/parallel/) - shell parallelization tool implemented as a large Perl script<br />
* GNU Automake (https://www.gnu.org/software/automake/) - core Autotools component; Automake requires Perl to generate Makefile.in files<br />
* latexmk (https://ctan.org/pkg/latexmk) - Perl script that automates LaTeX document builds<br />
<br />
=Uses Perl Heavily, Includes Perl Pieces, or Supports Perl Developers=<br />
<br />
* Git (https://git-scm.com/) - mostly C and shell, but ships Perl-based pieces such as git-svn and Git.pm<br />
* Debian packaging tools (https://packages.debian.org/) - the Debian packaging ecosystem includes many Perl-based tools and Perl helper packages, including debhelper/devscripts/lintian/dh-make-perl<br />
* cPanel/WHM (https://cpanel.net) - commercial hosting platform with strong Perl history and supported Perl integration points<br />
* MobaXterm (https://mobaxterm.mobatek.net/) - X server and Unix-like Windows environment; supports a usable Perl environment<br />
* wxGlade (https://github.com/wxGlade/wxGlade/releases) - wxWidgets GUI builder that can export wxPerl code<br />
* Slic3r (https://slic3r.org/) - open source 3D printing slicer; historically Perl-heavy in high-level flow, GUI, and testing, with later forks moving much of that work to C++</div>Adminhttps://wiki.perl-guilds.net/index.php?title=Portal:Perl_Powered_Programs_(PPP)&diff=337Portal:Perl Powered Programs (PPP)2026-07-05T06:45:16Z<p>Admin: </p>
<hr />
<div>=Introduction=<br />
<br />
This portal catalogs programs that are written in Perl, integrate Perl, use Perl heavily, or support Perl programmers.<br />
<br />
This is not the place for code that is strictly modules or libraries. You may [mailto:brett[.estrade@gmail.com](mailto:.estrade@gmail.com) email me] to get your program listed here after verification.<br />
<br />
=Written in Perl or Perl-Heavy=<br />
<br />
== GUI / Web Applications ==<br />
<br />
=== Blogging / Publishing ===<br />
<br />
* Movable Type (https://movabletype.org/) - long-running commercial blogging and publishing system built around Perl<br />
* Dada Mail (https://dadamailproject.com/) - web-based mailing list manager written in Perl<br />
<br />
=== Content Management Systems / Wikis / Collaboration ===<br />
<br />
* ShinyCMS (https://github.com/denny/ShinyCMS) - CMS built in Perl using Catalyst<br />
* Foswiki (https://foswiki.org/About/WebHome) - Perl-based enterprise wiki and collaboration platform<br />
* IkiWiki (https://ikiwiki.info/) - wiki compiler / static site generator written in Perl<br />
* Bugzilla (https://www.bugzilla.org/) - long-running bug tracking system, historically important and still maintained<br />
* Request Tracker / RT (https://bestpractical.com/request-tracker) - enterprise ticketing and workflow system<br />
* OTRS / ((OTRS)) Community Edition (https://otrs.com/) - historically important Perl-based help desk, customer service, and IT service management ticketing system. The former open source Community Edition ended after the 6.x line; modern open source continuation is mainly through forks such as Znuny and OTOBO.<br />
* Znuny (https://www.znuny.org/) - Perl-based help desk / ITSM system descended from the OTRS ecosystem<br />
<br />
=== Business / Institutional Systems ===<br />
<br />
* Koha (https://koha-community.org/) - open source integrated library system used by libraries<br />
* LedgerSMB (https://ledgersmb.org/) - open source accounting / ERP system for small and medium businesses<br />
<br />
=== Dev/Ops / System Administration ===<br />
<br />
* Rex (https://www.rexify.org/<nowiki/>) - use instead of Terraform, Puppet, Ansible, etc. for some automation workflows<br />
* Webmin (https://webmin.com/) - web-based Unix/Linux system administration panel<br />
* Virtualmin (https://www.virtualmin.com/) - hosting control panel built on the Webmin ecosystem<br />
* Usermin (https://www.usermin.com/) - web-based user account / mail / shell management from the Webmin family<br />
* Proxmox VE (https://github.com/proxmox) - major open source virtualization platform; the backend uses Perl heavily alongside Rust, JavaScript, and C<br />
* Netdisco (https://netdisco.org/) - web-based network discovery and management tool using SNMP, CLI, and device APIs<br />
* MySQLTuner (https://github.com/major/MySQLTuner-perl) - widely used MySQL/MariaDB/Percona tuning and diagnostics script written in Perl<br />
<br />
=== Email / Mail Filtering / Mail Archives ===<br />
<br />
* Apache SpamAssassin (https://spamassassin.apache.org/) - widely deployed anti-spam platform written in Perl<br />
* Sympa (https://www.sympa.community/) - scalable mailing list manager<br />
* MHonArc (https://mhonarc.org/) - Perl mail-to-HTML converter and mail archive generator<br />
* Dada Mail (https://dadamailproject.com/) - mailing list manager for announcement and discussion lists<br />
<br />
=== Monitoring / Logging / Statistics ===<br />
<br />
* AWStats (https://awstats.sourceforge.io/) - web, streaming, FTP, and mail log analyzer<br />
* Munin (https://munin-monitoring.org/) - networked resource monitoring and graphing tool<br />
* SmokePing (https://oss.oetiker.ch/smokeping/) - latency measurement and graphing tool<br />
* MRTG (https://oss.oetiker.ch/mrtg/) - Multi Router Traffic Grapher; classic network traffic graphing tool written in Perl and C<br />
<br />
=== Editors & IDEs ===<br />
<br />
* Kephra (https://kephra.sourceforge.net/site/en/home_news.shtml) - wxPerl-based editor<br />
* Padre (https://padre.perlide.org/) - Perl IDE<br />
<br />
=== Link Aggregation ===<br />
<br />
* Links (https://codeberg.org/gandalf/Links)<br />
<br />
=== Virtualization / VPS / Hosting Control Panels ===<br />
<br />
* Proxmox VE (https://github.com/proxmox) - open source virtualization and container platform with a Perl-heavy backend<br />
* cPanel/WHM (https://cpanel.net) - commercial webhosting control panel; historically Perl-heavy and still ships/supports Perl environments<br />
* Webmin / Virtualmin (https://webmin.com/) - web-based server administration and hosting management<br />
<br />
=== Scientific / Visualization Tools ===<br />
<br />
* Circos (https://circos.ca/) - visualization tool widely used for genomics and circular data visualization<br />
<br />
== Perl-Based Command-Line Tools ==<br />
<br />
* ack (https://beyondgrep.com/) - a better grep for programmers, written in Perl<br />
* cloc (https://github.com/AlDanial/cloc) - counts lines of code, comments, and whitespace; written entirely in Perl<br />
* cpanm / App::cpanminus (https://cpanmin.us/) - modern Perl module installer<br />
* dzil / Dist::Zilla (https://dzil.org/) - release/build automation for CPAN distributions<br />
* perlcritic (https://metacpan.org/dist/Perl-Critic) - judges Perl code against best practices and idiomatic traditions<br />
* perltidy (https://metacpan.org/dist/Perl-Tidy) - formats Perl code<br />
* perlbrew (https://perlbrew.pl/) - install and manage multiple Perl versions in user space<br />
* plenv (https://github.com/tokuhirom/plenv) - another Perl version manager<br />
* Carton (https://metacpan.org/pod/Carton) - dependency manager for Perl applications<br />
* Devel::Cover (https://metacpan.org/pod/Devel::Cover) - Perl code coverage tool<br />
* prove (https://perldoc.perl.org/prove) - TAP-based test runner included with Perl tooling<br />
* GNU Parallel (https://www.gnu.org/software/parallel/) - shell parallelization tool implemented as a large Perl script<br />
* GNU Automake (https://www.gnu.org/software/automake/) - core Autotools component; Automake requires Perl to generate Makefile.in files<br />
* latexmk (https://ctan.org/pkg/latexmk) - Perl script that automates LaTeX document builds<br />
<br />
=Uses Perl Heavily, Includes Perl Pieces, or Supports Perl Developers=<br />
<br />
* Git (https://git-scm.com/) - mostly C and shell, but ships Perl-based pieces such as git-svn and Git.pm<br />
* Debian packaging tools (https://packages.debian.org/) - the Debian packaging ecosystem includes many Perl-based tools and Perl helper packages, including debhelper/devscripts/lintian/dh-make-perl<br />
* cPanel/WHM (https://cpanel.net) - commercial hosting platform with strong Perl history and supported Perl integration points<br />
* MobaXterm (https://mobaxterm.mobatek.net/) - X server and Unix-like Windows environment; supports a usable Perl environment<br />
* wxGlade (https://github.com/wxGlade/wxGlade/releases) - wxWidgets GUI builder that can export wxPerl code<br />
* Slic3r (https://slic3r.org/) - open source 3D printing slicer; historically Perl-heavy in high-level flow, GUI, and testing, with later forks moving much of that work to C++<br />
<br />
=Moved / Not Perl-Based=<br />
<br />
These are useful programs, but should not be listed under "Written in Perl":<br />
<br />
* PmWiki (https://www.pmwiki.org/) - written in PHP<br />
* TiddlyWiki (https://tiddlywiki.com/) - written in JavaScript</div>Admin