Skip to content

πŸ–₯️ Windows πŸš€ Effortless web image downloads, subsite exploration, and HD selection. Windows app, .NET 4.5, no registry usage.

License

Notifications You must be signed in to change notification settings

bugfishtm/bugfish-image-downloader

Bugfish Image Downloader

πŸ” Overview

Note

No new features are planned for this project at this time.

Tip

This project is actively maintained, with regular updates and prompt fixes for reported issues.

Welcome to Bugfish Image Downloader, a versatile software tool designed for downloading images from websites. This utility enables you to input a URL, upon which it will retrieve and save all images found on the specified website. The downloaded images are organized into folders within the application's directory.

Preview

Key Features

  • Easily download images from websites of your choice.
  • Configure settings to search for images within subsites of the specified website.
  • Choose to download only high-definition images with a width of at least 1000 pixels.
  • Note: While Bugfish Image Downloader is compatible with many websites, it may not work on all. Feel free to give it a try for your image downloading needs.

System Requirements

To run Bugfish Image Downloader, you need a Windows operating system with .NET Framework 4.5 installed. The software is designed to run without the need for installation, and it does not write or utilize any registry keys. All folders and files are created in the same location as the executable file.

πŸ“– Documentation

The following documentation is intended for both end-users and developers.

Description Link
Access the online documentation for this project. https://bugfishtm.github.io/bugfish-image-downloader/index.html
If you'd prefer to access the documentation locally, you can find it at. ./docs/index.html

❓ Support Channels

If you encounter any issues or have questions while using this software, feel free to contact us:

πŸ“’ Spread the Word

Help us grow by sharing this project with others! You can:

  • Tweet about it – Share your thoughts on Twitter/X and link us!
  • Post on LinkedIn – Let your professional network know about this project on LinkedIn.
  • Share on Reddit – Talk about it in relevant subreddits like r/programming or r/opensource.
  • Tell Your Community – Spread the word in Discord servers, Slack groups, and forums.

πŸ“ Repository Structure

This table provides an overview of key files and folders related to the repository. Click on the links to access each file for more detailed information. If certain folders are missing from the repository, they are irrelevant to this project.

Document Type Description
.github Folder with github setup files.
.github/CODE_OF_CONDUCT.md The community guidelines.
_changelogs Folder for changelogs.
_packages Folder for installable packages mostly for suitefish-cms.
_releases Folder for releases.
_screenshots Folder with project screenshots.
_source Folder with the source code.
docs Folder for the documentation.
.gitattributes Repository setting file. Only for development purposes.
.gitignore Repository ignore file. Only for development purposes.
README.md Readme of this project. You are currently looking at this file.
repository_reset.bat File to reset this repository. Only for development purposes.
repository_update.bat File to update this repository. Only for development purposes.
CONTRIBUTING.md Information for contributors.
CHANGELOG.md Information about changelogs.
SECURITY.md How to handle security issues.
LICENSE.md License of this project.

πŸ“‘ Changelog Information

Refer to the _changelogs folder for detailed insights into the changes made across different versions. The changelogs are available in HTML format within this folder, providing a structured record of updates, modifications, and improvements over time. Additionally, GitHub Releases follow the same structure and also include these changelogs for easy reference.

🌱 Contributing to the Project

I am excited that you're considering contributing to our project! Here are some guidelines to help you get started.

How to Contribute

  1. Fork the repository to create your own copy.
  2. Create a new branch for your work (e.g., feature/my-feature).
  3. Make your changes and ensure they work as expected.
  4. Run tests to confirm everything is functioning correctly.
  5. Commit your changes with a clear, concise message.
  6. Push your branch to your forked repository.
  7. Submit a pull request with a detailed description of your changes.
  8. Reference any related issues or discussions in your pull request.

Coding Style

  • Keep your code clean and well-organized.
  • Add comments to explain complex logic or functions.
  • Use meaningful and consistent variable and function names.
  • Break down code into smaller, reusable functions and components.
  • Follow proper indentation and formatting practices.
  • Avoid code duplication by reusing existing functions or modules.
  • Ensure your code is easily readable and maintainable by others.

🀝 Community Guidelines

We’re on a mission to create groundbreaking solutions, pushing the boundaries of technology. By being here, you’re an integral part of that journey.

Positive Guidelines:

  • Be kind, empathetic, and respectful in all interactions.
  • Engage thoughtfully, offering constructive, solution-oriented feedback.
  • Foster an environment of collaboration, support, and mutual respect.

Unacceptable Behavior:

  • Harassment, hate speech, or offensive language.
  • Personal attacks, discrimination, or any form of bullying.
  • Sharing private or sensitive information without explicit consent.

Let’s collaborate, inspire one another, and build something extraordinary together!

πŸ›‘οΈ Warranty and Security

I take security seriously and appreciate responsible disclosure. If you discover a vulnerability, please follow these steps:

  • Do not report it via public GitHub issues or discussions. Instead, please contact the security@bugfish.eu email address directly.
  • Provide as much detail as possible, including a description of the issue, steps to reproduce it, and its potential impact.

I aim to acknowledge reports within 2–4 weeks and will update you on our progress once the issue is verified and addressed.

This software is provided as-is, without any guarantees of security, reliability, or fitness for any particular purpose. We do not take responsibility for any damage, data loss, security breaches, or other issues that may arise from using this software. By using this software, you agree that We are not liable for any direct, indirect, incidental, or consequential damages. Use it at your own risk.

πŸ“œ License Information

The license for this software can be found in the LICENSE.md file. Third-party licenses are located in the ./_licenses folder. The software may also include additional licensed software or libraries.

🐟 Bugfish