After doing some more experimentation, I believe this has something to do with the fact that the macro console is in it's own iFrame and thus the generic bootstrap css rules are not applied. I'm not sure how that works since I'm not a css expert. However, I figured out a way to do this using an embedded style tag, which isn't really ideal but I'm just happy I finally got the large macro console that I wanted. Sure, I can apply the css changes using the browser console, but every time I click "execute" the textbox would go back to the tiny state.
We are using source control and I will not be adding this file to the source repo, as this might cause problems when we upgrade the software. But I was able to make a massive improvement in the macro console by adding the following code in
\CMSAdminControls\UI\Macros\Dialogs\ObjectBrowser.aspx in the line after
<asp:Content ID="cntContent" ContentPlaceHolderID="plcContent" runat="Server">:
EDITED with my current layout, still loving this. Saving here for when I need it
If anyone knows a better way to do this I'm still curious. I think the macro console works a lot better with a bigger textbox, personally.
Also, is it possible to create a copy of this file and place it in a custom directory outside of the normal directory? I know not to change the stock files IE \CMSAdminControls\UI\Macros\Dialogs\ObjectBrowser.aspx in our repository but could I do something like _customCMSAdminControls\UI\Macros\Dialogs\ObjectBrowser.aspx then link the module up to that new webpart? Even doing that makes me kind of nervous so I'll probably just end up replacing this file manually as needed and never commit it to the repo.
Whenever I do any updates to kentico I clone the repo fresh out of source control anyway, so this won't affect our upgrades. It also never needs to leave dev because I don't use the large console window except to write macros in dev. I'm open for any type of advice that you have on this one.