Do you really need a classical GUI? Personally, where possible, I try to wrap a webservice around the app and let the browser do the visual stuff,
esp. adaptation to the visuals of the OS at hand. A combination of Mojolicious and Bootstrap worked well for me.
Pros:
- separation of business logic execution from presentation (can run locally but also on a remote server)
- no hassle with compilation of C/C++ libraries on different platforms
- with Responsive Design, looks decent on phone, tablet, PC, etc.
- HTML & CSS is easy to use and pretty portable
The drawbacks might be slower response times and sometimes more work to realise complicated GUI structures.
Also networking (firewalls) and security has to be considered when not working locally (localhost).
But then, there are a lot of frameworks available and being forced to think about easier ways to achieve a
given functionality has some worth of its own.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
