Note that there are some explanatory texts on larger screens.

plurals
  1. POC++ vim IDE. Things you'd need from it
    primarykey
    data
    text
    <p>I was going to create the C++ IDE <strong>Vim</strong> extendable <strong>plugin</strong>. It is not a problem to make one which will satisfy my own needs.<br></p> <p>This plugin was going to work with workspaces, projects and its dependencies.<br> This is for unix like system with <strong>gcc</strong> as c++ compiler.</p> <p>So my question is what is the most important things you'd need from an IDE? Please take in account that this is Vim, where almost all, almost, is possible.<br></p> <p><em>Several questions:</em><br> How often do you manage different workspaces with projects inside them and their relationships between them? What is the most annoying things in this process.<br> Is is necessary to recreate "project" from the Makefile? <br>Thanks.</p> <p><em>Reason to create this plugin:</em><br></p> <p>With a bunch of plugins and self written ones we can simulate most of things. It is ok when we work on a one big "infinitive" project.<br> Good when we already have a makefile or jam file. Bad when we have to create our owns, mostly by copy and paste existing.<br> All ctags and cscope related things have to know about list of a real project files. And we create such ones. This &lt;project#get_list_of_files()&gt; and many similar could be a good project api function to cooperate with an existing and the future plugins. Cooperation with an existing makefiles can help to find out the list of the real project files and the executable name. With plugin system inside the plugin there can be different project templates.<br></p> <p>Above are some reasons why I will start the job. I'd like to hear your one.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload