How To Use PixelDatabase.Net

Issue #3

How To Use PixelDatabase.Net

Forward

This blog is not a tutorial on software / web development like I usually create. The purpose of this post is to serve as the Help page for using a site I just published called PixelDatabase.Net.

For C# Programmers

Although I stated this blog is not for programmers, most of the code used / talked about is open source:

Nuget: 

DataJuggler.PixelDatabase            Dot Net Core

DataJuggler.PixelDatabase.Net     .Net Framework

Git Hub Projects *

DataJuggler.PixelDatabase Nuget source

https://github.com/DataJuggler/PixelDatabase

DataJuggler.PixelDatabase.Net (For .Net Framework) Nuget source

https://github.com/DataJuggler/PixelDatabase.Net

Transparency Maker (A Windows Form application).

https://github.com/DataJuggler/TransparencyMaker

* The source code for the website PixelDatabase.Net is not published as I plan on accepting donations and / or advertisements since open source does not pay very well and I am unemployed.

Pixel Database.Net

PixelDatabase.Net reads in a .jpg or .png and creates a Pixel Information Database, that can be manipulated in a language I invented called BQL or Bitmap Query language.

Motivation

The reason I wrote Transparency Maker is when I purchase stock photos, almost all come with a background color and often I need a transparent background. There are other tools that perform background removal, with more now than in 2012 when I started working on Transparency Maker, however I wanted a way to programmaticaly manipulate pixels.

Web Version

Fast forward to 2020 and Blazor is my new favorite development environment. Most of the features work the same in the web version as the Windows Forms version. A few things are different in the web version, with the biggest being every time the file is edited I must save the file to disc with some random characters added to the file name and reload. 

How To Use PixelDatabase.Net

3.28.2020: More to come, but I need the URL so I can publish the site while I work on the documentation.