![]() ![]() ![]() We can use the environment property to retrieve the path to our volatile environment settings. The line of code that creates the WshShell object is seen here: $wshshell = New-Object -comobject wscript.shell Even though the documentation is focused on VBScript, the methods and properties work in a similar fashion for Windows PowerShell. The Wscript.Shell object is documented here. Now we will create an instance of the Wscript.Shell object. We scripting guys are always prepared to go the extra mile for our readers, so we added it to the script: If it seems hardly worth the trouble, I might very well be inclined to agree with you-but think how bad it would be if you did not have this information. The window below was created with the -noprofile and the -nologo parameter. ![]() The top two lines are controlled by the -nologo parameter. These arguments are seen here: $arguments = " -noProfile -nologo"Īs seen in the image following this paragraph, the top Windows PowerShell window is launched with no arguments. For Windows PowerShell, we will be starting Windows PowerShell without using a profile and without displaying the logo. We next use the variable $arguments to hold the arguments we will pass to the application when it is launched via the shortcut. This is seen here: $appName = "PowerShell" In the first line of the script, we assign the string PowerShell to the $appName variable. When we run the CreateShortCutOnQuickLaunch.ps1 script, we are greeted with the friendly Windows PowerShell icon on our Quick Launch toolbar: $shortCut = $wshShell.CreateShortCut("$qlf\$appName.lnk") $qlf = join-path -path $em("appdata") -childPath "Microsoft\Internet Explorer\Quick Launch" $volEnv = $wshShell.environment("volatile") $wshshell = new-object -comobject wscript.shell Here is the CreateShortCutOnQuickLaunch.ps1 script: $appName = "PowerShell" See also a VBScript version of this script. Luckily, in Windows PowerShell we have a cmdlet that makes it rather easy to do. With semispecial folders, we have to work with the path ourselves. Don’t know why, but it just did not quite make the cut to be special. RS, as you no doubt discovered, the Quick Launch toolbar is not a special folder at all. When they are missing it is a major bummer. On the other hand, as we saw in the last “Hey, Scripting Guy!”, special folders have coded values that can make referring to them easier. ![]() They are just folders after all, but they live in a special place. One of the funny things about special folders is that they, for the most part, really are not all that special. So how can I create a shortcut to Windows PowerShell that will live on the Quick Launch toolbar? The problem is that I cannot find a special folder or anything that refers to this location. plist files for every script to let the action run in background.Hey, Scripting Guy! I love the Quick Launch toolbar. You can of course edit the scripts to fit your needs.ĭownload link: (Updated to work better with Mountain Lion) The German version of "Accordance Display" also uses the Elberfelder translation. The main difference is that in the German version book names are converted into s.th. If its to much text to display it will be shortened.Ģ) "Accordance Verses" will open scriptures inside the application.ģ) "Accordance Words" will search for words inside the application.īoth "Accordance Verses" and "Accordance Words" contain UI Scripting which can be buggy at times.įor both "Accordance Display" and "Accordance Verses" I made an English and a German version. I works best with single verses or a short passage. plist files)* to ~/Library/Application Support/LaunchBar/Actionsġ) "Accordance Display" shows scriptures in large type on your screen. You can download the Zip file and than move the scripts (and corresponding. Here are updated versions the scripts I use. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |