all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eric M. Ludlam" <eric@siege-engine.com>
Subject: Tooltipping enhancement request
Date: Thu, 4 Mar 2004 13:17:12 -0500	[thread overview]
Message-ID: <200403041817.i24IHC08001260@projectile.siege-engine.com> (raw)

Hi,

  I've got four enhancement requests based on some tools I've been
writing.  I think some of you already are familiar with some stuff
I've been doing called "cedet" which you can read about here:

  http://cedet.sourceforge.net

  A feature I've been working with lately is called "intellisense" in
other editors.  I thought it would be nifty to write something better.
I've opted to use an Emacs 21 tooltip to display completions.  Some of
that code was donated, and I had since attempted to fix some problems
I encountered.

  You can see a screenshot of what it should look like here:

http://cedet.sourceforge.net/intellisense.shtml    - page
http://cedet.sourceforge.net/inlinecompletion.png  - picture

  Here are the requests:

1) A function that takes a frame, window, and buffer position and
   returns an X/Y location on the screen that would allow
   accurate tooltip positioning.

At this time, a means of positioning the mouse pointer over a
particular character is used to then position the tool-tip.  That
requires that the mouse move.  In addition, things like header lines,
split windows, and toolbars seem to effect the accuracy of that
mechanism.

2) A means for accepting input from a tooltip (a strange idea)
   or a way to make a regular Emacs frame look like a tooltip.

The tooltip is pretty good for me.  I don't use the mouse much, but I
watch others use this feature in other editors, and they all like to
go clicky-clicky on the completion list.  I think it would help
mouse-bound users.

The tooltip part is important because a timer can cause Emacs to go
into this completion mode.  Splitting windows and moving the mouse
makes the feature difficult to accept.

Here are two other requests unrelated to tooltips:

3) A means of having an overline cross the entire window.

Also in the .png above, you can see some C definitions have a blue
line over them.  This overline is added to mimic a feature of IntelliJ
that has a thin line over all big functions, effectively dividing up
the buffer.  It is an interesting thought, which I quickly got used
to after implementing it.  It would be nice if that overline could
stretch across to the right side of the window to complete the effect.


4) Let multiple tools add header lines.

The mode line has had a means of management that lets different little
apps share it.  The header line does not.  I have a simple tools that
makes the function definition that is clipped at the top of the screen
appear in the header line.  I think it's pretty cool and quite
helpful.  That then conflicts with tabbar.  I had to turn it off in
the picture above because it changed how the tooltip was positioned.

The header line theme seems to be that tools use the entire line for
their purposes.  It would be nice if some official API made it easy
for apps that wish to use add a header line to be given something that
they can configure for their purposes without interfering with other
tools attempting to do the same thing.


Thanks for listening.
Eric

-- 
          Eric Ludlam:                 zappo@gnu.org, eric@siege-engine.com
   Home: http://www.ludlam.net            Siege: www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: www.gnu.org

             reply	other threads:[~2004-03-04 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 18:17 Eric M. Ludlam [this message]
2004-03-10  5:56 ` Tooltipping enhancement request Masatake YAMATO
2004-03-10 12:20   ` Re[2]: " Eric M. Ludlam
2004-03-11 22:03   ` Jan D.
2004-03-12  3:04     ` Re[2]: " Eric M. Ludlam
2004-03-12 11:18       ` Jan D.
2004-03-12 12:47         ` Re[4]: " Eric M. Ludlam

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=200403041817.i24IHC08001260@projectile.siege-engine.com \
    --to=eric@siege-engine.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.