I want (to make) a JS IntelliSense Plugin

[PeterJones]

@Sashank999 said in I want (to make) a JS IntelliSense Plugin:

I am a JS Dev. I develop on a lot of small individual files and have the habit of separating all functions into their own files. And I need the function names in all the JS files I edit. How can this be done ?
Is there any plugin that does this ? I think this is called as IntelliSense in VS Code, but my computer is too powerless to handle both VS Code and Chrome at the same time. Hence I chose Npp.

I think the “IntelliSense” name is trademarked… but there are other function-tagging libraries out there.
I know there are ways to run ctags-style function-name-searches through plugins like TagLEET or @Michael-Vincent’s modified fork of TagLEET.

This “javascript navigation” discussion from last year, where Michael describes how to get it working.

For more discussions, search for Michael’s posts mentioning TagLEET

If there are no plugins available, I will make my own if you give me the necessary tutorials or info on how to make it.

Writing a plugin is no task for the fainthearted. The usermanual has a section on plugins and the messaging system / plugin communication ; there are links from there to plugin templates. And you can look at the repos for other plugins to see other examples.

I am ready even to learn a new programming language if needed(I think I need to learn C/C++ for plugins, but IDK which one).

Any language that can create a DLL file should work; you just have to provide the right interface to functions with the appropriate names in the DLL. Many plugins are written in C++ or C#, and some plugins are written in Delphi…

[Sashank999]

… there are other function-tagging libraries out there.

I need auto completion too.

Writing a plugin is no task for the fainthearted…

Well, that doesn’t mean I can’t create one. Or does it ?

I think I’ll refer to the docs. Thanks.

[PeterJones]

@Sashank999 said in I want (to make) a JS IntelliSense Plugin:

I need auto completion too.

Like I said, I’m not the expert. The TagLEET might enable that… Again, @Michael-Vincent is our most-active user that I know uses ctags with Notepad++, so he would probably know. And there are probably other ctags users that I don’t know about.

Also, IIRC, Notepad++ uses the contents of any open file for auto-completion. So other source files that are open should supply words for builtin auto-complete… which means if you opened the ctags file, it should help autocomplete those words. But I’m not 100% sure.

And I’m having vague memories of someone once supplying a PythonScript or similar solution for doing extra function auto-complete, but I cannot remember in what context or whether it would help with what you want (other than I think it was for perl… so you might want to search for perl and autocomplete and maybe pythonscript in the forum, and see where that leads you)

Well, that doesn’t mean I can’t create one. Or does it ?

No, sorry, I didn’t mean to discourage you from writing one if the existing plugins don’t do what you want. You might even just fork the TagLEET and try to add the auto-completion if it doesn’t do what you need; that is probably easier than starting from scratch… assuming you can program in whatever language TagLEET is in.

[Michael Vincent]

@PeterJones said in I want (to make) a JS IntelliSense Plugin:

The TagLEET might enable that… Again, @Michael-Vincent is our most-active user that I know uses ctags with Notepad++

@Sashank999

Yes, my modified fork of TagLEET does autocompletion based on the tags file. I actually asked about this in a form post a while back and since I was already modifying TagLEET to do other stuff and realized the tags file would have function names, I added the autocompletion feature.

With my modified TagLEET, it can generate the tags file for your file and / or project (project more applicable in this case) and it auto-updates that tags file every time you save - so newly coded functions and tags are added automatically. Then when you’re coding away and need to autocomplete, you have some options. I have Notepad++ “native” autocomplete enabled:

The TagLEET “Scintilla autocomplete”:

works “seamlessly” with the Notepad++ “native” by just populating the autocomplete list with tags from the tags file that match. Note it does not merge the list with Notepad++ autocomplete list from the settings above - no way to do that as far as I know. But I do add an icon to help you see that it’s a TagLEET autocomplete. Below, regular Notepad++:

Typing something that does not exist in my current file, but is in another file from my project and thus in my tags file:

Notice the little boxes icon - that’s TagLEET offerings from the tags file.

If that isn’t getting you want you want, there is also a menu item “Plugins => TagLEET => Autocomplete” which forces a TagLEET window to pop-up with all possible autocompletions from the tags file:

I like the automatic Notepad++ / Scintilla autocomplete lists, but wanted to make sure I could always get an autocomplete from a tags file if available.

I assign shortcut keys to TagLEET. I forget if any are default set by the plugin, I’ve configured these through the menu Settings => Shortcut Mapper…:

Note that by doing a “Lookup Tag” on a file that does not have a tags file created or one can’t be found will create a prompt for you to create the tags file, so on your first tags lookup, you’ll be prompted to create the tags file (recursively, for the current file only, or cancel) and you can choose the directory to start the recursion in - so the top level directory of your project.

I include a version of Universal cTags executable in the plugin so if you have a %USERPROFILE%\.ctags.d\config.ctags file, it will respect those configs to ctags.exe - I use that to add a bunch of additional tags to search for a create a few new language parses like for SNMP MIB ASN.1 and Cisco router configs.

