.. index:: blog; 2016/11/13

.. Modified: 2016-11-14/01:44-0500

SourceForge
===========

Well met,

Just spent a few minutes, and it was just a few minutes, building Unicon on
SourceForge using the freely offered developer web services.  Revision 4616,
pulled fresh from svn, configured and built inside a SourceForge developer
shell.

Worked out great.  First sample of Unicon CGI is up at

http://btiffin.users.sourceforge.net/form.html

.. literalinclude:: ../examples/form-cgi.html
   :language: html

.. only:: html

    .. rst-class:: rightalign

        :download:`../examples/form-cgi.html`

That form has a Submit action that invokes a small server side Unicon CGI
program. The code was taken from the Programming with Unicon book and modified
slightly to make it safer for hosting on a public facing web site.

.. literalinclude:: ../examples/simple-cgi.icn
   :language: unicon
   :start-after: ##+

.. only:: html

    .. rst-class:: rightalign

        :download:`../examples/simple-cgi.icn`

That trial code simply echos the form data, after ruthlessly sanitizing any
data to avoid any potential cross site scripting efforts.  The code was
compiled, on SourceForge with ``unicon -B simple.icn`` and then the resulting
executable was moved into the ``cgi-bin`` directory as ``simple.cgi``

All tests so far have come up golden.

As a very satisfied Unicon customer, the good folk that provide and maintain
SourceForge services deserve a round of applause.


Recent news
-----------

Timers
......

:ref:`Jafar` posted up a little ``loadfunc`` sample for accessing interval
timers with ``setitimer``.

https://sourceforge.net/p/unicon/discussion/contributions/thread/db34541b/


Resizing windows
................

A bug with window resizing is being discussed on the mailing list.  If things
progress as they normally do, this will be fixed shortly.  *The code under
discussion works fine here, an X11 build on Xubuntu, and this seems to be an
issue only with certain configurations of Unicon.*


Procedural or Object oriented
.............................

Unicon, being a multi-paradigm programming environment, offers a lot of
flexibility when it comes to making design and implementation choices.  I
asked for some opinions on the Discussion forum on whether
Procedural/Imperative or Object oriented development is preferred by the
language designers for small Unicon programs.

Both :ref:`clint` and :ref:`jafar` opined that *it depends on the developer
and the problem being faced, there is no preferred style*.  This is good news
in terms of letting programmers attack problems from the most comfortable
position, and is a sign that no single paradigm is given more weight during
language development.  Unicon programmers are free to make choices without
worrying about decisions being *wrong* in any way.  Both paradigms are a
good choice.

By the nature of Unicon, the styles can easily be mixed, so that becomes yet
another valid choice available for developers.

https://sourceforge.net/p/unicon/discussion/general/thread/b68a2d34/


Markdown
........

The UP docs now include a seed work example of calling ``libsoldout`` by way
of :ref:`loadfunc`.  The soldout engine ships with example (production ready)
output renderers.  The ``soldout.icn`` sample parses extended Markdown from a
Unicon string, and produces HTML, returned as a string from the loaded wrapper
function.  See :ref:`soldout` for code listings and some explanations.

More information about ``libsoldout``, by Natacha Porté, can be found at

http://fossil.instinctive.eu/libsoldout/home

*Have good, make well.*

.. post:: Nov 13 2016
   :tags: SourceForge
   :category: project
   :author: Brian Tiffin
   :location: on.ca
   :language: en