fbpx

Yes, there are many ways of representing your code and its execution that we can’t wait to start working on. The current focus is on making the initial feature-set as fast and stable as possible before adding new features.

Most of WhiteBox’s codebase is not tied to a particular language and has been created with extending support in mind. Adding more languages is both doable as well as something we’d like to do.

We have yet to decide which languages to add support for next, so if you have one you would particularly like to see please get in touch to let us know.

Probably, and if we don’t, you’ll be able to add support yourself fairly easily.

WhiteBox only needs a few pieces of information from your editor to work and can be connected to like a server. More precise details on how this works will be released shortly. In the meantime,  join the Discord chat server and we can talk you through it.

Possibly, if there’s demand for it. Let us know if you would buy WhiteBox, if only it were on your platform-of-choice!

No, it connects to existing editors via plugin. You can keep using your favourite one & not lose all the muscle-memory for keyboard shortcuts you’ve built up.

Generally we’ve tried to go with the standard approach for each editor.

The plugin files for each editor can be found under their own name in the editor_plugins folder of the WhiteBox download.

 

4coder

If you haven’t customized your build, replace the custom_4coder.dll in 4coder Program Files directory with the one from the editor_plugins\4coder directory.

If you are using a custom build,  you need to update your tick function to call WhiteBox’s:

#include "whitebox_4coder.cpp"
...
// Option 1 - if you haven't customized the tick function:
set_custom_hook(app, HookID_Tick, wb_4c_default_tick);

// Option 2 - if you have customized the tick function:
function void my_custom_tick(Application_Links *app, Frame_Info frame_info) {
...
wb_4c_tick(app, view);
}

...

set_custom_hook(app, HookID_Tick, my_custom_tick);

You can see whitebox_4coder_bindings_sample.cpp for a complete example.


Notepad++

Copy the whitebox folder (the folder itself, not just the contents) into the plugins folder for Notepad++, e.g:

C:\Program Files\Notepad++\plugins

Vim

If you’re using a particular plugin manager then follow the normal instructions for that.

Otherwise add this line to your .vimrc (and edit the path as needed):

source C:\Program Files\whitebox\editor_plugins\whitebox-vim\plugin\whitebox.vim

Get in Touch

Thanks for showing interest in WhiteBox, if you have any questions, please feel free to get in touch using the contact form below:

    * This field is required.

    This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.