public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: Peace Everyone <dark.ts@gmx.de>
Cc: cygwin@cygwin.com
Subject: Re: EventListening
Date: Mon, 17 Oct 2005 01:03:00 -0000	[thread overview]
Message-ID: <4352F827.3010008@cygwin.com> (raw)
In-Reply-To: <4352EC94.7@gmx.de>

Peace Everyone wrote:
> Peace Everyone wrote:
> 
>>> I'm a noob with cygwin and have a question about EventListening, is 
>>> there an interface or a class I can use? Or some add on libraries to 
>>> include or do I have to write/implement my own EventListening Class?
>>
>>
>>
>> That's a good question.  I guess it depends on what kind of events you
>> want to listen for and where you believe the events are being generated.
>> You'll have to get much more specific about what you're trying to do
>> before someone on this list can offer you advice on this matter.
>>
> 
> Okey, It's like creating events in the (Console and Graphic)UI to inform 
> the ENGINE which data is needed.
> 
> One alternative is the console based UI, u type one command and several 
> options, from which u generate the adequate event to inform the ENGINE 
> what data the GUI needs
> 
> The other alternative is the "real" graphic based UI, with all the cute 
> little buttons and textfields in place of the console based UI....
> 
> I hope u now understand what I mean ;)


I think I do.  And it is as I suspected.

You're asking about application functionality.  This isn't a Cygwin-specific
question so it is off-topic for this list.  I believe you're really looking
for a framework for application development.  You may want to have a look at
QT, wxWindows, GTK and friends and other such toolkits.  You'll find QT3 and
GTK packages as part of the Cygwin distribution but you should really see
each toolkit's web site for complete information on what's available and
how it can be used.


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

      reply	other threads:[~2005-10-17  1:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 17:45 Where is documentation on bash "wait"? Eric Blake
2005-10-15 20:46 ` Bas van Gompel
2005-10-15 21:11   ` Eric Blake
2005-10-16  3:47     ` Buzz
2005-10-16  4:01       ` Eric Blake
2005-10-16 21:09         ` Bas van Gompel
2005-10-22 22:44         ` Where is documentation on keyring? Siegfried Heintze
2005-10-23  0:24           ` René Berber
2005-10-23  0:52           ` Gerrit P. Haase
2005-10-16 10:11       ` Where is documentation on bash "wait"? Dr. Volker Zell
2005-10-16 21:09         ` Bas van Gompel
2005-10-16 22:57           ` EventListening Peace Everyone
2005-10-16 23:10             ` EventListening Larry Hall (Cygwin)
2005-10-16 23:57               ` EventListening Peace Everyone
2005-10-17  1:03                 ` Larry Hall (Cygwin) [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4352F827.3010008@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --cc=cygwin@cygwin.com \
    --cc=dark.ts@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).