Editing Perl and wxWidgets RAD on Windows (section)

== DialogBlocks and XRC ==

[http://www.anthemion.co.uk/dialogblocks/ DialogBlocks] belongs in the history, but with an important caveat: it is a wxWidgets GUI builder that can export C++ and XRC, not Perl directly.

* [http://www.anthemion.co.uk/dialogblocks/features.htm DialogBlocks features]

That still matters for Perl because wxPerl can use XRC through <code>Wx::XRC</code>. XRC is a language-neutral XML resource format for describing wxWidgets interfaces.

In theory, this lets a Perl developer use a GUI builder that knows nothing about Perl, export XRC, and then write Perl code that loads the interface and attaches handlers.

This is probably the more mature long-term architectural path for larger wxPerl applications:

# Use a visual designer for layout.

# Keep layout in XRC.

# Keep Perl code focused on behavior and event handling.

However, it is less beginner-friendly than "generate Perl and run it," so it does not solve the initial RAD onboarding problem by itself.