• December 2012
    S M T W T F S
  • Subscribe

  • Meta

  • Notices:

    Except for provisions made within this blog, no portion of this blog may be stored in another Data Warehouse or other data retrieval system without the express permission of Steve Tabler and Finally, legal notices may not be sent to Steve Tabler at any email address or by any other electronic means!

SELECT program

Posted by stevetabler on December 7, 2012

The SELECT program has received the most work of all my projects so far, and in the past I have offered it up for sale as a download from my online store site (currently offline). The project started simply enough out of my need for a glue-program for a specific situation.

Background info: the groupware environment (some people call it a game) knows as ‘Second Life’ has a very unique and extensive scripting (programming) environment built into it. Naturally, it uses a proprietary language, called LSL or Linden Scripting Language. To write scripts, one had to be logged-in to Second Life using a program called a ‘viewer’. Originally, the only compatible viewers were provided by Linden Labs. Eventually, they started a formalized 3rd-party viewer program, and open-sourced the viewer for the most part, and several other developers started working on new viewer features. To write scripts inside the viewer, one had to use the script editor. Sounds simple enough, but there were a few drawbacks: there was no easy way of working on scripts off-line. Scripts could only be stored at the server and accessed using the tools in the viewer. The only way to work on a script while offline was to use the copy/paste features in Windows and other operating systems to transfer the contents of a script. This works but can be quite tedious. With a 3rd party viewer, hooks were put in to allow one to specify their own favorite editor and allow script editing with it. This worked fairly well, but there are some shortcomings with it. In particular, I found that if I wanted to change the script editor I had defined, I could do it just on the fly: I had to go through a few levels of config-menu in the viewer and specify a different editor.

The SELECT program was designed as a bridge between the viewer and the editor I use. Essentually, the viewer would invoke SELECT, and pass the filename for the script being edited as a command line argument. Then, SELECT, assuming it has been appropriately installed and configured, opens a small window. In the window is a collection of buttons, with each button representing a specific editor. One button could be for Notepad. Another button might be for Wordpad. Still another might be for LSL Editor (another 3rd party editor). So, one has the intermediate step of pressing a button on SELECT to invoke the current editor of choice to use. All functions within that editor will function on the current script. One thing that can very easily be done at this point is to save a copy of the script locally on the hard drive. Another thing is printing a hard-copy. You could be working on editing the script in Notepad, and simply use the print pulldown in Notepad. Another option might be to briefly open Word, do a little formatting (without saving), and print from it.

SELECT also became a bit complex for a simple glue-program: I wasn’t satisfied with default buttons, and I added the ability to edit various aspects of the buttons to control the appearance of a button. In the end, I ended up with a very handy program that I could use to re-organize all the icons scattered across the Windows desktop.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s