Attach
|
Edit
|
Revisions
How to Write Power Explorer Plug-InsPower Explorer is a free File Explorer replacement for Windows Mobile and Pocket PC. Power Explorer is extremely powerful in that you can expand its functionality with user-developed plug-ins. Download a copy of Power Explorer here: Power Explorer. Power Explorer plug-ins are extremely easy to write. All Power Explorer plug-ins are written in MortScript language; The same language that Power Explorer is written in. Power Explorer supports two types of plug-ins: 1) plug-in for Directory Navigator; and 2) plug-in for File Explorer. Following sections describes the two types of plug-ins. Directory NavigatorDirectory Navigator is an Power Explorer application that let you manipulate directories on your mobile device. Plug-ins written for Directory Navigator operates on directory paths. After the user selects a directory in Directory Navigator, the directory path is passed on to the plug-in script as argument 1. The following is a simple example of a plug-in for Directory Navigator. Local () plugInName = "Sample Directory Plug-In" selection = argv [1] Message ("The user selected " & selection, plugInName) The local () function call sets all of the variables in the plug-in to local scope, so that they won't conflict with the operation of Power Explorer. All plug-ins variables should operate in local scope, unless inter-plug-ins functionality needs to be met. Giving the plug-in a name on line two, helps you identify the plug-in in the dialog box on line four. Line three is where the plug-in script determine which directory the user has selected. PlacementAfter writing your script, you need to place the script into the "Directory Operators" directory under the "Power Explorer" directory. Directory Navigator searches that directory for all of its plug-ins. The extension must be ".mscr". The name of the plug-in is what is shown to the user in Directory Navigator. File NavigatorFile Navigator is an Power Explorer application that let you manipulate files on your mobile device. Plug-ins written for File Navigator operates on file paths. After the user selects a file in File Navigator, the file path is passed on to the plug-in script as argument 1. The following is a simple example of a plug-in for File Navigator. Local () plugInName = "Sample File Plug-In" selection = argv [1] Message ("The user selected " & selection, plugInName) The local () function call sets all of the variables in the plug-in to local scope, so that they won't conflict with the operation of Power Explorer. All plug-ins variables should operate in local scope, unless inter-plug-ins functionality needs to be met. Giving the plug-in a name on line two, helps you identify the plug-in in the dialog box on line four. Line three is where the plug-in script determine which file the user has selected. PlacementAfter writing your script, you need to place the script into the "File Operators" directory under the "Power Explorer" directory. File Navigator searches that directory for all of its plug-ins. The extension must be ".mscr". The name of the plug-in is what is shown to the user in File Navigator. Related Links
Attach
|
Edit
|
Revisions
|
Products
|
Services
72 Users Online
|
Copyright © 1996 - 2024. All Rights Reserved. |