Since the “real” TagLEET is offered through Plugin Admin, my forked version is always marked as “pre-release” and can only be manually installed. Instructions on the README.

Cheers.

[Michael Vincent]

@Michael-Vincent said in I want (to make) a JS IntelliSense Plugin:

Yes, my modified fork of TagLEET does autocompletion based on the tags file.

@Sashank999

Before you go down a single path, you may also take a look at NppGTags, which is in Plugin Admin, does the same (more or less) with cTags but also has autocompletion and reference lookup (in some cases) baked in to the mainline version of the plugin.

Try them both out and see which interface and workflow works better for you. I also believe autocomplete can be done with the jN plugin through JavaScript - you seem to be familiar / comfortable with that.

Cheers.

[TroshinDV]

У меня есть скрипт, который JS IntelliSense реализует.

https://github.com/trdm/jn-npp-scripts
скрипт: https://github.com/trdm/jn-npp-scripts/blob/master/includes/Intell.js

[Sashank999]

@Michael-Vincent Dude that is really awesome and perfectly fits for my needs
I found the original TagLEET and used it but it doesn’t work for me.
I used your fork and it worked great. I also setup a global tags file in my scripts directory and set it in TagLEET.
Now there are only 2 problems for me:

• ctags also includes CSS files for tags (but I solved that by adding an --exclude option)
• ctags also indexes the same name(or tag) multiple times in multiple files
  This is intended to show the locations of all matching tags but this results like
  I don’t need such thing. It also made the file quite big(227KB). I only need auto completion. But I didn’t find any option to remove multiple tags. If there is such thing, could you please say me ?

[Sashank999]

I also forgot to say another thing.
This kind of auto complete is really useful in JS but it sucks in CSS.
How do I enable TagLEET auto complete for only JS files and disable TagLEET but enable Npp default auto complete in all other files ?
Thanks for the modified TagLEET bro :)

[Michael Vincent]

@Sashank999 said in I want (to make) a JS IntelliSense Plugin:

ctags also indexes the same name(or tag) multiple times in multiple files

I don’t know if there is a way to control filtering the same tag found in multiple files / locations in cTags, I think it’s by design like you said, “This is intended to show the locations of all matching tags”. I agree that it makes the autocomplete list redundant in some cases.

In my TagLEET, the Scintilla autocomplete happens here:
https://github.com/vinsworldcom/nppTagLEET/blob/17ea5e6e2dc0fe67d69600b8a63cff3109dc9b14/tag_leet_app.cpp#L871

I could try to create a hash of the tags seen and if the Item->Next is in the seen hash, just continue;. I’m not a C++ expert especially with strings, so creating a hash of seen strings is a bit of a homework assignment I can’t do right now, but certainly something to look at for the next (pre)release.

Cheers.

[Michael Vincent]

@Sashank999 said in I want (to make) a JS IntelliSense Plugin:

How do I enable TagLEET auto complete for only JS files and disable TagLEET but enable Npp default auto complete in all other files ?

Currently no option for that. So long as a tags file exists in the working path, it will use it unless you disable Scintilla autocomplete from the TagLEET Settings menu, which disables it across all files.

Did you give jN a try - as seen in the above post? It seems more geared towards Javascript which may more directly address your specific use case.

Cheers.

[TroshinDV]

@Sashank999 said in I want (to make) a JS IntelliSense Plugin:

Heya!
I am a JS Dev. I develop on a lot of small individual files and have the habit of separating all functions into their own files. And I need the function names in all the JS files I edit. How can this be done ?

Это реализовано в https://github.com/trdm/jn-npp-scripts/blob/master/includes/Intell.js
function goToDefinitionsByCtagsGlobal()
Собирает и выдает все функции и классы текущей дирректории файла.
Используется ctags + сервер выбора https://github.com/trdm/jn-npp-scripts/blob/master/system/svcsvc.dll

[Alan Kilborn]

@TroshinDV

Isn’t this an English forum?

[TroshinDV]

@Alan-Kilborn I know English badly, If I try to write in English, it will be terrible

[TroshinDV]

@TroshinDV said in I want (to make) a JS IntelliSense Plugin:

Это реализовано в https://github.com/trdm/jn-npp-scripts/blob/master/includes/Intell.js

Although it is necessary to remake as it should, it was written in a hurry.

[Alan Kilborn]

@TroshinDV

I think when you want to use an English forum and you do not write it well, it is on you to use a translator before posting, and to feed any English responses through a translator so that you can read them.

And it appears you have done that in your most recent post, for which everyone thanks you, I’m sure.

[Sashank999]

@TroshinDV I absolutely don’t understand what you are saying.
I have no understanding of Russian Language.
Could you please also translate the README.md to English too so that not only me but many can find your plugin useful ?

[PeterJones]

@Sashank999 said in I want (to make) a JS IntelliSense Plugin:

@TroshinDV I absolutely don’t understand what you are saying.
I have no understanding of Russian Language.
Could you please also translate the README.md to English too so that not only me but many can find your plugin useful ?

