Sunday, August 06, 2006
InnerLoop as a Shell
One of the cool things about InnerLoop is you can do almost everything without ever leaving. To do most anything in Linux requires some typing at the shell prompt. InnerLoop has a very easy way to do it. Highlight the Build tab on the bottom of the tool. Initially, there is nothing there and if you don't use the Build options it may not have occurred to you that this is a shell. To try it out type any command in the box, for example pwd. You will get a nice shell prompt that you can use without having to leave InnerLoop and search for an xterm.
For me, I don't normally use the build system that is provided by InnerLoop. Unfortunately, not everybody I work with is enlightened enough to use InnerLoop and scripts and Makefiles tend to be the way things go. However, this doesn't stop me from using the Build window as a shell. When I want to check my e code and generate a stubs file to make sure life is good, I go to the Build window and type the script or make target to do this. If I have any errors (a rare situation) I can click on them and go directly to the source code and fix them.
I notice some users of InnerLoop have a "never leave" philosophy and other tend to leave when it's time to compile and run. The beauty is that it works either way and any way in between. I tend to spent lots of time in InnerLoop and stay in all the way until I'm ready to simulate and then I leave and go for specify or an xterm to run simulation.
Give the Build window a try as a shell today and see you how you like it.
One of the cool things about InnerLoop is you can do almost everything without ever leaving. To do most anything in Linux requires some typing at the shell prompt. InnerLoop has a very easy way to do it. Highlight the Build tab on the bottom of the tool. Initially, there is nothing there and if you don't use the Build options it may not have occurred to you that this is a shell. To try it out type any command in the box, for example pwd. You will get a nice shell prompt that you can use without having to leave InnerLoop and search for an xterm.
For me, I don't normally use the build system that is provided by InnerLoop. Unfortunately, not everybody I work with is enlightened enough to use InnerLoop and scripts and Makefiles tend to be the way things go. However, this doesn't stop me from using the Build window as a shell. When I want to check my e code and generate a stubs file to make sure life is good, I go to the Build window and type the script or make target to do this. If I have any errors (a rare situation) I can click on them and go directly to the source code and fix them.
I notice some users of InnerLoop have a "never leave" philosophy and other tend to leave when it's time to compile and run. The beauty is that it works either way and any way in between. I tend to spent lots of time in InnerLoop and stay in all the way until I'm ready to simulate and then I leave and go for specify or an xterm to run simulation.
Give the Build window a try as a shell today and see you how you like it.
# posted by Jason Andrews @ 10:41 PM 
