From: Simon Wright <simon@pushface.org>
Subject: Re: Tcl/TK + Ada
Date: Tue, 18 Sep 2012 20:30:36 +0100
Date: 2012-09-18T20:30:36+01:00 [thread overview]
Message-ID: <m2r4pz3z8j.fsf@pushface.org> (raw)
In-Reply-To: ed571781-cab3-4185-b2e3-0878b3b70193@googlegroups.com
Patrick <patrick@spellingbeewinnars.org> writes:
> I am still really in the planning stage right now...but when I say
> daemon I mean a process that stays alive and accepts instructions. I
> was planning on using a port to receive on.
OK
> So let's say we were controlling an optical spectrometer, we might
> have commands like:
> set_wavelength
> set_high_voltage
> set_stirrer
> plot
> etc
>
> So take the plot command for instance. I want the command to send an
> instruction and arguments to the daemon and then return right
> away. The plotting could take hours or days so the daemon could be
> responsible for it after that point.
OK. You could build the GUI in straight Tcl/Tk and have it talk to the
daemon's port (on Linux, I guess that'd be a UNIX-domain socket).
> If I had all these simple little commands to control the daemon I
> thought I could also build a gui for it to visualize the data being
> collected.
Yes, indeed; but it'd need to be on the user side, not the daemon's, so
you'd need a protocol to request the current stats/return them (2-way
comms).
Equally you could use the same architecture but with Gtk/Ada.
next prev parent reply other threads:[~2012-09-21 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 11:56 Tcl/TK + Ada Patrick
2012-09-18 12:42 ` Thomas Løcke
2012-09-18 12:51 ` Patrick
2012-09-18 17:36 ` Simon Wright
2012-09-18 18:57 ` Patrick
2012-09-18 19:30 ` Simon Wright [this message]
2012-09-19 10:02 ` john
2012-09-19 11:17 ` Pascal Obry
2012-09-19 12:08 ` Patrick
2012-09-19 13:05 ` john
2012-09-19 14:27 ` Patrick
2012-09-19 15:12 ` Dmitry A. Kazakov
2012-09-19 15:43 ` Pascal Obry
2012-09-21 23:23 ` Jerry
2012-09-21 8:54 ` leonid.dulman
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox