Re: Ada Library, called, returns and continues ?

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Mon, 17 Dec 2012 07:58:48 -0800 (PST), Patrick wrote:

> "100K lines of GUI code or 100K lines altogether? "
> 
> The whole toolkit.

There should be some hidden code somewhere else.

> I was thinking that if I could bind an Ada entry to C, I could use a gui
> toolkits idle callback to retrieve information that could be processed in
> the back ground such as data being collected from an instrument, a bitmap
> image being generated from svg etc..

GtkAda contributions which does something close to this, you could use it
as a template for your code. However, as Simon wrote, using Ada with the
C++'s main requires additional work of initializing Ada's run-time. 

>> 'You also need support for unsolicited calls from Ada tasks. Consider a
>> progress bar indicator driven by an Ada task. At some point it should send
>> a message to the main thread to update the bar state. The main thread has
>> no idea about when and if that could happen. "
> 
> yes, I don't know how to do this but perhaps I can do this in a year or so
> when I am further along.

Or come to the conclusion that this cannot be done. When you say that a
tool kit X is simpler than the tool kit Y, this implies that you already
know how to accomplish all necessary tasks in X.

This is a typical mistake - look, how easy to create a window with a button
in it using X! Yes it is easy and you probably could accomplish 80% of the
project in 20% less time than in Y. The caveat is that the rest 20% could
require 1000% as much, if ever doable.

I know nothing about your toolkit X, I only warn you for this sort of
mistakes.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de