Tools for packing files, converting images, manipulating text, checking code and working with the Gossamer codebase and app source code.



Features

• Fast, one-click tools for common tasks
  
• Pack a file, image or text into a binary Pascal array for direct inclusion in source code
  
• Indent blocks of text (or remove indents) by 1-5 spaces for code styling
  
• Clone a Gossamer project to a Lazarus project and use one common source code for both projects - supports Borland Delphi 3.0 (Build 5.83) as source and Lazarus 2.2.6 as target
  
• Convert an image file between these formats: PNG, GIF, JPG, JIF, JPEG, TJ32, BMP, ICO, CUR, ANI, TEA, TGA, PPM, PGM, PBM, XBM and IMG32
  
• Convert an image into mime/type base64 text
  
• A wide variety of tools to manipulate an image or text held in Clipboard
  
• List lines of text in ascending (A-Z) or descending (Z-A) order
  
• Remove leading and trailing whitespace from each line of text
  
• Remove duplicate lines of text
  
• Transform a Clipboard image into an auto-cropped, high-resolution, icon ready image in one of three shapes: square, squircle or circle
  
• Pack files in A-Z order as source code into a Pascal unit (*.pas) using named const arrays, with file data easily accessible from a fuss-free function, including file path, name, compression state, memory pointer and data length
  
• Fix multiple Pascal units in the same folder and/or sub-folders: remove bad return codes (#10#10 and #13#13) and invalid characters (#0..#31 except for #9, #10 and #13)
  
• Mark Pascal procedures and functions duplicated in other units with a comment, scanning the same folder and/or sub-folders
  
• Options Window - Easily change app color, font and settings
  
• Portable
  
• Smart Source Code (Borland Delphi 3 and Lazarus 2)

Information

Downloads

Images

Reference

• What makes a portable app special?
• MIT License

What makes a portable app special?A portable app is a big leap forward for apps in general.  A standard or traditionally engineered app requires a lot of support in the form of libraries, data files, images, scripts, etc and the list goes on.  You get the picture.  Some portable apps out there still include this bundle of bits, they merely offload it into a local folder.  A dump of goodies of sorts.

We tend to see a portable app in quite a different light.  Our vision of a portable app is designed tight, clean, free of bloat, and all data where possible is included directly within, structured right into the fabric of the app itself, and designed from the bare-metal up if required.

Though the most important difference between a traditional app and a portable app is that a portable app will not install on your computer.  This is extremely important as the installation process is often messy, and can clutter up your computer by dumping a lot of stuff all over the Windows file structure and registry, and over time may slow down and decrease the overall performance of your computer.

A portable app will not do this, which keeps your computer clean and running smooth and fast as it should.  Unfortunately most software is not designed with portable in mind.  They're more akin to a large leaky box of bits than tight engineering.  And because a portable app is not installed on your computer, it runs outside the normal scope of the operating system, and is not locked down or tied to it.  And thus can be moved about, from disk to disk, or computer to computer.

Typically a portable app will reside on a USB pen stick, removable media, or in a special folder on a portable hard disk.  This makes it easy to take from one computer to the next, and use over and over.  An immensely valuable freedom, and something an installed app can only dream of.

But a serious technical hurdle must be overcome for a truly portable app to be free.  And that is the humble setting.  Yes, a portable app must be able to handle it's settings on it's own.  It must be able to read them from disk, filter them, check and correct them where required, and write them back to disk.  All without the help of the Windows' registry or other operating system dependent structures.

An installed app typically can't or won't do this.  Instead, it relies on Windows and the registry to manage it's settings and other important data sets for it.  It therefore takes a higher degree of technical competence to escape this "tied to the operating system" situation.

Here is our current standard for a portable app:

• Require no installation or setup
  
• Require no additional DLL libraries to run and perform it's core function
  
• Make no alteration to the host operating system, or its settings, files, libraries or core functions, or the Windows registry, unless it forms a part or a whole of the app's core function, and then, only when initiated by the user
  
• Be able to run "out of the box"
  
• Require no compiling, conversion, installation or setup of support structures in order to execute, except for when such an environment constitutes an execution enabling environment, such as a command translation service like Wine
  
• Be free of zipped or otherwise externally bundled blob structures containing folders, files and bits
  
• Operate on less powerful hardware to facilitate operation on a broad spectrum of computers
  
• Less demanding API landscape to facilitate execution on a broad range of operating systems and software translation environments
  
• Require no special software libraries be present in order to run, such as .NET or JAVA, unless typically pre-installed on the target operating system or execution environment
  
• Not require an internet connection to run, unless the connection is required to fulfill the app's core function, such as a web server
  
• Require no downloads, addons, or registration in order to run
  
• Provide help and documentation offline via a built-in viewer, or by limited external means, such as Notepad
  
• Be self-contained with all necessary files, data sets, and samples stored within it's internal structure, such that access be provided preferably through direct enabling mechanisms
  
• Store, hold and manage external app settings and user data in a local sub-folder, and that sub-folder be easily identifiable as belonging to the app
  
• Provide a mostly consistent appearance and experience to the user across the widest possible range of operating systems and execution environments
  
• Value backwards compatibility, and be able to actively make use of that older hardware and software
  
• Possess a compact, bloat-free footprint
  

⏶MIT LicenseCopyright 2026 Blaiz Enterprises ( www.blaizenterprises.com )

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

⏶