Yes, including the IDE. If there is some language/library deficiency that makes impossible to convert one of the tools into CX code (why font generation for mojo/mojo2 needs to be written in BMAX for example?), the appropriate module should be developed/language improved.
This way not only we'll get an amazing general purpose language (though with keeping the focus on the games), but would also make the tool more marketable, as in, "Look, we've done all of this with just CerberusX, which means that you can AS WELL make with it anything you want".
Which in turn would bring more developers, some of which may even volunteer to work on Cerberus itself.
By writing all the tools in Cerberus itself, we would find all the possible weak spots in it and fix them. Because currently, despite lack of OOP, BlitzMax still can do more than Cerberus can. Even its IDE is written in BMAX. And Cerberus depends on BMAX to do its build process (mojo font generation) too - what if Brucey gets bored of developing BMAX-NG and it stops being compatible with Windows/newer versions of Linux? Not because of simple ABI incompatibility, because then it just can be recompiled to use newer libraries, but when a library decide to retire a function BMAX relies on?
By doing all the tooling in Cerberus itself, the tools would depend only on Cerberus, so as long as it is being maintained, the tools will all work fine. Not to mention all the module/language improvement it would bring in.
This way not only we'll get an amazing general purpose language (though with keeping the focus on the games), but would also make the tool more marketable, as in, "Look, we've done all of this with just CerberusX, which means that you can AS WELL make with it anything you want".
Which in turn would bring more developers, some of which may even volunteer to work on Cerberus itself.
By writing all the tools in Cerberus itself, we would find all the possible weak spots in it and fix them. Because currently, despite lack of OOP, BlitzMax still can do more than Cerberus can. Even its IDE is written in BMAX. And Cerberus depends on BMAX to do its build process (mojo font generation) too - what if Brucey gets bored of developing BMAX-NG and it stops being compatible with Windows/newer versions of Linux? Not because of simple ABI incompatibility, because then it just can be recompiled to use newer libraries, but when a library decide to retire a function BMAX relies on?
By doing all the tooling in Cerberus itself, the tools would depend only on Cerberus, so as long as it is being maintained, the tools will all work fine. Not to mention all the module/language improvement it would bring in.