Skip to main content

StartExplorer Eclipse Plug-in

http://basti1302.github.io/startexplorer/

In resource views like the Navigator or Package Explorer you can select files and folders. StartExplorer offers the following options here:
  1. Show in file manager
  2. Start shell here
  3. Open files with default application
  4. Copy resource path to clipboard
  5. Custom Commands
All options work with a single selected resource as well as with multiple resources. If multiple resources are selected and an option only works for files (or only for folders) all resources of the wrong type are ignored and the command is executed for the resources it is applicable for.
Show in file manager: (Works for files and folders) Starts a file manager (depending on your system, this might be the Windows Explorer, Finder on Mac OS, Nautilus on Gnome, Konqueror on KDE, Thunar on Xfce or PCMan File Manager on LXDE) for the selected resource. If it is a folder, the file manager is opened for this folder. If it is a file, the file manager is opened for the parent folder of this file. On some systems (currently on Windows and Mac OS) the file is also selected/highlighted in the file manager. If multiple resources are selected, a separate file manager instance is opened for each resource.
Start shell here: (Works for files and folders) Opens a shell/terminal/command line prompt with the selected folder as its starting directory. If multiple resources are selected, separate shells are opened for each of them. If a file is selected, a shell for its parent directory will be opened.
Open files with default application: (Works for files only) Opens the selected file in the application that is registered for this file type in your system. If multiple resources are selected then for each resource the default application will be started separately.
Copy resource path to clipboard: (Works for files and folders) Copies the absolute path of the selected resource to the clipboard. If multiple resources are selected, all resource paths are copied to the clipboard, separated by a Unix linebreak. The separator can be configured in the preference page for this plug-in.
Custom Commands: You can configure any command you like here. 

Comments

Popular posts from this blog

Quicksort implementation by using Java

 source: http://www.algolist.net/Algorithms/Sorting/Quicksort. The divide-and-conquer strategy is used in quicksort. Below the recursion step is described: 1st: Choose a pivot value. We take the value of the middle element as pivot value, but it can be any value(e.g. some people would like to pick the first element and do the exchange in the end) 2nd: Partition. Rearrange elements in such a way, that all elements which are lesser than the pivot go to the left part of the array and all elements greater than the pivot, go to the right part of the array. Values equal to the pivot can stay in any part of the array. Apply quicksort algorithm recursively to the left and the right parts - the previous pivot element excluded! Partition algorithm in detail: There are two indices i and j and at the very beginning of the partition algorithm i points to the first element in the array and j points to the last one. Then algorithm moves i forward, until an element with value greater or equal

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know. Symptom: 1.        The JVM became Out of memory when creating big consumption report 2.        Those JRTemplateElement-instances is still there occupied even if I logged out the system Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.     The clearobjects() method in ReportThread class has not been triggered when logging out Action I tried:      About the Virtualizer: 1.     Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.     Not use any FileVirtualizer for cache the report in the hard disk Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory        About the work around below,      I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object        

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold  highlighted in example below) which resolve the problems.   example: <band height="20" splitType="Stretch" > <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/>