It’s one thing to ask someone to somehow translate into English in an English-language forum. (And as @Alan-Kilborn suggested, I think if @TroshinDV isn’t comfortable composing posts and replies in English, using a translator like translate.google.com or deepl.com, paste in the Russian that @TroshinDV writes in and grab the English translation to post into the forum is a good idea.)

But as the developer of the plugin, it is perfectly reasonable for @TroshinDV to choose to write and pubish the README in whatetver language is most comfortable, without being required to translate for others. And since it’s easy to translate someone’s published webpage (if you are in Chrome, right-click and “Translate to English”; if you are on a different browser without google’s builtin translation, you can pass the URL to translate.google.com, like http://translate.google.com/translate?sl=auto&tl=en&u=https://github.com/trdm/jn-npp-scripts/blob/master/readme.md, and see the English translation), and since @TroshinDV has already indicated not being comfortable translating into English, I think it’s probably faster all around for you to use the auto-translation.

[TroshinDV]

@Sashank999 said in I want (to make) a JS IntelliSense Plugin:

Could you please also translate the README.md to English too so that not only me but many can find your plugin useful ?

Maybe it’s good that there is no translation, will not be ashamed of the software code in front of English programmers :)))))

[Sashank999]

Heya !

I need a small help.
I now have an F5 action that automatically generates a ctags database with only keywords. Nothing other than that.
So now, TagLEET refuses to work without the other things like path, keyword scope, etc.
Of course it would be great if TagLEET disables other features and enables auto completion only as it doesn’t have info for the other features. I feel a bit too greedy now :| .

As I can generate a database, I want to make a plugin that can read the database and provide autocompletion based on that.
So, the things I need in plugin:

• an on/off switch to enable/disable auto completion
• an input field with “Browse” option beside it that can select a keywords file

Can anyone please provide info of how I can do it ? I think C will be enough. I just need the documentation to plugin development.

[TroshinDV]

@Sashank999 said in I want (to make) a JS IntelliSense Plugin:

As I can generate a database, I want to make a plugin that can read the database and provide autocompletion based on that.

https://github.com/trdm/jn-npp-scripts/blob/master/includes/Intell.js

/* 
\todo.... 2018-3-07_19-25
	может не страдать херней, а для проектов на си и си++ использовать рекурсивные запуски типа:
	ctags.exe -R -f u_ctagsU.txt --language=c --excmd=number
	???? гораздо быстрее получается и гораздо точнее, что немаловажно..
	
// trdm 2019-02-14 08:05:07    
\todo - при сканировании директории C:\Progekts\_E\ReactOS 
	файл trdm.txt вырос до 80 мб. этот объем не осилить js.
	тут надо придумать что-то другое.
*/
//Парсим с помощью ctagsU.exe файл
function fileToCtags( psFileName, psFirst, psFIndex ) {
	var vFName = psFileName;
	if(!vFName) {
		return;
	}
	if(!psFIndex) {		psFIndex = 1;    }
	var vComandLine = '';
	var vComandLineM = ' --machinable=yes ';
	var ctagExePath = gIntelCTagsUExeFPath;
	if(IntellPlus.curExtension == '1s' || IntellPlus.curExtension == 'vbs' ) {
		ctagExePath = gIntelCTagsUExeFPathSpeshl; 
		vComandLineM = '';		// no '--machinable=yes'
    }
    var resFile = (psFIndex == 1) ? gIntelCTagsUFPath : gIntelCTagsUFPath2;
    resFile = gIntelCTagsUFPath; // Не помню зачем я сдел 2 файла,  пока оставим один.
	var isFolder = gFso.FolderExists(psFileName);
	if(!isFolder) {
		var vFirst = (psFirst) ? true : false;
		var vFChar = (vFirst) ? '' : ' -a ';
		if(!gFso.FileExists(vFName)) return;
		if(!gFso.FileExists(ctagExePath)) return; 	// --if0=yes --list-fields - не обрабатывается
		vComandLine = '"'+ctagExePath+'"'+vFChar+' -R -F '+vComandLineM+' --sort=no --excmd=number -f "'+resFile+'" "'+vFName+'"';	// debugger;
		if(psFIndex == 2) {
			vComandLine = '"'+ctagExePath+'"'+vFChar+' -R -F --sort=no --excmd=number -f "'+resFile+'" "'+vFName+'"';	// debugger;
        }
    } else {
		vComandLine = '"'+ctagExePath+'" -R -F '+vComandLineM+' --sort=no --excmd=number -f "'+resFile+'" "'+vFName+'"';	// debugger;
	}
	if(!gIntelShowParseLine) { 
		status('Parse: '+vFName);	// var gWshShell = new ActiveXObject("WScript.Shell");
	}
	status('WshShell.Run: '+vComandLine);	// var gWshShell = new ActiveXObject("WScript.Shell");
	if(gIntelShowParseLine) {
		//message(vComandLine);    
    }
	//writeToIntellLog('gWshShell.Run: '+vComandLine);
	
	gWshShell.Run(vComandLine,0,true);
	//gWshShell.Exec()
	return gFso.FileExists(resFile);
}