public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: loody <miloody@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: how to add additional script to add more register information
Date: Thu, 24 Jan 2013 15:51:00 -0000	[thread overview]
Message-ID: <CANudz+vy_cVyaaAX1A-aoyOJ+Lq6DLb881j2OsdAM8zwugnzZw@mail.gmail.com> (raw)
In-Reply-To: <51001905.7020808@redhat.com>

hi Keith:

2013/1/24 Keith Seitz <keiths@redhat.com>:
> On 01/23/2013 08:30 AM, loody wrote:
>>
>> Sorry for late response your mail.
>> should I get any script familiar fist, such tcl?
>> if tcl learning is necessary, where I can get it?
>
>
> Yes, you will need to know a bit of Tcl/Tk and iTcl/iTk/iWidgets.
>
> Tcl isn't all that difficult to learn. It has a few quirks, but nothing too
> major. iTcl is simply an OO extension for Tcl. It's also not very difficult
> to pick up.
>
> Once you know basic Tk-isms (packing vs grid, e.g.), iTk and iWidgets are
> pretty simple and quite a bit easier to use. It's simply a matter of
> remembering what kinds of widgets those packages offer. I don't remember
> much nowadays, so I just refer to the manual and demos.
>
> Tcl/Tk documentation, list of books, and tutorials listed on the Developer
> Xchange pages: http://www.tcl.tk/doc
>
> All things iTcl (incl iTk/iWidgets) are at
> http://incrtcl.sourceforge.net/itcl . [This is a bit outdated -- iTcl is now
> more closely integrated as a Tcl module, but this is the page that I always
> run to for documentation.]
Thanks for your great help,

-- 
Regards,

      reply	other threads:[~2013-01-24 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 15:53 loody
2013-01-11 16:07 ` Keith Seitz
2013-01-23 16:31   ` loody
2013-01-23 17:08     ` Keith Seitz
2013-01-24 15:51       ` loody [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=CANudz+vy_cVyaaAX1A-aoyOJ+Lq6DLb881j2OsdAM8zwugnzZw@mail.gmail.com \
    --to=miloody@gmail.com \
    --cc=insight@sourceware.org \
    --cc=keiths@redhat.com \
    /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).