public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Insight List <insight@sources.redhat.com>,
	Jim Ingham <jingham@apple.com>, Keith Seitz <keiths@cygnus.com>
Subject: Re: Interface to the generic menu and toolbar
Date: Thu, 01 Feb 2001 13:08:00 -0000	[thread overview]
Message-ID: <3A79CFEA.839FC913@redhat.com> (raw)
In-Reply-To: <3A707CAD.D216180F@redhat.com>

Nobody objected (what is reasonable -- the Tk and iwidgets style cannot
be that bad) so I went ahead and did it.  I will soon have a description 
as part of the new Plugin facility (I am still writting it).

	* library/gdbmenubar.itcl (constructor): Remove unused code.
	(add): New method.  Emulate the style of the menubar iwidget commands.
	(menubar_show): Old name.
	(show): New name.
	(menubar_menu_exists): Old name.
	(exists): New name.
	(menubar_clear_menu): Old name.
	(clear): New name.
	(menubar_delete_menu): Old name.
        (delete): New name.
	(menubar_new_menu): Make private.  Does not return anything.
	(menubar_add_menu_command): Make private.
	(menubar_add_menu_separator): Ditto.
	(menubar_change_menu_state): Ditto.
	* library/srcbar.itcl: Adjust to the above syntax.
	* library/plugins/plugins.tcl: Ditto.
	* library/plugins/rhabout/rhabout.itcl: Ditto.




Fernando Nasser wrote:
> 
> The existent interface to the menubar (which uses Tk menu) is
> currently:
> 
> # GDBMenuBar
>   public method menubar_show {}
>   public method set_class_state {enable_list}
>   method menubar_new_menu {name label underline}
>   method menubar_menu_exists {name}
>   method menubar_clear_menu {name}
>   method menubar_add_menu_separator {}
>   method menubar_add_menu_command {class label command args}
>   method menubar_change_menu_state {menu state}
>   method menubar_set_current_menu {menup}
> 
> Note that the code currently uses positional parameters.
> 
> I would like to make this more like iwidgets (or even Tk), with
> commands and arguments.
> 
> For instance:
> 
> $Menu add menubutton <name> -label <label> -underline <pos>
> 
> instead of
> 
> $Menu menubar_new_menu <name> <label> <pos>
> 
> I don't mean we should have all the operations the iwidget menubar has
> or that
> we do not add some operations we find useful.  I am just talking about
> the style.
> We do have some extra functionality anyway (like the classes that can be
> enabled/disabled).
> We could keep the names of the options that are equivalent the same
> though.
> 

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

  reply	other threads:[~2001-02-01 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25 11:23 Fernando Nasser
2001-02-01 13:08 ` Fernando Nasser [this message]
2001-02-01 15:04 ` Fernando Nasser

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=3A79CFEA.839FC913@redhat.com \
    --to=fnasser@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=jingham@apple.com \
    --cc=keiths@cygnus.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).