Sharidan

CMB v1.1-i

• Fixed: screen rendering bug in monochrome mode.
• Change: mono mode now has inverse selection bar, similar to color mode.
• Change: Overall screen text rendering has been optimized for faster rendering.
• ListBox control completely rewritten.
• New: mouse navigation & scrolling implemented. Touch activation implemented.
• New: theme handling added. Theme file can be found in /etc/cmb.theme

CMB v1.0-i

• Initial relese.

A simplistic theme manager is now part of CMB, should you wish to change the colors. After running CMB for the first time, you can locate the theme file in: /etc/cmb.theme
 
You can change the color combinations to anything you like. Make sure you only change the color names, between the quotes in the theme file to avoid corrupting the file. Color sets always go in pairs of two: the first color is the text color, the second the background color. Be aware that some color combinations might not translate too well on monochrome (black & white), so you may have to experiment with the color combinations to get it working in both color and monochrome mode.
 
Valid color names are, in Minecraft Wool order:

• white
• orange
• magenta
• lightBlue / light blue
• yellow
• lime
• pink
• gray / grey
• silver / lightGray / lightGrey / light gray / light grey
• cyan
• purple
• blue
• brown
• green
• red
• black

Anyone doing any kind of coding or scripting, knows just how important accessible and updated documentation is. For years I have had Component Methods Browser locked away as one of my personal tools. Then I migrated over to OpenComputers and decided I would start sharing my goodies.
 
CMB is a UI based code documentation browser, that scans any and all components attached to a computer (or robot). Internally CMB automatically detects when components are added and/or removed and forces a refresh of the components list. Yes, this is similar to using the "components" command in the command prompt, however CMB does so much more than simply list all available components and their addresses. Originally I wrote "Methods Browser" for a certain other mod and I've used it for years for in-game quick reference lookups of documentation. CMB for OC was rewritten from scratch based on the original MB. A very small portion of the code was ported while the rest was completely written from scratch.
 
So what makes CMB so much different?
 
CMB organizes the information through a category system, with component types at the top followed by address selection and finally a sorted methods list (which also contains properties). Use arrow keys to move the selection bar, enter to select and the backspace key to return to the previous menu. If in doubt, simply press "H" for help in any menu to get the keys explained. Pressing "Q" anywhere in the program will quit the program and return to OpenOS.
 
I am a bit unsure on the actual memory spendage, however I have done a lot of test runs on 384Kb memory (2x T1 memory sticks).
 
CMB internally handles T1/T2/T3 screen modes and adjusts as needed. On T1 systems 50x16 is assumed and you will notice a difference in the selection bar/marker as it shows up as grainy blocks (see screenshots). On higher systems CMB will force 80x25 in color while running and restore original settings at exit.
 
At the moment CMB only handles components, since the contents of the /lib folder doesnt have documentation calls as such.

Requirements:
OpenOS v1.5
384Kb memory or more
45Kb disk space

CMB is available on pastebin with everything integrated. No additional files are required, beyond what comes stock with OpenOS.
Pastebin link: http://pastebin.com/DnRBZfLb
 
With an internet card installed, you can fetch CMB directly from pastebin in-game via:

pastebin get DnRBZfLb cmb.lua

CMB is delivered "as is". CMB does not write anything to disk, nor does it manipulate components in any way, except read the already available in-game documentation. Some of the Mighty Pirates tutorial/presentation videos found on YouTube showcases how to retrieve in-game documentation through the Lua prompt. At it's core CMB does the same but presents the information in scrollable selectable listings so you can easier navigate the documentation and retrieve the proper information you need.
I have gone through extensive testing of CMB before this release, however I am just a human being which means there might be bugs hidden inthere somewhere. In case of crashes or bugs, please toss me a screenshot and leave some feedback so I can fix it.
 

Color mode in 80x25
 

 
Mono mode in 50x16

I'm sure some parts can be done smarter and/or more efficient than I have chosen to do. If when looking through my code you feel I've had my head up my butt, please don't talk down to me - please educate me instead. I'm an old code dog and you know how the saying goes in those regards. I have had my fair share of talking down and being treated as a complete noob on a certain other forum, which I why I for the most part kept away from there and never shared my scripts before.
 
Internally CMB has a few nifty mini-libraries.
 
There's my terminal object, which is basically a wrapper for the gpu component, just to get the fully cross screen/gpu handling I wanted and some easier to use widgets to place something on screen. The term object handles screen clearing, color selection (with mono conversion support) and the titlebar shown in CMB. This wrapper should not be confused with the OC supplied term API! In code, search for "function newTerm".
 
As an add-on for my term wrapper, there is also the statusBar renderer, which for the most part handles the help texts at the bottom of the screen. statusBar accepts any number of parameters. Each parameter can either be a single string value using ambersand (&) to denote the highlighted letter or a pair of number, string where the number is either 14 for "BckSpc" or 28 for "Enter" which will be rendered in brackets preceeding the text in the string.
 
Then there is the list box control which handles all the major selection screens. It is a fully integrated single column listbox with keyboard interfacing only. In code, search for "function newList".
 
If you find any parts of my code useful, feel free to snip a copy of the code but please give credit where credit is due. A simple comment inthere with my name and maybe which script you got the code from will be appreciated