On Mon, 18 Feb 2008 17:52:39 -0500, "John Gabriele" <jmg3000(a)gmail.com> wrote: Calltips are shown with Ctrl-Alt-Space inside a function's argument list, between the "()". They show the whole function signature, including the function's return value and the full argument list. This is a _tip_ on how to _call_ the function. Tags are just any kind of symbols in source code.These can be functions, (global) variables, preprocessor macros, classes, methods, members, interfaces, whatever (maybe other programing language dependent things). ^^^^^^^^^^^^^^^^^^^^^^^^ I'm in doubt whether this is really "pretty easy to implement". Maybe, hopefully, I'm wrong. But About the general "bubbletips": this can be indeed done without too much effort. there is also some code which takes (in C files) macros and other globally defined stuff and put it in a "user list" (Scintilla term) which looks like and works like the usual symbol auto completion list. However, this code wasn't touched for a very long time and as far as I remember it was never finished by me ;-(. But we could skip the current behaviour of reading some macros and similar unuseful things and instead, read a user's global list(maybe per filetype) of "tips". That is, you create a file with some text per line and each line will be shown in a list inside Geany similar to the usual symbol auto completion. If the above is desired, patches are welcome ;-). I won't work on this in the next months. Even better would be to solve this by a plugin. This is not yet possible due to missing keybinding support and because there is not yet a "char added" signal. Both will come in the near future. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.key

On Feb 19, 2008 8:20 AM, Nick Treleaven <nick.treleaven(a)btinternet.com> wrote: Ok. But just to be clear: I'm talking about a feature separate, distinct from, and in addition to calltips. Maybe the name "bubbletips" is too general, and "symboltips" or "identifiertips", or something else would be more accurate. Anyways, here's an example: Use case: User is writing a C source code file and keeps forgetting what the difference between functions foob1() and foob2(). Solution: User writes a file named `c_mine.tips` and drops it into `~/geany_tips`. The directory `~/.geany/calltips` contains the tips that come stock with Geany. The `c_mine.tips` file contains the following: === snip === foob1 Only call this when the frobnicator is positive. foob2 Only call this when the frobnicator is negative. === /snip === The user then goes to Geany and does "File --> Load tips file..." and chooses `c_mine.tips`. The tips are now available everywhere (while editing any file). Perhaps there were check boxes in the "load tips file" dialog that let you choose to either have the tips work for all filetypes or specific ones, and the user chose "all filetypes". Now the user is editing, types "foob1" and -- with the cursor somewhere in the foob1 string (or at either end) -- hits a key-combo that makes a bubble pop up which says "Only call this when the frobnicator is positive.". After that, they might then hit the key combo to get the calltip for foob1. Enrico's idea for doing it as a plug-in sounds good. I probably will not do it at the moment. Also, I took a quick peek at plugindata.h (and the geanylua ref doc) and didn't see anything in there about bubbles or popup help. ---John

Following John's idea, here is a Lua script to implement some crude "bubbletip" support... First, create the calltips file: ~/.geany/plugins/geanylua/support/calltips This syntax for the file is simply pairs of lines, the first line is the identifier and the second is the calltip. for example: -------------<snip>------------- someword This is the calltip for some word anotherword This is the calltip for another word thirdword This is the calltip for the third word -------------</snip>------------- Next, make a copy of the script shown below and put it somewhere in your scripts folder, for instance: ~/.geany/plugins/geanylua/show-calltips.lua -------------<snip>------------- -- @ACCEL@ <Shift><Control>h if geany.count()==0 then return end local ds=geany.dirsep local tipfile=geany.appinfo().scriptdir..ds.."support"..ds.."calltips" local token=#geany.word()>0 and geany.word() or geany.text():sub(1,geany.caret()):gsub("(.*%W)(%a%w*)(.*)", "%2") if not (token and #token>0) then return end local tips, err=io.open(tipfile) if not tips then geany.message("Can't file tips file!",err) return end local found=nil for line in tips:lines() do if found then found=line break end if line==token then found=line end end tips:close() if found then geany.scintilla("CALLTIPSHOW", geany.caret(), found) end -------------</snip>------------- And then restart Geany. Now, when you type any one of the identifiers from the calltips file and then press [Ctrl][Shift]H you should see a calltip for that identifier. Notes: Identifiers must start with an alphabetic character, followed by zero or more alphanumeric characters. (But the calltip itself can contain puncuation, etc.) You still need to press [Escape] to get the calltip to disappear when you are done with it. You can change the first line of the script to something else if you want a different hotkey. It should also be possible to use different calltips files for different filetypes by testing the .ext field from the geany.fileinfo function, but I will leave that as an exercise for the reader :-) - Jeff

another screen shot from PyDev: http://pydev.sourceforge.net/images/codecompletion/codecompletionattr1.png For instance Stanis IDE recognises imported modules in python and then provides the namespace as calltip. from easygui import easygui easygui.{msgbox} {choicebox} ... If I am looking for a feature already implemented then please give me a pointer to it. But again, it will not be possible to create a methods file for every python module in the world... How does one create such a file? again, see above. I expect to have something like: background-color:{color} width{px,|em,etc.}

On Wed, 20 Feb 2008 13:39:04 +0100 Enrico Tröger &lt;enrico.troeger(a)uvena.de&gt; wrote: If msgbox and choicebox are things that produce tags if the relevant library source file is loaded, then using --generate-tags and loading the tags file would enable autocompletion for them. Regards, Nick

Is there not any library that can be build upon? For instance for syntax highlighting in webpages there is geshi. Maybe there's something similar for these tag files. I still don't know how other python IDEs succeed in providing this kind of autocompletion for any module that one imports.

On Wed, 2008-02-20 at 13:39 +0100, Enrico Tröger wrote: Maybe using the function "dir": ['__all__', '__builtins__', '__doc__', '__file__', '__name__', '_resolve_link', '_varprog', 'abspath', 'altsep', 'basename', 'commonprefix', 'curdir', 'defpath', 'devnull', 'dirname', 'exists', 'expanduser', 'expandvars', 'extsep', 'getatime', 'getctime', 'getmtime', 'getsize', 'isabs', 'isdir', 'isfile', 'islink', 'ismount', 'join', 'lexists', 'normcase', 'normpath', 'os', 'pardir', 'pathsep', 'realpath', 'samefile', 'sameopenfile', 'samestat', 'sep', 'split', 'splitdrive', 'splitext', 'stat', 'supports_unicode_filenames', 'walk'] Getting function description: Test whether a path is a regular file But I still don't know how to extract the parameters that any function needs... Hope this help ;-), I really miss "real autocompletion" in Python. Tonight I'll take a look inside pydev. Pydev autocompletion is very very good, but I don't have RAM enough for Eclipse at work :-/. Best Regards! nat:.