Re: Easiest way to build Qt/Gtk interfaces for Ada programs

[Georg Bauhaus <rm.dash-bauhaus@futureapps.de>]

On 29.12.12 13:27, Dmitry A. Kazakov wrote:
> The point is, one influences another and if you consider the GUI framework
> fixed, then the application must adapt = you build around the GUI.

To build an application around a GUI is one example of
designing in accord with a given mechanism.
It is sad that there need to be so many variations of
basically the same mechanism.

Another popular given mechanism is based on web requests.
It is a technique for parallel execution just slightly
reminiscent of Paraffin.

Each request will perform part of a computation,
and will use no more than a limited amount of resources.
You therefore need to decompose a simple algorithm into
parts, assign these to request handlers, and start a
sequence of requests that trigger the handlers.

Topological order of requests and passing data is done
with the help of external storage. The latter has
transactions, and needs explicit cleanup (costly).
(This is Google's App Engine.)

For some setups, Paraffin seems simpler to use, though you'd
perhaps consider how to split the computation, and thus build
around a given mechanism.

Note that, in the US, using the specimen called MapReduce
incurs the cost of at least FUD via patent number 7,650,331.
Is the Paraffin library for Ada covered?

I suppose that you'd run into the same patent trouble (or not)
with GUIs once you start designing an application with a more
interesting UI.