Add #include functions to calltips / func popup list.

[flyingboz]

I have been considering the issue of how to best add my libraries to the scite function list.

Ideally, the functions that are available in all incorporated #include files would be made 'automatically' added to the function calltips and / or the function popup list.

While I am completely open to suggestions, I'm thinking of a LUA script like "Refresh Function Tips" that would add / remove function definitions from the list at file open, and also be able to be invoked manually.

Any hints , tips, suggestions for design approach, potential gotchas , and/or pseudocode would be welcome, as I am a lua dabbler at best.

On another (somewhat related) note, There are also a lot of the standard UDFs that I never use, a way to flag / disable their appearance in the function list that would be supported across upgrades would reduce clutter.

[Valik]

If your libraries are static (for the most part), then write a script (in AutoIt) to process it and generate an API file which you of course have SciTE load. API files provide the auto-complete and Calltip information. You really don't want to try to do that in Lua at run-time because you have to implement your own custom routines from scratch. If you're nice, maybe we can talk Jos into adding a new unused keyword class to SciTE so that you can also generate a keyword list so your library functions will be colored differently (Jos, this is a feature request, I think I would use this).

Now that you bring this up, I may write a script to parse my own library files and generate stuff for my own functions. I don't know when, however.

Keep in mind, the caveats with this approach would be, the library would have to be manually updated every once in awhile if you make changes to it. Even if did generate the API file at SciTE-run-time, you would have to restart SciTE in order to see the changes.

[Jos]

Did you see the "Scite User CallTips" page in the SciTE4AutoIt3 helpfile or is that not what you are looking for ?

[eltorro]

Mhz posted scripts some time ago.

Calltips

Api

[Jos]

Keep in mind, the caveats with this approach would be, the library would have to be manually updated every once in awhile if you make changes to it. Even if did generate the API file at SciTE-run-time, you would have to restart SciTE in order to see the changes.

When you get to it you can use this script to reload the properties files without having to restart SciTE:

;Send SciTE Director my GUI handle so it will report info back from SciTE
SendSciTE_Command("reloadproperties:")

Func SendSciTE_Command($sCmd)
    Opt("WinSearchChildren", 1)
; Get SciTE DirectorHandle
    $SciTE_hwnd = WinGetHandle("DirectorExtension")
    Local $WM_COPYDATA = 74
    Local $CmdStruct = DllStructCreate('Char[' & StringLen($sCmd) + 1 & ']')
    DllStructSetData($CmdStruct, 1, $sCmd)
    Local $COPYDATA = DllStructCreate('Ptr;DWord;Ptr')
    DllStructSetData($COPYDATA, 1, 1)
    DllStructSetData($COPYDATA, 2, StringLen($sCmd) + 1)
    DllStructSetData($COPYDATA, 3, DllStructGetPtr($CmdStruct))
    DllCall('User32.dll', 'None', 'SendMessage', 'HWnd', $SciTE_hwnd, _
            'Int', $WM_COPYDATA, 'HWnd', 0, _
            'Ptr', DllStructGetPtr($COPYDATA))
EndFunc ;==>SendSciTE_Command

Edited January 17, 2008 by Jos

[Valik]

But does that reload the API files?

[Jos]

But does that reload the API files?

ummmmm Nope, just assumed to much here, but this does (tested it this time):

SendSciTE_Command("open:c:\\program files\\autoit3\\scite\\properties\\au3.properties")
SendSciTE_Command("close:")

Edited January 17, 2008 by Jos

[flyingboz]

Did you see the Scite User CallTips

Yes. Have examined it pretty closely. The 'trick' I'm looking for is to have it dynamically display available functions based on the #includes in a .au3 script that is displayed in

the active window. Some of my libraries are dealing with XML, or Excel, or WhatHaveYou, and they are extensive enough that having them all around at once when I'm working on scripts that don't involve / need them is cluttering my workspace.

SendScite_Command()

There's a concept I hadn't even considered...

Perhaps my script should parse my library include director[y|ies], and generate calltip files, appending them to my base, and switching between them as needed, rather than parsing them dynamically at each switch. Have to test the performance of that, though I would think it would be better than having to do recurse the #include stack each time.

Valik: If you're nice, maybe we can talk Jos into adding a new unused keyword class to SciTE so that you can also generate a keyword list so your library functions will be colored differently (Jos, this is a feature request, I think I would use this).

I'll be very, very, nice.

[Jos]

Why not just utilize the existing UDFs setup and just add a user file free to use ?

API UserUDFs is already there and for the "Coloring" we would need to to make the following changes to allow a user keywords file:

changes:

# Import the separate au3.keywords.properties file containing AutoIt3 info (based on script by Valik)

import properties\au3.keywords

import properties\au3.UserUdfs

-snip-

# UDFS

keywords8.$(au3)=$(au3.keywords.udfs) $(au3.keywords.user.udfs)

;User UDFs

au3.keywords.user.udfs=_test _test2 _test3 \

_test4

[roach4411]

I have been considering the issue of how to best add my libraries to the scite function list.

Ideally, the functions that are available in all incorporated #include files would be made 'automatically' added to the function calltips and / or the function popup list.

While I am completely open to suggestions, I'm thinking of a LUA script like "Refresh Function Tips" that would add / remove function definitions from the list at file open, and also be able to be invoked manually.

Any hints , tips, suggestions for design approach, potential gotchas , and/or pseudocode would be welcome, as I am a lua dabbler at best.

On another (somewhat related) note, There are also a lot of the standard UDFs that I never use, a way to flag / disable their appearance in the function list that would be supported across upgrades would reduce clutter.

This would be really useful, please let me know if you make any traction on this.

Thanks,

hp

[Jos]

Why not just utilize the existing UDFs setup and just add a user file free to use ?

API UserUDFs is already there and for the "Coloring" we would need to to make the following changes to allow a user keywords file:

changes:

No comment means agreement ?

Made the changes as I proposed and will be in the next version of SciTE4AutoIt3.

Jos